HPE StoreOnce Catalyst Library - Best Practices
- Do not enable compression, encryption, or deduplication in the Commvault software. These processes will severely impact StoreOnce deduplication.
- Target similar data types to dedicated StoreOnce Catalyst stores, and avoid mixing data types within a 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 libraries/shares/stores reduces the complexity leading to optimum long-term performance.
Synthetic Full Backups
To ensure successful completion of Synthetic Full jobs, always start with a Full backup, when a storage policy accessing the HPE StoreOnce library is used. For example, the job will go into pending with an error message stating error writing to media, if the following sequence is used:
- Run an Incremental backup on Storage_Policy_1.
- Change the storage policy on the subclient to Storage_Policy_2, that writes to a HPE StoreOnce library.
- Run an Incremental backup from the same subclient.
- Run a Synthetic full backup job from the same subclient.
In this situation, a full backup must be performed as step 3, after changing the storage policy.
- Where possible, split a backup session into multiple backup streams. Allowing StoreOnce to process multiple backups streams in parallel increases backup performance.
- Do not delete backup items (StoreOnce Catalyst items) directly from the StoreOnce Management Console. Instead, use the Commvault software to age expire the backup items to ensure application consistency.
- StoreOnce Secure Erase on stores will have a system performance impact due to increased disk I/O. Enable Secure Erase on a Catalyst store when it is needed, and disable it when it is no longer needed.
- When using ProLiant media servers and database servers for low-bandwidth StoreOnce Catalyst, enable “HPE Static High-Performance Mode” through the ProLiant “Power Management” settings for best backup performance. This setting is not enabled, by default.
- When configuring the Commvault software to use a Fully Qualified Domain Name (FQDN) address for a StoreOnce, be sure that the FQDN is fully registered with a Domain Name Server. Do not use local host file entries. This step is important when using StoreOnce Catalyst Copy jobs because the source StoreOnce System will use the FQDN to communicate directly with the target StoreOnce System. Using local client host file entries will result in the source StoreOnce System not being able to resolve the target FQDN address.
Connection Failures on Windows
To reduce the chance of connection failures on busy Windows clients when using Catalyst over Ethernet,
- Decrease the TIMED_WAIT Windows TCP parameter.
When an outbound connection is finished, the port associated with the connection is temporarily put into a TIMED_WAIT state in which time it is temporarily unavailable for reuse.
Decrease the TIMED_WAIT parameter from 120 seconds to 30 seconds by creating the TcpTimedWaitDelay DWORD parameter with value 30 in the following Windows registry:
- If needed, also increase the ephemeral port range.
Ephemeral ports are range of ports that Windows Server uses for outbound communications over TCP/IP.
Last modified: 9/6/2018 8:31:36 PM