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

[For bare metal recovery using flexible mapping] If rootvg was not in the scope of bare metal recovery, during next reboot, you must manually change the boot order to boot the system from hard drive.

Note

Also consider the following before you reboot the recovered system:

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.
[For bare metal recovery using automatic or manual disk mapping] If the system recovers successfully, at the next launch the machine will automatically boot from the hard drive.

To finish working with the wizard:

Reboot the machine.
Wait for the IBM AIX 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 volume groups did not get imported after bare metal recovery, import such volume groups 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 prompts you to re-enter the password for the backup server account. After Veeam backup server confirms the password, the connection will be restored.