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
- 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
- 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
Accessibility of the unified logs
NetBackup sets the permissions on the unified log directories to a restrictive but configurable level. This change is designed to prevent unauthorized access to the NetBackup logs, which may contain sensitive information.
You can change the default log file permissions to make them less restrictive. Use the vxlogcfg command to change the log file or folder permissions. You can change the permissions of a specific Originator ID (OID) or you can change the default permissions that applies to all the OIDs. For folder permissions, the Default.LogFilePermissions is considered.
The folder and file permissions do not change instantly after running the vxlogcfg command. If you want to apply the permissions immediately, restart the NetBackup services. For more information on restarting the services, see this article. The file and folder permissions are applied during the next log rollover cycle that depends on the length of the logs and the configured log file sizes. The maximum rollover period is one day. So, in this case, the new permissions reflects after one day afer changing the file permissions. The permissions of existing log files in the system are not changed.
Here are some examples for changing the default log permissions:
These two example commands change file permissions to 644 for all the components. The folder gets additional execute permissions (755).
/usr/openv/netbackup/bin/vxlogcfg -a --prodid 51216 -o ALL -s LogFilePermissions=644
/usr/openv/netbackup/bin/vxlogcfg -a --prodid 51216 -o ALL -s DynaReloadInSec=120
To change the permissions for any originator ID, use the following example command:
/usr/openv/netbackup/bin/vxlogcfg -a --prodid 51216 --orgid 111 -s LogFilePermissions=644
This command applies the 644 permission to the originator ID 111, which represents
nbemm. For all other componentorgid,refer to/usr/openv/netbackup/nblog.conf.Note:
By default, the parameter Default.LogFilePermissions from the
nblog.conffile is followed for all folder permissions. When you use OID specific permissions, <OID>.LogFilePermissions parameters are used.To change permissions for a PBX log in the
icsul.conffile, use the following example command:/usr/openv/netbackup/bin/vxlogcfg -a --prodid 50936 -o 103 -s LogFilePermissions=644
If you want to apply the permissions immediately, restart the PBX services. For more information on restarting the services, see this article.