Sometimes collecting Data Protector debugs can be challenging because of the disk space required where the debugs are written to. There are several strategies that can assist with managing this:
1) The debugs can be redirected to an alternate volume/directory by setting OB2DBGDIR=<desired destination path> in the omnirc file.
2) The debug range can be adjusted to collect only the debug range required to analyze the problem. Example:
OB2DBG=199-231 debugs.txt
Note that using this method requires highly advanced knowledge of what ranges report what information.
3) Debugs can be enabled only for the Data Protector Processes that are being examined. Example:
OB2DBG=1-331,333-500 debugs.txt BMA
This option will only generate debugs for the BMA (Backup Media Agent Process).
4) Debugs can be compressed on the fly by specifying the following syntax:
OB2DBG=1-331,333-500,gz debugs.txt
Note the "gz" appendage onto the debug range. This will produce a debug file that is created in gzip format.
All of the above strategies can be combined to further tune and minimize the size of the DP debugs. These are considered advanced topics for debugging. I strongly recommend that if you are interested in using these features that you speak with Data Protector Support Consultant for assistance.