Registered users
Linkedin Twitter Facebook Google+

In order to improve user's experience and to enable some functionalities by tracking the user accross the website, this website uses its own cookies and from third parties, like Google Analytics and other similar activity tracking software. Read the Privacy Policy
33HOPS, IT Consultants
33HOPS ::: Proveedores de Soluciones Informáticas :: Madrid :+34 91 663 6085Avda. Castilla la Mancha, 95 - local posterior - 28700 S.S. de los Reyes - MADRID33HOPS, Sistemas de Informacion y Redes, S.L.Info

XSIBACKUP-PRO ::: Restore module

XSIBACKUP-PRO offers a restore module as part of the Pro version. It allows to easily browse stored backups choose one of them and restore it to the desired local path. The restore module can restore any of the backup types performed with XSIBACKUP-PRO: local (vmkfstools), Rsync & Borg.

You can browse stored backups in case of local or Borg backups, filter the results and choose from a list. In case of remote backups, you must provide the full path to the VM on the remote server:

Example1 (restore remote backup stored in an Rsync server):

(*) In case you use paths with interstitial spaces, please, don't forget to quote them appropiately.

Restoring a local backup is very easy by using the built in functions to list and filter results. You just have to tell the restore module which folder your backups are stored in. The browser will detect two levels underneath the proposed path. This is not arbitrary, as XSIBackup allows to create timestamped subfolders. You can then filter by VM name, date strings (by using the same format), or by any part of the full path. Filtering matching is performed partial, thus, any piece of information that matches the VM name or timestamped subfolder will do the trick.

To restore a remote (over IP) backup, you must parse --restore-vms=IP:port:/path/to/vmx/file/yourvm/

The following example demonstrates how to browse and restore a backup from a local repository.


Here we firstly obtain a list of all backups present at the /vmfs/volumes/backup storage point by running the command:

At this point you may decide to restore one of the VMs, let's say number 18, but you may want to filter the results (which could be much longer) to get to the list of VMs you stored on a given date, per instance on agoust the 18th 2016, thus you would enter 20160818 into the filter prompt and get:

After you have filtered the results, you can just input the corresponding VM number in the listing and you will get:

In this example we have decided to restore the VM [New Virtual Machine 2] to the folder /vmfs/volumes/backup_usb. At this point you will be prompted to chose the restore method: vmkfstools or Rsync. Vmkfstools is much faster, but it will detect any present snapshots and restore the VM fully from the topmost snapshot in the chain, thus the resulting VM will be a consolidated guest including all data in all snapshots. The resulting VM will be the equivalent to delete all snapshots in a live VM.

If on the contrary you decide to keep all existing snapshots, you must choose Rsync as the backup mean. Do not worry if you commit a mistake, the backed up VM will remain untouched, so you can repeat the process as many times as you want to.

Confirm that you want to overwrite data and that's it.

Restoring (c)XSITools backups

Restoring (c)XSITools backups is much the same as restoring any other type of backup. The restore module will detect the type of backup it is and will just ask you where you want to place the restored VM. Since version 11.1.7 restoring virtual machines previously backed up with XSITools can be resumed, should something go wrong in the restore process, such as a broken TCP pipe.

The restore module keeps track of restored chunks in a file named after the disk with a .partial appendix. If the restore process gets interrupted the XSITools restore module reads this file and allows you to resume the latest restore operation at the point where it stopped in the previous restore attempt or to start from the beginning. If the previous restore operation was interrupted before getting to the fifth block in the file, the process is commenced from the start. Once the restore process completes, the eventual .partial files are removed.

Restoring a Borg Backed up VM

It is pretty much the same, but you will parse a path in a server and not just a local path.

Website Map
IT Manager
In Site
Resources & help
Index of Docs
33HOPS Forum

Fill in to download
The download link will be sent to your e-mail.

            Read our Privacy Policy