Calagopus supports server backups with pluggable storage backends. Backups can be taken manually at any time or created automatically via schedules. Each server has a backup limit set by an admin, and backups can optionally be locked to prevent accidental deletion.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/calagopus/panel/llms.txt
Use this file to discover all available pages before exploring further.
Creating a backup
Add ignored files (optional)
Enter any file paths or glob patterns to exclude from the backup. For example,
logs/*.log to skip log files.If you have reached your server’s backup limit, the Create button is disabled. Ask an admin to raise your limit or delete an existing backup first.
Backup list
The backup list shows all backups for the server. Each row displays:| Column | Description |
|---|---|
| Name | The backup name you provided |
| Checksum | SHA-256 hash of the backup archive, useful for integrity verification |
| Size | Compressed size of the backup |
| Files | Number of files included |
| Created | Timestamp of when the backup completed |
| Locked | Whether the backup is protected from deletion |
Restoring a backup
Open the context menu
In the backup list, click the actions menu (three dots) on the backup you want to restore.
Choose restore options
- Truncate directory: When enabled, all existing files in the server’s working directory are deleted before the backup is extracted. When disabled, the backup contents are overlaid on top of the existing files.
- Restore startup: When enabled (and if the backup contains startup metadata), the server’s startup command and Docker image are also restored to the state captured in the backup.
Backup configurations
Backup configurations define where backups are stored. They are created by admins and assigned to nodes or individual servers. A server inherits its backup configuration from its node, which in turn inherits from its location — unless a specific configuration is assigned at a lower level.Backup storage types
- Local
- S3-compatible
- Restic
Backups are stored directly on the Wings node’s filesystem in a directory managed by the daemon. No additional configuration is required. This is the default when no backup configuration is set.
Creating a backup configuration
Fill in storage-specific settings
For S3, provide the access key, secret key, bucket, region, endpoint, and part size. Enable Using path-style URLs if your provider requires it (common with MinIO and Cloudflare R2).For Restic, provide the repository URL and any environment variables your Restic backend requires (for example, credentials for an S3-backed Restic repository).
Set sharing (optional)
Enable Shared if backups on this configuration are stored in a location accessible by all nodes (for example, a shared NFS mount or a common S3 bucket). This allows backup transfers between nodes without copying data.
S3 settings reference
| Field | Description |
|---|---|
| Access Key | The S3 access key ID |
| Secret Key | The S3 secret access key |
| Bucket | The name of the S3 bucket |
| Region | The AWS region or provider-specific region string |
| Endpoint | The S3-compatible endpoint URL (omit for native AWS S3) |
| Part Size | Multipart upload chunk size in bytes. Default is 1 GB |
| Using path-style URLs | Use endpoint/bucket/key URLs instead of bucket.endpoint/key. Required for MinIO and some other providers |
Maintenance mode on a backup configuration prevents new backups from being created while allowing existing ones to be read and restored.