Recovery System
Discord Backups and Recovery for Channels, Roles, and Emojis
Security Bot backs up your server layout on a schedule and saves deleted roles, channels, categories, and emojis. After a nuke, a compromised account, or a mistake, check a preview and restore. It is part of Premium and off until you turn it on.
- Off until you turn it on. Then backups run every 24 hours by default, plus up to 10 manual ones.
- Backups hold server settings, roles (permissions, colors, order), channels and categories with permission overrides, custom emojis, and each member's roles.
- Recently deleted keeps each deleted role, channel, category, or emoji for 90 days, with who deleted it.
Discord Server Recovery Bot
Security Bot for Discord servers
- Backups
- Every 24 hours by default, newest 7 kept
- Recently deleted
- Kept for 90 days
- Availability
- Premium
Last reviewed 2026-10-12
Recovery coverage
Discord Server Recovery Bot features
Scheduled and manual backups
Automatic backups run every 24 hours by default, or every 6, 12, 48, or 168 hours. The newest 7 are kept (you can set 1 to 14). You can add up to 10 manual backups, 25 in total.
Recently deleted
Each role, channel, category, or emoji deleted while Recovery is on is saved right away, with who deleted it (from Discord's audit log). It stays 90 days, so you can bring back one channel without restoring the whole server.
Restores you check first
A restore starts with a preview of what will be created, changed, reordered, and given back. Then it runs in the background and shows its progress. If you choose, it also deletes channels and roles created after the backup.
Why prevention alone is not enough
Even with tight anti-nuke limits, an attacker gets a few actions in before the punishment fires. A limit of two channel deletes still means two channels are gone. Staff mistakes are not attacks at all, and no limit stops an admin from deleting the wrong category.
Recovery turns those events from a rebuild into a restore. It matters most for communities with dozens of channels, complex permission overrides, and role setups that took months to get right.
How Security Bot recovery works
Recovery is off until an administrator turns it on. Use the switch on the Recovery page in the dashboard, or run /recovery enable. Nothing is saved before Recovery is on.
From then on, Security Bot keeps two kinds of data. Backups are point-in-time copies of the server layout. They are taken on the schedule you choose, and whenever you take one by hand in the dashboard or with /recovery backup.
Recently deleted saves each role, channel, category, or emoji at the moment it is deleted, with who deleted it. It keeps each item for 90 days.
To restore, pick a backup or items from Recently deleted and check the preview. It lists each step: roles, categories, and channels to recreate, items to put back, order changes, and how many members get a role back.
Steps that would touch a role above Security Bot's highest role are marked as blocked. Start the restore and it runs in the background, shows its progress, and can be cancelled. A backup restore first takes a safety backup of the current state, unless you turn that off.
Recovery and anti-nuke work together
When anti-nuke or Beast Mode punishes someone, Recovery records an incident. The newest backup from before the incident is kept, so automatic cleanup never deletes it. Automatic backups also pause for 2 hours, so a damaged layout does not replace good backups.
Turn on Restore automatically after anti-nuke, and Recovery puts back everything the punished user deleted in the last 30 minutes. Nobody has to run a command, and restored roles go back to the members who had them.
Restore fixes structure and roles, not bans. Members banned during a nuke have to be unbanned, which is why a low anti-nuke ban limit matters.
The stack works in order. Verification and anti-raid keep attackers out. Anti-nuke and Beast Mode stop the ones with permissions. Logs show what happened, and Recovery puts the server back.
What a restore covers and what it does not
A backup restore can recreate missing roles, categories, and channels of every type, with their permission overrides. It can put changed roles, channels, overrides, and @everyone back, and restore the saved order of roles and channels.
It can also re-upload deleted emojis and restore server settings such as the name, icon, verification level, and system channels. It gives recreated roles back to members who had them and are still in the server.
On by default: recreating, reordering, re-uploading emojis, and giving roles back. Options you turn on: putting changed items back, server settings, and deleting channels and roles created after the backup.
Some things are outside Recovery. Know them before an incident to avoid confusion during one. Messages are not restored. Recreated roles, channels, and emojis are new objects with new IDs, and emoji re-upload is best effort.
Announcement, stage, and media channels can only be recreated while the server has Community enabled. A forum channel that cannot be recreated as a forum comes back as a text channel. Restoring server settings does not change the server description.
Roles above Security Bot's highest role cannot be changed or moved, so keep its role at the top. Member roles are saved for servers up to 50,000 members.
Bans are not reversed. Anything deleted before Recovery was on, or inside a category you ignore with /recovery whitelist add, cannot be restored.
Recovery by server type
A small community with a dozen channels and five roles can rebuild by hand in an hour. The question is whether that hour, and remembering every permission override, is worth $4.99 a month.
Usually the overrides decide it. If you have private channels, a staff category, and a verification gate, a manual rebuild gets details wrong for weeks. If your server is a general channel and a voice channel, keep anti-nuke tight and spend the money elsewhere.
A public gaming or creator server may have a hundred channels, dozens of roles, and a permission model that took months to get right. That is exactly what the module exists for.
Keep the anti-nuke channel and role delete limits at two, with ban as the punishment. Then you lose at most two of each before the attacker is stopped. Turn on Restore automatically after anti-nuke so Recovery puts those back without waiting for an administrator.
Take a manual backup before any large restructure. Turn Recovery on in a test server, delete a channel, and restore it once. Then the administrators who will run it have seen it work before they need it at 3 a.m.
For a network of servers, the multi-server slots make sense: three servers for $12.99 a month or seven for $24.99.
A network shares staff, so it shares compromised accounts. Every server in it needs Recovery turned on. Each server turns it on separately and has its own backups and restores.
Decide which two administrators per time zone run restores, the same people who hold lockall. Pin one message in each staff channel saying who restores, who unbans, and where the security log is.
Incident runbook: the first hour
Stop the attacker before you restore anything. Strip the responsible account's roles or ban it. If a bot did the damage, kick the bot. Run /lockall and pause invites in Server Settings > Invites so nothing else changes while you work.
Then open Discord's audit log and filter by the attacker. Note every deleted channel and role, every ban, and any webhooks or bots they created. Delete those webhooks and bots now. Restoring while the attacker's tools are still in the server just gives them a fresh target.
With the server locked and the account handled, open the Recovery page. If Restore automatically after anti-nuke was on, check what it already put back. For a few missing items, restore them from Recently deleted.
For wider damage, pick the newest backup from before the attack, which Recovery keeps after an anti-nuke incident. Read the preview and start the restore. Include putting changed items back if the attacker renamed or edited things.
Compare the result with your audit log notes. Then find the bans from the attack window in Discord's audit log, filtered by Ban Member, and revoke them. Only then run /unlockall, which reopens the channels Security Bot locked. Resume invites and post a short note to members about what happened.
Before the day ends, close the hole. Turn on Discord's 2FA requirement for moderation and remove Administrator from everyone but the owner. Check that Security Bot's role is above every staff role. Confirm the anti-nuke limits and Beast Mode limit would have caught this attack sooner.
Have the compromised account reset its password, which logs out every device. Report the account through Discord's report form with the audit log entries. Write one paragraph in the staff channel: who, when, how they got in, and what changed. That note helps the team spot the same attack next time.
Keeping Recovery ready
Recovery only helps if it was on before the damage. Turn it on as soon as the server has Premium and take a first backup by hand. Note in your staff channel when it was turned on and by whom.
Check now and then that new automatic backups appear in the dashboard or in /recovery backups. Once a quarter, delete and restore a test channel alongside the Beast Mode simulator drill so the procedure stays familiar.
Ignore categories whose channels you never want back, such as ticket channels a bot creates and deletes all day. Use /recovery whitelist add or Ignored categories on the Recovery page, so backups and Recently deleted stay readable.
Keep the rest of the stack in a state where there is less to restore. Low channel and role delete limits, Beast Mode with a realistic limit, and Anti Bot Add on mean an attacker gets a few actions instead of dozens.
Recovery is the last layer. The less the earlier layers let through, the shorter the restore and the fewer members you have to unban afterwards.
Setup
How to set up Discord Server Recovery Bot
Steps that list a command can also be done in Discord. On Premium, settings commands such as /setlimit and /whitelist reply with a dashboard link instead.
Step 1: Activate Premium on the server
Recovery is a premium module. Assign a premium slot to the server from your account dashboard. Then add the Premium Bot, the separate bot that runs the premium modules. Settings from the free bot do not carry over.
Step 2: Turn on Recovery
Use the switch on the Recovery page, or run the command below as an administrator. Nothing is saved before you turn it on.
Command:
/recovery enableStep 3: Choose the backup schedule
Automatic backups run every 24 hours by default and keep the newest 7. On the Recovery page, change the interval (6, 12, 24, 48, or 168 hours) and how many to keep (1 to 14). Also decide whether to restore automatically after anti-nuke.
Step 4: Ignore temporary categories
If a bot creates and deletes channels all day, such as ticket channels, ignore that category. Its channels are then left out of backups and Recently deleted.
Command:
/recovery whitelist addStep 5: Take a first backup
Take a manual backup now so you have one before the first scheduled run, and again before any large change.
Command:
/recovery backupStep 6: Restore after an incident
Pick a backup or items from Recently deleted, check the preview, and start the restore. It runs in the background and shows its progress on the Recovery page.
Command:
/recovery restoreStep 7: Unban members and review the log
Find bans from the attack window in Discord's audit log, filtered by Ban Member, and revoke them. Use the security log to see who Security Bot punished.
Command reference
Discord Server Recovery Bot commands
Slash commands you can run in Discord. Moderation commands work on every plan; on Premium, settings commands reply with a dashboard link instead.
| Command | What it does |
|---|---|
/recovery enablePremium | Turn Recovery on: start automatic backups and saving deleted items. |
/recovery disablePremium | Turn Recovery off: stop taking backups and saving deleted items. |
/recovery statusPremium | Show Recovery's current status and latest backup. |
/recovery backup [name]Premium | Take a manual backup now. |
/recovery backupsPremium | List the saved backups. |
/recovery restore [backup]Premium | Show the restore plan for a backup, with a button to confirm and start it. |
/recovery view typePremium | List recently deleted items of one type with their IDs. |
/recovery role idsPremium | Restore deleted roles from Recently deleted by ID, separated by spaces. |
/recovery text idsPremium | Restore deleted text channels by ID. |
/recovery voice idsPremium | Restore deleted voice channels by ID. |
/recovery category idsPremium | Restore deleted categories by ID. |
/recovery emoji idsPremium | Re-upload deleted custom emojis by ID (best effort). |
/recovery whitelist add categoryPremium | Leave a category's channels out of backups and Recently deleted. |
/recovery whitelist remove categoryPremium | Stop ignoring a category. |
/recovery whitelist viewPremium | List the ignored categories. |
Guides
Recovery guides
Step-by-step articles that go deeper on discord server recovery bot setups and problems.
Questions
Discord Server Recovery Bot FAQ
Common questions about Discord Server Recovery Bot use cases, coverage, and setup.
What can Security Bot recovery restore?
From a backup: roles, categories, and channels of every type with their permission overrides, custom emojis, server settings, the order of roles and channels, and which members had which roles. From Recently deleted: single roles, channels, categories, or emojis. Either way, Recovery has to be on before the damage.
Can it restore deleted messages?
No. Discord does not allow bots to restore deleted messages. Recovery restores structure and member roles.
Is recovery free?
No. Recovery is part of Premium at $4.99 per month per server and runs on the Premium Bot.
Does it restore banned members?
No. Recovery recreates roles, channels, categories, and emojis and gives roles back to members still in the server. Banned members must be unbanned separately. Discord's audit log, filtered by Ban Member, shows the bans from the attack.
Does Recovery take scheduled backups?
Yes, once it is on. Automatic backups run every 24 hours by default, or every 6, 12, 48, or 168 hours. The newest 7 are kept (you can set 1 to 14). You can also take up to 10 manual backups. A server keeps 25 at most.
What if something was deleted before I turned Recovery on?
It cannot be restored. Recovery saves nothing until it is on, so turn it on as soon as the server has Premium and take a manual backup right away.
Can I restore the whole server at once?
Yes, from a backup: on the Recovery page, or with /recovery restore, which shows the plan and a button to confirm. The restore runs in the background with progress.
Can Recovery undo a nuke automatically?
Yes, if you turn on Restore automatically after anti-nuke. When anti-nuke punishes someone, Recovery puts back what that user deleted in the last 30 minutes and gives restored roles back to their members.
Are there things a restore cannot change?
Roles above Security Bot's highest role cannot be changed or moved. The preview marks those steps as blocked. Recreated items get new IDs, and emoji re-upload is best effort.
Related
Explore more Security Bot features
Ready to protect your Discord server with Security Bot?
Add Security Bot to your server to get started with Discord Server Recovery Bot. Anti-raid, anti-spam, and the other Premium modules run on a separate bot; the Premium page explains how to add it.