-
Notifications
You must be signed in to change notification settings - Fork 0
Server Backup
Snapshot your server's structure and restore it after a nuke or an accident.
View this page in the localized AntiLink documentation
Server Backup saves a snapshot of your server as it is - so you can rebuild it if a nuke, a rogue admin, or an accident destroys it. It is the recovery companion to Anti-Nuke: Anti-Nuke tries to stop the damage, Backup lets you undo what got through.
Info
Restore is additive and safe: it recreates whatever is missing and never deletes or changes what is already there. A restore can never itself wipe a server. Server Backup is AntiLink Premium and off until you take your first backup.
You choose exactly what each backup includes - tick any of these (someone who only wants their roles can back up just roles):
- Roles & permissions - all roles (name, color, permissions, hoist, mentionable) and order
- Channels & categories - every channel/category (topic, NSFW, slow-mode, voice bitrate/limit) and their permission overwrites
- Server settings - name, icon, banner, verification level, content filter, AFK and system channels, notification level
- Ban list
- Emoji and Stickers - the images are stored and re-uploaded on restore
- Message archive - the recent messages of each channel
Never saved: members (they must rejoin), and anything secret - no tokens, no webhook URLs. A backup is safe to keep.
Warning
About messages: Discord does not let any bot recreate a message as its true original author (with the original ID, reactions, and edit history) - no security bot can, Wick and ProBot included. So the message archive is restored by re-posting each message through a webhook that mimics the author's name and avatar. It looks like the original, but it is a labelled archive, not a perfect restore. Everything else - structure, settings, emoji, stickers, bans - restores faithfully.
Restore matches by name + type. For each role/category/channel in the backup:
- If one with the same name already exists, it is left alone and reused.
- If it is missing, it is recreated - with its permissions and overwrites remapped onto the rebuilt roles.
So restoring after a nuke recreates exactly the roles and channels that were deleted, without touching anything that survived. Running a restore twice is safe - the second run sees everything already exists and does nothing.
Warning
The bot can only recreate roles below its own highest role, and only grants permissions it holds itself. Keep AntiLink's role near the top so a restore can rebuild your full role list. Restore does not move roles/channels back to their exact old positions - it recreates them; you may need to reorder a few.
Run /backup create (optionally /backup create name:before-the-event), or use the
dashboard Backups tab. Take one whenever your server is in a good state - and again
before any risky change. The newest 10 backups are kept per server.
/backup list shows your saved backups; /backup info id:<id> shows what one contains.
/backup restore id:<id> confirm:True (owner only) recreates the missing roles and
channels. In the dashboard, open Backups, click Restore on the one you want, and
confirm. The bot needs Manage Roles and Manage Channels.
A backup is not tied to the server it came from - you can restore it into another server you manage, which makes Server Backup a clone / template tool. In the dashboard Backups tab of the destination server, open Clone from another server, pick a server you manage that has a backup, pick the backup, and confirm. AntiLink checks that you manage both servers and that the destination is AntiLink Premium, then recreates the source's roles, channels, permissions and content in the destination.
| Command | What it does |
|---|---|
/backup create name: [roles:] [channels:] [settings:] [bans:] [emoji:] [stickers:] [messages:] |
Take a snapshot - tick what to include |
/backup list |
List saved backups |
/backup info id: |
Show what a backup contains |
/backup restore id: confirm: |
Restore a backup - owner only |
/backup delete id: |
Delete a saved backup |
The dashboard Backups tab does the same, with a checkbox per type, a one-click Restore (confirmation required), Delete, and the cross-server Clone. Both are backed by the same backups, so it does not matter where you create or restore them.
Creating, listing and deleting backups needs Manage Server. Restore is owner-only (or the AntiLink team) - because it recreates structure, a plain admin cannot trigger it, which keeps a compromised moderator from abusing it. A cross-server clone additionally requires that you manage the source server too.
- AntiLink Premium on the server (Server Backup is a top-tier feature end to end).
- To restore, the bot needs Manage Roles and Manage Channels, and its role must sit above the roles it recreates. The extras also need the matching permission at restore time: Manage Server (settings), Manage Expressions (emoji/stickers), Ban Members (bans), and Manage Webhooks (the message archive). Any part the bot cannot do is simply skipped - the rest still restores.
Website | Dashboard | Documentation | Status | Support