NetBackup™ Logging Reference Guide
- Using logs
- About logging
- Logging properties
- Logging levels
- Log retention and log size
- Changing the logging levels
- About unified logging
- Gathering unified logs for NetBackup
- Types of unified logging messages
- File name format for unified logging
- Originator IDs for the entities that use unified logging
- About changing the location of unified log files
- About rolling over unified log files
- About recycling unified log files
- About using the vxlogview command to view unified logs
- Examples of using vxlogview to view unified logs
- Examples of using vxlogmgr to manage unified logs
- Examples of using vxlogcfg to configure unified logs
- Accessibility of the unified logs
- About legacy logging
- UNIX client processes that use legacy logging
- PC client processes that use legacy logging
- File name format for legacy logging
- Directory names for legacy debug logs for servers
- Directory names for legacy debug logs for media and device management
- How to control the amount of information written to legacy logging files
- Limit the size and retention of legacy logs
- Accessibility of the legacy logs
- Setting retention limits for logs on clients
- UNIX logging with syslogd
- Logging options with the Windows Event Viewer
- Backup process and logging
- Media and device processes and logging
- Restore process and logging
- Advanced backup and restore features
- Storage logging
- NetBackup Deduplication logging
- OpenStorage Technology (OST) logging
- Storage lifecycle policy (SLP) and Auto Image Replication (A.I.R.) logging
- NetBackup secure communication logging
- About NetBackup secure communication logging
- Tomcat logging
- NetBackup web services logging
- Command-line logging
- NetBackup cURL logging
- Java logging
- Embeddable Authentication Client (EAT) logging
- Authentication Services (AT) logging
- vssat logging
- NetBackup proxy helper logging
- NetBackup proxy tunnel logging
- PBX logging
- Sending secure communication logs to Veritas Technical Support
- Snapshot technologies
- Locating logs
- Overview of NetBackup log locations and processes
- acsssi logging
- bpbackup logging
- bpbkar logging
- bpbrm logging
- bpcd logging
- bpcompatd logging
- bpdbm logging
- bpjobd logging
- bprd logging
- bprdproxy logging
- bprestore logging
- bptestnetconn logging
- bptm logging
- daemon logging
- ltid logging
- nbemm logging
- nbjm logging
- nbpem logging
- nbproxy logging
- nbrb logging
- NetBackup Vault logging
- NetBackup web services logging
- NetBackup web server certificate logging
- PBX logging
- reqlib logging
- Robots logging
- tar logging
- txxd and txxcd logging
- vnetd logging
- NetBackup Administration Console logging
- NetBackup Administration Console logging process flow
- Enabling detailed debug logging for the NetBackup Administration Console
- Setting up a secure channel between the NetBackup Administration Console and bpjava-*
- Setting up a secure channel between the NetBackup Administration Console and either nbsl or nbvault
- NetBackup Administration Console logging configuration on NetBackup servers and clients
- Logging Java operations for the NetBackup Remote Administration Console
- Configuring and gathering logs when troubleshooting NetBackup Administration Console issues
- Undo logging
- Using the Logging Assistant
Hot catalog restore
You can start a catalog restore with the option or with the bprecover command. More information is available in the "Disaster Recovery" chapter of the NetBackup Troubleshooting Guide.
Note:
Before you run a hot catalog restore in a disaster recovery situation, the identity of the primary server should be recovered either by the disaster recovery installation or the nbhostidentity -import -infile drpkg.path command. Once the identity is recovered, the hot catalog recovery can be completed as usual.
Figure: Catalog restore and recovery illustrates the catalog restore and recovery process.
A restore of the NetBackup database from a hot catalog backup consists of the following steps (in the order presented):
The NetBackup catalog image and configuration files are restored.
The NBDB database is restored to:
/usr/openv/db/staging (UNIX) install_path\NetBackupDB\staging (Windows)
NBDB is recovered.
The NBDB database is moved from the staging directory to the target location. This location is set by the VXDBMS_NB_DATA setting. (In the bp.conf file on UNIX and by the corresponding registry key on Windows.) The default location is /usr/openv/db/data and install_path\NetBackupDB\data.
If the database is relocated, it is moved from the staging directory to the directory that is indicated in
vxdbms.conf./usr/openv/db/data/vxdbms.conf (UNIX)
install_path\NetBackupDB\data\vxdbms.conf (Windows)