Minecraft server planning
How often should you back up a Minecraft server?
The useful schedule is not simply “as often as possible.” Match backup frequency to how quickly your world changes, how much progress you can afford to lose, and how many recovery points you retain.
For a small private server, a simple schedule you understand and occasionally test is more valuable than a complicated plan nobody has restored from. Important worlds should also have independent exports outside the hosting account.
Quick recommendation
| Server pattern | Starting schedule | Why |
|---|---|---|
| Casual world with infrequent play | Weekly or manual | Fewer meaningful changes between sessions |
| Active survival server | Daily overnight | Limits normal progress loss without constant backup churn |
| Busy server with frequent changes | Twice daily | Adds another recent recovery point during active days |
| Before updates, imports, or migrations | Manual immediately before | Creates a known rollback point tied to the risky change |
These are starting points, not guarantees. Backup usefulness also depends on retention, storage health, and whether the recovery path has been tested.
What should a backup protect?
A useful backup normally includes the world plus the configuration needed to rebuild how it behaves. Depending on the server, that can include server properties, plugin configuration, permissions, mod or loader configuration, and related files.
Create a manual recovery point before Minecraft updates, server-software changes, plugin or mod changes, world imports, major permission edits, migrations, or manual repair work.
Daily, twice-daily, weekly, or manual?
Daily overnight
Daily is a practical default for an actively used private server. A normal rollback is measured in roughly a day rather than a week.
Twice daily
Twice-daily backups make more sense when meaningful changes happen throughout the day. They are not automatically better when limited slots cause healthy older recovery points to disappear faster.
Weekly
Weekly can fit an occasional-use server, but it creates a larger potential progress-loss window. Add a manual backup before unusual changes.
Manual
Manual backups are useful when timing matters more than cadence, especially immediately before updates and migrations.
Retention matters as much as frequency
Frequency and retention are connected. If a server keeps only a few recovery points, frequent backups can overwrite an older healthy state quickly.
Exaltry currently includes two panel backup slots per plan. These are best-effort recent recovery points, not an unlimited archive. Keep your own exports of worlds you cannot afford to lose.
Test the recovery path
A backup is useful only if you can recover from it. Periodically confirm where it is, when it was created, and how you would restore or export the files.
You do not need a destructive restore drill on a live server. Downloading an export or restoring into a separate test environment is safer when practical.
Keep an independent copy
Hosting backups should not be the only copy of an important world. Independent exports protect against account loss, accidental deletion of retained backups, or discovering that you need an older archive after normal retention has rolled forward.
Choosing a schedule in Exaltry
Exaltry's configurator currently offers manual, daily overnight, twice-daily, and weekly scheduling, plus a preferred backup window. Every plan includes two panel backup slots.
For most active private survival servers, daily overnight is the simplest starting point. Choose twice daily when losing up to a day of progress would be unacceptable; weekly is better suited to occasional-use worlds.
Backups are best-effort recovery points rather than a durability guarantee. Exaltry is currently a home-server public beta with no formal uptime SLA, so keep independent copies of important worlds.
Choose your backup schedule before checkout.
Configure RAM, software, version, gameplay settings, and backups together.