Restore to Xen Server Hypervisor

To use this restore method you have to set a “where=/” Bacula restore parameter, then set any other required restore plugin parameters for your restore.

The guest VM archive will be sent to the XenServer hypervisor and always restored as a new guest VM. You can change the Storage Repository where your VM Guest will be restored.

To list available Storage Repositories you can use a listing mode, see listing. If you set an improper (eg: non-existent) Storage Repository for restore, then the restore process will fail. The Restore process requires a block level patching of saved disks which has to be performed on local filesystem (default directory: /$WorkingDirectory/xenapi/$JobID/).

Note

This is a XenServer limitation as XAPI does not support block level incremental restore but full image restore only.

In the following restore session example, the “Preserve vm config on restore” plugin restore option is set to “yes”:

* restore where=/
...
Run Restore job
JobName:         RestoreFiles
Bootstrap:       /opt/bacula/working/srv-xen-01-dir.restore.2.bsr
Where:           /
Replace:         Always
Fileset:         Full Set
Backup Client:   srv-xen-01-fd
Restore Client:  srv-xen-01-fd
Storage:         File1
When:            2018-01-05 12:47:16
Catalog:         MyCatalog
Priority:        10
Plugin Options:  *None*
OK to run? (yes/mod/no): mod
Parameters to modify:
     1: Level
     2: Storage
     3: Job
     4: Fileset
     5: Restore Client
     6: When
     7: Priority
     8: Bootstrap
     9: Where
    10: File Relocation
    11: Replace
    12: JobId
    13: Plugin Options
Select parameter to modify (1-13): 13
Automatically selected : xenserver: uuid=fe1ccf3b-1865-3942-c928-d98138397ff1
Plugin Restore Options
server:              *None*               (*None*)
port:                *None*               (*None*)
user:                *None*               (*None*)
password:            *None*               (*None*)
passfile:            *None*               (*None*)
storage_res:         *None*               (*Default location*)
preserve:            *None*               (*No*)
Use above plugin configuration? (yes/mod/no): mod
You have the following choices:
     1: server (Restore server name)
     2: port (Restore server port number)
     3: user (Restore user name)
     4: password (Restore user password)
     5: passfile (Restore user password file)
     6: storage_res (Storage Resource location for restore)
     7: preserve (Preserve vm config on restore)
Select parameter to modify (1-7): 7
Please enter a value for preserve: yes
Plugin Restore Options
server:              *None*               (*None*)
port:                *None*               (*None*)
user:                *None*               (*None*)
password:            *None*               (*None*)
passfile:            *None*               (*None*)
storage_res:         *None*               (*Default location*)
preserve:            yes                  (*No*)
Use above plugin configuration? (yes/mod/no):

The restore job log will inform you about what guest VM is restored and what new guest VM was created.

JobId 131: Start Restore Job RestoreFiles.2017-12-28_14.42.25_15
JobId 131: Using Device "FileChgr1-Dev2" to read.
JobId 131: xenserver: VM restore: vm1/10908c8a-f932-6f91-9cac-3034e3acf45b
JobId 131: Forward spacing Volume "Vol-0002" to addr=1758441248
JobId 131: Elapsed time=00:04:51, Transfer rate=3.158 M Bytes/second
JobId 131: xenserver: VM UUID created: 45c49e07-ff20-ab55-e622-05ff2fbb0c1f

The new VM Guest created during restore will get the same name-label as the original VM. All VDIs connected to the restored VM will be marked with -restored suffix.