Plan CoreProtect retention without losing evidence needed for recovery

Applies to: CoreProtect; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

Older audit records consume storage but may be the only evidence for a delayed grief report. Decide a retention policy from actual recovery needs before scheduling any irreversible purge.

Follow the procedure

Measure the current database size and growth over several normal days. Record the existing retention policy, backup coverage and the oldest report staff are expected to investigate.
Check which logging categories account for growth and which are needed for your moderation workflow. Do not disable essential logging merely to make a storage graph smaller.
Read the installed purge documentation carefully. Time cutoffs remove records older than the chosen age, and database optimization behaviour differs between storage backends.
Agree a retention period that covers your published support and appeal expectations. Keep a consistent archived database copy if older records must remain available outside the live server.
Rehearse the proposed purge on an isolated restored database and compare record availability before and after. Measure actual reclaimed space rather than assuming row deletion immediately shrinks every database file.
Only schedule a separately approved production purge after backup recovery has been checked. Restrict purge access to administrators and record the cutoff, scope and completion result.

Check the result

The retention plan should state what remains searchable live, what can be recovered from archives and what will be permanently unavailable. Its storage estimate should come from a rehearsal on the same backend. A purge is a data-loss decision, not a routine fix for an unexplained full disk.

If the result is wrong

If the rehearsal removes records you still need, increase the retention period and keep production unchanged. Restore the isolated test from its backup when comparing alternatives. Do not run a shorter production purge first and expect a later setting change to recover deleted history.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report