Last updated on Tuesday 14th of March 2023 07:04:02 PM

©XSIBackup-DC 2.0, what has changed?

©XSIBackup becomes an appliance able to backup multiple servers

Download XSIBackup Appliance  Download the appliance here at

First of all we want to state clear that ©XSIBackup's arguments, syntax and working principles remain untouched. Thus you won't have to learn a lot of new things, but just some additional arguments that allow to connect to other servers.

XSIBackup splash screen

There are multiple reasons that led us to take the decision to move ©XSIBackup to an appliance:

   • Adapt to an increasingly ©ESXi closed down hypervisor.

   • Allow to backup multiple hosts from one single installation point.

   • Consolidate ©XSIBackup into a stable foreseeable environment.

   • Improve backup speed, in special local backups.

   • Allow the programming of a web GUI in a fully enabled Linux OS (scheduled for early summer).

How does it work now?

As commented now ©XSIBackup is an appliance able to connect to multiple ©ESXi hosts via SSH. You won't have to install it on ©ESXi, thus you won't lose ©VMWare's support and guarantee in case you paid for it.

The appliance is built on top of CentOS 7.0 as of its first release, although it will evolve to Rocky Linux in the mid term. We chosed CentOS 7.0 for being compatible and a well tested OS with all features you may need. The software is installed to the directory /home/root/.xsi/

Now ©XSIBackup is not a service installed in ©ESXi any more, but an independent hub from where you can backup multiple servers. Of course, the lower the latency and the faster the IP link the better, thus, unless you have a low latency 10GB network, installing the appliance to every host is the recommended procedure. A fast 1 GB network should do it well too.

The hosts you add via the --add-host action are mounted at /mnt/XSI/srvs/ by their IP. You can browse their file system or restore VMs to every host via this mount points.

In order to operate ©XSIBackup now needs to connect to the hosts that you wish to backup. In order to do so we added the --add-host argument, which will link by RSA key to the host to be backed up and will connect to it permanently by adding an entry to the /etc/fstab file.

The appliance will also need to connect to the backup servers where the backup data and replicas are to be stored. You have a plethora of possibilities: from local virtual or physical disks ( see RDM disks), NFS, iSCSI or Samba shares to directly passing the data through to any IP/SSH backend of your choice. In fact you don't need to attach anything to the appliance to use it, just link to some backend host and put the data in there.

Once you have connected to some host to be backed up you will need to specify the host you want your job to be run at, you achieve that by means of the --backup-host argument, see example below.

xsibackup \
--backup=cbt \
"VMs(Win10_01)" \
root@ \
--backup-host= \

(*) Note that ©XSIBackup 2.0's xsibackup binary is in the path, thus you don't need to cd to the installation dir.
(**) Remember that the first three arguments: action, source and target are fixed. The rest of arguments can be set in any order.


We haven't changed how licenses work, you can use previously acquired licenses just as long as they aren't more than one year old when compared to the appliance release date. Of course you can always renew to reuse your license keys. You will need to contact us to free the MAC slot that you want to use with ©XSIBackup 2.0 though.

What does change indeed is where those license files are stored. As ©XSIBackup 2.0 is not installed in the hypervisor any more, the license.key files must be kept in the appliance in the /home/root/.xsi/lic directory. You can place them there as they come out of our licensing server. The files must just comply with a simple naming scheme MAC_*.key. By prepending the main MAC of your backup server you are telling ©XSIBackup 2.0 which license corresponds to which host.

Place as many license files as you need in the lic folder. They will be checked as you use the --backup-host argument. In case you backup some host without a license, the default Free features will be applied to that job.

So, how do I perform a backup from the appliance

Everything remains the same, so remember, to backup from the appliance you just have to:

1/ Use the --add-host argument to connect to the host you want to backup.

xsibackup --add-host root@

2/ Add the --backup-host argument to your job.

xsibackup --backup=cbt \
"VMs(CRM)" root@ \
--backup-host= \

(**) Note that if you backup to a backend over IP ( in the example) you will need to link via private key to the target server using the --add-key action.

Removing a host

The same way you add a host with the --add-host argument, you remove it by using --remove-host. You pass it exactly the same parameter: root@a.b.c.d:port

xsibackup --remove-host root@