Forum Discussion

Level 4

13 years ago

Solved

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 7.1.0.3 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 6.6.3.49048

- 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=khapbak001.ketthealth.com;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!

Mark_Solutions
12 years ago
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

SAF
Level 3
13 years ago
Beavisrulz,

Some times this error happens when somebody move (manually) the image files from its location and when the duplication job looks for them fails with the error: get image properties failed: error 2060013: no more entries

I dont know if you checked these links so I put them just in case:

http://www.symantec.com/business/support/index?page=content&id=TECH53336

http://www.symantec.com/business/support/index?page=content&id=TECH153873

You could also have a look of some others helpfull post in this community, like this one:

https://www-secure.symantec.com/connect/forums/pddo-duplications-using-slp-failing-error-84-media-write-error

Let me know your comments.
Mark_Solutions
Level 6
13 years ago
I have also seen this when an image has been corrupted (glitch in the system somewhere)

In that case you have no choice but "loose" that backup

You would need to cancel that backup id from the SLP to prevent it being duplicated (nbstlutil cancel .... -backupid ***)

You can then expire it via the Catalog Section

Not a great solution but stops it constantly failing if that is all it will ever do.

You could try duplicting it manually once cancelled from the SLP but that depends if you are using Opt De-Dupe or AIR for replication (guessing you are using AIR in which case you could not do such a duplication)

Hope this helps
Beavisrulz
Level 4
13 years ago
Yeah, I've canceled them before, but just don't understand why I get them on a daily basis. It just started happened more frequently over the past few weeks and we have not changed anything.

I will keep an eye on it some more and see if it's coming from the same client, media server, etc.

Thanks!
Mark_Solutions
Level 6
13 years ago
OK - keep an eye on the All Log Entries report - maybe you disk pools are going Up and Down or similar and something needs tuning or repairing

You may also want to check for errors on the 5020's (/Storage/log; /Storage/log/spoold/storaged.log; /Storage/log/pdwfe.log; /Storage/log/agent.log and /Storage/tmp/workflow.xxx)

Hope this helps
RVellore
Level 2
13 years ago
run this command on the master server: /usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -force then run a cleanup job /usr/openv/netbackup/bin/admincmd/bpimage -cleanup -allclients
RVellore
Level 2
13 years ago
Sorry ERROR 83
SAF
Level 3
13 years ago
Any update on this case?
Beavisrulz
Level 4
13 years ago
We still do have them occasionally, but it's dropped down a little. I did receive one last night.

We had to apply an EEB to our production appliances to fix an issue with the content router crashing, and I'm planning on applying 1.4.2 early next week. We are then scheduled to upgrade NetBackup to 7.5 either Thursday or the following week.

I will update the thread with more info once we get to that point and see if the issue still exists.

Thanks!
AV-IT
Level 3
13 years ago
Hi,

Any uodates on this case? Has it been been resolved with 7.5?
zafar1907
Level 3
13 years ago
Hi,

BUG REPORT: SLP duplication fails with read failed, media open error (83).

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH160733