+1Hey Community,
A couple of days ago, I received an email with this anomaly notification “Garbage Collection Delay in DDB Stores.” What does this issue indicate, and what should I be checking when this appears?
When I click the link to see the more details about this notification, it opens a DDB Pruning Performance Anomaly Report, but it doesn’t seem to provide any useful information. Has anyone run into this before or have suggestions what to do with this?
Thanks in advance!
Best answer by kkarthikk
Hi
The “Garbage Collection Delay in DDB (Deduplication Database) Stores” anomaly notification means that the system has detected an unusual delay or backlog in the pruning (garbage collection) process for one or more DDBs. It may indicate that aged data blocks or job records are not being deleted as expected, which can lead to increased disk usage.
Prunable records or blocks are not being cleared from the DDB at the expected rate. The number of prunable records (aged data blocks or job records) is consistently increasing.
In Command Center or CommCell Console, review the DDB properties for the affected DDB(s).
Look for the “Number of Pending Prunable Records.” If this number is high and not decreasing, it indicates there is pruning backlog.
If there are pruning backlog we need review the logs from the media agent.
I would recommend opening a support case to have an engineer do a deeper dive of the DDB and its activity.
Share the case number with me once you do so I can track it accordingly.
Regards,
Karthik
Hi
The “Garbage Collection Delay in DDB (Deduplication Database) Stores” anomaly notification means that the system has detected an unusual delay or backlog in the pruning (garbage collection) process for one or more DDBs. It may indicate that aged data blocks or job records are not being deleted as expected, which can lead to increased disk usage.
Prunable records or blocks are not being cleared from the DDB at the expected rate. The number of prunable records (aged data blocks or job records) is consistently increasing.
In Command Center or CommCell Console, review the DDB properties for the affected DDB(s).
Look for the “Number of Pending Prunable Records.” If this number is high and not decreasing, it indicates there is pruning backlog.
If there are pruning backlog we need review the logs from the media agent.
I would recommend opening a support case to have an engineer do a deeper dive of the DDB and its activity.
Share the case number with me once you do so I can track it accordingly.
Regards,
Karthik
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
