Forum Discussion

satpat's avatar
satpat
Level 3
11 years ago

Vmware backup failing with error code: 83

Hi all, Weekly-Full backup on vmware (Windows client) is failing with error code: Media Open error- 83 (Error pasted below); but the diff-incremental backup was completed successfully.  Looking f...
Backup and Recovery
NetBackup Appliance
Windows 8
  • Mark_Solutions's avatar
    Mark_Solutions
    11 years ago

    This may be a case sensitivity issue if at some point you changed the name of your schedule - see this tech note but you need to go a level or two deeper to see the schedule names:

    http://www.symantec.com/docs/TECH207194

    Otherwise it is getting overloaded and your disk pool is going up and down at full backup times in which case you should add /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO with a value of 800 in it to the Media servers and Master server (needs a service re-start to activate the setting)

    Hope this helps

SYMAJ's avatar
SYMAJ
Level 6
11 years ago

What versions are you running ??  If it is the 'case-sensitiviity' issue as Mark notes above (I have had this in the past) that one is fixed in 7506 / 253 as noted in the technote.  See excerpt from technote below:  

Starting with NetBackup 7.5.0.6 (appliance 2.5.3) and PureDisk 6.6.5 (appliance 1.4.4), writing to the deduplication database has been updated to fix the issue. The database writes are fixed so that a change in the case of the characters that are used for the NetBackup client name and policy do not cause a read of the backup images to fail. If you do not upgrade to these minimum versions, there is a possibility that you may encounter read errors with future backup images due to this issue.

AJ.