Back up and restore with Advanced Backups
Mod version shipped with FlammiCraft: 3.26.0
Deutsch · Complete operation reference
This handbook follows the current Minecraft 1.21.1 NeoForge fork. Historical adapter instructions and README future plans do not define the current operator workflow.
Configure and create a backup
Review destination, type, schedule, activity requirements and retention in advancedbackups-common.toml. Successful legacy Properties migration preserves its sources; the resulting TOML becomes authoritative. Keep storage outside the world. Profile destinations cannot overlap or nest, including resolved aliases.
Choose ZIP for a full independent point, differential for changes since its full point, or incremental for changes since the preceding member. Preserve all required parents.
Use /backup reload-config and await acceptance. Invalid updates are rejected together; reload cannot change an active operation's settings. Permission-level-2 operators or the authorised singleplayer/LAN owner can run /backup start. Follow /backup status and /backup history until a terminal result appears. Admission is not completion.
The payload-free process lock music_disc_maker/audio/.lock is omitted. Music Disc Maker recreates it when opening its audio store. Audio and ownership files remain selected; other locked or unreadable payload files still fail the backup. This is not a general exclusion of .lock files. Audio and ownership files are captured individually, without an atomic snapshot guarantee for concurrent music changes.
Top-level settings form the default profile. Named profiles inherit them; /backup start daily starts a configured daily profile. Profile commands inspect its own history and files. Operations serialize.
Inspect integrity and retention
Use /backup verify <archive-filename> full to read every required archive payload and check available CRC/SHA-256. Quick verification without full checks structure and ancestry rather than every payload. Legacy files may lack stored SHA-256. Verification does not repair archives.
Snapshots created by /backup snapshot Name are excluded from automatic deletion. /backup retention-plan previews retention; ordinary successful backups can automatically delete old points. Required ancestry and protected points can keep storage above nominal limits. A SUCCESS_WITH_CLEANUP_ERROR result means archive publication succeeded but later work failed.
Inspect incomplete staging with /backup staging. Explicit cleanup is a deletion operation. Do not confuse a recent successful backup with the latest failed or skipped attempt.
Restore offline
Stop the server and verify the target, complete chain, free space and safety destination. Run the matching JAR with Java 21; the reference supplies full CLI examples.
- Inspect a restore plan for the offline target.
- Prefer a drill into a new separate directory, then verify that reconstructed world.
- Run restore without
--applyfor a preview. - Apply only the reviewed selection with an existing external safety directory.
Apply verifies the archives, locks the target and creates an external safety archive before replacement. The safety archive includes nested files named session.lock before removal or replacement; only the root world lock is preserved and omitted. It is not an atomic whole-world transaction; preserve reported target/safety paths after partial failure. New .abchain files record deletions and need the matching CLI or a materialized ZIP export for older tools. A verified archive is not yet gameplay or restart acceptance.