Veritas NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Recovering the master server when root is intact
The following procedure recovers the master server by reloading the operating system, restoring NetBackup, and then restoring all other files.
To recover the master server when root is intact
- Verify that the operating system works, that any require patches are installed, and that specific configuration settings are made. Take corrective action as needed.
- Reinstall NetBackup software on the server you want to recover.
See the NetBackup Installation Guide for instructions:
- Install any NetBackup patches that had been previously installed. See the documentation that was included with the patch software.
Note:
Veritas does not support the recovery of a catalog image that was backed up using an earlier version of NetBackup.
- If any of the default catalog directories have changed that may be reflected in the NetBackup catalog backups, recreate those directories before the catalog recovery.
The following are examples:
Use of symbolic links as part of the NetBackup catalog directory structure.
Use of the NetBackup nbdb_move command to relocate parts of the NetBackup relational database catalog.
If the recovery scenario involves restoring policy or catalog backups, the appropriate recovery device(s) must be configured, which may involve the following tasks:
Install and configure the robotic software for the devices that read backups of the NetBackup catalog and regular backups of the disk being restored. If a non-robotic drive is available that can read these backups, then no robot is required. Although manual intervention is required if multiple pieces of media are required.
See the NetBackup Device Configuration Guide:
Use the NetBackup Device Configuration Wizard to discover and configure the recovery device in NetBackup.
See the NetBackup Administrator's Guide, Volume I:
Use the NetBackup tpautoconf command to discover and configure the recovery device in NetBackup.
See the NetBackup Commands Reference Guide:
Update the device mapping files.
See the NetBackup Administrator's Guide, Volume I:
- If you must restore from the policy backups or catalog backups that were done to media, the appropriate media may have to be configured in NetBackup
See the NetBackup Administrator's Guide, Volume I:
http://www.veritas.com/docs/DOC5332
Configuring the media may require some or all of the following tasks:
Manually load the required media into a standalone recovery device.
Use the NetBackup utilities such as robtest or vendor-specific robotic control software to load media into the required recovery device or devices.
Use the NetBackup Volume Configuration Wizard to inventory the media contents of a robotic device.
Use the vendor-specific robotic control software to load the media into the required recovery device(s).
- Recover the NetBackup catalogs.
The NetBackup catalogs can be recovered only to the same directory structure from which they were backed up (alternate path recovery is not allowed).
- Stop and restart all NetBackup daemons. Use the following NetBackup commands, or use the Activity Monitor in the NetBackup Administration Console.
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
- Start the NetBackup Backup, Archive, and Restore interface (or the bp command) and restore other files to the server as desired. When the files are restored, you are done.