Currently I'm testing trial version of xsi-dc and discovered very strange issue in case of VM with snapshots.
During backup procedure xsi-dc reported that it's impossible to delete temporary snapshot with name like xsi7834010995546.
Also it's impossible to delete manually the single snapshot afterwards or all snapshots.
Failed - A general system error occurred: vim.fault.GenericVmConfigFault
And it's impossible to delete this VM:
Failed - Unable to access file since it is locked
Announced feature All pre-existing snapshots are preserved doesn't work.
Of course it's great solution, but some features need to be fixed. Or maybe I'm doing something wrong.
Last edited by bullet_flame (2019-10-14 14:51:41)
You are describing a general issue. First of all delete any lock files .lck in the VM folder. Then make sure your VM is working O.K., take a snapshot, then another one on top of it, three our four piled snapshots should not harm, then delete them one by one. If you can't, then you will need to find out what's wrong and fix it before actually using (c)XSIBackup-DC
This is a detailed post on (c)ESXi snapshots and the most common errors that you may encounter along with solutions and workarounds.
Thanks a lot for feedback !
So I deployed another VM from scratch and no issues during backup process were detected.
Possibly it was something wrong with my first VM.
After that I deleted all the existing snapshots and tried to restore.
When restoration finished I checked that snapshots don't appeared and tried to re-register VM.
After re-registration 2 snapshots made by me became in place and additional temporary xsi snapshot.
This xsi snapshot can't be deleted.
I checked that no lock files are presented inside VM folder.
Last edited by bullet_flame (2019-10-15 09:35:06)
It seems I found workaround:
I tried to make disk consolidation and got the same error :
Consolidate VMDisks VM-Deb-x64-02 root 10/15/2019 16:26:22 10/15/2019 16:26:22 Failed - Unable to access file since it is locked
The same error when tried to revert snapshot:
Revert To Snapshot VM-Deb-x64-02 root 10/15/2019 16:27:15 10/15/2019 16:27:15 Failed - Unable to access file since it is locked
After that tried to consolidate disks again and it was successful :
Consolidate VMDisks VM-Deb-x64-02 root 10/15/2019 16:27:28 10/15/2019 16:27:28 Completed successfully
So twice consolidation helped in my case.
All operations with the snapshots became successful.
Last edited by bullet_flame (2019-10-15 13:39:54)
Mmm, whatch your disks, don't wait till they wear out.
Disks are OK, it's not the reason.
I upgraded Xsibackup-DC to version 18.104.22.168 and it restored VM with snapshots without any issues.
So I suppose it was a bug of version 22.214.171.124 used by me previously.
When I deleted all the snapshots and recovered VM from backup - I was needed to remove VM from inventory and register again to see all the snapshots.
Also it's possible to reload vmx file without unregister/register action:
vim-cmd vmsvc/reload Vmid
Maybe it's will be good to add automatic reload of vmx file configuration after restore.
And also to add key to delete all existing snapshots before backup.
Last edited by bullet_flame (2019-10-21 15:41:05)
I am also getting a disk locked error.
Vsphere reports the following: virtual machine disk consolidation failed
If I manually try to consolidate (through the menus) it reports: An error occurred while consolidating disks: msg.fileio.lock.
Consolidation failed for disk node 'scsi0:0': msg.fileio.lock.
I've reviewed posts on this issue but am not clear how to progress.
The errors you are describing in this post related to snapshot deletion and disk consolidation are typical when you move a VM from VMFS5 to VMFS6. (c)XSIBackup-DC is an extremely flexible tool, it will allow you to copy virtually anything to anywhere, but you have to keep the basic set of rules in mind when doing so: don't mix VMFS versions, don't try to run VMs with higher HW versions than supported by the ESXi host, etc...
Delete any .lck files in the VM directory. (c)XSIBackup-DC deletes them after cloning, backing up or doing any task, but if you kill some job you might leave some leftover.
You will find a detailed guide to dealing with snapshot errors here: (c)ESXi snapshot errors, its solutions and workarounds