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
Saving custom files on UNIX or Linux
The following information applies only to UNIX and Linux clients.
Usually, NetBackup restores client files as the last step in the restore process. You can specify custom files on the client so they are available in the temporary operating system environment on the client during the restore process.
For example, a specific device driver configuration from a protected client is required in the temporary operating system. You can specify those device driver files so they are included in the restore environment.
Custom files are saved as part of the client's configuration. Specify the custom files in the following text file on the client:
/usr/openv/netbackup/baremetal/client/data/ClientCustomFiles
Specify one custom file per line, using the full path name to the file. Use a pound sign (#) as the first character of comment lines.
After custom files are saved (when the client is backed up), they are copied to the SRT. They are available during the restore when you enable the SRT for exclusive use. More information is available on how to enable the SRT.
When you specify a custom file, it does not remove it from backups. Custom files are also backed up by NetBackup and then restored when NetBackup restores the client files. (They are backed up and restored if the files or their directories are included in the backup directives of the policy.)
More Information