Removing Stuck VMDK’s from the Veeam Proxy

KB ID: 1775
Product: Veeam Backup & Replication
Version: 8.x, 9.x
Published:
Last Modified: 2018-06-14
KB Languages: FR

Challenge

A VM that was processed by Veeam is found to require consolidation, yet consolidation attempts fail.

or

A VM that was processed by Veeam is found to have an orphaned snapshot.

 

Cause

This can occur when Virtual Applicane Mode (HOTADD) is used due to:

  • The command to release the virtual machines's disk from the proxy is not processed by VMware.
  • The Veeam server crashes while processing a virtual machine.
  • Jobs running within Veeam are forced to stop, and those jobs were using Virtual Appliance Mode (HOTADD).
  • A backup or replication job creating a snapshot on the backup proxy while the proxy is being used by another job. (Note: It is advised to build dedicated Proxies, and not backup or replicate them

Solution

 

Before beginning ensure that all jobs have stopped. This way the only disks that will be found attached to proxies will be the proxy's own disks and ones that need to be removed.
Identify Problem VMs

  1. Using a vSphere Client find any virtual machines which are displaying a warning that consolidation is needed.

     
  2. Perform consolidation, and note which virtual machines continue to have a warning regarding consolidation.


Find Stuck HOTADDed Disks

Review the settings of each Veeam Proxy looking for any disks which match the following:

  • Name of VMDK does not match the proxy, and matches a VM identified in the previous section.
  • Disk has a Disk Mode of [Independent - NonPersistent]
    Note: If the proxy is used as a Target Proxy for replication, the replica disks will be attached as Dependant.

Release Stuck HOTADDed Disks

Once you have found a disk HOTADDed to a proxy which needs to be released perform the following steps to release it.

  1. Click the symbol to select the disk for removal.

    Note: Do not check the box to delete files from datastore!
  2. Click [OK] to Confirm removal.
  3. After the disk is released from the proxy, attempt Consolidation again.

More Information

If you find that a specific proxy continues have issues with disks becoming stuck HOTADDed to it, please review: https://www.veeam.com/kb1882

For more information regarding orphaned snapshots please read: https://kb.vmware.com/s/article/1005049

Please be aware that starting from September 2018 downloading updates will require an active contract for the corresponding product.

OK

Rate the quality of this KB article: 
4.2 out of 5 based on 44 ratings

Couldn't find what you were looking for?

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

Request new content

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!

Orphus system