hi Vamsi,

1) are you getting these failurss every day same time?

2) what is happening if you re-trigger the jobs some other time?

3)  are they regular failurs ?

4) are you taking the backup of all local drives?

and also please provide the bptm , bpbrm and bpbkar logs 

What is NBU version on the clients? 

Please show us all the text in Details tab of one of the failed jobs.

Please post clients' bpbkar logs as File attachments. (rename to bpbkar.txt)

Nagalla, :

Please find the answers below :

1) are you getting these failurss every day same time?

• Schedule Backups are failing daily

2) what is happening if you re-trigger the jobs some other time?

• Yes after re triggering also teh backups are failing with same error.

3)  are they regular failurs ?

• Yes Failing daily

4) are you taking the backup of all local drives?

• All Local Drives

and also please provide the bptm , bpbrm and bpbkar logs 

Hi

Usually an error 50 occurs when the backup of a client is busy running and the media server doing the backup and or client being backup is rebooted or has shutdown. Any such issues in your environment?

hi Vamsi

see the below errors for acn043vieapp01

there is delay almost 2 hours to have the media server to connect client 

possibly the reason may be related to

1)Network  or

2) Files that you are included.

these erros most commanly see when its process the files of system state, remove the system state from the backup selection and check the backup for another Drives.

next step would be with the timeout values.

so you can try client read and connect timeout and test backups..

and after that will see the about the buffer tuning..

make only one chage at a time and test the job.. 

Good luck.. let me know if you got something.. 

The Status 50 you show actually ocurrs after the backup completes successfully

This indicates a communication issue between the Client and Media Server and The Master Server

Quite a few of these also appear:

20:10:28.053: [2148.2476] <16> dtcp_write: TCP - failure: send socket (736) (TCP 10054: Connection reset by peer)

20:10:28.053: [2148.3008] <16> dtcp_write: TCP - failure: attempted to send 1 bytes

20:10:28.053: [2148.3008] <16> tar_base::keepaliveThread: INF - keepalive thread abnormal exit :14

Also listed are these:

11/19/2012 10:15:37 PM - Error bpbrm(pid=7520) from client 043-sas01-210d: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification

So .. things to check ...

1. As the clients are Windows 2000 and XP what version of the NBU Client do you use on them

2. If they are an old client are they using VSS or VSP for the open file backups? (Master Server Host Properties - Client Attributes

3. What are the client read and client connect timeout values on the media server (they may need increasing)

4. Does a netstat -a on the Master / Media show a large number of ports in use? If it is a Master/Media Server it may be running out of TCPIP ports to use and hence loss of communication, even internally. If this is the case then do the following:

From an administrative command prompt run:

netsh int ipv4 set dynamicport tcp start=10000 num=50000

This greatly increase the number of TCPIP ports available for a Windows 2008 Server

Also go to:

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\

and add a new  DWORD named TcpTimedWaitDelay with a decimal value of 30 and then reboot the server.

You can do these settings anyway as they will help the system - then try points 1 to 3 above one at a time - Hope this helps

Thanks for all your reply's. Let me implement and check and get back to you all if any more information needed.