Looks like a pretty standard disconnect according to the bpbkar logs:

I'd start with disabling TCP chimney/offload as a start
http://www.symantec.com/docs/TECH60844

Hi Amaan,

> Does IP address resolve from hostname in all parties?  

> Does NBU master/media server able to connect on the client?  (Host Properties > Clients > (find host)

Thanks

Thanks Martin,

I will go through each and every one of these TNs. Will try and share the results.

Some of your questions has been answered in the main thread. Will answer others later.

I went throug all above mentioned TNs. none of them helped. opened case with Symantec. working on that. will keep you updated.

I just had another look at your opening post:

NIC details: Media server: 100MBs Full / Client: 1GBs Full.

You need a 1GB NIC in the media server as a minimum!

Aman,

Hmm, one of the above normally fixes it ... Marianne has a good point, 100M NIC on media server is madness.

The case should have be opened with the operating system vendor - not Symantec - Status 24 are network / operating system related.  I am unsure why Symantec are expected to solve non NetBackup issues ...

When troubleshooting a problem, it makes sense to get those on board who have the best information / experience with the problem, in the case of network issues, and in particular Status 24, as mentioned already, this is very unlikely to be NetBackup.  In fact, I don't think I have every seen a status 24 caused by NetBackup personally ...   Therefore, the most likely cause of the issue will be the Network or Operating system, hence the suggestion to log the call with those who are 'responsible' for the 'part' most likely causing the problem.

Martin

I agree with you Marianne, when i saw this issue first time i thought the same as you, but after posting this i didnt get anything like that from our experts, so decided that i may be wrong

in this case i will try to change client to Full 100MBS and will see if the backup ends successfully.

thanks!

I see a major issue with media server with 100BaseT NIC. How old is this media server if it has a NIC that old? My last 3 laptops (replaced every 3 years) all had 1 GB NIC's. Which poses the question - how old is the firmware on the NIC? How old is the driver?

Why not motivate for a 1 GB NIC? Or even better - if Data Protection is important to Business - a new media server.

I found that compression is enabled on the same drive (E:\). is this could cause the issue. if the compression is enabled how netbackup gets the files. does it get them compressed or it will uncompress them first and then sent it to storage?

When compress in policy attribute checked(say Client Compress feature), compression take part in client host. Client process read data, compress it, and sent it to media server. Media Server just recieve it, and store it into storage. No additional operation take place in Media server.
Uncompression will take place in client host when you restore data.

You do not have 'file read errors'. As can be seen in bpbkar log, you have 'socket write error':

Exception of type [SocketWriteException]
 > tar_tfi::processException:
An Exception of type [SocketWriteException] has occured at:
  Module: @(#) $Source: src/ncf/tfi/lib/TransporterRemote.cpp,v $ $Revision: 1.51 $ , Function: TransporterRemote::write[2](), Line: 307
  Module: @(#) $Source: src/ncf/tfi/lib/Packer.cpp,v $ $Revision: 1.85 $ , Function: Packer::getBuffer(), Line: 659
  Module: tar_tfi::getBuffer, Function: H:\701\src\cl\clientpc\util\tar_tfi.cpp, Line: 296
  Local Address: [0.0.0.0]:0
  Remote Address: [0.0.0.0]:0
  OS Error: 10054 (An existing connection was forcibly closed by the remote host.)

You will need bpbrm log on media server as well.

I have seen similar errors resolved when NIC in media server was replaced.