Home > Storage > ObjectScale and ECS > Product Documentation > Dell ECS with Commvault: Configuration and Best Practices > Best practices
The following table summarizes suggested best practices, and configuration and tuning recommendations for consideration when you use Dell ECS with Commvault Complete Backup & Recovery:
Topic | Recommendations |
Managing traffic to ECS | The best practice for distribution of S3 REST traffic among the ECS nodes is to use an external IP load balancer. Dell Technologies recommends using a hardware load balancer such as ECS Connection Manager. The CAS protocol supports internal load balancing, so the address resolves directly to a single ECS node; do not use an external load balancer. Commvault provides several tools that enable the ability to connect to the cloud library and explore its contents or test connectivity by uploading and downloading data. |
MediaAgent performance tuning | In Commvault v11, nCloudEnableHighPerformance is set to 1 by default. This setting enables a group of tunable parameters for optimal cloud library performance. Each parameter can also be set individually if required.
|
Cloud connection performance | When using a high-speed network of 10 GbE or higher, see the Cloud Connection Performance tuning guide for guidance. |
CommCell performance tuning | When using a 10 GbE connection, see the CommCell Performance Tuning guide for tuning considerations. |
Data transfer: Optimize for concurrent LAN backups | This option is enabled by default and is useful when the MediaAgent is used for concurrent data protection operations from several clients. For example, if 25 clients are concurrently using the MediaAgent for 50 or more data transfer streams in a specific operation window, enable this option to help optimize the operating system resources on the MediaAgent. |
Maximum number of parallel data transfer operations / Restrict to | This option specifies how many concurrent read/write operations need to be established to the MediaAgent. The value can be set between 1 and 75. The default number of concurrent read/write operations to a MediaAgent is 25. If the Optimize for Concurrent LAN Backup option is enabled on the MediaAgent Properties > Control tab, the default value is set to 100 (this value can be set to a maximum of 500). |
Number of data readers | Modifying the number of data readers can significantly affect storage library performance. For information about optimizing data streams, see the Commvault documentation Data Readers. |
DDB Pruning Performance | This additional setting indicates the number of pruner threads that can optimistically be running at one time for a deduplication database (DDB). All DDBs associated with the disk library are allowed one default thread. After that, for every pruning request that the CommServe sends, an extra zeroref pruner thread is started until the start of (DedupMaxDiskZerorefPrunerThreadsForStore - 1) threads. If all pruning requests are for the same DDB (optimistically), the DDB will have the number of pruner threads that have been defined for the additional setting DedupMaxDiskZerorefPrunerThreadsForStore. Default value: 3 Adjusting this value might be useful to increase the speed at which data is pruned. |