Highlighted
wryokom
1 Nickel

Avamar 7.1: Backups fail with "Internal Error: backtree: bad response"

I have a new Avamar 4S grid running 7.1 sending data to a Data Domain running v5.5.  I am trying to back up three Windows secondary domain controllers / file servers, which are at remote sites (all 50+ miles from my datacenter).  All three of these used to back up to my old Gen3 grid (which ran 7.0) without any issues.  Since trying to convert them to the new grid, they all fail during scheduled backups with the following errors:

2014-12-08 18:45:57 avtar Info <7694>: Server(avamarutil) not responding (possible network congestion?) (300 seconds)

2014-12-08 18:50:52 avtar Error <5775>: Internal Error: backtree: bad response 48df4c612d23a6d5f1af0...


2014-12-08 18:50:54 avtar FATAL <5399>: Internal error, aborting
2014-12-08 18:50:54 avtar Info <9772...



These clients work fine when I do on-demand backups, though I've never tried doing an on-demand backup of the entire server.  Given the distance and the fact that the network connectivity to the remote clients isn't the best, I expect there to be times when there may be congestion.  In the logs, it always has the line about the utility server being back around 590 seconds.  I've read other posts and in the documentation where it says that the 300 seconds is a default.


Is there somewhere I can change that value to give these clients more time to re-establish a connection if it fails or becomes busy?  Or am I barking up the wrong tree here for a resolution to this problem?


Thank you,

Waide R. Yokom

0 Kudos
1 Reply
pawankumawat
3 Silver

Re: Avamar 7.1: Backups fail with "Internal Error: backtree: bad response"

Hello,

In backup logs, Can you see such message -

2014-02-27 16:07:37 avtar Info <8688>: Status 2014-02-27 16:07:37, 100,277 files, 14,799 folders, 62.73 GB (5,969 files, 0 bytes, 0.00% new) 321MB  16% CPU C:TEMP

2014-02-27 16:08:38 avtar Info <8688>: Status 2014-02-27 16:08:38, 100,277 files, 14,799 folders, 62.73 GB (5,969 files, 0 bytes, 0.00% new) 321MB  0% CPU  C:\TEMP

In Above example, backup is running for 100,277 files and CPU utilization drops to 0% from 16%.

If you can find similar message, see if you can exclude that folder.

Regards,

Pawan

0 Kudos