Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

Thank you for the clarification.

I recognized a behaviour when a VM has been renamed.  XSIBackup-DC then creates two folders for the VM in the repo. One folder is named like the new VM name, the other is named like the folder.
The folder named like the new VM name is always empty, the actual backup data (map files) are placed the other folder which is named like the VMs folder.

Is this behaviour intentional?
Would it be possible not to create a empty folder named like the new VM name? I think it's just confusing to have two folders.

Regarding the snapshot failures I found out the following:

For the machines that failed with Error code 1223 the vmware.log showed these error messages:

2021-08-14T05:15:01.439Z| vcpu-0| I125: ToolsBackup: changing quiesce state: COMMITTED -> FINISHING
2021-08-14T05:15:02.446Z| vcpu-0| I125: Msg_Post: Warning
2021-08-14T05:15:02.446Z| vcpu-0| I125: [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing.
2021-08-14T05:15:02.446Z| vcpu-0| I125+ The error code was: 3
2021-08-14T05:15:02.446Z| vcpu-0| I125+ The error message was: Quiesce operation aborted
2021-08-14T05:15:02.446Z| vcpu-0| I125: ----------------------------------------
2021-08-14T05:15:02.448Z| vcpu-0| I125: ToolsBackup: changing quiesce state: FINISHING -> ERROR_WAIT

Which makes clear that the issue is within the VMs Windows OS.

Further investigation in the Windows event log showed multiple occurrences of Event ID 8 for Volsnap (a timeout occurred when Windows tried to make a snapshot).
But I could not make out a cause why this happened. There was sufficient free space to create the VSS snapshot and the I/O load was also low during that time.

For the machine that failed with Error code 4574 neither the vmware.log nor the Windows event log showed any helpful messages.

For all machines the "final" solution was to reboot the Windows OS. After the reboot the snapshot was working fine on all of them. Not a satisfying solution but at least it works now ...

I hope this information is helpful to others with the same issues.

Can you tell something about these two minor questions I asked?

/scratch/XSI/XSIBackup-DC/var/log/xsibackup.log is always empty.

It seems that I accidentally posted in the wrong forum - I found out now that the different forums are hard to distinguish because they all are titled "Index» General matters"

If you would have read my post more carefully you would have recognized that I talk about "XSIBackup-DC" several times.

Could you please move this post to the correct forum and read it again taking into account that it is about "XSIBackup-DC"?

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.

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.

I didn't assume so and also did not expect perfection. That's why I wrote

I shared my improved code to help other users of xsibackup.

You shouldn't treat each post which is pointing out a flaw as a criticism.

could you please explain how to use regexp for VMs source selection in XSIBackup-DC?

I tried different variants like --backup "VMs(REGEXP(^PROD))", --backup "REGEXP(^PROD)", ...
none of them works.

The documentation only explains the optional regexp pattern to exclude disks from the backup.

Could you please add how to use regexp pattern for the source selection to
https://33hops.com/xsibackup-dc-full-ma … tml#source