Separate local and remote DriveBackupV2 retention counts

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

Keeping fewer remote backups does not necessarily reduce local archive storage, and the reverse is also true. DriveBackupV2 documents separate remote and local retention controls. Decide how many recovery points belong in each place before changing a count.

Record the starting point

List recent local archives and the corresponding remote copies. Record their dates, sizes and whether uploads completed. Keep the current configuration and identify the oldest recovery point the community still needs before applying a policy that may remove copies.

Work through the change

Read the installed release's storage documentation and locate the remote keep-count and local-keep-count controls. Confirm the documented meaning of each value, including any special values.
Choose counts based on the actual schedule and recovery need. Three hourly copies provide a different history from three daily copies, even though the count is identical.
Apply the intended policy and observe one normal backup cycle. Check the log and both destinations to see which archive was created, uploaded and retained.
Download a retained remote copy and inspect a small restore sample in a separate folder. A remote filename alone does not establish that the archive is usable.

Check the result

Local usage should stay within the chosen capacity while remote storage retains the intended history. Document the schedule beside the counts. Confirm the newest successful remote copy before considering removal of any older local recovery point.

If the result differs

If local usage remains high, inspect whether archives were produced under an older naming or destination arrangement. If remote history differs, check upload success and provider listing behaviour. Do not assume a retention setting has cleaned every historical file outside its managed set.

Restore the previous counts if the new policy is too aggressive, while recognising that deleted copies are not recreated by changing a number back. Preserve remaining good copies and repair the policy before the next cycle. Do not delete live game files to satisfy archive retention.

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