Best Practices; Storeonce Catalyst - HPE StoreOnce 6500 User Manual

Best Practices

For the latest user guides and white papers, see the HPE Information Library at www.hpe.com/info/
storeonce/docs.
To ensure the backup application, backup application feature, and the Fibre Channel (if applicable)
configuration being used is supported, see the Data Availability, Protection and Retention (DAPR)
compatibility matrix.

StoreOnce Catalyst

• Target similar data types to dedicated StoreOnce Catalyst stores, and avoid mixing data types 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.
• Wherever possible, use low bandwidth StoreOnce Catalyst for optimal backup performance and
network usage.
• When performing low bandwidth StoreOnce Catalyst backups, spread the number of backup sessions
across multiple media servers to reduce the possibility of a media server becoming a performance
bottleneck.
• Where possible, split a backup session into multiple backup streams. Allowing StoreOnce to process
multiple backups streams in parallel increases backup performance.
• 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
the best backup performance. This setting is not the default.
• Do not delete backup Catalyst items (backups) directly from the StoreOnce Management Console.
Instead, use the backup application to expire the backup items to ensures application consistency.
• Enable StoreOnce Catalyst client permission checking on each StoreOnce service set to ensure that
client data access is restricted. Restrict Catalyst store access to only those client identifiers that
require access.
• For optimum performance, set StoreOnce Catalyst client log levels to the default ERROR log level.
• Catalyst store Secure Erase will involve a system performance impact due to increased disk I/O.
Enable Secure Erase when it is needed, and disabled it when it is not needed.
• StoreOnce Housekeeping can run in parallel to StoreOnce Catalyst backups. However, the best
StoreOnce performance is achieved using Housekeeping blackout windows so Housekeeping only
runs at nonpeak times.
• Do not enable backup application level compression, encryption, or deduplication. These processes
will severely impact StoreOnce deduplication.
• When performing backups with StoreOnce Catalyst over Fibre Channel or StoreOnce Catalyst
Ethernet backups over LAN, StoreOnce Catalyst compression and checksums can be set to
DISABLED through the backup application configuration file. When performing StoreOnce Catalyst
Ethernet backups over WAN, StoreOnce Catalyst compression and checksums must be ENABLED
(default) through the backup application (plug-in) configuration file.
• When configuring a backup application 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 appliance will use the FQDN to communicate directly with the target StoreOnce appliance.
232 Best Practices