Optimized Duplication fails with status 191

Problem

Optimized Duplication ("optdup") fails with status 191 on NetBackup 10.1. The issue possibly affects other Open Storage (OST) plug-ins.

Error Message

The bpdm log from the media server reports:

Sep 27, 2022 7:13:48 AM - Critical bpdm (pid=10964) image copy failed: totalbytesCopied = 0, image size = 8192
Sep 27, 2022 7:13:54 AM - Error bpduplicate (pid=9512) host mymedia.mydomain.com backup id client.mydomain.com_1664278181 optimized duplication failed, media write error (84).
Sep 27, 2022 7:13:54 AM - Error bpduplicate (pid=9512) Duplicate of backupid client.mydomain.com_1664278181 failed, media write error (84).

Cause

A regression occurred in NetBackup 10.1 which affects the ExaGrid Open Storage (OST) plug-in and possibly other OST plug-ins. There is an issue regarding the difference between copying NetBackup catalog header file (HDR) fragment data using the function sts_copy_extent vs. writing data using sts_write_image.

The following vendor plug-ins have been tested with NetBackup 10.1 and are not affected by this issue. Plug-ins not listed do not necessarily exhibit the issue; rather, it may indicate they have not been tested.

• MSDP
• DataDomain
• HPE
• Quantum

Solution

Apply the Emergency Engineering Binary (EEB) 4092071, which will force the ExaGrid plug-in to use sts_copy_extent to copy the HDR from the source to the target copy. By using sts_copy_extent, the target copy inherits the source copy values for the HDR fields, which may not match the correct values for the target copy.

For non-ExaGrid plug-ins which exhibit this same problem, apply EEB 4092071 as it also introduces a configuration file for media servers that can be used to force sts_copy_extent to be used.

• On UNIX: /usr/openv/netbackup/bin/OPTDUP_WRITE_COPY_HDR
• On Windows: %NB_INSTALL_DIR%\NetBackup\bin\OPTDUP_WRITE_COPY_HDR

The file contents should be a single integer: '0' (zero) in the file means: copy the HDR; '1' (one) in the file means: write the HDR. Writing the HDR results in the unique, correct values for the target copy. Use '0' if the plug-in cannot support write to a target copy.

Incorrect values in the target copy HDR file usually will not cause problems. For example, retention for the target copy is stored in the NetBackup catalog by different means during the duplication itself. The only situation where an incorrect HDR will cause problems is if the target copy is imported using the bpimport command. As bpimport will use the values in the HDR to re-create the NetBackup catalog entry for the copy.

Veritas Technologies LLC is aware of the issue mentioned in this article. Veritas is committed to product quality and will look to include the fix covered by EEB 4092071 in a future release.