Implementation of Commvault with HPE Storeonce appliance

Hello Team,

Just want check the store once catalyst with Commvault integration, the best practise will use multiple catalyst store with different disk library for specific data types like FS, Database & VMs or will use one store with single disk library to use all for getting performance level and deduplication ratio.

Please advise.

Regards,

Anand

Correct on the first one, use different catalyst stores for different type of data, it is an HPE best practice

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00003357en_us&docLocale=en_US&page=GUID-D7147C7F-2016-0901-0705-000000000756.html

• Target similar data types to dedicated StoreOnce Catalyst stores and avoid mixing datatypes within a StoreOnce Catalyst store. Backups of differing data types, such as two different database types, will not deduplicate well against each other. Separating different data types into separate StoreOnce Catalyst stores reduces the store complexity leading to optimum long-term performance.

Here are the best practices for implementing Commvault with HPE StoreOnce 3660 NAS (Network Attached Storage) share:

1. Deduplication & Compression Configuration

• Deduplication and Compression on Hardware vs. Commvault:

  • If HPE StoreOnce is configured to perform deduplication and compression at the hardware level, you should disable deduplication and compression in Commvault for the associated storage policy.
  • Enabling deduplication/compression on both Commvault and StoreOnce can cause performance degradation and excessive storage consumption due to redundant processing.
  • Choose one deduplication/compression method—preferably hardware-level on StoreOnce for optimal efficiency.

• Reference:

  • For more details on deduplication and compression best practices, see Encrypting Backup Data.

2. Backup Strategy: Synthetic Full vs. Full + Incremental

• Synthetic Full + Incremental:

  • For file system and VMware agents, the recommended backup scheme is synthetic full + incremental. Synthetic full backups reduce the load on the source client by consolidating data on the MediaAgent, allowing the client to maintain regular workloads.
  • Synthetic full backups are generally preferred unless your environment or agent type requires traditional full backups (e.g., Snap jobs, databases).
  • For NAS shares, confirm agent compatibility with synthetic full backups. If unsupported, use full + incremental backups.

• Reference:

  • Synthetic Full Backups
  • Best Practices for Synthetic Fulls
  • Agents That Support Synthetic Full Backups

3. HPE StoreOnce Catalyst Integration

• If using StoreOnce Catalyst, leverage Catalyst Copy for auxiliary copy operations. This enables efficient, direct replication between StoreOnce appliances, bypassing the MediaAgent for data payload transfer and optimizing bandwidth and storage usage.
• For configuration steps, refer to Configuring Auxiliary Copy for HPE StoreOnce Catalyst Library.

4. General NAS Share Configuration

• Commvault supports backup to any CIFS/NFS-based NAS share, not just NetApp. Add the NAS share as a disk library mount path in Commvault.
• Test the configuration to ensure backup data is correctly stored on the centralized NAS share.
• For guidance, see Disk Libraries Getting Started.

5. Additional Recommendations

• Confirm compatibility: HPE StoreOnce 3660 should be running a supported software version (minimum 4.1.0 for 4th generation appliances).
• Monitor backup and restore performance, especially if using hardware deduplication/compression.
• Regularly review storage usage and backup job logs for any issues.