About deduplication logs

The NetBackup deduplication components write information to various log files.

More information about the log files is available.

Deduplication configuration script log

The following is the path name of the log file for the deduplication configuration script:

  • UNIX: storage_path/log/pdde-config.log

  • Windows: storage_path\log\pdde-config.log

NetBackup creates this log file during the configuration process. If your configuration succeeded, you do not need to examine the log file. The only reason to look at the log file is if the configuration failed. If the configuration process failed after it created and populated the storage directory, this log file identifies when the configuration failed.

NetBackup Deduplication Engine logs

The NetBackup Deduplication Engine writes several log files, as follows:

  • Log files in the storage_path/log/spoold directory, as follows:

    • The spoold.log file is the main log file

    • The storaged.log file is for queue processing.

    • A log file for each connection to the engine is stored in a directory structure. The following describes the pathname to a log file for a connection:

      IP address/application/TaskName/FirstDigitofSessionID/sessionID-current_time_in_seconds.log

      For example, the following is an example of a crcontrol connection log pathname on a UNIX system:


    Usually, the only reason to examine these connection log files is if a Symantec support representative asks you to.

  • A VxUL log file for the events and errors that NetBackup receives from polling. The originator ID for the deduplication engine is 364.

    See About VxUL logs.

NetBackup Deduplication Manager logs

The log files are in the /storage_path/log/spad directory.

  • spad.log

  • sched_GarbageCollection.log

  • sched_QueueProcess.log

  • SchedClass.log

You can set the log level and retention period in the Change Storage Server dialog box Properties tab.

See Changing deduplication storage server properties.

Deduplication database log

The deduplication database log file (postgresql.log) is in the storage_path/databases/pddb directory.

You can configure log parameters. For more information, see the following:


The default configuration for the PostgreSQL database does not add timestamps to log entries on Windows systems. Therefore, Symantec recommends that you edit the configuration file on Windows hosts so timestamps are added to the log file.

To configure log file timestamps on Windows

  1. Use a text edit to open the following file:


    The database path may be the same as the configured storage path.

  2. In the line that begins with log_line_prefix, change the value from %%t to %t. (That is, remove one of the percent signs (%).)

  3. Save the file.

  4. Run the following command:

    install_path\Veritas\pdde\pddb\bin\pg_ctl reload -D dbpath\databases\pddb\data

    If the command output does not include server signaled, use Windows Computer Management to restart the PostgreSQL Server 8.3 service.

PureDisk plug-in log

You can configure the location and name of the log file and the logging level. To do so, edit the DEBUGLOG entry and the LOGLEVEL in the pd.conf file.

See the NetBackup Deduplication Guide.

Client deduplication proxy plug-in log

The client deduplication proxy plug-in on the media server runs under bptm, bpstsinfo, and bpbrm processes. Examine the log files for those processes for proxy plug-in activity. The strings proxy or ProxyServer embedded in the log messages identify proxy server activity.

They write log files to the following directories:

  • For bptm:

    UNIX: /usr/openv/netbackup/logs/bptm

    Windows: install_path\Veritas\NetBackup\logs\bptm

  • For bpstsinfo:

    Windows: /usr/openv/netbackup/logs/admin

    UNIX: /usr/openv/netbackup/logs/bpstsinfo

    Windows: install_path\Veritas\NetBackup\logs\admin

    Windows: install_path\Veritas\NetBackup\logs\stsinfo

  • For bpbrm:

    UNIX: /usr/openv/netbackup/logs/bpbrm

    Windows: install_path\Veritas\NetBackup\logs\bpbrm

Client deduplication proxy server log

The deduplication proxy server nbostpxy on the client writes messages to files in an eponymous directory, as follows:

UNIX: /usr/openv/netbackup/logs/nbostpxy

Windows: install_path\Veritas\NetBackup\logs\nbostpxy.

About VxUL logs

Some NetBackup commands or processes write messages to their own log files. Other processes use Veritas unified log (VxUL) files. VxUL uses a standardized name and file format for log files. An originator ID (OID) identifies the process that writes the log messages.

Table: NetBackup VxUL logs shows the NetBackup logs for disk-related activity.

The messages that begin with a sts_ prefix relate to the interaction with the storage vendor software plug-in. Most interaction occurs on the NetBackup media servers.

To view and manage VxUL log files, you must use NetBackup log commands. For information about how to use and manage logs on NetBackup servers, see the NetBackup Troubleshooting Guide.

Table: NetBackup VxUL logs



Processes that use the ID

NetBackup Deduplication Engine


The NetBackup Deduplication Engine that runs on the deduplication storage server.

Backups and restores


Messages appear in the log files for the following processes:

  • The bpbrm backup and restore manager

  • The bpdbm database manager

  • The bpdm disk manager

  • The bptm tape manager for I/O operations

Backups and restores


The nbjm Job Manager.

Device configuration and monitoring


The nbemm process.

Device configuration and monitoring


The Disk Service Manager process that runs in the Enterprise Media Manager (EMM) process.

Device configuration and monitoring


The storage server interface process that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.

Device configuration and monitoring


The Remote Disk Service Manager interface (RDSM) that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.