Here is a screenshot of the current status of the ddb. Backups are running over desired time windows with 98.27% of load being ddb lookups. We are close to capacity currently with backup storage though this will be resolved soon. How can we resolve the high DDB lookup % issue?
DDB and job status screenshots below.
Best answer by Onno van den Berg
Here is a screenshot of the current status of the ddb. Backups are running over desired time windows with 98.27% of load being ddb lookups. We are close to capacity currently with backup storage though this will be resolved soon. How can we resolve the high DDB lookup % issue?
DDB and job status screenshots below.
Make sure your DDB is hosted on a SSD, preferably one that is NVMe connected, and if this is already the case then you should look into the specs and health state of the drive.
Hi
Here the issue is with the Q&I value. The average Q&I time is the average time (in micro seconds) that was taken for insertion and query of signature in the deduplication database.
https://documentation.commvault.com/2024e/expert/monitoring_deduplication_database_partitions.html
https://documentation.commvault.com/v11/expert/hardware_specifications_for_deduplication_mode.html
https://documentation.commvault.com/2024e/expert/testing_iops_of_deduplication_database_disk_on_windows.html
Please refer to the below document, to run the IOmeter test to validate the IOPS.
Regards,
Wasim
+24Here is a screenshot of the current status of the ddb. Backups are running over desired time windows with 98.27% of load being ddb lookups. We are close to capacity currently with backup storage though this will be resolved soon. How can we resolve the high DDB lookup % issue?
DDB and job status screenshots below.
Make sure your DDB is hosted on a SSD, preferably one that is NVMe connected, and if this is already the case then you should look into the specs and health state of the drive.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
