Overview
StellarStack provides a robust backup system to protect your game server data. Create manual backups, schedule automated backups, lock critical backups from deletion, and restore servers to previous states.Manual & Automated
Create backups on-demand or schedule automatic backups
Compressed Archives
Backups are compressed to save storage space
Lock Protection
Lock important backups to prevent accidental deletion
Download & Restore
Download backups locally or restore servers with one click
Backup Limits
Each server has a configurable backup limit:- Limit: Maximum number of COMPLETED backups allowed (e.g., 3, 5, unlimited)
- Admin Configurable: Set per-server in admin panel
- Zero Limit: Backups are disabled
- Cannot create new backups
- Must delete existing backups first
- In-progress backups don’t count toward limit
Backups are stored on the daemon node’s disk. Plan storage capacity accordingly based on server sizes and backup limits.
Creating Backups
Create a manual backup:- Navigate to Server → Backups
- Click Create Backup
- Optionally provide a name (e.g., “Pre-Update Backup”)
- Click Create Backup
- Creates a compressed archive of
/home/container - Shows progress in real-time
- Displays backup in the list when complete
backups.create
Backup Naming
If no name is provided, backups are auto-named:- “Before Plugin Update”
- “Working Configuration”
- “Pre-Migration”
Backup Status
Backups progress through several states:- IN_PROGRESS
- COMPLETED
- FAILED
- RESTORING
Creating backup…
- Archive is being created
- File system is being scanned
- Compression in progress
- Cannot download or restore yet
Backup Actions
Each completed backup supports multiple actions:Lock/Unlock
Protect critical backups from accidental deletion:- Lock: Click the lock icon on an unlocked backup
- Locked: Backup shows a yellow “LOCKED” badge and cannot be deleted
- Unlock: Click the unlock icon to allow deletion
backups.create (same permission for lock/unlock)
Download
Download a backup to your local machine:- Click Download icon on a completed backup
- System generates a temporary signed download URL
- Browser opens download in new tab
- URL expires after 5 minutes for security
backups.download
Use Cases:
- Local backup storage
- Migration to another host
- Archive important configurations
- Transfer to development environment
Restore
Restore a server to a previous backup state:- Click Restore icon on a completed backup
- Confirm the destructive action
- Server transitions to
RESTORINGstate - Current files are replaced with backup contents
- Server returns to previous state
backups.restore
Restoration Process:
- Server is stopped if running
- Current
/home/containeris deleted - Backup archive is extracted to
/home/container - Server status set to
STOPPED - You can start server after restoration completes
Delete
Remove a backup to free space:- Click Delete icon on an unlocked backup
- Confirm deletion
- Backup is removed from daemon storage
backups.delete
Restrictions:
- Cannot delete locked backups (unlock first)
- Cannot delete in-progress or restoring backups
Backup Information
Each backup displays:Metadata
- Name: User-provided or auto-generated name
- Created: Timestamp when backup was created
- Size: Compressed archive size (B, KB, MB, GB)
- Status: Current state (completed, in-progress, failed)
- Locked: Whether backup is protected from deletion
Size Calculation
Backup sizes depend on:- Server file count and total size
- Compression ratio (varies by file types)
- World/map complexity (for games)
- Small Minecraft server: 50-200 MB
- Large modded server: 500 MB - 2 GB
- Rust server with large map: 1-5 GB
Permissions
Backup management requires these permission nodes:| Permission | Description |
|---|---|
backups.read | View list of backups |
backups.create | Create new backups and lock/unlock |
backups.delete | Delete unlocked backups |
backups.restore | Restore server from backup |
backups.download | Download backup files |
Permission Examples
View Only:Backup Workflow
Pre-Update Workflow
Regular Backup Schedule
Establish a backup routine:- Daily Backups: Create backup before significant play sessions
- Pre-Event Backups: Before large events or tournaments
- Configuration Backups: After successful configuration changes
- Migration Backups: Before hardware or location changes
Future StellarStack versions will support automated scheduled backups (e.g., daily at 3 AM). Currently, backups are manual only.
Storage Considerations
Daemon Storage
Backups are stored on the daemon node’s filesystem:- Each server with 3 backup limit needs ~3x server size
- Example: 1 GB server × 3 backups = 3 GB backup storage
- 10 servers × 3 GB = 30 GB total backup storage needed
Cleanup Strategies
Manual Cleanup:- Delete old backups when limit is reached
- Prioritize keeping:
- Locked backups
- Recent backups
- Pre-update backups
- Keep last 3 backups
- Delete oldest when creating new backup
- Lock critical snapshots to exclude from rotation
Troubleshooting
Backup Creation Fails
Symptoms:- Backup stuck in
IN_PROGRESS - Backup transitions to
FAILED - Error in daemon logs
-
Insufficient Disk Space
- Check daemon node disk usage
- Free up space or expand storage
- Delete old backups
-
Permission Issues
- Daemon cannot read server files
- Check Docker volume permissions
- Review daemon logs for details
-
Large File Count
- Servers with millions of files (e.g., databases)
- Backup takes very long (appears stuck)
- Wait for completion or exclude large directories
Cannot Download Backup
Symptoms:- Download link returns 404 or 401
- Download fails immediately
-
Token Expired
- Download tokens expire after 5 minutes
- Generate new download link
- Download immediately after clicking
-
Missing Permission
- User lacks
backups.downloadpermission - Grant permission or contact admin
- User lacks
-
Node Offline
- Daemon node is unreachable
- Wait for node to come online
- Check node status in admin panel
Restore Stuck
Symptoms:- Server stuck in
RESTORINGstate - Restore taking very long
-
Large Backup Size
- Extracting multi-GB backups takes time
- Monitor daemon logs for progress
- Wait for extraction to complete
-
Daemon Issue
- Daemon crashed during restore
- Restart daemon service
- Check daemon logs for errors
- May need to manually set server status to
STOPPED
Best Practices
Backup Before Major Changes
Backup Before Major Changes
Always create a backup before:
- Game version updates
- Plugin/mod installations
- Configuration file edits
- Map/world regeneration
Use Descriptive Names
Use Descriptive Names
Name backups clearly:
- ✅ “Pre-1.20.4-Update (Working)”
- ✅ “After Event Setup”
- ❌ “Backup 1”
- ❌ “Test”
Lock Critical Backups
Lock Critical Backups
Lock backups you’ll need later:
- Working configurations
- Pre-major-update states
- Event-ready setups
Download Important Backups
Download Important Backups
Store critical backups off-server:
- Download to local machine
- Upload to cloud storage (Google Drive, Dropbox)
- Protects against node failure or data loss
Monitor Backup Storage
Monitor Backup Storage
Track daemon disk usage:
- Backups consume significant space
- Delete old backups regularly
- Increase backup limits cautiously