- Veeam Support Knowledge Base
- Repeated snapshot consolidation requests on VM by Snapshot Hunter
Repeated snapshot consolidation requests on VM by Snapshot Hunter
| KB ID: | 2091 |
| Product: | Veeam Backup & Replication | 8.0 | 9.0 | 9.5 | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 |
| Published: | 2016-01-25 |
| Last Modified: | 2025-07-28 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
–LinkedClone parameter.Challenge
Cause
Solution
Starting in Veeam Backup & Replication v8 P1 (build 8.0.0.917), Snapshot Hunter will not attempt to process orphaned snapshots on VMs created by vCloud Director. The Snapshot Hunter checks for the presence of the cloud.uuid parameter in the VM configuration (.vmx file).
Example:
cloud.uuid = "001.00000000-0000-0000-0000-000000000000"cloud.uuid value can be added to the VM configuration file to cause Snapshot Hunter to skip auto snapshot cleanup for that specific VM, even for VMs not managed by vCloud Director. The parameter can be added to a VM's configuration files using the vSphere client, PowerCLI, or by editing the VMX file using the editor available in the Veeam Backup & Replication Files view.
More Information
Previously, this article included information about disabling the entire Snapshot Hunter module. However, due to extensive improvements to the stability of this feature, it is no longer advisable to disable Snapshot Hunter.
Instead, customers are advised to open a Veeam Support case if issues are experienced with Snapshot Hunter functionality.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
