Plan a consistent external SQL backup with DriveBackupV2

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

A plugin using MySQL or another external SQL service may keep its important records outside the game files. Copying the plugins directory is not a database backup. DriveBackupV2 documents external backup features, but consistency still depends on how the application writes its data.

Record the starting point

List plugins that store data externally and identify the database owner, schema and supported backup method. Keep credentials private. Decide which files and SQL records must represent the same recovery point, particularly for inventories, currency or cross-server state.

Work through the change

Read the installed DriveBackupV2 external SQL documentation and the database-dependent plugin's recovery instructions. Confirm supported database types and the service account's required privileges.
Configure only the intended database source using the documented fields. Keep secrets out of screenshots and do not grant a broad administrator account merely to make a test connect.
Plan a quiet or controlled write window where required by the application. Capture related game files and SQL data in a sequence that the plugin's recovery procedure supports.
Inspect the resulting backup and trial a restore into an isolated database and service copy. Confirm representative records without pointing a test server at the live database.

Check the result

The recovery set should include the required SQL data and related files with a documented consistency window. Record which application versions produced it. A successful export message is useful evidence, but a separate restore test is stronger evidence that the data can be recovered.

If the result differs

If connection succeeds but export fails, inspect database privileges, tool requirements and the first error. If restored records disagree with files, revisit write coordination rather than treating the newest filename as automatically correct. Avoid public sharing of SQL dumps.

Restore the previous backup configuration if the trial affects normal jobs, preserving existing verified copies. Keep test databases clearly isolated and remove them only through the agreed test cleanup. Do not overwrite live SQL data during a backup validation.

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