Workflow Safety & Recovery
Guides and release notes are shown in their original language.
On this page
← All guides · MANAGE & MAINTAIN
Synix's setup, configuration, imports, updates, backups, and restores share safety checks. These protections improve the existing workflows; they do not replace game-specific requirements or independent backups.
What each stage requires
| Stage | Before changes proceed | What happens if it cannot finish |
|---|---|---|
| Setup | Required fields valid and current step 3 Review shown | Save stays unavailable until requirements and review are satisfied |
| Configuration save | Server stopped, valid supported file, no conflicting external edit | Save is refused or recovery restores the prior state; read the reported result |
| Mod import | Correct route, reviewed destinations, checks/confirmation, stopped server | Unsafe or changed packages are rejected; no automatic start |
| Requested pre-start backup | Backup succeeds before update/start | Server stays stopped; later steps do not continue |
| Requested update | Update/validation reports success | Launch is blocked after a failed update |
| Full backup restore | Files staged/verified and shared settings synchronized | Recovery state remains available; incomplete settings sync blocks Start |
This is not an unattended “fix everything” command. Resolve the named failure before retrying.
Startup and maintenance order
For a normal start with the corresponding options enabled:
- Complete any pending restore/settings recovery.
- Pass launch validation and applicable readiness checks.
- Finish the requested stopped-server backup.
- Finish the requested game update.
- Launch the server.
A requested backup failure prevents both the update and launch. A requested update failure prevents launch.
Scheduled Smart Maintenance also respects the requested backup/update results after stopping the server. The server is not deliberately restarted into a half-finished update.
Crash recovery has a different policy: it skips the normal pre-start backup so it does not replace useful backup history with a potentially broken state. It is not a substitute for scheduled backups.
Backup failure and retention
An unavailable custom backup destination is an error, not permission to switch silently to another folder.
A new backup is considered published only after its archive and integrity receipt are in place. Retention runs afterward and never selects the newly created archive, including when an older file has a future timestamp.
If an old archive is locked, cleanup reports a warning while preserving the new backup. Incomplete creation removes its partial output and preserves existing backups.
Review manual backup errors in the dashboard or Minecraft Control Center. “The operation returned” is not the same as “the backup succeeded.”
Full restore has two parts
A restore first activates the restored server files, then reads supported shared values back into Synix.
The second step uses the game's configuration mappings, not guessed key names. It does not rewrite restored config files just to read their values. Minecraft additionally refreshes recorded runtime/change history and its saved player-limit information.
If synchronization fails, Synix reports a partial completion: the backup files are restored, but Synix's saved settings have not caught up. This is not an automatic rollback to the old files.
The previous installation and recovery record are retained until this step succeeds. Do not delete them to clear the warning.
Recover from an interruption
- Keep the server stopped and preserve the reported recovery files.
- Read whether file activation failed or whether only settings synchronization remains.
- Correct the named issue, such as unavailable storage, permissions, invalid mapped configuration, or inability to save Synix's database.
- Reopen Synix if necessary. Pending recovery is retained across reopening.
- Retry Start. Synix retries pending settings synchronization before launch validation, updates, or starting the game.
- Confirm the selected world, ports, player limit, and credentials after recovery.
If the earlier file-activation phase was interrupted, Synix uses its existing original-folder recovery path. Follow that message; do not mix files from both installations manually.
Which recovery tool should I use?
| Change | Appropriate recovery |
|---|---|
| One failed config edit | Editor backup/recovery and comparison with the original |
| A recorded add-on import | Roll Back Import, subject to later-edit/integrity checks |
| Recorded Minecraft runtime/pack/world changes | Change recovery, where the operation is eligible |
| World content changed after playing | A matching full backup, not only a file-import receipt |
| Moving the full Synix setup | Verified transfer package and separate copies of data outside its coverage |
A filesystem backup does not necessarily capture external saves or a consistent running database/VM. Review the backup coverage, especially for external deployments such as Dune.
For persistent errors, use Troubleshooting & FAQs. Do not share unredacted configs, tokens, or the entire servers.json file.