> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vetox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Backup commands

> The /backup command group and /chatlog — create, list, inspect, restore, schedule, export, import and purge your server's backups from Discord.

`/backup` drives [Server Backup](/en/server-management/server-backup) from inside Discord. One command, **thirteen subcommands**, plus [`/chatlog`](#chatlog-channel-backups) for backing up a single channel's messages.

| Requirement     | Value                                                     |
| --------------- | --------------------------------------------------------- |
| **You need**    | Manage Server                                             |
| **Vetox needs** | View Channel, Read Message History — plus more to restore |
| **Cooldown**    | 5s                                                        |
| **Where**       | Servers only. Not available in DMs                        |

<Warning>
  **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.
</Warning>

<Note>
  Each subcommand can be disabled or restricted to particular roles and channels individually, through [Command Management](/en/server-management/command-management). `/backup create` can be open to your admins while `/backup load` is off entirely.
</Note>

## Creating and inspecting

<AccordionGroup>
  <Accordion title="/backup create — take a backup" icon="camera">
    | Option     | Required | Notes                                         |
    | ---------- | -------- | --------------------------------------------- |
    | `name`     | No       | Up to 64 characters. A name makes it findable |
    | `messages` | No       | 0–250, capped at your plan's maximum          |

    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.

    <Note>
      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](/en/server-management/server-backup#permissions) the owner alone.
    </Note>
  </Accordion>

  <Accordion title="/backup list — see your backups" icon="list">
    | Option  | Required | Notes                                                                                            |
    | ------- | -------- | ------------------------------------------------------------------------------------------------ |
    | `page`  | No       | From 1. Twenty rows per page                                                                     |
    | `scope` | No       | **This server** (default), **Channel backups of this server**, or **My backups on every server** |

    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.
  </Accordion>

  <Accordion title="/backup info — what a backup contains" icon="circle-info">
    | Option      | Required | Notes                     |
    | ----------- | -------- | ------------------------- |
    | `backup_id` | **Yes**  | Autocompletes as you type |

    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.

    If you are an administrator, 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.
  </Accordion>
</AccordionGroup>

<Tip>
  `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.
</Tip>

## Restoring

<AccordionGroup>
  <Accordion title="/backup load — restore a backup" icon="rotate-left">
    | Option      | Required | Notes                                                        |
    | ----------- | -------- | ------------------------------------------------------------ |
    | `backup_id` | **Yes**  | Autocompletes, including your own backups from other servers |
    | `messages`  | No       | 0–250, capped at your plan's maximum                         |
    | `options`   | No       | Up to 200 characters. See the grammar below                  |

    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, and whether any announcement or stage channels have to be left out. Behind **Confirm** and **Cancel** buttons that expire after **60 seconds**. Only on Confirm does Vetox take the safety copy and start the restore.

    <Tip>
      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.
    </Tip>

    <Warning>
      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.
    </Warning>

    <Note>
      `/backup load` obeys the server's [permission level](/en/server-management/server-backup#permissions). Under the default **Admins can not take destructive actions**, anyone but the owner is refused even with Administrator.
    </Note>

    <Note>
      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.
    </Note>
  </Accordion>

  <Accordion title="/backup cancel — stop the running job" icon="ban">
    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.
  </Accordion>

  <Accordion title="/backup status — what is running, and any active limit" icon="heart-pulse">
    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 and whether it can be resumed from the dashboard.
  </Accordion>
</AccordionGroup>

### The `options` grammar

`options` is a space-separated list of tokens, applied **left to right**.

| Token                                                                                                      | Effect                   |
| ---------------------------------------------------------------------------------------------------------- | ------------------------ |
| `settings` `roles` `delete-roles` `channels` `delete-channels` `members` `bans` `pins` `emojis` `stickers` | Turns that part **on**   |
| `!` before any of them — `!members`                                                                        | Turns that part **off**  |
| `*`                                                                                                        | Turns **everything** on  |
| `!*`                                                                                                       | Turns **everything** off |

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.

| Example                                  | Result                                                         |
| ---------------------------------------- | -------------------------------------------------------------- |
| `options:!* roles delete-roles`          | Roles only — deletes the current roles, recreates the backup's |
| `options:!* channels roles settings`     | Structure, adding to what is there — nothing is deleted        |
| `options:* !members !bans`               | Everything except member data and bans                         |
| `options:!delete-channels !delete-roles` | The default, made additive                                     |

<Warning>
  **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.
</Warning>

<Note>
  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.
</Note>

## Scheduling

<AccordionGroup>
  <Accordion title="/backup interval — automatic backups" icon="clock">
    Three separate subcommands, each shown with its own description as you type.

    | Subcommand      | Options                                                                                                                                        | Effect                                            |
    | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
    | `interval on`   | `interval` optional (4 hours, 8 hours, 12 hours, 24 hours, 2 days, 3 days, 7 days), `messages` optional (0–250, capped at your plan's maximum) | Turn automatic backups on, or change the schedule |
    | `interval off`  | —                                                                                                                                              | Turn them off                                     |
    | `interval show` | —                                                                                                                                              | Report the schedule without changing it           |

    `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.

    <Note>
      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.
    </Note>
  </Accordion>
</AccordionGroup>

## `/chatlog` — channel backups

Backing up one channel's messages is its own command. Six subcommands, the same requirements as `/backup` (Manage Server, 5s cooldown, every reply ephemeral).

<AccordionGroup>
  <Accordion title="/chatlog create — back up one channel" icon="hashtag">
    | Option     | Required | Notes                                                         |
    | ---------- | -------- | ------------------------------------------------------------- |
    | `channel`  | No       | Text, announcement or thread. Defaults to the current channel |
    | `messages` | No       | 0–1000, capped at your plan's maximum                         |
    | `before`   | No       | A message ID. Stores the messages **before** it               |

    <Tip>
      `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.
    </Tip>

    <Note>
      Creating needs the Administrator permission, like `/backup create`.
    </Note>
  </Accordion>

  <Accordion title="/chatlog list — see your chatlogs" icon="list">
    | Option | Required | Notes                        |
    | ------ | -------- | ---------------------------- |
    | `page` | No       | From 1. Twenty rows per page |

    Only this server's channel backups, newest first, each showing the channel it came from.
  </Accordion>

  <Accordion title="/chatlog info — what one contains" icon="circle-info">
    | Option       | Required | Notes                       |
    | ------------ | -------- | --------------------------- |
    | `chatlog_id` | **Yes**  | Autocompletes chatlogs only |

    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.
  </Accordion>

  <Accordion title="/chatlog load — post them into a channel" icon="paste">
    | Option       | Required | Notes                                          |
    | ------------ | -------- | ---------------------------------------------- |
    | `chatlog_id` | **Yes**  | Autocompletes chatlogs only                    |
    | `channel`    | No       | Where to post. Defaults to the current channel |
    | `messages`   | No       | 0–1000, capped at your plan's maximum          |

    Messages are posted oldest first, with their pins.

    <Note>
      **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.
    </Note>
  </Accordion>

  <Accordion title="/chatlog delete and /chatlog purge" icon="trash">
    `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](/en/server-management/server-backup#permissions).

    <Note>
      `/chatlog purge` takes only chatlogs. Your server backups are untouched — those are `/backup purge`.
    </Note>
  </Accordion>
</AccordionGroup>

<Info>
  Channel backups require **Basic** or above.
</Info>

<Note>
  These six were `/backup channel create` and `/backup channel load` until September 2026. The old subcommands no longer exist.
</Note>

## Moving backups

<AccordionGroup>
  <Accordion title="/backup export — download as JSON" icon="file-export">
    | Option      | Required | Notes         |
    | ----------- | -------- | ------------- |
    | `backup_id` | **Yes**  | Autocompletes |

    Sends the backup as a Discord-format `.json` file attached to the ephemeral reply. Above **8 MB** you get a dashboard link instead.

    <Note>
      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.
    </Note>
  </Accordion>

  <Accordion title="/backup import — build a backup from a file" icon="file-import">
    | Option | Required | Notes                                       |
    | ------ | -------- | ------------------------------------------- |
    | `file` | **Yes**  | A Discord-format server `.json`, up to 5 MB |

    Vetox validates the file, turns it into a backup and replies with its ID. Restore or inspect it like any other.

    <Warning>
      A file that does not follow Discord's server format is rejected outright, naming the first field that failed. Vetox never half-applies one.
    </Warning>

    <Info>
      Import requires **Basic** or above.
    </Info>
  </Accordion>
</AccordionGroup>

## Deleting

<AccordionGroup>
  <Accordion title="/backup delete — delete one backup" icon="trash">
    | Option      | Required | Notes         |
    | ----------- | -------- | ------------- |
    | `backup_id` | **Yes**  | Autocompletes |

    Asks for **Confirm** first. Deleting removes the snapshot and every file stored with it, immediately and permanently.
  </Accordion>

  <Accordion title="/backup purge — delete every backup" icon="dumpster-fire">
    No options. Asks for **Confirm**, then deletes **every** backup of this server together with their stored files.

    <Warning>
      There is no undo and no recycle bin. Export anything you want to keep first.
    </Warning>
  </Accordion>
</AccordionGroup>

<Note>
  `/backup delete` and `/backup purge` are destructive actions under the server's [permission level](/en/server-management/server-backup#permissions), so under the default level they are the owner's alone.
</Note>

## Examples

```text theme={null}
/backup create name:before-rework
/backup list page:1
/backup list scope:mine
/backup info backup_id:GB7K2QX4M1ZP
/backup load backup_id:GB7K2QX4M1ZP options:!* channels roles
/backup status
/backup interval on interval:12h
/backup interval show
/chatlog create channel:#general messages:500
/chatlog list
```

## When a command is refused

Vetox always names the reason. The common ones:

| The reply says                                                                | What to do                                                                                                                                                        |
| ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A backup was created here recently                                            | Wait out the 10-minute per-server creation cooldown                                                                                                               |
| Another backup job is already running                                         | Wait for it, or `/backup cancel`                                                                                                                                  |
| Today's limit for restores and reverts has been reached                       | This server or your account has spent its daily allowance of 10 per server / 20 per person. Try again tomorrow                                                    |
| You have reached your plan's backup limit                                     | Delete one, or upgrade                                                                                                                                            |
| This backup is beyond your plan's limit                                       | It is locked by a downgrade. Delete a newer backup or upgrade                                                                                                     |
| Only people allowed by the server's backup permissions can do this            | The server's permission level leaves this to the owner. The owner acts, or changes the level under Settings → Permissions                                         |
| That interval is shorter than your plan allows                                | Use the minimum the message names, or upgrade                                                                                                                     |
| One of the selected options is not valid                                      | An unknown `options` token — check it against the grammar above                                                                                                   |
| Vetox is missing the permissions it needs                                     | Give Vetox Administrator and move its role above the roles being restored                                                                                         |
| Announcement and stage channels are left out                                  | Discord only allows those in a Community server. Turn Community on in Server Settings and load again to include them — the rest of the backup restores either way |
| Discord allows a bot to create only 250 roles or 500 channels within 48 hours | Discord's own creation limit. `/backup status` shows when it lifts; wait and resume, or load again with `options:!delete-roles !roles`                            |
| That file is not a valid Discord server export                                | The import file does not match Discord's format                                                                                                                   |
| Server Backup is temporarily unavailable                                      | Paused for maintenance. Your backups are untouched                                                                                                                |

## Related

<CardGroup cols={2}>
  <Card title="Server Backup" icon="server" href="/en/server-management/server-backup">
    The full feature — restoring, schedules, change tracking and Time Machine.
  </Card>

  <Card title="My Backups" icon="box-archive" href="/en/members/my-backups">
    Your backups across every server.
  </Card>

  <Card title="Command Management" icon="sliders" href="/en/server-management/command-management">
    Disable or restrict each subcommand individually.
  </Card>

  <Card title="Command reference" icon="terminal" href="/en/commands/overview">
    How permissions and cooldowns work across all commands.
  </Card>
</CardGroup>