Attach a bot, click Create Backup, then prove it restores.
Before you start
- A custom bot installed in the server — keep its token out of chat (secure it)
- The server added in the dashboard, with the bot able to see the channels you want captured
- An empty Discord server to test restores into
Create the backup
Servers
Search servers
AC
Aurora CommunityOwner
restorecord.com/verify/aurora
Manage
Pull Members
Create Backup
Create Backup opens the snapshot dialog: name, message count, attachment mode, emojis, excluded channels.
The dialog pre-fills a name; rename it after what it protects, like before-permission-redesign. Then set the scope:
- Option
- Messages per channel
- Pick
- The smallest count that meets your goal
- Why
- Higher counts slow both capture and restore
- Option
- Attachment mode
- Pick
- None, Standard (images) or Premium (all files)
- Why
- See pricing and limits
- Option
- Excluded channels
- Pick
- Anything you would not want re-posted
- Why
- Excluded channels are absent from the recovery point
| Option | Pick | Why |
|---|---|---|
| Messages per channel | The smallest count that meets your goal | Higher counts slow both capture and restore |
| Attachment mode | None, Standard (images) or Premium (all files) | See pricing and limits |
| Excluded channels | Anything you would not want re-posted | Excluded channels are absent from the recovery point |
Watch the job to a terminal state. If it fails on permissions or rate limits, fix the cause — do not assume a recovery point exists.
Preview it
The previewer opens the backup as a read-only Discord client, so you can see what was really captured.
Snapshot preview — read-onlyAurora Community · March 4, 14:05
AC
Community
announcements
general
support
Voice Lounge
general
Mira14:02
Snapshot captured before the permission redesign.
Kelan14:04
Roles and overwrites look right in the preview.
Aurora Bot14:05
Backup completed — 42 channels, 18 roles, 6,300 messages.
Online — 3
Mira
Kelan
Aurora Bot
- Check channel order, roles and a few real messages, links and attachments.
- Excluded channels should be absent; a padlock means the bot could not read that channel.
- Pin known-good backups so scheduled rotation cannot delete them.
Test the restore
- Step
- Prepare
- Do this
- Install the same bot in an empty server and drag its role above the roles it must create
- Step
- Restore
- Do this
- Pick the backup, the message count, and whether to clear the destination
- Step
- Measure
- Do this
- Time it and note what was skipped — that is your real recovery time
- Step
- Verify
- Do this
- Channel order, roles, permission overwrites, and that private channels stayed private
| Step | Do this |
|---|---|
| Prepare | Install the same bot in an empty server and drag its role above the roles it must create |
| Restore | Pick the backup, the message count, and whether to clear the destination |
| Measure | Time it and note what was skipped — that is your real recovery time |
| Verify | Channel order, roles, permission overwrites, and that private channels stayed private |
Restored messages are re-posted, not reinstated — Discord cannot recreate a deleted message with its original author and timestamp.
Troubleshooting
- Symptom
- Backup button is greyed out
- Check first
- No custom bot is attached to that server
- Symptom
- Channel missing from the backup
- Check first
- Excluded on purpose, or the bot could not read it — the previewer shows a padlock
- Symptom
- Restore fails on roles or channels
- Check first
- Bot role position and Manage Roles / Manage Channels
- Symptom
- Restore stalls
- Check first
- Discord rate limits — let the task finish instead of starting a second one
- Symptom
- Attachments missing after restore
- Check first
- Attachment mode was None, the file was over 8 MB, or the source file was already deleted
- Symptom
- Roles not applied to members
- Check first
- Members were not pulled back before the role restore ran
| Symptom | Check first |
|---|---|
| Backup button is greyed out | No custom bot is attached to that server |
| Channel missing from the backup | Excluded on purpose, or the bot could not read it — the previewer shows a padlock |
| Restore fails on roles or channels | Bot role position and Manage Roles / Manage Channels |
| Restore stalls | Discord rate limits — let the task finish instead of starting a second one |
| Attachments missing after restore | Attachment mode was None, the file was over 8 MB, or the source file was already deleted |
| Roles not applied to members | Members were not pulled back before the role restore ran |