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
External procedure logging examples
The following logs are created on the BMR master server during the restore process:
/usr/openv/netbackup/logs/bmrrst/client_name/log.mmddyy (UNIX) install_path\NetBackup\logs\bmrrst\client_name\log.mmddyy (Windows)
On UNIX and Linux systems, the BMR restore process writes external procedure begin and end messages to the logs. (On Windows systems, the BMR restore process does not perform begin and end logging.) You can use the bmrc command in your external procedure scripts to write messages to the logs also.
External procedures write messages when they start and finish. A message includes the date and time that the procedure began, the client name, and a description that includes the external procedure name. See the following examples:
2005/08/02 12:10:38.180 w2k200,sol157 INFO: Executing External Procedure: sol123,sol123_prerestore. 2005/08/02 12:10:38.350 w2k200,sol157 INFO: Completed executing External Procedure: sol123,sol123_prerestore.
You can use the bmrc command to write messages to the restore log. The following is an example of a bmrc command that writes a message during a restore of client sol123:
bmrc -operation create -resource message -client sol123 -msg " message text to log"
Alternatively, you can pipe data to the bmrc command, as in the following example:
echo "Hello World" | bmrc -operation create -resource log -client sol123
The following is the log entry from the previous command:
Restoration log start time: 2005/03/28 10:59:27 Hello World. Restoration log end time: 2005/03/28 10:59:27
When you start the bmrc command in an external procedure, specify the full path in the restore environment, as follows:
On UNIX and Linux clients:
/usr/openv/netbackup/bin
On Microsoft Windows clients:
%SystemDrive%\BMR\NBU\bin
At the first boot external procedure point, the path to the bmrc command is
install_path\NetBackup\bin
on Microsoft Windows clients.
For more information about the bmrc command, see the NetBackup Commands Reference Guide.