cancel
Showing results for 
Search instead for 
Did you mean: 

Error 13, getting failed before its start to wirte

Chan_backup
Level 5

 

Hi,

Details below

Linux master 7.5.0.6

Client OS/Release = Windows2003 5 and version 7.1

I have attached the bpcdtest and actvity monitor details, please check give you soultions.

i have increased the client read time out in Media server but it did not worked.

one more question is what is difference in increasing client read time out in media server and the client?

 

-Chan

 

 

 

6 REPLIES 6

Marianne
Level 6
Partner    VIP    Accredited Certified

'Timer expired' is a sign of Client Read Timeout.

Once connection is made to the client, the media server is waiting for the client to start sending data.

If nothing is received within the timeout period, the media server will terminate the connection and fail the backup. For this reason, you can understand that Client Read Timeout goes on the Media server.

It seems that the timeout is already at 30 minutes (1800).

You need to check bpbkar log on the client to see why no data is sent to the media server.

Increase client's logging level to a 3.

Chan_backup
Level 5


i still have the issue with error 13, i will update with new set of logs tomorrow.

Marianne
Level 6
Partner    VIP    Accredited Certified

Two more questions:

What is Backup Selection in Client's backup policy?
Is 'Allow multiple data streams' selected in Policy Attributes?

We need to know where exactly the problem is - with one specific drive letter or all drive letters/file systems.

Chan_backup
Level 5

Hi,

VSS writers are not stable, some are waiting for completion, probably reboot is required for the server, will soon update with further findings.

Marianne
Level 6
Partner    VIP    Accredited Certified

Seems you are on a mission all of your own... not answering any questions...

Good luck!

Yogesh9881
Level 6
Accredited

Ever this backup worked ? or newly implemented host ?

Not sure you will revert or not but still....wink