Client-Side deduplication with HPE Store once

Question

Hi All,When implementing the solution with HPE StoreOnce, the best practice is to enable deduplication at the hardware level rather than on the Commvault side. We agree with this approach and have not created a Deduplication Database (DDB) in Commvault.We also noticed a recommendation in the Commvault documentation to disable deduplication on the Commvault side.Does this mean that, when associating File System and VMware clients with the HPE StoreOnce storage target, we should disable both deduplication and compression at the client level and on the VMware subclients as well? This requirement is not explicitly mentioned in the documentation we reviewed.Support for HPE StoreOnce Catalyst StorageBest Practices for HPE StoreOnce Catalyst Library

Ledoesp · Answer

Do not enable compression, encryption, or deduplication in the Commvault software. These processes will severely impact StoreOnce deduplication.

So when defining a HPE Catalyst library, you will associate a VSA or FS subclient with a plan. In 11.44 you can now disable compression at the storage level, in earlier version you have to do that at the primary copy level for each plan/storage policy or at the subclient level.

Plan will be linked with HPE Catalyst library and you can disable compression on the plan in the primary copy or at the storage level in 11.44. At the subclient level you can also disable the compression but it is easier if you do that at each plan you define with a HPE Catalyst library or at the storage level for each Store you define instead per each subclient. Dedupe setting at the subclient level does not affect if the storage is not using CommVault deduplication like with StoreOnce, I think when you define an HPE Catalyst library you cannot select the Commvault dedupe feature:

Client-Side deduplication with HPE Store once

1 reply

Readiverse Academy Certifications

Readiverse Academy Certifications

Sign up

Login to the community