I had a VM that was listed in the VM database but no longer existed. It caused the backup to show as failed.
The error message is as below. The orphaned VM is VM '140'. In spite of the error messages, the backup was successful and once the offending VM was removed from the database the backup completed and shows success. Just thought you should be aware.
ERROR CLDELSN3, details: [SSL] error: cannot delete snapshot, details: Skipping invalid VM '140' Skipping invalid VM '140'
Last edited by zarthan (2018-09-04 14:10:17)
That error is thrown to the shell when taking a snapshot and it is thusly reported. An orphaned VM must be correctly unregistered for the ESXi database to be consistent. We'll try to detect this special condition to turn it into a general warning instead of an error related to a given VM.
Just to add a little more information, I only back up a list of VM's, not everything. The error message occurred after each VM backup completed and it listed each VM backup as failed. In spite of the backup being listed as failed, all the backups were successful.
for future reference
vim-cmd /vmsvc/unregister ID# removed the orphaned VM
Yes, we know that command unregisters a VM, but XSIBackup cannot take decissions in regards to your VM inventory, it's each admin that must keep his VM inventory consistent.
I wasn't trying to tell you how to fix it. That was in case anyone had a similar problem as in "for future reference". Also not suggesting that XSI make my decisions. I was just filling in details. I do think that the error condition should NOT flag the backup as failed. On the plus side, it did cause me to look into what caused the failure.