Skip to main content
/backup drives Server Backup from inside Discord. One command, thirteen subcommands, plus /chatlog for backing up a single channel’s messages.
Every /backup reply is ephemeral — only you see it. A backup ID is a key to your server’s contents, so Vetox never posts one where other members can read it.
Only the server owner and members with Administrator can use /backup — Manage Server is not enough, and by default Discord hides the command from everyone else. Command Management can still switch each subcommand off or keep it to particular channels — /backup create can stay on while /backup load is off entirely — but its role settings cannot open /backup to anyone without Administrator.

​
Creating and inspecting

Premium sections are included automatically up to what your plan allows. The reply carries the new backup ID and then updates with progress. When the backup is done, the reply shows the ID, the two commands to use it with (/backup info and /backup load) and a link to the backup in the dashboard — and on Starter, a reminder that messages, member data, bans and attachments were not saved.
One manual backup per server every 10 minutes, and one backup or restore job at a time. Creating needs the Administrator permission, and under the Only the owner permission level the owner alone.
Newest first. Automatic and safety backups are marked so you can tell them apart at a glance. scope:mine lists every backup you created, on any server, with the server it came from — the way to find the ID of a backup you took elsewhere before loading it here.
Titled with the server the backup came from. It shows the ID, the kind, the size, when it was taken and how long it is kept; a count for every section — categories, channels, threads, roles, emojis, stickers, bans, members, messages and pins — including the ones at zero, so “this backup has no messages” is something you can see rather than infer; the options it was captured with; any warnings; and a link to the dashboard’s Snapshot Viewer, where you can read every channel, role, setting, ban and member it holds.A section your plan does not include is marked ⭐ rather than hidden, with a link to what each plan covers.For a backup of this server, the card also draws the backup’s channel tree beside its role list, so you can see the server the backup holds at a glance. Two buttons under it, Load this backup and Delete this backup, take you straight into either flow with its usual confirmation.
backup_id autocompletes on every subcommand that takes one, so you never need to copy an ID by hand. It offers only backups you are allowed to use.

​
Restoring

Nothing is restored on the first press. /backup load asks two questions before it does anything.Step one — what to load. A dropdown lists the eleven parts of a backup, with the five that make up a normal restore already ticked and a one-line note under each saying what it does to your server. Change the ticks if you want, then press Continue — or Cancel and nothing happens.Step two — what will change. Vetox works out the plan for exactly what you ticked: how many channels and roles will be deleted and created, whether any roles sit above Vetox’s own role and so cannot be touched, whether any announcement or stage channels have to be left out, and — under Adapted to this server — what this server cannot take exactly as the backup has it, such as roles past Discord’s limit, emojis beyond its free slots or role icons it has not unlocked. Behind Confirm and Cancel buttons that expire after 60 seconds. Only on Confirm does Vetox take the safety copy and start the restore.
The options argument does the same job in one line, and the two agree — pass it and the dropdown opens with your tokens already applied, so you can adjust from there.
Loading a backup replaces this server’s channels and roles. Members are never kicked, but anything created since the backup was taken will be gone.
/backup load obeys the server’s permission level. Under the default Admins can not take destructive actions, anyone but the owner is refused even with Administrator.
Restores and reverts are rationed daily — 10 per server, 20 per person. /backup load, /chatlog load and reverting a tracked change each count against both; resuming a failed restore does not.
No options. Cancels this server’s active backup or restore. The checkpoint is kept, so a cancelled restore can still be resumed from the dashboard.
No options. Shows the job running on this server (kind, phase, progress, warnings, when it started) or that nothing is running; when the next manual backup is possible if the 10-minute cooldown is active; when Discord’s creation limit lifts if a restore hit it; and, when nothing runs, why the last job stopped — with the phase and progress it reached and the warnings it raised — and whether it can be resumed from the dashboard.

​
The options grammar

options is a space-separated list of tokens, applied left to right. Leave options out entirely and Vetox uses the default: delete-channels channels delete-roles roles settings — a full structural replace, without members, bans, pins, emojis or stickers.
Order matters. * !members turns everything on and then members off. !members * turns members off and then everything back on, including members. Read your token list left to right.
Tokens can never widen what your plan allows — the plan limit is applied last. An unknown token is refused by name rather than ignored, so a typo is never silently dropped.

​
Scheduling

Three separate subcommands, each shown with its own description as you type.show gives the interval, how many are kept, the last and next run, and the ID of the latest automatic backup. Turning the schedule on tells you when the first backup will run. Any change to the schedule counts as creating under the server’s permission level, so under Only the owner only the owner can make one.
An interval shorter than your plan allows is refused, and the refusal names your plan’s minimum in hours. Automatic backups rotate: the oldest beyond the number your plan keeps are deleted as new ones land.

​
/chatlog — channel backups

Backing up one channel’s messages is its own command. Six subcommands, the same requirements as /backup (Administrator, 5s cooldown, every reply ephemeral).
before is how you go further back than one run allows: take a chatlog, then take another with before set to the oldest message ID the first one reached.
Creating needs the Administrator permission, like /backup create.
Only this server’s channel backups, newest first, each showing the channel it came from.
The channel, the message count, the size and when it was taken — with Load and Delete buttons. Load posts it into the channel you are in.
Messages are posted oldest first, with their pins.
Nothing is deleted. The stored messages are added to whatever is already in the channel. A large chatlog takes a while — the reply reports progress as it goes.
delete takes a required chatlog_id; purge takes no options and removes every chatlog of this server. Both ask for Confirm first, and both are destructive actions under the server’s permission level.
/chatlog purge takes only chatlogs. Your server backups are untouched — those are /backup purge.
Channel backups require Basic or above.
These six were /backup channel create and /backup channel load until September 2026. The old subcommands no longer exist.

​
Moving backups

Sends the backup as a Discord-format .json file attached to the ephemeral reply. Above 8 MB you get a dashboard link instead.
Exports carry the server, roles, channels, emojis and stickers. Messages, members and bans are not included — restore the backup to move those. Export works on every plan.
Vetox validates the file, turns it into a backup and replies with its ID. Restore or inspect it like any other.
A file that does not follow Discord’s server format is rejected outright, naming the first field that failed. Vetox never half-applies one.
Import requires Basic or above.

​
Deleting

Asks for Confirm first. Deleting removes the snapshot and every file stored with it, immediately and permanently.
No options. Asks for Confirm, then deletes every backup of this server together with their stored files.
There is no undo and no recycle bin. Export anything you want to keep first.
/backup delete and /backup purge are destructive actions under the server’s permission level, so under the default level they are the owner’s alone.

​
Examples

​
When a command is refused

Vetox always names the reason. The common ones:

Server Backup

The full feature — restoring, schedules, change tracking and Time Machine.

My Backups

Your backups across every server.

Command Management

Disable or restrict each subcommand individually.

Command reference

How permissions and cooldowns work across all commands.