I've been looking at disk usage on a few systems recently and noticed journal receivers quietly taking up a lot of space. In most cases, the issue wasn't growth itself; it was that receivers were not getting cleaned up as expected.
Where to check
I've found that menu option 3.32 is the easiest place to manage this. It provides a quick view of journals and their associated receivers without running multiple commands.
What stood out to me:
- You can quickly spot journals with a high number of receivers.
- You can identify receivers that are older than the defined retention.
- It makes it obvious where cleanup is not happening.
-
What to review
When I see growth, I usually check a few things:
- Retention settings for receivers
- Whether receivers must be saved before deletion
- Whether there is a backlog of old receivers waiting on save or cleanup
If retention is too long, or if save requirements are blocking deletion, receivers will stack up fast.
Helpful option for deeper details
Option 11 is useful when you want more detail. It shows disk usage tied to receivers, which helps confirm whether a specific journal is driving the issue.
What has worked for me
Keeping retention times reasonable and validating that cleanup conditions are actually being met has helped prevent unexpected disk growth. The menu makes it easy to spot problems early instead of reacting after storage gets tight.
Have you run into journal receivers building up like this, and what settings have worked best for you?
------------------------------
Brian Bybee
*Precisely Software Inc.
------------------------------