This call of xsibackup
xsibackup --backup "VMs(XBC_IGMS101 - Zabbix)"
fails although the VM exists with this name. This is the error produced:
2021-06-25T15:14:23 | Error code 2672 at file xsibackup.c, line 2672 | Error description: could not find any VM in list: xbc_igms101 - zabbix, please check that the VM files exist
"vim-cmd vmsvc/getallvms" shows that this VM really exists with this name:
64 XBC_IGMS101 - Zabbix [SSD-RAID5] IGMS101/IGMS101.vmx centos8_64Guest vmx-15
A similar backup call
xsibackup --backup "VMs(XBS_DMZ01 - Redmine Test)"
works just fine.
Could the VM hardware version be the cause?
The non-working VM has hardware version "vmx-15", the working VM has hardware version "vmx-14".
The ESXi host is Version:
6.7.0 Update 3 (Build 15160138)
Last edited by Int (2021-06-25 15:33:54)
No, that can't be the reason. The most likely reason is that the VM's name is not the one you believe it is.
Please, avoid such naming.
We have taken the time to make ©XSIBackup-DC work with spaces, dashes, hyphens, underscores, at signs, etc.., still we have detected a number of shell component bugs in the past related to space handling.
On top of that there exist a number of different characters that will produce an invisible space. Same applies to hyphens, dashes, etc...
Make your life easier and renounce to using fancy characters in production environments, you will for sure save yourself time and money enough for some days of vacation in the Caribbean after a decade.
When I remove all spaces, special characters and even capital characters xsibackup still fails with the same error:
2021-06-28T12:12:15 | Error code 2672 at file xsibackup.c, line 2672 | Error description: could not find any VM in list: xbcigms101zabbix, please check that the VM files exist
The datastore path of the VM also does not contain spaces or special characters.
You can contact support so that we debug this for you, nonetheless it looks like there's something in that VM which is not what you believe it to be.
When starting the backup for all running VMs
xsibackup --backup "VMs(RUNNING)"
the VM was included in the list of VMs to backup but the backup itself did not work correctly.
The email report gave this garbled output for the VM
Num VM Name Size Diff. State Time Speed Compress Errors 16 [9686dc-ab09e0c8-b200-a0369fd6b900/IGMS101/IGMS101.vmx] b200-a0369fd6b900/IGMS101/IGMS101.vmx 2.00 MB 0.00 B /vmfs/volumes/5c9686dc-ab09e0c8-b200-a0369fd6b900/IGMS101/IGMS101.vmx 00:00:00 inf MB/s 1626120946 0
I solved the issue by recreating the VM configuration (.vmx) from scratch and just kept the original virtual hard disks.
With this new VM configuration the xsibackup works fine now.