Unsolved
This post is more than 5 years old
7 Posts
0
4825
December 18th, 2013 06:00
Server not responding possible network congestion
Have a file server that constantly fails to backup. The backup is about 3.3 terabytes.
I see this error every time it fails.
Was wondering if changing the freezetimeout to something like 400 instead of 300 would help.
The failure time are not all at the same time.
2013-12-17 23:06:09 avtar Info <7694>: Server(10.210.249.50) not responding (possible network congestion?) (300 seconds)
2013-12-17 23:08:22 avtar Info <8688>: Status 2013-12-17 23:08:22, 3,613,205 files, 895,227 folders, 3,364 GB (5,901 files, 2.065 GB, 0.06% new) 512MB 30% CPU E:\docs\folder name changed\something.pdf
2013-12-17 23:10:48 avtar Error <5775>: Internal Error: backtree: bad response edc5f39560b2b511e7c88af3141ef2404d448588 270805 ADD_HASH_DATA=2 serial=270805 seq=0 flags=R:N:0 kind=9 rsp=MSG_ERR_INVALID_PARAMETERS
2013-12-17 23:10:48 avtar Info <5726>: Aborting backup due to error (3:EXC_HFSERROR)
2013-12-17 23:10:55 avtar FATAL <5399>: Internal error, aborting
2013-12-17 23:10:55 avtar Info <0000>: Starting graceful (staged) termination, error reported in nbackmain (wrap-up stage)
0 events found


ionthegeek
2 Intern
•
2K Posts
0
December 18th, 2013 07:00
"Server not responding" messages are informational. The message means that the Avamar client has not received a reply to any messages it has sent to the server in x seconds (x is 300 in this case). This can happen for a number of reasons. Typically we see this message if there is a network interruption or if the server is unable to respond because it's too busy or has gone read only for maintenance.
The reason for the failure is the "bad response" message. This message is essentially the server saying "You're not allowed to reference that piece of data in a backup because I don't have it." This can happen for a number of reasons as well. We have seen this message if the hash cache on the client is damaged or if the server is failing hfscheck. It's also possible that the server is processing messages from the client out of order for some reason.
The freezetimeout parameter controls volume freezing on Windows clients (e.g. VSS or OTM) so modifying this parameter is unlikely to make any difference. I would recommend opening a service request for this issue.
pawankumawat
355 Posts
0
December 18th, 2013 07:00
Hello,
Did you try to run on demand backup for this client ? if yes, did backup complete ?
This issue may occur with several reasons. If number of files on client is huge, it may take long time to create f_cache and p_cache and may fail for backup. One option would be to run backup for smaller chunks.
Regards,
Pawan
pp082c
38 Posts
0
March 5th, 2015 00:00
Hi Pawan,
I got the same error Error <5775>: Internal Error: backtree: bad response and 5399 aborting.
On-demand too failed with the same error.
Could you please check the attached logs and suggest if this the issue related with large number of files.
The f_cache file started writing at 18:00:21 and went on updating till 22:04:53.