Remove Snapshot Failed.

[Timbo74]

Hi,

We had a number of backups fail last night with errors like the one below:

Code: Select all

Replicating file "[VFMS3-2-R5] Fin-Production/Fin-Production-flat.vmdk"
BackupDisk failed
Client error: The specified transports are not available. Available transports: [nbd]. Specified transports: [hotadd]. VMDK path: [[VFMS3-2-R5] Fin-Production/Fin-Production-000002.vmdk].

Server error: The specified transports are not available. Available transports: [nbd]. Specified transports: [hotadd]. VMDK path: [[VFMS3-2-R5] Fin-Production/Fin-Production-000002.vmdk].
Failed to process VM disk backup. VMDK path: [vddk://<vddkConnSpec><viConn name="vcenter.bendigo.vic.gov.au" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-4766" datacenterRef="datacenter-2" datacenterInventoryPath="Bendigo" snapshotRef="snapshot-13443" datastoreName="VFMS3-2-R5" path="Fin-Production/Fin-Production.vmx" /><vmdkPath datastoreName="VFMS3-2-R5" path="Fin-Production/Fin-Production-000002.vmdk" /><transports seq="hotadd" /><readBuffer size="2097152" /></vddkConnSpec>].

More importantly was the job has left "Consolidated Helper-x" snapshots on the virtual machines. When it has tried to remove the snapshots VCenter gives us this error:

Code: Select all

Remove snapshot
Fin-Production
Cannot complete operation due to concurrent 
modification by another operation.

We've mad sure there are no running jobs on the Veeam server and have also restarted that machine with no difference to the snapshots.

We've got 3 servers with this issue and all of them are critical production applications so any help with this would be greatly appreciated.

Thanks,

Tim Coombes

[Gostev]

Hello Tim, what product version are you running? Please contact our support directly for any technical issues to speed up the resolution. They would need full logs from Help | Support information, not just summary information from session results.

"Consolidated Helper-x" snapshots are not produced by Veeam Backup, but rather by ESX itself during snapshot removal, so it is not Veeam Backup which is locking these/holding these snapshots.