Hi, this is Daniel from ©XSIBackup development. We have followed your case here too. We couldn't help much in the beginning as you didn't provide much information, apart from these two lines
./xsibackup: eval: line 1: disk0: not found - not sure what this error refers to
Backing up virtual disks...
The error is not very helpful, that's why we recommended you to debug the script to narrow the problem down.
You should keep in mind some basic principles that will for sure help you in the future.
- The contents of your VM, no matter whether they are files or programs can't affect the hypervisor functioning. Only in very seldom cases some service that can't be quiesced may delay the snapshot taking phase and end up in a snapshot error. For that to happen, you should be using the --snapshot=doquiesce argument, which was not the case.
- In your case, as you were not trying to quiesce the VM, snapshotting the VM couldn't fail, even if you were running an exigent service inside the guest (except for some other reason: lack of space, hardware problem...). You could end up with a VM copy which may not have consistent data (as you weren't quiescing the VM), some of the last data in your I/O buffers could have been partially written if the snapshot request interrupted it being written to disk, but that is a different issue which is not detected at the hypervisor level.
- When you convert virtual disks from some other format, you are adding an additional factor that could add some uncertainty, as whether the resulting .vmdk and -flat.vmdk files are fully consistent with what your ESXi version expects to find. You should mention that when requesting help.
- In most of the cases, if not all. Any inconsistency in the .vmdk disks can be solved by cloning them to a new file via vmkfstools.
- Editing any of the config files with some external editor may render them unusable or inconsistent.
- Disk consistency at the VM level can be rapidly checked by:
1/ Making sure the .vmdk files pointed by the .vmx file are present.
2/ Making sure that the .vmdk files point to the right -flat.vmdk files.
3/ Deleting all snapshots and consolidating the VM plus deleting the .vmsd file, which will be automatically generated again next time you switch the VM on.
In your case the problem seemed to be originated in the .vmsd file, as its syntax includes the .diskX keyword, where disk is an ordinal related to the existing snapshots.
If you are an ©XSIBackup-Free user and need to request help, please do so in our forum at: https://33hops.com/forum/
And remember that all we know is what you let us know, thus please always provide the backup job the full output log and any other relevant circumstance.
