- Created comprehensive Pterodactyl-based world backup procedure - No SSH required - all through Panel interface - Step-by-step archive, download, rename, upload workflow - Troubleshooting section for common issues - Created Holly's retirement checklist for 10 servers - Special section for RAD2 (her build) - 3 TX1 Dallas servers + 6 NC1 Charlotte servers - Checkboxes for start, Nextcloud upload, deletion - Notes section for each server - Troubleshooting and contact info included Related to soft launch preparation and server fleet optimization. Supports server sunset evaluation (Task #45).
185 lines
5.2 KiB
Markdown
185 lines
5.2 KiB
Markdown
# Server Retirement - World Backup Procedure
|
|
|
|
**Created:** March 19, 2026
|
|
**Effective:** Immediately
|
|
**Applies To:** All game servers being retired from the Firefrost Gaming network
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
This procedure documents how to backup world data from a game server before deletion using the Pterodactyl Panel interface. No SSH access required.
|
|
|
|
---
|
|
|
|
## Prerequisites
|
|
|
|
- Access to Pterodactyl Panel (https://panel.firefrostgaming.com)
|
|
- Access to Nextcloud (https://cloud.firefrostgaming.com)
|
|
- Sufficient local disk space for temporary archive downloads
|
|
- Confirmation that server is being retired (see `docs/planning/server-deletion-policy.md`)
|
|
|
|
---
|
|
|
|
## Procedure
|
|
|
|
### Step 1: Access Server Files
|
|
|
|
1. Log into Pterodactyl Panel
|
|
2. Navigate to the server being retired
|
|
3. Click **Files** tab in server management interface
|
|
|
|
### Step 2: Locate World Folder
|
|
|
|
Common world folder names by server type:
|
|
- **Most Minecraft modpacks:** `/world/`
|
|
- **Some servers:** `/worlds/`, `/saves/`, or custom name
|
|
- **Verify** by checking for region files and level.dat
|
|
|
|
### Step 3: Create Archive
|
|
|
|
1. **Right-click** the world folder
|
|
2. Select **Archive**
|
|
3. Wait for archive creation to complete
|
|
4. Archive will appear in the same directory as `world.tar.gz`
|
|
|
|
**Note:** Archive creation time varies by world size (30 seconds to 5+ minutes for large worlds)
|
|
|
|
### Step 4: Download Archive
|
|
|
|
1. **Right-click** the newly created `world.tar.gz` file
|
|
2. Select **Download**
|
|
3. Save to local machine (Downloads folder or preferred location)
|
|
4. Wait for download to complete
|
|
|
|
### Step 5: Rename Archive
|
|
|
|
Rename the downloaded file using this format:
|
|
|
|
**Format:** `servername-world-YYYY-MM-DD.tar.gz`
|
|
|
|
**Examples:**
|
|
- `homestead-world-2026-03-19.tar.gz`
|
|
- `mayview-world-2026-03-19.tar.gz`
|
|
- `rad2-holly-build-2026-03-19.tar.gz`
|
|
- `atm10-world-2026-03-19.tar.gz`
|
|
|
|
### Step 6: Upload to Nextcloud
|
|
|
|
1. Log into Nextcloud at https://cloud.firefrostgaming.com
|
|
2. Navigate to **Server World Backups** folder
|
|
3. Upload the renamed archive file
|
|
4. Wait for upload to complete
|
|
5. Verify file appears in Nextcloud with correct name and size
|
|
|
|
### Step 7: Verify Backup Integrity
|
|
|
|
1. Check file size matches between local download and Nextcloud upload
|
|
2. Optionally: Download from Nextcloud and verify checksum matches
|
|
3. Document backup in archive manifest (if maintaining one)
|
|
|
|
### Step 8: Clean Up
|
|
|
|
1. Delete local copy of archive (free disk space)
|
|
2. Return to Pterodactyl Panel
|
|
3. Delete the archive file from server Files tab
|
|
4. **DO NOT delete the server yet** until confirmed backup is good
|
|
|
|
### Step 9: Delete Server from Panel
|
|
|
|
**Only after backup is confirmed in Nextcloud:**
|
|
|
|
1. Pterodactyl Panel → Server list
|
|
2. Locate retiring server
|
|
3. Click server settings
|
|
4. Scroll to danger zone
|
|
5. Delete server
|
|
|
|
---
|
|
|
|
## Special Cases
|
|
|
|
### Large Worlds (10GB+)
|
|
|
|
- Archive creation may take 10+ minutes
|
|
- Download may take significant time depending on connection
|
|
- Consider splitting into chunks if browser download fails
|
|
- Alternative: Use SFTP client for more reliable large file transfer
|
|
|
|
### Player-Built Structures (e.g., Holly's RAD2 Build)
|
|
|
|
- Create backup BEFORE players finish (safety copy)
|
|
- Create final backup AFTER completion
|
|
- Rename clearly: `servername-playername-description-YYYY-MM-DD.tar.gz`
|
|
- Example: `rad2-holly-final-build-2026-03-19.tar.gz`
|
|
|
|
### Multiple Worlds Per Server
|
|
|
|
Some servers have multiple worlds (Overworld, Nether, End):
|
|
- Check for multiple world folders: `world/`, `world_nether/`, `world_the_end/`
|
|
- Archive each separately OR archive parent directory containing all
|
|
- Name accordingly: `servername-all-worlds-2026-03-19.tar.gz`
|
|
|
|
---
|
|
|
|
## Nextcloud Folder Structure
|
|
|
|
Recommended organization in Nextcloud:
|
|
|
|
```
|
|
/Server World Backups/
|
|
/2026-03-Retirements/
|
|
homestead-world-2026-03-19.tar.gz
|
|
mayview-world-2026-03-19.tar.gz
|
|
reclamation-world-2026-03-19.tar.gz
|
|
atm10-world-2026-03-19.tar.gz
|
|
emc-subterra-tech-world-2026-03-19.tar.gz
|
|
minecolonies-create-conquer-world-2026-03-19.tar.gz
|
|
ember-project-world-2026-03-19.tar.gz
|
|
vanilla-world-2026-03-19.tar.gz
|
|
all-of-create-creative-world-2026-03-19.tar.gz
|
|
rad2-holly-build-2026-03-19.tar.gz
|
|
```
|
|
|
|
---
|
|
|
|
## Troubleshooting
|
|
|
|
**Archive creation fails:**
|
|
- Check available disk space on node
|
|
- Try archiving smaller subdirectories individually
|
|
- Contact hosting provider if persistent issues
|
|
|
|
**Download fails/times out:**
|
|
- Use browser download manager or extension
|
|
- Try SFTP client (FileZilla, WinSCP) for more reliable transfer
|
|
- Split large archives if possible
|
|
|
|
**Upload to Nextcloud fails:**
|
|
- Check Nextcloud storage quota
|
|
- Verify network connection stability
|
|
- Try splitting into smaller chunks
|
|
- Use Nextcloud desktop sync client for large files
|
|
|
|
---
|
|
|
|
## Post-Retirement
|
|
|
|
After all backups are complete and servers deleted:
|
|
- Document retirement in infrastructure manifest
|
|
- Update server count in documentation
|
|
- Reclaim disk space on dedicated nodes
|
|
- Update any automation/monitoring that referenced deleted servers
|
|
|
|
---
|
|
|
|
## Related Documentation
|
|
|
|
- Server Deletion Policy: `docs/planning/server-deletion-policy.md`
|
|
- Server Sunset Evaluation: `docs/tasks/server-sunset-evaluation/README.md`
|
|
- Infrastructure Manifest: `docs/core/infrastructure-manifest.md`
|
|
|
|
---
|
|
|
|
**Fire + Frost + Foundation = Where Love Builds Legacy** 💙🔥❄️
|