Avamar: Backend report fails with "INTERNAL CYCLE ERROR: bad response in repldata SRC_GET_DATA: GET_HASH_DATA"

avtar Info <5667>: 40 backups found for client "clientA.avamar.com"
------8<------  SNIP! ------8<-------
avtar Info <6654>: Replicating backup 383, Label "Daily_8PM-I-2400001442-1419789602587#0", 189.4 GB
------8<------  SNIP! ------8<-------
avtar Info <6654>: Replicating backup 384, Label "Daily_8PM-I-2400001442-1419789602587", 1,793 GB
------8<------  SNIP! ------8<-------
avtar Error <5445>: INTERNAL CYCLE ERROR: bad response in repldata SRC_GET_DATA: GET_HASH_DATA=3 serial=4436336 seq=0 flags=R:N:0 kind=0 rsp=MSG_ERR_MISC
------8<------  SNIP! ------8<-------
2015/01/28-08:44:59.72488 [avtar]  INTERNAL ERROR: <0001> assert error (!uapp::staging().canRun() || rechunk), /local/jenkins/workspace/client_Hermosa_SLES11-64/abs2/work/src/avclient/repldir.cpp line 160
2015/01/28-08:44:59.72521 [avtar]  | 00000000009be1c1
2015/01/28-08:44:59.72523 [avtar]  | 00000000009bef07
------8<------  SNIP! ------8<-------
avtar Info <5992>: Error found in backup number 384
avtar Info <5675>: Replicated 1 of 40 backups (1 error) for client "clientA.avamar.com"


Summary: 

After successfully replicating backup #383 for "clientA.avamar.com", a problem was found with backup #384.  Avtar subsequently fails with an assert error

There appears to be a problem with backup #384 belonging to clientA.avamar.com.  

Avtar was unable to retrieve a hash for backup #384.

avtar Error <5445>: INTERNAL CYCLE ERROR: bad response in repldata SRC_GET_DATA: GET_HASH_DATA=3 serial=4436336 seq=0 flags=R:N:0 kind=0 rsp=MSG_ERR_MISC

Since the report was successful for backup #383 but not backup #384, it could be that backup #384 was a daily backup which has since expired.

Check if the backup still exists.

• If the backup no longer exists. This is expected behavior since backend report is trying to retrieve data which no longer exists. Try running backend report again for this client only to ensure that it completes before the next backup to expire can be removed from the system.    
• If the backup still exists try validating the backup by right-clicking it in the Administrator UI restore screen.  Check the health of the Avamar server and ensure that a recently validated checkpoint exists.