BUG REPORT: A differential incremental backup to a NetApp NearStore storage unit running Data Ontap version 7.

2 fails with a NetBackup Status Code 83 (media open error) even though there is a synthetic full backup image available.

Error
status code 83: media open error

Solution
Bug ID: ETrack 918477 - A differential incremental fails with status 83 after expiring a full backup for NearStore storage unit. Symptom(s): A differential incremental backup to a NetApp NearStore storage unit running Data Ontap version 7.2 fails with a NetBackup Status Code 83 (media open error) even though there is a synthetic full backup image available. As outlined in the System Administrator Guides (see links below under related documents), "A synthetic full...backup is a backup assembled from one previous, traditional (non-synthesized) full backup, and subsequent differential backups and/or a cumulative incremental backup." Log Files: In the bpdm log file, the following message is observed.
11:31:50.661 [16175] <2> f3020: entering stspi_create_image(4) 11:31:50.663 [16175] <16> f3020: checkSend: Message reply error: 23 11:31:50.663 [16175] <16> f3020: cannot create an incr image without a full image 11:31:50.663 [16175] <32> bp_sts_open_image: sts_create_image failed: error 42 11:31:50.663 [16175] <2> set_job_details: Sending Tfile jobid (1064) 11:31:50.663 [16175] <2> set_job_details: LOG 1165977110 32 bpdm 16175 Cannot create an incremental image with out a preceding full image 11:31:50.663 [16175] <2> set_job_details: Done 11:31:50.663 [16175] <2> db_error_add_to_file: dberrorq.c:midnite = 1165935600 11:31:50.673 [16175] <32> bp_sts_open_image: Cannot create an incremental image with out a preceding full image 11:31:50.673 [16175] <2> set_job_details: Sending Tfile jobid (1064) 11:31:50.673 [16175] <2> set_job_details: LOG 1165977110 32 bpdm 16175 bp_sts_open_image failed: error 42 11:31:50.674 [16175] <2> set_job_details: Done 11:31:50.674 [16175] <2> db_error_add_to_file: dberrorq.c:midnite = 1165935600 11:31:50.685 [16175] <32> io_open_disk: bp_sts_open_image failed: error 42 11:31:50.686 [16175] <2> bpdm: EXITING with status 83

Workaround:

If this issue is encountered, contact Symantec Enterprise Technical Support with this TechNote number (286875) and Etrack number (918477) and request assistance with a workaround. ETA of Fix: Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers. This issue is currently being considered by Symantec Corporation to be addressed in a forthcoming Maintenance Pack or version of the product. The fix for this issue is expected to be released in the 2nd quarter of 2007. 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. Please refer to the maintenance pack readme or contact NetBackup Enterprise Support to confirm this issue (ET918477) was included in the maintenance pack. As future maintenance packs are released, please visit the following link for download and readme information: http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143

STATUS CODE 83: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error).

Error
media open error

Solution
Overview: When attempting a backup which goes to a NAS server, the backup fails with a NetBackup Status Code 83 (media open error). Troubleshooting: Please review the TechNote on Status Code 83 in the Related Documents section, and confirm that is not the issue. Then, check the NetBackup Client Service, and see what Windows account is starting the service. Log files: N/A

Resolution: If the backup is going to a network location on a NAS server, the NetBackup Client Service needs to start with an account that has access to the network. The local system account does not have access to the network (see Figure 1). Figure 1

Changed the NetBackup Client Server to start with an account with network privileges, and stop and restart the service (see Figure 2).

Figure 2

Problem
STATUS CODE 83: SAN Client backups fail reporting status 83 (media open error).

Solution
Overview: SAN Client backups fail reporting status 83. The FAT pipe services (originator id 199) log will report errors opening the FAT pipe as follows:
07/25/08 07:16:12.938 [FTServerMgr_i::openPipe] FTServerMgr_i::openPipe received for pipe 1 07/25/08 07:16:12.939 [FTServerMgr_i::openPipe] FTServerMgr_i::openPipe called with invalid bufferSegmentSize 1048576

Resolution:

The FT media server uses the SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS settings to set the size and number of buffers for setting up FT Pipes if not overridden by their respective *_FT counterparts. The rules for setting these values are as follows: SIZE_DATA_BUFFERS must be a multiple of 1024 with a value from 65536 to 524288. SIZE_DATA_BUFFERS_FT can be used for overriding SIZE_DATA_BUFFERS for FT jobs. For a Fibre Transport Media server, Symantec's recommendation is not to exceed 262144 for SIZE_DATA_BUFFERS_FT

NUMBER_DATA_BUFFERS must be an integer with a value from 4 to 32. NUMBER_DATA_BUFFERS_FT can be used for overriding NUMBER_DATA_BUFFERS for FT jobs. For a Fibre Transport Media server, Symantec's recommendation is not to exceed 16 in general. Also, if the FT media server is Linux, the value of (number of FT pipes * NUMBER_DATA_BUFFERS_FT) should not exceed 161. Please see the related documents section to learn more about NetBackup's buffer settings and how to tune them. .

Problem
STATUS CODE 83: Backups to disk storage units on NFS mounted file systems may hang or fail with a NetBackup Status Code 83 (media open error) on NetBackup 6.5 media servers.

Error
media open error

Solution
Overview: If a disk storage unit of the type BasicDisk or AdvancedDisk is configured on a NFS mounted file system on media server, backups to it may hang or fail with status 83. The bptm process on NetBackup 6.5 media servers try to use file locking while accessing the NFS volume. The job either hangs or fails immediately with NetBackup Error Code 83 - media open error. Though this issue was discovered for NFS mounted file systems from Data Domain filers, it can happen for NFS mounted file systems from any NFS servers if the NFS client is configured to send file lock requests to NFS server.

NetBackup 6.5 ensures data integrity for disk images by making use of file locks. When an NFS mounted file system is used, file lock and unlock requests are handled either by sending the requests to NFS server or by managing it locally. NFS clients configured not to manage file locks locally tend to have performance issues but ensures data integrity across all clients accessing the same NFS file system. Since BasicDisk and AdvancedDisk type disk storage units are dedicated for one media server, a file system used by one storage unit will not be used by another media server. Hence it is safe to use to enforce locking locally. Please note that NetBackup administrator should carefully examine disk storage units of the type BasicDisk and AdvancedDisk to ensure that no two storage units share the same NFS mounted file system. Troubleshooting: Enable the bptm log file on the media server. Log files: The bptm log file on the media server shows the following messages (please note that the messages in bold are not present if the backups are hanging):
14:32:49.923 [5350] <2> db_logschedrec: s_fast_recovery: 0 14:32:49.923 [5350] <2> db_logschedrec: unused_window: open=0, duration=0 14:32:49.923 [5350] <2> read_schedlist_x2: found 3 14:32:49.923 [5350] <4> write_disk_header: Data Classification & Storage Lifecycle action 8 14:32:49.923 [5350] <2> duct: entering stspi_create_image(4) 14:32:51.036 [5350] <16> duct: STSImageManager: Caught exception in STSIMGImageManager::CreateImage, FILE=STSIMGImageInfo.cpp, FUNCTION=, LINE=904, ERROR=STS_ESYS 14:32:51.037 [5350] <32> bp_sts_open_image: sts_create_image failed: error 2060017 14:32:51.040 [5350] <2> set_job_details: Sending Tfile jobid (112019) 14:32:51.040 [5350] <2> set_job_details: LOG 1190831571 32 bptm 5350 image open failed: error 2060017: system call failed 14:32:51.040 [5350] <2> set_job_details: Done 14:32:51.040 [5350] <2> db_error_add_to_file: dberrorq.c:midnite = 1190779200 14:32:51.075 [5350] <32> write_disk_header: image open failed: error 2060017: 14:32:51.101 [5350] <2> duct: STSImageManager: open() failed on image file /var/local/dd400/backup/netbackup/ImageBasename_1190831559_C1_F1.1190831559.i nfo (No such file or directory) 14:32:51.101 [5350] <2> delete_image_disk_sts: file ImageBasename_1190831559_C1_F1 does not exist

Resolution: Please mount the NFS volumes using the following syntax for the disk storage units and re-run the backups to the disk storage unit.
mount -o llock <NFS-Server>:<file-system-path> /<mount point>

Additional note: On HP-UX 11.11 systems patch PHNE_34293 or later is needed to use local locks. On 11.23 systems the patch required is PHNE_33099 or later.

Problem
STATUS CODE 83: After upgrading to NetBackup 6.0, backups to a disk storage unit fail with a NetBackup Status Code 83 (media open error).

Error
media open error

Solution
Overview: After upgrading to NetBackup 6.0, backups to a disk storage unit (DSU) that point to a mapped drive no longer work. Troubleshooting: Enable the bpdm log file on the media server. Log files: The bpdm log file shows the following messages:
15:06:04.031 [4116.1732] <32> path_on_root: failed to get mount point for Z:\ (2) 15:06:04.031 [4116.1732] <2> set_job_details: Sending Tfile jobid (38) 15:06:04.031 [4116.1732] <2> set_job_details: LOG 1186344364 32 bpdm 4116 invalid storage unit path 15:06:04.031 [4116.1732] <2> set_job_details: Done 15:06:04.031 [4116.1732] <2> db_error_add_to_file: dberrorq.c:midnite = 1186290000 15:06:04.031 [4116.1732] <32> do_get_lsu_info: invalid storage unit path 15:06:04.031 [4116.1732] <2> set_job_details: Sending Tfile jobid (38) 15:06:04.031 [4116.1732] <2> set_job_details: LOG 1186344364 32 bpdm 4116 Invalid STS storage device: Z:\

Resolution: As indicated in the NetBackup 6.0 Release Notes (see Related Documents below), on page 35, DSU location no longer support mapped drives. In order to use previously mapped drives, specify the universal naming convention (UNC) location of the share.