Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

This thread is from 2019, five years ago.
Since then the way to invoke the GUI has changed.
It's still very easy though, enter: xsibackup-gui from the command line in DC edition or plainly gui from the App edition command line.

Well, you can monitor the logs with Nagios or any similar tool if you will. Doing so with ©XSIBackup-App is easy, as it's a CentOS 7 appliance. You can also achieve that by connecting to an ©ESXi host via SSHFS if you are using ©XSIBackup-DC (the service running directly on ©ESXi).

You can also use tail -f on the log files from a command line.

Well the problem seems clear: "No such file or directory", now let's try to find out what is the file that ©XSIBackup expects to find and it does not.

Prepend strace to your job to have some finer level of detail on what's going on.

Things like a full disk can trigger this kind of behavior. Last time we stumbled on something like this it was due to some remote disk not being mounted. The root file system filled, no new files or dirs could be created and this triggered this error.

In your case it could be some renamed or missing file out of what ©XSIBackup can handle in the following VM.

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.

Yes, if you are a user of the trial you need to redownload. You may extract the xsibackup binary from the new version and overwrite yours at: /home/root/.xsi/xsibackup and also at /home/root/.xsi/bin/xsibackup

Yes, it's the wrong forum, we moved it here.
Yes, of course you can use CBT with rotation. You are probably making wrong assumptions, CBT doesn't probably work the way you think it does.

We created a date line prefixed log file as requested by the majority of users. This is also something rather canonical. If you miss some info in the log increase verbosity, if you still miss something create a feature request for that info to be added.

Use some real Linux server. Synology devices are expensive and have little RAM and outdated CPUs. Any 4th to 6th Intel generation i3 or i5 will perform way better for a fraction of the cost of a Syonology device.

FULL will uncompress the block and check the hash of the contents against the block name, which should match. It's obviously much slower.

Can you share what you did to sort your issue?.

The local ESXi server is 6.7, but the remote server to which you are delegating the job must be >= 8.0, otherwise the execInstalledOnly command would not be used (the version is checked before running that command).

Contact support dept. for a more personalized support. The forum is OK for general errors, we need some more details from your setup though.