Skip to main content

Verify GriefDefender storage before a database migration

Applies to: GriefDefender; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

Claims, flags and player allowances need a consistent storage checkpoint. Identify the backend selected by storage.yml before moving data or changing a connection string.

Before you start

GriefDefender uses LuckPerms and claim-aware rules. Current documentation describes YAML by default with optional HOCON; check the format your server actually generated. Claim, parent and wilderness contexts matter, so record the location and affected player before changing rules.

Work through the check

  1. Record the installed platform, plugin release, active storage backend and all servers that share it, keeping passwords out of public notes.
  2. Pause writes through a supported maintenance procedure and back up the backend with its documented database tooling together with GriefDefender configuration and matching world data.
  3. Prepare an isolated restore target with a unique database or path and no connection to live shared storage, then follow the release’s documented migration or restore instructions.
  4. After startup, inspect several known owners, claim bounds, trust settings and player allowances, and test one harmless normal-player action at a protected boundary.

Confirm the result

The isolated server should preserve the checkpoint’s claim identity and protection behavior without writing to production. A successful database connection alone is not enough to prove that the right dataset loaded.

If the result differs

Table prefixes, platform-specific directories and optional configuration formats can select different data than expected. Inspect startup errors before treating an empty claim list as evidence that the original data is gone.

Recover safely

Retain the original backend and immutable checkpoint while testing. Do not initialize a new empty dataset over the existing database or push older test records over newer production claims.

CloudExa game-panel controls for creating a backup.
The game-panel backup controls. Confirm separately whether the chosen backup includes an external plugin database; this screenshot does not show a plugin-specific backup tool.

Documentation and related help

Check the GriefDefender maintainer documentation and GriefDefender maintainer reference against your installed release before applying changes.

No comments to display