Backup Best Practices

A good backup strategy protects your server from data loss. Learn when to backup, how to organize backups, and what to do when things go wrong.

Why Backups Matter

Data loss can happen from:

• Accidental deletion - Oops, wrong file
• Corruption - Server crash during save
• Bad updates - Update broke something
• Griefing - Someone destroyed your world
• Mistakes - Config change gone wrong

The 3-2-1 Backup Rule

A solid backup strategy follows 3-2-1:

• 3 copies of your data
• 2 different storage types
• 1 copy offsite

Applied to Plex Host

1. On-server backup - Your Plex Host backup slots
2. Downloaded copy - Saved on your computer
3. Cloud storage - Google Drive, Dropbox, etc.

When to Backup

Always Backup Before

Regular Schedule

Backup Naming Strategy

Use descriptive names you'll understand later:

Good Names

2024-01-15-before-fabric-update
2024-01-16-stable-after-update
2024-01-20-spawn-build-complete
weekly-backup-jan-week3

Bad Names

backup1
backup
asdf
new backup

Managing Limited Slots

With limited backup slots, you need a rotation strategy:

For 3 Slots

For 5 Slots

For 10+ Slots

More flexibility! Consider:

• Multiple locked milestones
• Weekly + monthly rotations
• Pre-update checkpoints
• Major build completions

Downloading for Safety

Don't rely solely on server backups:

When to Download

1. Before deleting old backups
2. Major milestones (big builds, server setup)
3. Monthly archive
4. Before major changes

Where to Store

• Local computer
• External hard drive
• Cloud storage (Google Drive, Dropbox)
• Multiple locations for critical backups

Disaster Recovery Plan

If Something Goes Wrong

1. Don't panic - Backups exist for this reason
2. Stop the server - Prevent further damage
3. Assess damage - What's actually broken?
4. Choose backup - Find the best restore point
5. Restore - Follow the restore guide
6. Verify - Test that everything works
7. Document - Note what happened to prevent it again

Recovery Scenarios

Common Mistakes to Avoid

Don't Do This

• ❌ Never having any backups
• ❌ Only one backup (gets overwritten)
• ❌ Never downloading backups
• ❌ Vague backup names
• ❌ Forgetting to backup before changes
• ❌ Deleting all old backups at once

Do This Instead

• ✅ Regular backup schedule
• ✅ Multiple backups with rotation
• ✅ Download important backups
• ✅ Descriptive naming
• ✅ Backup before every major change
• ✅ Keep at least one "golden" backup locked

Backup Checklist

Before any major change:

• Create a new backup
• Give it a descriptive name
• Verify backup completed
• Consider downloading if very important
• Then make your changes

After successful changes:

• Create a new "known good" backup
• Clean up old unnecessary backups
• Update your golden backup if appropriate