03-05-2013 02:55 AM
Hi,
I have been encountering some issues with backups within a netbackup 7.5.0.4 environment. The topology is
1 x Master server 7.5.0.4 - RHEL 6.3 (virtualised)
2 x Symantec 5220 2.5.1 appliances (media servers)
2 x Symantec 5020 1.4.3.1 appliances (single storage pool)
The issues encountered (failed backups with status 87, 83) are not always isolated to the same clients; the client log below shows the errors.
<FQDN-CLIENT> is windows 2008 R2
03-17-2013 09:11 AM
Seems nobody has encountered this before...
Probably best to log a support call?
03-19-2013 05:49 AM
When you do client side de-dupe the client needs to properly resolve the appliances and each node of a 5020 SPA
Make sure your clients can resolve the appliances and the appliances can resolve the clients as they communicate directly with each other when doing client side de-dupe
Use hosts files if needs be
Also check on the client under its ost-plugins directory in case it has gathered false media server name due to incoreectly resolving an appliance
Hope this helps
06-10-2013 07:50 PM
I am also getting this error
9/06/2013 9:19:53 AM - Critical bptm(pid=8352) sts_close_handle failed: 2060019 error occurred on network socket
9/06/2013 9:19:53 AM - Critical bptm(pid=8352) cannot write image to disk, media close failed with status 2060019
Did you get this resolved? Im using Windows 2008R2 7.5.0.5 Master/media and a Windows 2008R2 7.5.0.5 Client. This is its first backup and server is about 1.5TB backed up via Lan.
Simon
06-13-2013 08:44 AM
Also along with what Mark suggested.
You don't mention if you are doing client side dedupe or weather these are writing to the 5220 or the 5020.
With the 5220 there are known performance issues at 2.5.1 that is resolved in 2.5.2 that may be causing this issue. This would mean you would need to patch your master to 7.5.0.5 also.
http://www.symantec.com/docs/TECH145136
this technote lists a few patches you will want to apply once you install 2.5.2.
http://www.symantec.com/docs/TECH178334
as well as the 7.5.0.5 late breaking news page for downloads and patches.
I would suspect though with those errors that you are hitting the performance issue with 2.5.1.
If you have any further questions please ask
Thanks