Video Screencast Help

Very bad behaviour and week behaviour with windows clients

Created: 21 Jan 2013 • Updated: 08 Feb 2013 | 3 comments
This issue has been solved. See solution.

Dear All , 

    I have something that makes me very very stock at 

I've a netbackup  and windows clients with nb client 6.5.5 which I'll upgrade soon but not now due to some limitation policies from the customer side , the problem is that the backup process is very slow at some clients eventhough now I have a new D2D appliance which works as VTL and it's supposed to be faster than the old Tape library LTO3 that was connected to the old master server 6.5.5 

the thing is that the transfer rate in some clients is very slow sometimes in KBs some times it's in MBs 

Note that the Windows is 2003 with all the clients , the only client with Windows 2008 server is very fast 

the network speed there is 1GB 


Something that I want to mention that sometimes when I look at the details for the backup process I can find that there are some files that it can't open some files so may be this has any effect however it used to happen as well in the old solution 

so I'd like to hear from any of you here suggestions and what do you think ? what are the possible solutions or work arounds or diganostics ?

Thanks in Advance :)

Discussion Filed Under:

Comments 3 CommentsJump to latest comment

Marianne's picture

TCP Chimney on W2003 clients is known for causing slow backups and/or status 24.
Please work with system owners to disable TCP Chimney on NIC properties. (Will post URL to TN a bit later.)
Symantec reccommends to leave this feature enabled on W2008.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Nicolai's picture

I think this is the tech note Marianne is talking about.

Network connectivity tuning to avoid network read/write failures and increase performance

I also found this :

Netbackup 7 running on Windows 2008 R2 platform may encounter slow performance

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Marianne's picture

Thanks Nicolai! TECH60844 explains how to disable TCP Chimney on W2003 to increase performance (personally seen it working great). Just work with system owners - NIC will be reset the moment the changes are applied.

TECH145791 says that it should be left enabled on W2008 clients.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links