Repeated snapshot consolidation requests on VM by Snapshot Hunter

KB ID:
2091
Product:
Veeam Backup & Replication
Version:
8.x, 9.x
Published:
Last Modified:
2016-01-26

Challenge

This article specifically applies to a situation where the VM was created using a third-party VDI, fast-provisioning application, or PowerCLI with the –LinkedClone parameter.
 
Shortly after a backup or replication job runs, multiple Consolidate Snapshot operations are performed against the VM.

Cause

Snapshot Hunter misidentifies the user snapshot of a VM created from a linked clone template as an orphaned snapshot and attempts to consolidate it.
 
Beginning in 8.0.0.917 (v8 Patch 1), Snapshot Hunter will not attempt 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"

Solution

There are two workarounds available:

Add the cloud.uuid parameter to each linked clone to cause Snapshot Hunter to not attempt to process that VM.

The cloud.uuid parameter will need to be added to each affected VM. If vCloud Director is not being used, the content of the cloud.uuid parameter does not matter. Snapshot Hunter only checks the VMX to see whether or not the parameter exists. You can add the parameter to a VM using a vSphere client, a PowerCLI script, or by editing the VMX file using the editor available in Veeam B&R’s Files view.


Disable Snapshot Hunter entirely.

Snapshot Hunter can be disabled which will disable automatic consolidation for all VMs. Warnings regarding VMs that Backup and Replication believes need consolidation will still occur.

Create the following registry value on the backup server:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Value name: DisableAutoSnapshotConsolidation
Value type: DWORD
Value: 1 = disable consolidation, 0 = enable consolidation

To apply the changes made in the registry the Veeam Backup Service must be restarted. Ensure that all jobs are stopped before doing so, when the service stops it will terminate all running jobs.
 

More Information

The best way to resolve this in an environment with many affected VMs is with a PowerCLI script. However, Veeam Support organization does not provide assistance with the creation or deployment of PowerCLI scripts.
 

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
3.9 out of 5 based on 8 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit