ProblemUnder affected NetBackup/NetBackup Appliances versions, long delays have been seen between the time the bptm buffer statistics were reported and the process reported its exit status. During this time, MSDP is finalizing the changes to the refDBs that were impacted by the backup or replication job. Delays as long as 3000 seconds and higher have been seen on multiple types of backups which include VMware, MS-Windows, Standard, among others. The delays were noticed more often on backup policies that also use Accelerator. When Accelerator is not enabled, fewer refDBs are changed and the overall performance of the commits is improved, but the overall problem is not eliminated.
Similarly, slow replication performance can be observed due to each replicated backupid requiring numerous updates to refdb. These delays would occur between backupids in a replication job and would be viewed as 'slow' or poor replication performance.
These delays will keep allocations for writing or reading the disk pool alive for much longer periods than are necessary. This can create problems in getting backup or replication jobs completed in a timely way. Status code 196 failures may also be registered against other jobs waiting to use the same disk pool.
Efforts have been made improve the performance of these refDB commits. A currently available EEB provides improvements to spoold that helps improve the overall time to commit refDBs in MSDP, lowering the overall time between the report buffer stats in bptm, and the final exit status message.
This issue affects NetBackup 7.6.1 and above (including NetBackup Appliances 2.6.1 and above). It is resolved in NetBackup Appliance version 3.0 and NetBackup version 8.0
Error MessageThe bptm process will report buffer stats prior to reporting the final Exit Status message at the end of the job. For example, the Job Detail Status tab in Activity Monitor might report a line similar to the following:
02/11/2016 01:06:36 - Info bptm(pid=168334) waited for full buffer 13 times\
There is then a delay before the final bptm "EXITING with status 0" message is reported. For example:
02/11/2016 01:27:59 - Info bptm(pid=168334) EXITING with status 0 <----------
In this example, a total of 21 minutes, 23 seconds have passed between the time the bptm buffer statistics were reported and the process reported its exit status.
CauseInefficiencies in making commits to the changed refDBs created long delays in getting the job to finally complete. These are improved with the installation of an EEB.
SolutionVeritas Technologies LLC has acknowledged the the above-mentioned issue (Etrack 3857680) is present in the current version(s) of the product(s) mentioned in this article. Veritas is committed to product quality and satisfied customers. This issue was scheduled to be included in a future version of the product(s).
When these versions are available, please access the following links for download and README information:
NetBackup Appliances: http://www.veritas.com/support/en_US/58991.html
For NetBackup Appliances 22.214.171.124, 2.7.2 or 2.7.3, please download and apply the hotfix which can by accessing the Download Attachments link. Instructions for installing hotfixes on an Appliance can be found by accessing the linked Related Article.
For NetBackup 7.7.3, please contact Veritas technical support, referencing this document ID and Etrack 3891282 to obtain an Emergency Engineering Binary (EEB) containing a resolution for this issue.
For NetBackup 7.7.2, please contact Veritas technical support, referencing this document and Etrack 3869080 to obtain an EEB containing a resolution for this issue.
For NetBackup 126.96.36.199, please contact Veritas technical support, referencing this document ID and Etrack 3862695 to obtain an EEB containing a resolution for this issue.
For other Appliance versions or NetBackup versions not listed, please contact Veritas technical support, referencing this document and Etrack 3857680 to determine EEB availability or next steps.
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):