Forum Discussion

Beavisrulz's avatar
Level 4
13 years ago

Duplications fail with media open error(83)

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;;MediaServer=khw2k046
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!


  • Back after a 3 week break (needed it!!) and just picking up on things.

    Just a thought on the difference between linking and renaming when this issues ocurr ....

    A link makes both upper and lower case versions valid where as a rename only makes one valid

    The case sensitivity only shows up when we duplicate or verify the back images - the trouble is that this will also apply to restoring them .. so if we use the link method then restores from when the client or policy was in one case will always work - if we rename we may find an issue in the future when we come to do restores from old backups.

    I haven't been in a position to test this but I would still prefer the link method just to be on the safe side as, after all, we only back things up in order to be able to restore them!

    Hope this gives more food for thought

21 Replies