Showing results for 
Search instead for 
Did you mean: 

Duplications fail with media open error(83)

Level 4

Hello, we're having random issues where a few duplications fail each day out of an easy hundred or so. Here's our current configuration:

- NetBackup on master, all media servers, and most clients

- NetBackup Disk Appliance 5020, set at production site and set at DR site, all running v1.4.1.1, and

- Master server running on Windows 2008 R2 SP1 64bit.  Media servers are Windows 2003 32bit.

We are backing up to our local production appliances and duplicating to the DR appliances. Several times a day, duplication jobs fail with the "media open error(83)" status message. It's appears to be the same client, dupe job runs and fails 4 times within a short period, then waits 10 hours and tries and fails again. Here is a copy of the backup status log:

6/12/2012 12:40:22 PM - requesting resource LCM_KMC_Pool_1_All
6/12/2012 12:40:22 PM - granted resource LCM_KMC_Pool_1_All
6/12/2012 12:40:22 PM - started process RUNCMD (8096)
6/12/2012 12:40:22 PM - requesting resource @aaaan
6/12/2012 12:40:22 PM - reserving resource @aaaan
6/12/2012 12:40:22 PM - reserved resource @aaaan
6/12/2012 12:40:22 PM - granted resource MediaID=@aaaan;DiskVolume=PureDiskVolume;DiskPool=KMC_Pool_1;Path=PureDiskVolume;StorageServer=khapb...
6/12/2012 12:40:23 PM - Info bpdm(pid=4356) started           
6/12/2012 12:40:23 PM - started process bpdm (4356)
6/12/2012 12:40:48 PM - Critical bpdm(pid=4356) get image properties failed: error 2060013: no more entries   
6/12/2012 12:40:48 PM - Error (pid=8096) ReplicationJob::Replicate: Replication failed for backup id khfsvs34_1339468206: media open error (83) 
6/12/2012 12:40:48 PMReplicate failed for backup id khfsvs34_1339468206 with status 83
6/12/2012 12:40:48 PM - end operation
media open error(83)


I've searched the forums and knowledgebase to no avail. Any ideas? Thanks!



Level 5
Partner Accredited Certified

Mark... Keep in mind I stated that I ran into a SIMILAR situation to what you were referring to, not the exact situation. In the case where the client appears multiple times with case issues I would agree linking is the safest way to go due to it's inderlying directory/file structure.

I was referring to an issue with the POLICY the client belongs to which is a subdirectory underneath the client did not match the case of the policy defined within NetBackup. This directory is a single instance where in your scenerio the client appears multiple times. This is easily corrected by renaming the policy directory to reflect the correct case.


Level 4

Hope the TN help's