09-13-2011 10:30 PM
Hi,
Currently i have a Netbackup Server / Media server running version 6.5.5 and my Netbackup Client are running version 5.0GA? i have google around and hoping to find out that. Does it because the miss match of the version causing the slowness in restoration?
Thanks
09-13-2011 10:49 PM
You did not mention OS on media server or client?
Slow restore is normally caused by network card(s) set to auto-negotiate. Check media server as well as client.
A couple of TN's (some VERY old but still worth a read):
http://www.symantec.com/docs/TECH8003
09-13-2011 11:01 PM
Hi,
Thanks for the quick respond.
First of all ,Our environment are using media server with the current version NetBackup-HP-UX11.11 6.5.5 and my Client are using NetBackup-HP-UX11.11 5.0GA. Operating system for both servers are running HP-UX 11.11. I found that there is performance issue if using netbackup media server / server 6.0 with netbackup client 5.0GA . But i cant seem to find any documents to support on this issue between 6.5.5 server with 5.0GA client.
So far the network are using auto nego (currently running full duplex) with 1GB connection. We didnt see any errors or drop packet in the network interface. Nor of any errors in the Server Logs. Also any document on "Slow restore is normally caused by network card(s) set to auto-negotiate" will be nice. So that i can advice the to change the auto nego to full duplex
Any suggestion will be greatly appreciate. Thanks
09-13-2011 11:11 PM
Hi,
Yes ...right provide the details and along what is the type of backup ..is it file/folder backup or database or any thing alse
Check this guide which may help you to tune the performance of Master/Media or the client as required...
Here is the link:-
http://www.symantec.com/business/support/index?page=answerlink&url=http%3A%2F%2Fwww.symantec.com%2Fbusiness%2Fsupport%2Fresources%2Fsites%2FBUSINESS%2Fcontent%2Fstaging%2FTECHNICAL_SOLUTION%2F62000%2FTECH62317%2Fen_US%2F3.0%2F307083.pdf&answerid=16777217&searchid=1315979607682
Thanks.
09-13-2011 11:22 PM
In addition to above-mentioned TN's, please see this one for HP-UX:
http://www.symantec.com/docs/TECH15108
Although you are not seeing socket errors, it might be worth it to check TCP settings : http://www.symantec.com/docs/TECH7576
Any reason why such an old, usupported version of NBU is used on the client when newer, supported versions are available?
09-13-2011 11:26 PM
Hi,
have cheded the performance ....
If a restore takes an unusually long time ....
The media speed between the adapter and the switch or hub where it connects may not match.
Just for an example, ............
The media speed is set to 100 MB full duplex, but the restore slows down because the hub uses half duplex.
Change the media speed to match the hub speed or switch speed, or change the hub-switch setting to match that of the client.
And aslo you may want to check the ways for the reatore.
Here is a link that may help you where is says , how the restore happens in NBU..
http://www.symantec.com/docs/TECH34967
Thanks.
09-14-2011 01:09 AM
Hi,
All the network device and server network are configure full duplex and running on 1GB. Not errors are spotted. Possible that the slowness is due the netbackup version?
09-14-2011 04:29 AM
The problem is not really with different versions, but with old, outdated and bugged version of the unpatched client software.
Unpatched version of 5.0 probably had some 'shortcomings' or bugs. Finding documentation/proof will be close to impossible. Newer NBU versions contain lots of enhancements and bug fixes.
You can enable NBU logs to try and pinpoint where the bottleneck is - on client, you will need tar log folder. On media server, bptm folder. Look at the end of the restore for something like 'waited for empty buffers' or 'waited for full buffers'
Also test ouside of NBU - ftp a decent-sized file (+- 1 Gb) from the media server to the client.