Investigate overlapping backup jobs and temporary disk pressure

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

A backup may require space for the source, a new local archive and retained copies while an upload runs. If a scheduled interval is shorter than the complete job, repeated work or waiting can make the service look stuck. Measure the full cycle before increasing frequency.

Record the starting point

Record the configured schedule, recent start and finish times, free disk space and archive sizes. Check whether another panel or plugin backup runs at the same time. Keep the current schedule and identify the last successful remote recovery copy.

Work through the change

Read a complete DriveBackupV2 cycle from archive creation through upload and retention. Separate time spent compressing from time spent transferring.
Compare the duration with the next scheduled start and inspect the installed release's handling of an already-running job. Do not repeatedly trigger manual backups while the state is uncertain.
Choose a schedule that leaves room for the observed workload and other maintenance. Reduce unnecessary source files through reviewed selection rules rather than deleting live data.
Observe one revised cycle, checking free space before and after. Confirm the remote archive and retention result rather than relying only on a task-start message.

Check the result

The complete cycle should finish before the next intended run under representative conditions, with adequate working space. Keep the measured duration and source size with the schedule. A quieter test can be faster than a busy-world backup, so leave practical margin.

If the result differs

If compression is slow, inspect source size and nested archives. If transfer dominates, collect provider and upload evidence instead of changing Java memory blindly. If disk usage never falls, review local retention separately from scheduling.

Restore the previous schedule if the revised one misses the required recovery window, then arrange capacity or source changes deliberately. Preserve the last verified copies. Do not kill unknown transfer processes or remove an in-progress archive without first understanding which task owns it.

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