Managing deduplication 83
Monitoring deduplication activity
Monitoring deduplication processes
The following are the deduplication processes about which NetBackup reports:
■NetBackup Deduplication Engine in the Administration Activity Monitor Services tab on Windows systems. On UNIX, the NetBackup Deduplication Engine appears as spoold on the Daemons tab.
■NetBackup Deduplication Manager in the Activity Monitor Services tab on Windows systems. On UNIX, the NetBackup Deduplication Manager appears as spad on the Daemons tab.
■The database processes (postgres) appear in the ActivityMonitor Processes tab on Windows systems.
■The NetBackup bpps command shows the spoold, spad, and postgres processes.
See “Deduplication server components” on page 109.
Monitoring deduplication logs
The NetBackup deduplication components write information to various log files. The following subsections describe the log files for each component.
Deduplication configuration script log
The log file is in the storage_path/log/spoold directory. The log file name is
NetBackup creates this log file during the configuration process. If your configuration through the wizard 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 log
The NetBackup Deduplication Engine writes several log files, as follows:
■VxUL log files for the events and errors that NetBackup receives from polling. See “About VxUL logs” on page 86.
■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.
