Duplication jobs end with a Status 83, read side failure.
When client names are specified using two different combinations of upper and lower case (for example, configurations containing both an all upper-case HOSTNAME as well as a lower-case hostname elsewhere), duplication jobs for that client may fail with status code 83 reported by bpdm. An additional error code of 2060018 may appear in the log as well (see below).
Note: This configuration can cause additional symptoms - see the related documents below.
The bpdm log may contain a message similar to the following:
04:02:58.652 [8732.5684] <32> bp_sts_open_image: sts_open_image failed: error 2060018
An enhancement has been filed (Etrack 2024375) to change NetBackup to be case insenstive when dealing with the hostname part of images.
Be consistent with case sensitivity when using client hostnames in NetBackup configuraiton.
If this workaround is unfeasible, please contact Symantec technical support, referencing this case and Etrack 2024362 (NetBackup 7.0) or 2149179 (NetBackup 7.0.1) to obtain an Emergency Engineering Binary (EEB) replacement library for this issue.
ETA of Fix:
Symantec acknowledges that the above mentioned issue (Etrack 2024375) is present in the current versions of the products mentioned at the end of this article. Symantec is committed to product quality and satisfied customers. This issue was scheduled to be addressed in the following release:
- NetBackup 7.1
Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
This issue affects NetBackup 7.0 and 7.0.1 on Windows systems.