Bare Metal Recovery

If the operating system on your machine fails to start, you can perform bare metal recovery of your system. To do this, you must have Veeam Recovery Media that you created on your functional system and a full backup with system metadata.

At the first stage of bare metal recovery, you must boot your machine from Veeam Recovery Media which launches the recovery image OS in your machine RAM. You then import the backup file into the Veeam Agent database and run the restore. Veeam Agent erases all data on the machine, reconstructs partition structure using system metadata, restores data from the backup and creates the boot loader.

Before you reboot the machine upon successful bare metal recovery, you may need to restore additional data from another backup. To do this, you can use the standard file-level restore functionality. Veeam Agent mounts the backup file to the file system of the recovery image OS. After that, you can copy the necessary files or directories to a desired location.

Considerations and Limitations for Bare Metal Recovery

Bare metal recovery to dissimilar hardware is not supported.
Bare metal recovery of SVM configurations is not supported.
Bare metal recovery from backups created from within non-global zones is not supported.
Bare metal recovery only from file-level backups created by version 4.0.0.1029 (or later) of Veeam Agent for Oracle Solaris is supported.
Bare metal recovery requires a backup that includes the full contents of the root directory (the --includedirs option must be set to /).
[For Veeam Agent version 4.0 running on Oracle Solaris 11.4] To create Veeam Recovery Media, Veeam Agent must have access to Oracle Solaris Image Packaging System (IPS).
Paths longer than 1006 symbols cannot be restored during bare metal recovery and must be restored manually afterwards.
Bare metal recovery supports file system encryption keysource: "raw,ephemeral" and "passphrase,prompt". For file systems whose encryption has an different keysource, Veeam Agent will prompt to specify a passphrase to keep the encryption after restore.
During bare metal recovery, Veeam Agent does not restore data from ZFS volumes.
[For flexible mapping] You cannot map a ZFS pool that resides on a disk slice.

[For flexible mapping] You cannot map the system rpool to multiple disks.
[For flexible mapping] Any special ZFS pool configurations, such as RAIDZ, mirroring, cache devices, and so on, are ignored. All the disks assigned to the source ZFS pool are simply added together to form the target ZFS pool.
During bare metal recovery, access (atime), modified (mtime) and changed (ctime) timestamps are reset for all non-empty files and directories.

Related Task

Performing Bare Metal Recovery