NetBackup™ Logging Reference Guide
- Using logs
- About logging
- 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
- 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
- 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
OpenStorage Technology (OST) configuration and management
The OpenStorage Technology (OST) technology uses a plug-in architecture, similar to a software driver, that lets the third-party vendors direct the NetBackup data streams and metadata into their devices. The plug-in is developed and created by the OST partner and it resides on the media server for use by NetBackup. NetBackup depends on the OST plug-in for a path to the storage server.
Communication to the storage server is through the network; name resolution on the media server and the storage server must be configured correctly. All supported vendor plug-ins can communicate over a TCP/IP network and some can also communicate to the disk storage on a SAN network.
To determine the capabilities of a disk appliance, NetBackup uses the plug-in to query the storage appliance. The capabilities can include deduplicated storage, optimized off-host duplication, and synthetic backups.
Each OST vendor can report different log messages. A review of the bptm log and/or plug-in log for a backup or a restore job is the best way to understand the specific calls made to the storage server through the plug-in.
The basic steps include the following:
Claim the resource
sts open_server
Create the image
write
close
sts close_server
The example of calls in a vendor plug-in log are as follows:
2016-03-14 09:50:57 5484: --> stspi_claim 2016-03-14 09:50:57 5484: --> stspi_open_server 2016-03-14 09:50:57 5484: <-- stspi_write_image SUCCESS 2016-03-14 09:50:57 5484: --> stspi_close_image 2016-03-14 09:50:59 5484: <-- stspi_close_server SUCCESS
To display the plug-in version, use the following commands:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/bpstsinfo -pi
Windows: install dir\netbackup\bin\admincmd\bpstsinfo -pi
To test the basic communication to the storage server, use the following commands:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/bpstsinfo -li -storage_server storage server name -stype OST_TYPE
Windows: install dir\netbackup\bin\admincmd\bpstsinfo -li -storage_server storage server name -stype OST_TYPE
To display the configured storage servers, use the following commands:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/nbdevquery -liststs -stype OST_TYPE -U
Windows: install dir\netbackup\bin\admincmd\nbdevquery -liststs -stype OST_TYPE -U
To show the configured disk pools, use the following commands:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/nbdevquery -listdp -stype OST_TYPE -U
Windows: install dir\netbackup\bin\admincmd\nbdevquery -listdp -stype OST_TYPE -U
To show the configured disk volumes, use the following commands:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype OST_TYPE -U
Windows: install dir\netbackup\bin\admincmd\nbdevquery -listdv -stype OST_TYPE -U
Review the flags in the diskpool information, for example:
CopyExtents - supports optimized duplications
OptimizedImage - supports optimized synthetics and accelerator
ReplicationSource - supports AIR (replication)
ReplicationTarget - supports AIR (imports)
After the initial configuration of the diskpools, you must run the nbdevconfig -updatedp command as follows to recognize any new flag that the vendor added:
UNIX/Linux: /usr/openv/netbackup/bin/admincmd/nbdevconfig -updatedp -stype OST_TYPE -dp diskpool -M master
Windows: install dir\netbackup\bin\admincmd\nbdevconfig -updatedp -stype OST_TYPE -dp diskpool -M master
To manually add the supported flags, you can use the following commands:
nbdevconfig -changests -storage_server storage server name -stype OST_TYPE -setattribute OptimizedImage
nbdevconfig -changedp -stype OST_TYPE -dp diskpool name -setattribute OptimizedImage
You should also review the following flag for the storage server:
OptimizedImage - supports accelerator
To list the OpenStorage credentials for all of the media servers, use the following commands:
UNIX/Linux: /usr/openv/volmgr/bin/tpconfig -dsh -all_hosts
Windows: install dir\volmgr\bin\tpconfig -dsh -all_hosts