Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
- Introducing Bare Metal Restore
- Configuring BMR
- Protecting clients
- Setting up restore environments
- Shared resource trees
- Pre-requisites for Shared Resource Tree
- Creating a shared resource tree
- Managing shared resource trees
- Adding software to a shared resource tree
- Importing a shared resource tree
- Copying a shared resource tree
- Deleting a shared resource tree
- Managing boot media
- Restoring clients
- BMR disk recovery behavior
- About restoring BMR clients using network boot
- About restoring BMR clients using media boot
- About restoring to a specific point in time
- About restoring to dissimilar disks
- Restoring to a dissimilar system
- About restoring NetBackup media servers
- About external procedures
- About external procedure environment variables
- About SAN (storage area network) support
- About multiple network interface support
- Managing Windows drivers packages
- Managing clients and configurations
- Client configuration properties
- Managing BMR boot servers
- Troubleshooting
- Troubleshooting issues regarding creation of virtual machine from client backup
- A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
- Creating virtual machine from client backup
- Virtual machine creation from backup
- Monitoring Bare Metal Restore Activity
- Appendix A. NetBackup BMR related appendices
- Network services configurations on BMR boot Server
- BMR client recovery to other NetBackup Domain using Auto Image Replication
First boot after BMR restore fails on UNIX platforms
After BMR restore, first boot may fail at Grub if root disk that is originally mirrored across two disks is changed to concatenate layout. In the system setup, root disk was mirrored across 2 disks say c3t0d0 and c4t0d0. In BIOS settings, c3t0d0 is the first disk in boot sequence. During DDR configuration, root disk is changed from mirror to concatenate and mapped on c4t0d0. In BIOS, this disk is the second disk in boot sequence. So, after BMR restore, when system boots for the first time, as c3t0d0 is the first disk in boot sequence AND as "grub signature is still present on this disk as it was mirrored earlier", system tries to boot from the grub on c3t0d0 and then fails to boot as it does not get root file system and other bootable files which are now on c4t0d0.
After BMR restore, during system boot, change the BIOS settings and choose the correct disk for system to boot.