Article Number: 000068694
avvcbimage Warning <16002>: Too many extra snapshot files (3) were found on the VMs datastore. This can cause a problem for the backup or restore. avvcbimage FATAL <16018>: The datastore information from VMX '[MLUN] Datastore/TestMachine.vmx' will not permit a restore or backup. avvcbimage Info <0000>: Starting graceful (staged) termination, Too many pre-existing snapshots on the datastore will not permit a restore or backup. (wrap-up stage) avvcbimage Error <9759>: createSnapshot: snapshot creation failedThe log shows that Avamar did not detect a Snapshot for this VM initially:
avvcbimage Info <14664>: no snapshots are present on this VM.
However, there are Snapshot files on the Datastore:
avvcbimage Info <14677>: All VM file Info: File:'TEST-000003-ctk.vmdk ' last modified on '07-Dec-2015 15:58' size=3932672 File:'TEST-000003-delta.vmdk ' last modified on '07-Dec-2015 15:57' size=134344704 File:'TEST-000003.vmdk ' last modified on '07-Dec-2015 15:55' size=408
Issue #2 The Virtual Machine has too many existing snapshots (30 or more).
avvcbimage Info <14665>: 30 snapshots are present on this VM: level=1, children=1, ref='snapshot-4223', 'snapshot1':desc='na' ... *level=30, children=0, ref='snapshot-4252', 'snapshot30':desc='na avvcbimage FATAL <0000>: [IMG0019] The pre-existing snapshots from VMX '[MLUN] Datastore/TestMachine.vmx does not permit a backup.
"Snapshot hierarchy is too deep."We must take a new "Avamar" snapshot (bring Snapshot count to 31).
goav vm snapshot clean --name winpe-testing-2- This can run against ALL VMs, as seen below.
admin@ave:~/>: ./goav vm snapshot clean =========================================================== GoAv : 1.49 Avamar : 19.7 Date : 03 Mar 2023 10:29 EST =========================================================== COMMAND : ./goav vm snapshot clean NOTE: This is not an official tool =========================================================== Running "./goav proxy clean" to clean proxies : ConsolidateTask=True ================== Checking Active Vmware Image backups ================= No active Vmware backups found ================== Checking PROXIES for unwanted DISK ================= ------------ 192proxy.lab ------------ Proxy 192proxy.lab is clean ------------ 197proxy.lab (19.7.100-82) ------------ Proxy 197proxy.lab (19.7.100-82) is clean ================== Checking Vms for leftover snapshots and disk consolidation ================= ....
MANAUL FIXSnapshot files must be removed from the Virtual Machines Datastore Directory.
In vCenter, select a proxy and browse the Settings > Hardware tab
Each proxy should have two disks, any additional should be removed
To remove an extra disk, select the disk and click "Remove" and leave the "Removal Options" selection to "Remove from Virtual Machine."
In vCenter browse the Virtual Machine, then in the tool bar select > Inventory > Virtual Machine > Snapshot > Consolidate
Manually remove the Snapshots if Consolidate does not work. Do not do this if there are other valid user Snapshots or if the VM disks are using any Snapshot file.
Browse the Datastore directory of the Virtual Machine
Create a Folder in the VM Directory Called "SS Removal"
Drag and drop the offending snapshot files into the new directory created above.
Inspect the Datastore directory for the Virtual Machine in question and check that the Snapshot files exist.
Once removed perform a backup.
If the issue is not resolved, contact Avamar Support.
Avamar
Avamar, Avamar Client for VMware
29 Feb 2024
7
Solution