Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

smccloud

Member

Registered: 2017-06-28

Posts: 9

One VM not backing up

After the patch you provided today, everything is working much better.  Except for one single VM that refuses to back up.  I am not getting any error, it just does not back up.  It is a Cisco Unity Connection VM, on the other two servers in the cluster I have a Cisco Unified Communication Manager and a Cisco IM & Presence server, both of which backup fine.  It does back up its data using an internal method to an internal SFTP server so if I have to just skip it, while not ideal it is a workable solution.  I am worried though, because one of our lab servers that needs to be backed up hosts multiple Cisco Unity Connection and Cisco Unified Communication Manager, and now I'm worried about them backing up.

Command to backup everything on the production host is

xsibackup --backup "VMs(ALL)" /mnt/XSI/nfs/ESXCORPB/ --backup-host=root@192.168.250.2:22 --mail-to=smccloud@donotemail.com --exclude="vmware-[0-9]{1,9}.log" --rotate=30D

Troubleshooting command of the affected VM is

xsibackup --backup "VMs(CUC-ucn1)" /mnt/XSI/nfs/ESXCORPB/ --backup-host=root@192.168.250.2:22 --mail-to=smccloud@donotemail.com --exclude="vmware-[0-9]{1,9}.log" --rotate=30D --verbosity=10 > output.log

I will post the output when I get it, it will take a while.

admin

Administrator

Registered: 2017-04-21

Posts: 2,066

Re: One VM not backing up

If the VM machine is plainly skipped the most likely cause is that you are calling it by the wrong name or that ©XSIBackup can't find it by the provided name in the /etc/vmware/hostd/vmInventory.xml file.

Check the name using the following command.

vim-cmd vmsvc/getallvms

Make sure that the name is not too complicated or has any special characters in it. If it contains spaces make sure that they have not been replaced by some other blank character different than char(32), some people end up with char(255) instead. Or even better, do not use spaces in your VM names.

smccloud

Member

Registered: 2017-06-28

Posts: 9

Re: One VM not backing up

So, it backed up fine on its own.  It might be something with the VM before it.  Which does have a space in its name.  However, I have other VMs on other hosts with spaces in their names which work fine.  I will rename all VMs to get rid of spaces.

admin

Administrator

Registered: 2017-04-21

Posts: 2,066

Re: One VM not backing up

Well, we overlooked the most obvious reason: if you are using a cluster, each VM may be moved around by DRS anytime depending on the cluster conditions. Just make sure that you set some policy to prevent DRS from acting during the backup windows.

smccloud

Member

Registered: 2017-06-28

Posts: 9

Re: One VM not backing up

Well, we overlooked the most obvious reason: if you are using a cluster, each VM may be moved around by DRS anytime depending on the cluster conditions. Just make sure that you set some policy to prevent DRS from acting during the backup windows.

We have Essential Plus licensing, no DRS.  I have manually move VMs between hosts, which I do not do very often.

Here is the verbosity=10 output from the last backup attempt right before it stops.  The next VM is CUC-ucn1 which backs up fine if I do it on its own.

   25/26	                        Cooper Web-000001-sesparse.vmdk                 [skipped excluded]
REGEX check failed for string '/mnt/XSI/srvs/192.168.250.2/vmfs/volumes/62e06338-9d0d86e8-05ec-0cc47afdf9c8/Cooper Web/Cooper Web-000001.vmdk' with pattern 'vmware-[0-9]{1,9}.log'

   26/26	                                 Cooper Web-000001.vmdk                 [skipped excluded]
Removing snapshot, please wait...
*** Snapshot was removed ***
Total CPU ticks:       2545724373148
Avg frequency (Ghz):   2.20
Real data ticks:       13832100151980
Real data seconds:     6286
Raw data speed:        3.00
Avg block seek:        0
2024-02-17T20:47:55 | Error code 272 at file signal.c, line 272 | Error description: Signal Handler: the process received signal 11, desc: No such file or directory

2024-02-17T20:47:55 | Error code 352 at file signal.c, line 352 | Error description: SIGTERM (11) condition was trapped: check logs for more details, error: No such file or directory
2024-02-17T20:47:55 | Error code 357 at file signal.c, line 357 | Error description: total errors: 2, check error.log
Removed directory: /scratch/XSI/XSIBackup-DC/tmp/xsi-root/31677
Removed file 3: /home/root/.xsi/tmp/31677/.blocklog.diff
Removed file 4: /home/root/.xsi/tmp/31677/346.snaptmp
Removed file 5: /home/root/.xsi/tmp/31677/350.snaptmp
Removed file 6: /home/root/.xsi/tmp/31677/402.snaptmp
Removed file 7: /home/root/.xsi/tmp/31677/Cooper Web.vmdk.vmdkmapf
Removed file 8: /home/root/.xsi/tmp/31677/405.snaptmp
Removed directory: /home/root/.xsi/tmp/31677
Sending e-mail to smccloud@unimax.com through SMTP#1...