Hi @Kumar Devaraj ,
Good day!
During the backup process, Commvault (CV) creates a snapshot for the VM. At the end of the backup job, a request is made to delete the snapshot. If the snapshot removal doesn't complete in time, the job will be marked as complete, and the snapshot will be added to the cleanup queue.
After the initial snapshot removal request via the VDDK API is sent, if it fails, subsequent requests are made with exponential backoff delays: 4 minutes, then 9 minutes, 16 minutes, 25 minutes, and so on, until 4 hours have passed. After 4 hours, further requests will continue. These delays provide sufficient time for the host to complete the task.
If you observe that consolidation requests are being sent even after the backup is complete, please check why the initial snapshot removal request isn't completing in a timely manner on the VMware side. If the snapshot is properly removed, CV will not send further requests.
If snapshots are left unattended for too long, they will continue to grow dynamically, consuming storage space until the datastore reaches capacity. Additionally, prolonged snapshot retention can degrade virtual machine performance. To mitigate these impacts and maintain the stability of the environment, Commvault’s cleanup mechanism operates continuously and cannot be modified, ensuring that snapshots are removed promptly to prevent storage and performance issues.
Regards,
Sureshkumar S
