the Backup Manager does not respond to the request every few minutes at least, as
defined by the actionTimeoutMin, the action is considered “locked,” the Backup
Manager is told to terminate the job, and an error is reported.
If actions on your libraries or devices take longer than actionTimeoutMin, increase
the value. There are, however, some side effects. For example, when a medium is
not in the CAP, but the Backup Manager is instructed to load it, some Backup
Managers, such as Data Protector, wait for you to load media. The
actionTimeoutMin terminates this request and returns a CapEmpty error.
While the action is locked and waiting, that thread is not available to any other
request. When all threads are used, all requests wait until one of the other requests
is complete. If you increase actionTimeoutMin, it is recommended that you
increase your threading level as well.
Polling
<BackupManagerPollTimeFrame> is used to produce media reports during the
polling cycle. Based on this parameter value, full and incremental media reports are
requested by the backup manager. Running a Media Report for the entire timeframe
on the backup manager is time and resource consuming. By default, the parameter
is set to 150 hours, but you can reduced it when the DP RDS utilization is very high
or the media report takes too long to produce.
NOTE:
Do not set the parameter to zero unless you want to run media reports for the entire
timeframe.
The XML gateway uses the parameter to run media reports with optimized CPU
utilization on the DP cell manager. The value is not used while running media reports
during manual synchronization.
Logs
To change the logging level of XML Gateway:
Diagnostics and tuning160
To Next Page
Loading...
Need help?
General