Server Backup Phantom Pro

Snapshots your server's structure — roles, channels, categories, channel overwrites, server settings, emoji — into a single restorable record. The recovery side of the security suite.

Not yet generally available

Server Backup is finished but still held back while snapshot storage limits and restore throttling are hardened — a bad restore rewrites every role and channel in a server, so this one ships slowly. The page is hidden from the sidebar and shows a "coming soon" notice until it opens up. Everything below describes how it behaves when it does.

It will be a Phantom Pro feature.

What gets snapshotted

• Every role: name, colour, permissions, position, mention-able, hoist.
• Every channel + category: name, type, topic, slowmode, NSFW flag, parent, position.
• Per-channel permission overwrites.
• Custom emoji + stickers (metadata; the bot does not store the asset files).
• Server-level settings: name, verification level, AFK channel, etc.

What does NOT get backed up:

• Member roles (those are on each user, not server-state).
• Message history (Discord doesn't expose message-bulk-export to bots).
• Pinned messages.
• Soundboard sounds.

Where it lives

Dashboard: Security → Server Backup.

Backup kinds

Kind	When it's created
manual	An admin clicked "Create backup".
scheduled	Auto-created on a recurring schedule (if configured).
pre_restore	Auto-created the moment before restoring a different backup (the safety net for "I clicked the wrong backup").

Creating a backup

Open the page → Create backup → name it → save.

A backup builds in a few seconds for small servers, up to a minute for very large ones. Status moves: queued → building → ready.

Restoring

Restore is destructive

A restore will recreate / modify roles, channels, and overwrites to match the snapshot. It cannot recover message history or member-role assignments. Always read the diff preview before confirming.

1. Pick a backup → Restore preview.
2. The preview shows the diff: what would be created, deleted, modified.
3. Click Restore → confirm the modal.
4. Phantom auto-creates a pre_restore backup of the current state before applying.
5. The restore runs; status moves: restoring → ready.

Auto-backup schedule

You can configure a recurring schedule (daily / weekly). Each scheduled backup is kept until the per-guild cap is hit; oldest auto-prune.

Limits

• 25 backups per guild (oldest auto-prune above this).
• 8 MB max payload per backup.
• Very large servers (1,000+ channels) may hit the size cap; configure a more focused backup (e.g. role-only) in that case.

Tips

• Backup before risky changes. Big role-permission sweeps, mass channel reorders, integration installs — snapshot first.
• Test a restore in a test server. The restore flow is well-tested but you should know what it looks like before you need it.
• Keep at least one weekly backup retained indefinitely. Use the dashboard's pin / lock toggle to prevent it from being pruned.

Permissions

• security.view — see backup list
• security.edit — create, restore, delete, pin

Behaviour

• Building runs in the background; the dashboard updates as it progresses.
• Restore applies changes to Discord on a best-effort basis with retries.
• If a restore fails mid-flight, your server may be left in a partial state. The auto-created pre_restore backup is your rollback path.

Related pages

• Server Scanner — find issues to fix before restoring
• Anti-Nuke — auto-revert can fix small things; Backup is what you use when it can't
• Audit Log — every restore action is logged