About the Logging properties

Article:HOWTO13891  |  Created: 2008-01-20  |  Updated: 2009-01-31  |  Article URL http://www.symantec.com/docs/HOWTO13891
Article Type
How To

Product(s)

Environment


About the Logging properties

The Logging properties apply to the master servers, media servers, and clients that are currently selected. The available properties differ between master servers, media servers, and clients.

The Logging properties contain the processes that continue to use legacy logging as well as processes that use unified logging.

Unified logging

Unified logging creates log file names and messages in a format that is standardized across Symantec products. Some NetBackup processes on the server use unified logging.

Unified logging writes the logs into the following locations:

  • UNIX: /usr/openv/logs

  • Windows: install_path\NetBackup\logs

Note:
Do not save logs to a remote file system such as NFS or CIFS. Logs that are stored remotely and then grow large can cause critical performance issues.

Unlike legacy logging, administrators to not need to create subdirectories for the logs before unified logging can occur.

To control the size and number of unified logs, use the vxlogcfg command and the vxlogmgr command.

Legacy logging

For those processes that use legacy logging, administrators must first create a log directory for each process to be logged. A logging level selection on the Logging properties page does not enable logging.

Create the NetBackup legacy log directories in the following locations:

  • UNIX: /usr/openv/netbackup/logs/process_name

  • Windows: install_path\NetBackup\logs\process_name

Note:
Do not save logs to a remote file system such as NFS or CIFS. Logs that are stored remotely and then grow large can cause critical performance issues.

On a Windows server, you can create all of the NetBackup debug log directories at one time by double-clicking mklogdir.bat in the following directory:

install_path\NetBackup\logs\

Create the Media Manager legacy log directories in the following locations:

  • UNIX: /usr/openv/volmgr/debug

  • Windows: install_path\Volmgr\debug


For details on both unified and legacy logging, see the NetBackup Troubleshooting Guide.

Figure: Logging dialog box

Logging dialog box

The Logging properties can contain the following options:

Enable robust logging

A check in the Enable robust logging check box indicates that when a log file grows to the maximum size, the log file is closed. When the log file is closed, a new log file is opened. If the new log file causes the maximum number of log files in the directory to be exceeded, the oldest log file is deleted.

See the NetBackup Troubleshooting Guide for more information about controlling the log file size.

If this property is enabled, the following processes produce log files:

  • bprd

  • bpbkar

  • bpbrm

  • bpcd

  • bpdbm

  • bptm

  • bpdm

The logs are named using the following convention:

MMDDYY_NNNNN.log

where NNNNN is an incrementing counter from 00001 - 99999

If the Enable robust logging property is disabled, a single log file is produced each day:

MMDDYY.log

Whether Enable robust logging is selected or not, the log file is pruned by using KEEP_LOGS_DAYS and DAYS_TO_KEEP_LOGS settings.

Note:
If a NetBackup environment uses scripts depending on the MMDDYY.log naming convention, either update the scripts or disable Robust Logging.

Global logging level

This property is used for debugging purposes. The logging levels control the amount of information that the NetBackup server writes to logs. Six levels are supported. A value of 0 sets logging to minimum (default) and a value of 5 sets it to maximum.

Note:
Use the default setting of 0 unless advised otherwise by Symantec Technical Support. Other settings can cause the logs to accumulate large amounts of information.

Some NetBackup processes allow individual control over the amount of information the process writes to logs. For those processes, specify a different logging level other than the Global logging level.

Process specific overrides

To override the Global logging level property for any of the following services, select a different logging level. Select from between 0 (minimum) through 5 (maximum).

The services within this section use legacy logging:

  • BPBRM logging level

  • BPTM logging level

  • BPDM logging level

  • BPDBM logging level

  • Vault logging level

    Select a logging level for bpvault.

  • BPRD logging level

These services require that you first create a log directory in the following location:

  • UNIX: /usr/openv/netbackup/logs/process_name

  • Windows: install_path\NetBackup\logs\process_name

Debug logging levels for NetBackup services

The Logging properties page offers configurable debug levels for the services that use unified logging.

Each service creates a log automatically in the following directories:

  • UNIX: /usr/openv/logs

  • Windows: install_path\NetBackup\logs

To override the Global logging level property for any of the following services, select a different logging level. Select from between 0 (minimum) through 5 (maximum). To retain no logging information, select No logging for the service.

You can also use the vxlogcfg command to change debug levels.

See the NetBackup Troubleshooting Guide for more information.

The following services use unified logging:

  • Policy Execution Manager

    This property appears for EMM servers. The Policy Execution Manager (NBPEM) compiles a worklist for jobs and determines when jobs are due to run. This property does not appear for NetBackup hosts earlier than 6.0.

  • Job Manager

    This property appears for EMM servers. The Job Manager (NBJM) accepts the jobs that the Policy Execution Manager submits and acquires the necessary resources. This property does not appear for NetBackup hosts earlier than 6.0.

  • Resource Broker

    The Resource Broker (NBRB) makes the allocations for storage units, tape drives, client reservations. This property does not appears for NetBackup hosts earlier than 6.0.



Legacy ID



314790


Article URL http://www.symantec.com/docs/HOWTO13891


Terms of use for this information are found in Legal Notices