Although documented, but not commonly known, it is possible to use the regular Data Protector backup scheduler to enable debugging. This allows for a more surgical approach to debugging so that debugs do not have to be turned on for all backups. If there is a specific backup job which is problematic, the schedule file can be edited so that if the problematic backup runs at an inconvenient time or is intermittent debugs will be generated. The basic syntax is as follows:
-debug 1-200 sch.txt <------------ Add debug statement
-full
-only 2010
-day 14 -month Dec
-at 22:00
This information is documented in the Data Protector Troubleshooting Guide