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
About NetBackup catalog recovery and symbolic links
When you recover the NetBackup catalog, you must account for any symbolic links in the NetBackup catalog directory structure, as follows:
| If the NetBackup |
| If any of the client subdirectories under the |
Catalog recovery of clustered master server | To recover the NetBackup catalog from a clustered master server to a single master server at a disaster recovery site, you must create the following symbolic links on the recovery host before you recover the catalog: /usr/openv/netbackup/db -> /opt/VRTSnbu/netbackup/db /usr/openv/db/staging -> /opt/VRTSnbu/db/staging On Solaris systems only, you also must create the following symbolic links before you recover the catalog: /usr/openv -> /opt/openv |
If the symbolic links and their targets do not exist, catalog recovery fails.