Please enter search query.
Search <book_title>...
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
Last Published:
2019-02-18
Product(s):
NetBackup & Alta Data Protection (8.1)
- 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
- 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
If the boot server has a base installation of Solaris 10 update 11, the creation of SRTs can fail
If the boot server has a base installation of Solaris 10 update 11, the creation of Bare Metal Restore (BMR) shared resource trees (SRTs) that have a lower OS update can fail due to a kernel patch ID check. The issue occurs because Solaris 10 update 11 has a kernel patch ID that is lower than the ID for previous Solaris 10 updates.
Workaround: Update the kernel patch on the Solaris 10 update 11 BMR boot server. You can update the kernel by applying any of the provided kernel bug fix patches from Oracle Solaris. The kernel bug fix patches to Solaris 10 update 11 correct this issue by modifying the patch number to be higher than the other patches.