Forum ©XSIBackup: ©VMWare ©ESXi Backup Software

The double quote issue will be addressed in 11.2.1 as well as the three digit format check. You were right in that it's not checked in the GUI, sorry about the misinformation. It is stated in the Man Page though.

[b]--backup-room[/b] argument is useless if your disk is already full. Free some space manually.
The [b]--backup-room[/b] value is expressed in Mb., thus 690 means: use 690 Mb. to store my backups.

[b]CORRECTION 2019-01-03:[/b]

--backup-room is expressed in Gb., not Mb.

You can do something even easier since v. 11.0.0, which is to just place your script inside the job file and chain as if they were regular backup jobs.
To know why your scripts aren't executing we would need to debug your setup. Post the relevant part of the log or contact support.

You are using [b][https://33hops.com/xsitools-vmfs-deduplication.html](c)XSITools[/url][/b] whcih is a deduplication engine that stores data in a deduplicated repository.

[url]https://33hops.com/xsitools-vmfs-deduplication.html[/url]

If you don't know what deduplication is and you don't want to learn what it is, we suggest that you use a regular copy method like: [b]--backup-prog=Vmkfstools[/b]

XSIBackup does not copy all files in your VM, just the files needed to have a working backup.

We will be sending [b]XSIBACKUP-PRO 11.2.0[/b] to registered users from [b]Dec 27th[/b], which includes [b](c)XSITools[/b] repository pruning, both on demand via the [b]--prune-xsitoolsrepo[/b] and automatic by means of the [b]--backup-room[/b] argument, which will limit the size to which an [b](c)XSITools[/b] repository can grow.

Did you set [b]--backup-how=custom[/b]?

Well, you have a working cron and a working job script, you just need to put the ball through the round hole.
Did you assign proper execution permisssions on the job and write on the xsibackup.log?, they should be assigned automatically, but you never know.
Program your job to some point close in time and debug, we can't do that for you.

Well, you need to comprehend what's into play to in turn know what you can achieve with it.
When you backup the ESXi configuration you are really backing up the contents of the /etc directory, which contains all configuration details and inventory database. So, to minimize the possibilities of ending up with a corrupt system, you should reinstall the same version and build that you backed up. You can restore the ESXi configuration by using the built in command or manually:

a/ [url=https://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.upgrade.doc_41/esx_upgrade/post_esx/t_restore_the_esxi_host_configuration.html]Restore by using the vicfg-cfgbackup -l command[/url].
b/ [url=https://graspingtech.com/backup-vmware-esxi-6-5-configuration/]By using a different command line option[/url]

vim-cmd hostsvc/maintenance_mode_enter
vim-cmd hostsvc/firmware/restore_config /tmp/configBundle.tgz

c/ Restore manually by uncompressing the host configuration backup and overwritting the /etc folder. This is a more flexible approach, as it will allow you to restore your configuration without limitations. You must assume all risks derived from restoring to a different version or build.

Copy and uncompress the hostname-a.b.c.d-config.tgz file to /tmp
tar -xvzf /etc/hostname-a.b.c.d-config.tgz
cd /tmp
tar -xvzf /tmp/state.tgz
cd /
cp /tmp/local.tgz .
tar -xzvf local.tgz
Reboot the ESXi Host

When you do so, you restore an inventory of VM's in their original paths, so you should make sure that you restore each VM to the same path where it was before. If you can't reproduce your exact same setup, you will end up with orphan VM definitions pointing to wrong paths, in that case, it may be better to just reinstall ESXi, restore your VM's individually and add them to the new host's inventory again.

Do not use physical paths for your backups, but the hardlinked paths, i.e.: [b]/vmfs/volumes/localRaid5[/b] instead of [b]/vmfs/volumes/58468b1e-752c135f-2ab0-1866dae9637a[/b]

If your cron daemon is working, you can run your jobs manually but the jobs are not triggered, then, you have some wrong path, or you have not published the crontab changes.

Have you run the [b]./xsibackup --update-cron[/b] command after populating the [b]conf/root-crontab[/b] file?

You could also be using some wrong syntax in the crontab, post the contents of the crontab.

Thank you for the feedback

BTW, just an update. The simplest kind of local backup: vmkfstools will also preserve the snapshots, but only in the side of the VM being backed up. The resulting backed up VM will be a consolidation from the topmost snapshot.