OpenStorage Technology (OST) backup logging
In this scenario, the client backs up the data directly to the media server and the media server accesses the vendor plug-in to transfer the data to the storage server.
For logging that is specific to OST, enable the following on the media server or plug-in host:
In the registry or
bp.conffile, set VERBOSE = 5.Ensure that the following directories exist under
/usr/openv/netbackup/logs(for Windows, useinstall_path\NetBackup\logs):bptmbpbrmbpstsinfo
Create the
volmgr/debug/tpcommanddirectory.Put VERBOSE in the
vm.conffile.Set DebugLevel=6 and DiagnosticLevel=6 for the following processes:
OID 178 (Disk Manager Service, dsm)
OID 202 (Storage service, stssvc)
OID 220 (Disk Polling Service, dps)
OID 221 (Media Performance Monitor Service)
OID 222 (Remote Monitoring & Management Service)
OID 230 (Remote Disk Manager Service, rdsm)
OID 395 (STS Event Manager, stsem)
These OIDs all log to the
nbrmmsunified log file on the media server.Increase the vendor plug-in logging. Most vendors have their own plug-in logging in addition to what is logged within the NetBackup logs.
Reproduce the backup failure.
Within the NetBackup Administration Console, click on , open the job details and click the Detailed Status tab. It displays the media server host name that ran the backup and the bptm process ID number (PID).
Find a line similar to bptm(pid=value); this value is the bptm PID to locate in the bptm log.
Extract the bptm PID found in step 8 from the bptm log on the media server. This step gathers only the single-line entries; review the raw logs to see the multi-line log entries. In the following examples, 3144 is the bptm PID:
Windows command line:
findstr "\[3144." 092611.log > bptmpid3144.txt
UNIX/Linux command line:
grep "\[3144\]" log.092611 > bptmpid3144.txt
Gather the vendor specific plug-in logs that cover the dates from when the backup started and when it failed.