Veritas NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- About troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting installation problems
- Troubleshooting configuration problems
- Device configuration problem resolution
- Testing the master server and clients
- Testing the media server and clients
- Resolving network communication problems with UNIX clients
- Resolving network communication problems with Windows clients
- Troubleshooting vnetd proxy connections
- vnetd proxy connection requirements
- Where to begin to troubleshoot vnetd proxy connections
- Verify that the vnetd process and proxies are active
- Verify that the host connections are proxied
- Test the vnetd proxy connections
- Examine the log files of the connecting and accepting processes
- Viewing the vnetd proxy log files
- Troubleshooting security certificate revocation
- How a host's CRL affects certificate revocation troubleshooting
- NetBackup job fails because of revoked certificate
- NetBackup job fails because of apparent network error
- NetBackup job fails because of unavailable resource
- Master server security certificate is revoked
- Determining a NetBackup host's certificate state
- About troubleshooting networks and host names
- Verifying host name and service entries in NetBackup
- Example of host name and service entries on UNIX master server and client
- Example of host name and service entries on UNIX master server and media server
- Example of host name and service entries on UNIX PC clients
- Example of host name and service entries on UNIX server that connects to multiple networks
- About the bpclntcmd utility
- Using the Host Properties window to access configuration settings
- Resolving full disk problems
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Troubleshooting problems with the NetBackup web server certificate
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Troubleshooting network interface card performance
- About SERVER entries in the bp.conf file
- About unavailable storage unit problems
- Resolving a NetBackup Administration operations failure on Windows
- Resolving garbled text displayed in NetBackup Administration Console on a UNIX computer
- Using NetBackup utilities
- About NetBackup troubleshooting utilities
- About the analysis utilities for NetBackup debug logs
- About network troubleshooting utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the NetBackup consistency check repair (NBCCR) utility
- About the nbcplogs utility
- About the robotic test utilities
- Disaster recovery
- About disaster recovery
- About disaster recovery requirements
- Disaster recovery packages
- About disaster recovery settings
- Recommended backup practices
- 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
- Generating a certificate on a clustered master server after disaster recovery installation
- About restoring disaster recovery package
- Restoring disaster recovery package on Windows
- Restoring disaster recovery package on UNIX
- About recovering the NetBackup catalog
- About NetBackup catalog recovery on Windows computers
- About NetBackup catalog recovery from disk devices
- About NetBackup catalog recovery and symbolic links
- About NetBackup catalog recovery and OpsCenter
- NetBackup disaster recovery email example
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
- Recovering the NetBackup catalog when NetBackup Access Control is configured
- Recovering the NetBackup catalog from a nonprimary copy of a catalog backup
- Recovering the NetBackup catalog without the disaster recovery file
- Recovering a NetBackup user-directed online catalog backup from the command line
- Restoring files from a NetBackup online catalog backup
- Unfreezing the NetBackup online catalog recovery media
- Steps to carry out when you see exit status 5988 during catalog recovery
Recovering the NetBackup relational database files from staging
During a catalog backup, NetBackup copies the relational database files to the staging directory. The recovery option that restores the image files and the configuration files also restores the relational database files to the staging directory.
See About recovering the NetBackup catalog image files.
You can recover the NetBackup NBDB relational database files from the staging directory. You can also use NetBackup commands process the NBDB relational database files further.
See About processing the relational database in staging.
When the relational database is recovered from staging, NetBackup also applies the current online transaction log during the recovery. Applying the transaction log ensures that the database is as consistent as possible with the currentdb/images directory.
Two recovery procedures from the staging directory exist, as follow:
The database is not corrupted | See “To recover relational database files from staging if the database is corrupted”. |
The database is corrupted | See “To recover relational database files from staging if the database is corrupted”. |
To recover relational database files from staging if the database is not corrupted
- Run the following command on the master server to recover NBDB from staging:
UNIX: /usr/openv/netbackup/bin/nbdb_restore -dbn NBDB -recover -staging
Windows: install_path\NetBackup\bin\nbdb_restore -dbn NBDB -recover -staging
- Stop and restart NetBackup, as follows:
UNIX:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
To recover relational database files from staging if the database is corrupted
- If the NetBackup services are running, stop them as follows:
UNIX: /usr/openv/netbackup/bin/bp.kill_all
Windows: install_path\NetBackup\bin\bpdown
- Move the
*.dband*.logfiles from the following database file directories to a temporary directory:UNIX:
/usr/openv/db/dataWindows:
C:\Program Files\Veritas\NetBackupDB\data - Configure SQL Anywhere so that it does not try to start automatically when the host is started, as follows:
Linux: /usr/openv/db/bin/nbdb_admin -auto_start NONE
Windows: install_path\NetBackup\bin\nbdb_admin -auto_start NONE
- Start the SQL Anywhere server, as follows:
UNIX: /usr/openv/netbackup/bin/nbdbms_start_stop start
Windows: install_path\NetBackup\bin\bpup -e SQLANYs_VERITAS_NB
- Create an empty database, as follows:
UNIX: /usr/openv/db/bin/create_nbdb -drop
Windows: install_path\NetBackup\bin\create_nbdb -drop
- Stop and restart NetBackup, as follows:
UNIX and Linux:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
- Run the NetBackup tpext command to update the device mapping files, as follows:
UNIX: /usr/openv/volmgr/bin/tpext -loadEMM
Windows: install_path\Volmgr\bin\tpext -loadEMM
- If you used the nbdb_move command to relocate NetBackup database files, re-create the directories where the files were located when you backed up the catalog.
- Start the NetBackup Device Manager, as follows:
UNIX: /usr/openv/volmgr/bin/ltid -v
Windows: Start the device manager service.
- Run the following command on the master server to recover NBDB from staging:
UNIX: /usr/openv/netbackup/bin/nbdb_restore -dbn NBDB -recover -staging
Windows: install_path\NetBackup\bin\nbdb_restore -dbn NBDB -recover -staging
- Stop and restart NetBackup, as follows:
UNIX:
/usr/openv/netbackup/bin/bp.kill_all /usr/openv/netbackup/bin/bp.start_all
Windows:
install_path\NetBackup\bin\bpdown install_path\NetBackup\bin\bpup
- After the services are restarted, run the following command:
On a non-clustered setup:
Windows:
install_path\netbackup\bin\nbcertcmd -renewcertificate
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -renewcertificate
On a clustered setup:
Windows:
install_path\netbackup\bin\nbcertcmd -renewcertificate -cluster
UNIX:
/usr/openv/netbackup/bin/nbcertcmd -renewcertificate -cluster
If the command fails with the exist status 5988, refer to the following topic:
See Steps to carry out when you see exit status 5988 during catalog recovery.