Step 10. Finish Working with Veeam Recovery Media

When the restore operation is completed, finish working with Veeam Recovery Media and start your operating system.

Important

Depending on the system architecture, before you reboot the recovered machine, consider the following:

[For Oracle Solaris on x86 architecture] On the machine, you must manually change the primary boot device to hard drive, otherwise after reboot the machine will boot from Veeam Recovery Media again.

[For Oracle Solaris on SPARC architecture] Veeam Agent will automatically change the boot order on the machine, and after reboot the machine will boot from hard drive. However, if your machine is managed by Oracle VM Manager, the next time you restart the machine from Oracle VM Manager, the boot order settings defined in Oracle VM Manager will apply. Make sure that in Oracle VM Manager, the boot order for the recovered machine starts with hard drive.
[For Oracle Solaris on SPARC architecture] If you performed bare metal recovery with flexible mapping and the system rpool was not part of the restore scope, you must manually change the boot order to configure boot from hard drive.

Note

Veeam recovery environment starts in the machine RAM. Bare metal recovery logs are saved to the /var/log/veeam directory of the recovery system OS file system and to the repository that contains the backup file you used for data restore. If the repository does not support log export, you risk losing all bare metal recovery logs because local logs are lost on system reboot. We recommend saving them to a remote location or to the recovered file system for further reference.

To finish working with the wizard:

Reboot the machine.
Wait for the Oracle Solaris operating system to start.
Verify network settings. If necessary, reconfigure the network interface.
[For bare metal recovery with flexible mapping] If any of the non-system ZFS pools did not get imported after bare metal recovery, import such ZFS pools manually.
[Optional] If Veeam Agent on the original machine had integration with Veeam backup server, verify connection to the server by running the following command:

veeamconfig vbrserver resync

If the machine obtained a different ID after recovery, Veeam Agent may have a problem connecting to Veeam backup server. To fix the issue, use the following command:

veeamconfig vbrserver edit --password

Veeam Agent will prompt you to re-enter the password for the user account to connect to the backup server. After Veeam backup server confirms the password, the connection will be restored.