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 external procedure error handling
By default, external procedures halt the restore process and await user action if the procedure returns a non-zero return code.
For UNIX and Linux restores, the following menu appears:
What do you want to do next? Choices are: a) Abort the restore. r) Retry the external procedure again. I) Ignore the error and continue the restore. s) Escape to shell prompt, return here when done.
If you retry, a prompt asks if you want to transfer the external procedure again from the BMR server before you run it. The prompt lets you edit the external procedure on the master server before you run it again.
Note:
When a UNIX first boot external procedure is started with no terminal defined and the procedure returns non-zero, the Bare Metal Restore process ends.
For Windows restores, a dialog box appears with the following choices:
halts the restore.
starts the external procedure again.
ignores the error and continues with the restore.
If you try again, a prompts asks if you want to transfer the external procedure again from the BMR server before you run it. The prompt lets you edit the external procedure on the master server before you run it again.