Problem
When the SLP window closes with a non standard SIZE_DATA_BUFFERS setting, it causes a block size mismatch upon the duplication. The result is a status 157 on the initial duplication, status 174 on the subsequent duplications followed by status 191's. The copy two of the image will need to be expired so the duplication can be retried.
Error Message
Upon Initial duplication status 157 will occur:
18:00:14.377 [8496.10056] dupreadline: read: EXIT STATUS 157
18:00:14.377 [8496.10056] wait_for_statuses: Received read status: 0, 157, 0, 0, 0, 0
18:00:14.377 [8496.10056] bpduplicate: bpduplicate sent EXIT STATUS acknowledgement to reader, status: 0, err: 0
18:00:16.936 [8496.10056] dupreadline: read: EXIT STATUS 157
18:00:16.936 [8496.10056] wait_for_statuses: Received write status: 0, 157, 0
18:00:16.936 [8496.10056] wait_for_statuses: bpduplicate sent EXIT STATUS acknowledgement to writer, status: 0, err: 0
18:00:16.936 [8496.10056] set_job_details: Tfile (232322): LOG 1415671216 16 bpduplicate 8496 host CLIENTNAME backup id CLIENTNAME_1415441553 read failed, suspend requested by administrator (157).
Subsequent jobs will fail with status 191, and status 174 in bptm
Cause
bpduplicate is mishandling the block size
Solution
SLP processing of affected images can be halted and the suspended copies resumed by using the command:
bpexpdate -backupid <backup_id_value> -d 0 -copy <copy_number> -force_not_complete.
This command will remove the duplication copy and further SLP processing of the image will cease.
The following work arounds can then be used:
1) Use the default block size.
2) Use the default 24x7 SLP window.
3) Put in the NOSHMDUP touch file in place
*NOTE* This touch file will disable the use of shared memory during duplication. This may cause slowness during the duplication process
Veritas Corporation has acknowledged that the above-mentioned issue (ETrack 3606030) is present in the current version(s) of the product(s) mentioned in this article. Veritas Corporation is committed to product quality and satisfied customers. This issue was scheduled to be addressed in the following release(s):
NetBackup 7.7
When released, please visit this link for download and README information:
https://www.veritas.com/support/en_US/15143.html (for NetBackup Enterprise Server)
https://www.veritas.com/support/en_US/58991.html (for NetBackup Appliances)
Please note that Veritas 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. Veritas'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.
Applies To
NBU 7.6
1. SLP windows configured
2. Target duplication device is tape or AdvancedDisk.
3. The data buffer size has been set in /usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS.
Related Knowledge Base Articles
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.