Troubleshooting

Debugging

 

Debugging

 

You should collect debugs only when the support organization requires

 

them to resolve a technical issue. When Data Protector runs in debug

 

mode, it creates debug information that consumes a large amount of disk

 

space. Consult the support organization about the detail level that

 

should be applied and environmental conditions for running Data

 

Protector in the debug mode.

 

Limiting the Maximum Size of Debugs

Circular

Data Protector can run in a special debugging mode called circular

Debugging

debugging. In this mode, debugging messages are added until the size of

 

the debug file reaches a preset size (n). The counter is then reset and the

 

oldest debugging messages are overwritten. This limits the trace file

 

size, but does not affect the latest records.

When to Use

Using this mode is recommended only if the problem occurs near the end

Circular

of the session or if Data Protector aborts or finishes soon after the

Debugging

problem has occurred.

Estimating the With circular debugging turned on, an estimate of the maximum

Required Disk required disk space is as follows:

Space

On Media Agent client(s): 2*n [kB] for each running MA in a backup or restore.

On Disk Agent client(s): 2*n [kB] for each mount point in a backup or restore.

On the Cell Manager client: 2*n [kB].

On a integration client: 2*n [kB] * parallelism.

For Inet and CRS debugging, the upper limit cannot be reliably determined, because separate debug traces are produced for various actions.

Chapter 12

553

Page 583
Image 583
HP B6960-90078 manual Debugging, Limiting the Maximum Size of Debugs