Verify a Lands database backup on an isolated server
A successful backup message is useful, but a restore test proves whether claims and bank data can be recovered. Keep that test isolated because the documented restore replaces the current dataset.
Before you start
Lands separates land membership, areas and role flags. Select the intended land before editing it, and verify with an ordinary player rather than an administrative bypass. Use the documentation matching your release when menus or permission settings differ.
Work through the check
- Check the installed release supports
/lands admin database backup, then create a checkpoint and locate the resulting backup under the documented plugin backup directory. - Save the plugin configuration, release information and world references alongside the archive, keeping database passwords private and exporting a protected copy off the game node.
- Prepare an isolated server with its own storage connection and use the documented restore flow there only, reading its restart and overwrite warning before confirmation.
- After the test restart, compare several known claims, owners, subareas and bank balances with the checkpoint record, then test a harmless ordinary-player access rule.
Confirm the result
The isolated restore should contain the expected protection and account state from that checkpoint. Neither its startup nor its test actions should write into production storage.
If the result differs
A missing backup filename or backend mismatch needs investigation before confirmation. Do not use an administrative restore command on the live server as a quick way to inspect an archive.
Recover safely
Keep the original backup immutable and rebuild the isolated test when repeating recovery. Production rollback needs a separate maintenance plan to avoid replacing newer claims and transactions.
Documentation and related help
Check the Lands maintainer documentation and Lands maintainer reference against your installed release before applying changes.