Backup and restore guide

Data loss is not a matter of if — it is a matter of when. A plugin update gone wrong, a staff mistake, or a corrupted world file can wipe out months of progress.

Backup types

Automated backups

• Created daily at a time you choose
• Retention: 7 days on Starter, 14 days on Growth, 30 days on Pro
• Includes server files and database dumps
• Stored off-site on redundant storage

Manual snapshots

• Trigger instantly from the panel before risky changes
• Unlimited count — only storage quota applies
• Restored in under 5 minutes

Setting up automated backups

1. Open your server panel and navigate to Backups

2. Click Configure Schedule

3. Choose a time when your player count is lowest (typically 4-6 AM)

4. Select what to include: world, plugins, config, and database

5. Save and verify the first backup completes successfully

Manual snapshot best practices

Always create a manual snapshot before:

• Updating server software (Paper, Spigot, Forge)
• Installing new plugins or mods
• Major world edits or terrain generation changes
• Changing database schemas
• Migrating to a new host

Restoring from backup

Full restore

1. Go to Backups → select the snapshot you want

2. Click Restore and confirm the warning

3. The server will stop, restore, and restart automatically

4. Verify the server boots correctly before announcing it to players

Partial restore (single file or folder)

1. Download the backup archive

2. Extract only the files you need

3. Upload them via SFTP or the file manager

4. Restart the server to reload configs

Database backups

Database dumps are included in every backup. For extra safety, export manually via phpMyAdmin before schema changes.

Testing your backups

A backup you have not tested is a gamble. Once per month, restore a backup to a temporary test server and verify the world loads and player data is intact.