09-30-2013 06:48 AM
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 forward to get a solution for this.
09/30/2013 13:23:38 - Critical bptm (pid=31092) image open failed: error 2060029: authorization failure
09/30/2013 13:23:38 - Info bptm (pid=31092) EXITING with status 83 <----------
09/30/2013 13:23:42 - Info bpbkar (pid=0) done
09/30/2013 13:23:42 - Info bpbkar (pid=0) done. status: 83: media open error
09/30/2013 13:23:42 - end writing
media open error (83).
Solved! Go to Solution.
10-01-2013 07:33 AM
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
10-01-2013 12:27 AM
All,
Even today,diff-inc backup is completed successfully & Weekly-Full backup is still failling.
Can any one help me on this.
10-01-2013 07:33 AM
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
10-02-2013 03:35 AM
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.
11-01-2013 05:37 AM
I have also noticed that when upgrading to 2.5.3 it seems to re-set all of the keep alive setting to poor values
It is worth checking those if Full backups get affected - what you want to see is the following:
# cat /proc/sys/net/ipv4/tcp_keepalive_time
510
# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
3
# cat /proc/sys/net/ipv4/tcp_keepalive_probes
3
11-03-2013 06:31 AM