Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    19
  • Subscribers subscribers
    12
  • Views views
    905
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What is cloud support for dedupe device

HowardArch

Does anyone know what the cloud support to create a store in the dedupe device actually does.

I've posted this before and neither MF support nor the documentation have anything about it.

There are  several things not documented here including the purpose of the cache and sizing for dedupe store installed locally versus cloud backed?

Picture below.

Any ideas appreciated as having undocumented feature in your product is never a good look.

Parents
  • 0  

    By checking the Cloud Support box, you can configure the cloud storage for your deduplication device. The purpose of the cache is actually documented in the Admin guide: Data Protector Deduplication store

    "Each deduplication store with cloud storage has a local cache that enables faster data transfer."

    The sizing of the store clearly depends on the amount of data backed up and the deduplication ratio. About the size of the local cache, I cannot find any recommendations. I would say it depends on the amount of data being backed up at a time. I will come back here if I can find any additional info.

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

Reply
  • 0  

    By checking the Cloud Support box, you can configure the cloud storage for your deduplication device. The purpose of the cache is actually documented in the Admin guide: Data Protector Deduplication store

    "Each deduplication store with cloud storage has a local cache that enables faster data transfer."

    The sizing of the store clearly depends on the amount of data backed up and the deduplication ratio. About the size of the local cache, I cannot find any recommendations. I would say it depends on the amount of data being backed up at a time. I will come back here if I can find any additional info.

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

Children
  • 0 in reply to   

    Thanks for the info,  

    I don't think it's actually a cache, generally a cache is a temporary area to improve performance, but I have noticed that the cache is actually integral to the backup and easily runs out of space -so again an undocumented feature.  If you run more than a few large VM backups (100Gb+)  it just comes back with:   Not enough disk space available on store partition.   Clearly not a space issue in Azure blob.........

  • 0   in reply to   

    What I have seen is that the drive is completely full. What you forgot to answer is:

    • What's the disk usage of the "Dedupe_store" directory now?

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.