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
About dissimilar system restore
A dissimilar system restore (DSR) restores a protected Windows client to a new system that has a different hardware configuration.
Note:
Changes in the hardware configuration may prevent clustered resources from going online after a restore. BMR does not attempt to adjust clustered resource attributes to account for a dissimilar system restore.
A DSR is useful in the following situations:
You change the preferred vendor for a class of systems in your enterprise.
You migrate an application from older hardware to the newer hardware.
Your system experiences critical hardware failure and similar hardware is not available for replacement.
Your disaster recovery provider does not have identical hardware to yours at the disaster recovery site.
You stage and verify an application at a test site with different hardware from the production site. (You can migrate the application from test to production.)
Use DSR when any of the following conditions apply:
The target system has a disk controller that the protected system does not have.
The target system has a network card that the protected system does not have.
The target system requires a different hardware abstraction layer (HAL) or kernel than the protected system.
The target system has different TCP/IP settings than the protected system has. (Only TCP/IP properties are restored. Other networking properties, such as Internetwork Packet Exchange (IPX), are not restored and must be configured after the restore.)