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

# Backups

> Snapshot your whole server and restore it if something goes wrong.

A backup captures your server's structure — roles with their permissions and colours, categories, channels with their overwrites and settings, emojis, and member role assignments. If the server gets nuked or you break something rebuilding it, you can restore.

```javascript theme={null}
!backup
```

Opens an interactive menu for creating, browsing and restoring backups.

<Warning>
  Only the **server owner** can use this, and it requires **Administrator**. Restoring rewrites your server's structure, so it's deliberately the most locked-down command in the bot.
</Warning>

## What's captured

| Captured                                              | Not captured              |
| ----------------------------------------------------- | ------------------------- |
| Roles — names, colours, permissions, positions, icons | Message history           |
| Categories and channels, with overwrites              | Members themselves        |
| Channel topics, slowmode, NSFW flags                  | Bans and audit logs       |
| Forum tags and settings                               | Other bots' configuration |
| Emojis                                                | Server boosts             |
| Which members had which roles                         | Invites                   |

Roles are matched back to members on restore, so people get their permissions back rather than starting from nothing.

## Automatic backups

Scheduled backups run on an interval you set through the menu. Up to **10 backups** are kept per server; the oldest is removed as new ones are made.

<Tip>
  Take a manual backup before any large change — a permissions overhaul, a channel restructure, a mass role operation. It costs nothing and it's the difference between an undo and an afternoon.
</Tip>

## Backups vs. antinuke restore

They solve different problems and you want both.

|          | [Antinuke restore](/security/antinuke#restoring-after-an-attack) | Backup                  |
| -------- | ---------------------------------------------------------------- | ----------------------- |
| Covers   | Only what antinuke saw deleted                                   | The whole server        |
| Window   | 1 hour                                                           | Until it's rotated out  |
| Speed    | One button on the alert                                          | Guided restore          |
| Best for | Catching an attack in progress                                   | Anything after the fact |

Antinuke restore is faster and more precise if you catch the attack. Backups are the fallback for everything else — including your own mistakes.

## Command reference

| Command  | Aliases         | Permission                   | Description          |
| -------- | --------------- | ---------------------------- | -------------------- |
| `backup` | `bk`, `restore` | Administrator + server owner | Open the backup menu |