Symptoms
Garbage Collection (GC) failures are seen in the Avamar Administrator Console, and reported in the outputs of the status.dpn and dumpmaintlogs commands when run on the Avamar Utility Node.
These failure messages include, but not limited to:
MSG_ERR_BACKUPSINPROGRESSMSS_ERR_DISKFULLMSG_ERR_TIMEOUTMSG_ERR_NOPARITYMSG_ERR_MISC
The event code for a GC Failure is 4202.
Cause
Garbage Collection can fail for various reasons. There is typically an error message associated with the failure that indicates why the Garbage Collection failed.This resolution path walks the reader through how to troubleshoot the Garbage Collection failures based on the associated error reported.
Resolution
Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, to eliminate possible causes and take corrective action as necessary.
Step 1: Gathering Information
a. Log in to the Avamar Utility Node as admin and load the admin keys. See Avamar: How to Log in to an Avamar Server and Load Various Keys for instructions on loading keys.
The rest of this KB article assumes that the admin keys are loaded.
b. Collect all the following information listed in Avamar: How to gather the information required to troubleshoot capacity issues.
Step 2: High checkpoint overhead can cause the Garbage Collection (GC) to fail if the Operating System (OS) capacity is too high. By default, GC fails with MSG_ERR_DISKFULL if OS capacity rises above 89%. Verify that there are no capacity issues on the grid using Avamar OS Capacity (Resolution Path).
Step 3: A type of timing issue (Avamar v7+) can be seen with MSG_ERR_TRYAGAINLATER due to certain Avamar tasks that cannot allow GC to run simultaneously. See Avamar: Garbage collection failing with MSG_ERR_TRYAGAINLATER.Step 4: If garbage collection fails with MSG_ERR_GARBAGECOLLECT, see Avamar - Symptom Code 4202 >> Error: Failed garbage collection with error MSG_ERR_GARBAGECOLLECT.Step 5: If garbage collection fails with MSG_ERR_BADTIMESYNC, see Avamar - Symptom Code 4202 - failed garbage collection with error MSG_ERR_BADTIMESYNCStep 6: If garbage collection fails with MSG_ERR_DUPLICATE, see Avamar Garbage collection fails with MSG_ERR_DUPLICATE (v7.x)Reference:
For other GC error messages including MSG_ERR_TIMEOUT, MSG_ERR_DDR_ERROR, MSG_ERR_NOPARITY (or anything not mentioned in this article), contact the Dell Technologies Avamar Support Team. The rest of the error messages have internal-only solutions.If any other Non-GC-error capacity issues are found, see Avamar Capacity Troubleshooting, Issues, and Questions - All Capacity (Resolution Path).
