Veritas NetBackup™ Troubleshooting Guide
- 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 and Windows
This procedure assumes that all disk partitions in Windows are lost.
To recover the master server and Windows
Install a minimal Windows operating system (perform the Express install).
Install the same type and version of Windows software that was used previously.
Install Windows in the same partition that was used before the failure.
Install any required patches. Take corrective action as needed.
Specify the default workgroup. Do not restore the domain.
Install and configure special drivers or other software that is required to get the hardware operational (for example, a special driver for the disk drive).
Install SCSI or other drivers as needed to communicate with the tape drives on the system.
Follow any hardware manufacturer's instructions that apply, such as loading SSD on a Compaq system.
Restart the system when Windows installation is complete.
- Determine the install_path in which NetBackup is installed. By default, NetBackup is installed in the C:\Program Files\VERITAS directory.
- Determine if any directory paths or locations need to be created for NetBackup catalog recovery.
- If necessary, partition any disks being recovered as they were before the failure. Then reformat each partition as it was before the failure.
- Reinstall NetBackup software on the server being recovered. Do not configure any NetBackup policies or devices at this time.
For the NetBackup Web Services, you must use the same user account and credentials that were used when you backed up the NetBackup catalog. More information is available:
- Install any NetBackup patches that had been previously installed. See the documentation that was included with the patch software.
- If the catalog directories differ from those in the NetBackup catalog backups, recreate that directory structure on disk before you recover the catalog. For example, use 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 or devices have to be configured.
You may have to do all or some of 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.
Use the NetBackup command tpautoconf to discover and configure the recovery device in NetBackup.
See the NetBackup Commands Reference Guide manual:
Update the device mapping files.
- 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.
When you configure the media, you may have to do some or all of the following:
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 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 devices.
- Recover the NetBackup catalogs.
- When catalog recovery is complete, stop and restart the NetBackup services. Use the following bpdown and bpup commands, the Activity Monitor in the NetBackup Administration Console, or the Services application in the Windows Control Panel.
In step 12, do not restore files to the install_path\NetBackup\db, install_path\NetBackupDB, install_path\NetBackup\var, or install_path\Volmgr\database directories. These directories were recovered in step 10 and overwriting them with regular backups leaves the catalogs in an inconsistent state. If the relational database files were relocated using nbdb_move from install_path\NetBackupDB\data, they are recovered in step 10 and should not be restored in step 12.
To restore all other files, do the following steps in the order presented:
Start the NetBackup Administration interface on the master server.
Start the Backup, Archive, and Restore client interface.
Browse for restores and select only the partitions that were lost. Select the system directory (typically C:\Windows), which ensures that all registry files are restored.
Deselect the install_path\NetBackup\db, install_path\NetBackupDB (or relocated NetBackup relational database path), install_path\NetBackup\var, or install_path\Volmgr\database directories.
See the caution in this procedure.
If you reinstall Windows, select the Overwrite existing files option, which ensures that existing files are replaced with the backups.
Start the restore.
- Restart the system, which replaces any files that were busy during the restore. When the boot process is complete, the system is restored to the state it was in at the time of the last backup.