Backing up and restoring the server

Make a copy of the server or its emojis, automatically or on demand, and put it back after a raid or a mistake.

3 min read Updated October 11, 2026

A backup is a copy of your server that you can put back later: after a raid, a wrong move, or to start again from a clean setup. There are two kinds of backups:

server: the roles, the channels and their permissions, the server's settings and the members' roles;
emojis: the server's emojis.

Backups are kept for the bot's owners.

In short

+backup serveur before-redesign makes a copy of the server.
+autobackup serveur 7 makes one automatically every 7 days.
If something goes wrong: +backup load serveur before-redesign.

Making a backup

+backup serveur my-name copies the server;
+backup emoji my-name copies the emojis.

The name is then used to load, show or delete the backup; it can't contain a /. If a backup already has that name, the bot asks you to confirm before replacing it.

Automatic backups

+autobackup serveur 7 takes a server backup every 7 days (+autobackup emoji 30 for emojis). The bot keeps the last two; they show in +backup list. +autobackup serveur off stops them, without erasing those already made.

Seeing and managing backups

+backup list serveur (or emoji) lists your backups, automatic ones included, with their date;
+backup show serveur my-name shows what it contains, without changing anything;
+backup delete serveur my-name deletes it, permanently.

Putting a backup back

+backup load serveur my-name compares the backup with the server as it is, and only changes what differs: a deleted channel is recreated, an edited role gets its settings back, what hasn't moved isn't touched.

Before starting, the bot shows a restore plan:

what it is going to do, and the estimated time;
the categories to apply: roles, channels, members' roles, server settings. Remove what you don't want put back;
notes, for example the roles placed above the bot's role, which it can't touch.

Click Apply to start, or Cancel. The bot shows its progress, then the result. If it couldn't put everything back (a missing permission, a Discord limit…), it says so: run the load again, only what is missing is done again.

Before loading

The bot's role must be at the very top of the role list, to put every role back.
The bot needs the permissions to manage roles and channels.
If the channel where you started the load is deleted along the way, the bot sends you the result elsewhere.

Emojis

+backup load emoji my-name only adds the missing emojis, and renames those whose name changed. Discord limits emoji creation to about 50 per hour, and the server needs free slots: if there aren't enough for all of them, the bot offers to create only some.

Two tools to tidy up

+sync aligns the permissions of the channel you're in with its category's; +sync #channel targets another channel, a category targets all its channels, +sync all every channel of the server.
+clear duplicate invite deletes duplicate invites: for each creator and each channel, only one is kept, preferably a permanent one.

If it doesn't work

"Pre-flight check failed": the bot lists what prevents it from starting (often a missing permission); fix it and try again.
Some roles aren't put back: they are above the bot's role; move its role to the very top.
"This backup could not be read": its file may be damaged; try another backup, an automatic one for example.

Every command

Each command of this guide, with its arguments, its default level and examples: Backups.