If the auxiliary copy fallen behind alert is configured, then an alert is generated when the system predicts that the auxiliary copy operation will exceed the number of hours specified for the operation to complete. Use the following table to verify and resolve the auxiliary copy fallen behind alert issues.
Cause for the Fallen Behind Alert |
Resolution |
The query and insertion (Q&I) time of the deduplication database (DDB) is high |
To improve the DDB performance, upgrade the DDB volume with faster solid state drive (SSD) disks. For more information, see Performance of Query and Insertion (QI) of the DDB is Slow. |
The total throughput is low |
To improve the bandwidth utilization, see Improving Bandwidth Utilization with DASH Copy or Backups with Deduplication |
Insufficient bandwidth configured on the destination |
If the bandwidth configured on the destination is low, you can choose from either of the following options:
|
Destination tape library is not optimally utilized |
If you have a tape library configured as the destination, verify the following:
|
Destination tape library is not scalable |
If tape management is slowing down the copying process, you might want to configure the cloud storage as the destination for secondary copy. For more information on configuring cloud library, see Creating a Cloud Storage Library. |
The auxiliary copy operation is not configured to run optimally |
Tune the configurations to run the auxiliary copy operation by modifying the settings as described in Performance Tuning for the Auxiliary Copy Operation. |
Data is not equally distributed across all streams on the source copy |
Enable stream randomization to distribute data evenly among the streams. For more information, see Configuring Dynamic Stream Allocation. |