Return
-
Title
DR Alarmed System has a huge backlog of book keeping work. Filesystem cleaner will be enabled outside of schedule setting and performance impact will be observed. -
Description
The DR alarmed, System has a huge backlog of book keeping work. Filesystem cleaner will be enabled outside of schedule setting and performance impact will be observed. -
Cause
This message is expected especially if there are huge amounts of ingesting. No user intervention is required.However, the message as well could be an indication the cleaner has not had a complete cycle. Your system logs support that logic. The cleaner process will show no known completed cycle and may also show a high amount of pending work, see below. To display the output run stats --cleaner from the command line.Last Completed Run:
Last Completed Start Time : Unknown
Last Completed End Time : Unknown
Last Completion time(s) : 0.00
Cleaner Pending Work:
Estimated Logical Bytes Left : 106477739815142 -
Resolution
Not configuring a cleaner schedule could also impact the cleaner full cycle completion
So current functionality The cleaner will auto start during system idle time. Once a backup starts, the cleaning process will stop, not completing it's work. So if there is no full cycle completed it could add to pending work. Pending work mounts and that is part of the reason for the message.
Recommended actions:
Set a cleaner schedule to allow the cleaner to run full cycles.
The cleaner auto start when the system is idle process will be more effective as well since there will be less to clean
For immediate impact, if possible consider suspending backups and manually running the cleaner to clear current pending work. Based on the amount of pending work that process could take some time to complete, keep that in mind if suspending backups.
However, the schedule without the manually run should eventually catch up.
I'll include cleaner best practice guide. https://support.quest.com/dr-series/kb/228226/cleaner-best-practice