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

# Server Backup

> Save an encrypted snapshot of everything Vetox stores for your server, export it, and restore it here or into another server. Max tier.

Backup saves everything **Vetox** stores for your server into one encrypted snapshot, so a bad configuration change, a departing admin or a mistake never costs you your setup.

<Info>
  Requires **Max** premium. Max, Max+, Black and Black+ all qualify. Below that the entire page is replaced by pricing — no backup data is shown or reachable.
</Info>

## What is and is not saved

<CardGroup cols={2}>
  <Card title="Saved" icon="circle-check">
    Every Vetox setting and record for this server — Auto-Mod, Leveling, Welcomer, Logging, Tickets, Applications, Starboard, Giveaways, Battle Pass, Streaks, notifications, embeds, panels and the rest.
  </Card>

  <Card title="Not saved" icon="circle-xmark">
    Anything that belongs to **Discord** — your channels, roles, permissions, messages, emojis and members. Vetox cannot read or recreate those.
  </Card>
</CardGroup>

<Warning>
  **A backup is not a copy of your Discord server.** Restoring it will not recreate a deleted channel or role. It restores Vetox's configuration and points it back at whatever channels and roles exist at that moment.

  Delete a channel and restore a backup, and the setting that used it will simply have nothing to point at.
</Warning>

## Two copies, and why

Your server always holds up to two snapshots.

| Copy               | Who controls it | When it changes                                            |
| ------------------ | --------------- | ---------------------------------------------------------- |
| **Current backup** | You             | Every time you press Backup now                            |
| **Protected copy** | Vetox           | Only once your current backup is at least **24 hours old** |

The protected copy exists for one specific scenario: somebody with access wrecks your server and immediately presses Backup now, hoping to overwrite the good snapshot with the ruined one.

<Note>
  They can overwrite your **current** backup. They cannot touch the protected copy, because it only accepts a snapshot that has already survived a full day. Elapsed time is the one thing an attacker cannot fake.
</Note>

So the worst case is losing up to a day of configuration changes — never your whole setup.

## Backup now

One button. The snapshot is built, compressed, encrypted and stored, and the page updates when it lands.

| Restriction | Value                   |
| ----------- | ----------------------- |
| Per server  | Once every **12 hours** |
| Per person  | **5** per day           |

<Note>
  If nothing has changed since your last backup, Vetox tells you so and keeps the existing snapshot rather than writing an identical one. This does not consume your 12-hour window unfairly — it is simply a no-op.
</Note>

### Size limits

|                      | Max       | Black      |
| -------------------- | --------- | ---------- |
| Backup size          | **25 MB** | **100 MB** |
| Items per collection | 50,000    | 50,000     |

<Warning>
  If a server exceeds either limit, the backup is still created but marked **truncated**, and the page says so. A truncated backup is missing data — a restore will not return the server to its exact previous state.

  These ceilings are generous: a compressed snapshot of a very active server is normally well under a megabyte.
</Warning>

## Export

Export downloads the snapshot as a single `.vetoxbackup` file you can keep anywhere.

<Warning>
  **The file is encrypted with a key only Vetox holds.** You cannot open it, read it, or edit it, and no other software can import it. It is only useful when handed back to Vetox.

  This is deliberate: the file contains your entire server configuration, so it must be worthless to anyone who obtains a copy of it.
</Warning>

Any tampering — a changed byte, a spliced header, a file from a different system — is detected and the file is refused on import rather than partially applied.

| Restriction   | Value                            |
| ------------- | -------------------------------- |
| Per server    | **10** per hour                  |
| Per person    | **20** per hour                  |
| Download link | Valid **60 seconds**, single use |

<Note>
  There is a single **Export** button, and it always hands you the protected copy when one exists, falling back to your current backup only before the first protected copy has been created. If your current backup is the ruined one, the protected copy is the file you want.
</Note>

## Restore

Upload a backup file and Vetox shows you **exactly** what would change before anything is written.

<Steps>
  <Step title="Choose the file">
    Vetox verifies it is a genuine, untampered Vetox backup and reads which server it came from.
  </Step>

  <Step title="Read the preview">
    You are told how many items will be restored, how many roles and channels were matched by name, how many references could not be matched, and what will be skipped.
  </Step>

  <Step title="Confirm">
    You press **Confirm restore**. Nothing is written before that, and the restore then runs in the background — the page reports when it finishes.
  </Step>
</Steps>

<Note>
  Immediately before overwriting, Vetox takes a rollback snapshot of the server's current state and keeps it for **7 days**, so a restore you regret is itself reversible.
</Note>

<Warning>
  Restore **replaces**, it does not merge. Settings in the backup overwrite what is there now.
</Warning>

Restore is limited to **3 per server per rolling day**, counted on restores that actually ran. Uploading a file, changing your mind, or an attempt that fails before the restore starts all cost nothing.

### Into the same server

Everything in the snapshot is restored as-is. This is the ordinary "undo my mistake" case.

### Into a different server

Both servers must have an eligible subscription — the one the file came from, and the one you are restoring into.

Two things change automatically:

<AccordionGroup>
  <Accordion title="Roles and channels are matched by name">
    A backup from another server refers to IDs that do not exist where you are restoring. Vetox matches each one to a role or channel with the **same name** in the destination.

    Anything with no name match is removed from that setting rather than left pointing at nothing. The preview tells you how many.

    Rename your channels and roles to match **before** restoring and far more will carry across.
  </Accordion>

  <Accordion title="Member data is skipped entirely">
    Ten kinds of record belong to the original server's members and are never copied: tickets, ticket staff preferences, starboard entries, giveaway entries, application submissions, Battle Pass progress, quest completions, streaks, moderation history and Temp Voice preferences.

    Copying another community's members into your server would be both a privacy breach and meaningless data. Your configuration transfers; their members' records do not.
  </Accordion>
</AccordionGroup>

## Who can use it

Viewing the page follows your normal dashboard access. **Creating, restoring and deleting** backups is deliberately narrower:

* The **server owner**
* The person who **bought the subscription**
* Anyone granted the **Backup** section in [Access Control](/en/server-management/dashboard-permissions)

<Note>
  A moderator with dashboard access cannot touch backups unless you explicitly grant them the Backup section. That is the point — the backup system is the last line of defence, so it does not inherit ordinary staff permissions.
</Note>

## Deleting a backup

The danger zone deletes your **current** backup only. The protected copy is kept, and remains exportable and restorable.

There is no way to delete the protected copy from the dashboard.

## When premium ends

<Warning>
  The moment a server stops being eligible — expiry, cancellation, downgrade below Max, or a transfer away — **the entire Backup page becomes inaccessible.** No viewing, no export, no restore, no download.
</Warning>

Your snapshots are **kept for 30 days**, then permanently deleted.

| When you resubscribe | Result                                       |
| -------------------- | -------------------------------------------- |
| Within 30 days       | Everything is exactly as you left it         |
| After 30 days        | The backups are gone and cannot be recovered |

<Note>
  If you are letting a subscription lapse and want to keep your configuration, **export the file before it expires.** Once the page locks you can no longer download anything, and an exported file has no expiry.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Backup now is greyed out with a countdown">
    You are inside the 12-hour per-server window. The countdown shows when it reopens.
  </Accordion>

  <Accordion title="It said nothing changed">
    The new snapshot was byte-identical to the stored one, so Vetox kept the existing file. Your backup is current.
  </Accordion>

  <Accordion title="The backup is marked truncated">
    The server exceeded the size or item ceiling for its tier and some data was left out. Black raises the ceiling from 25 MB to 100 MB.
  </Accordion>

  <Accordion title="The protected copy has not updated">
    Working as designed. It only accepts a current backup that is at least 24 hours old.
  </Accordion>

  <Accordion title="The file was rejected as not a valid Vetox backup">
    The file was modified, truncated, or produced by something other than Vetox. A backup file cannot be repaired — export a fresh one.
  </Accordion>

  <Accordion title="Most settings came across empty after a cross-server restore">
    The destination has different channel and role names, so there was nothing to match. Rename them to match the source and restore again.
  </Accordion>

  <Accordion title="Member data did not transfer between servers">
    Expected and permanent. Member-scoped records are never copied between servers.
  </Accordion>

  <Accordion title="The stored file is missing">
    The snapshot could not be found on disk and cannot be restored. Create a new backup, and contact support if it recurs.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Access Control" icon="user-lock" href="/en/server-management/dashboard-permissions">
    Grant the Backup section to someone other than the owner.
  </Card>

  <Card title="Feature limits" icon="list-check" href="/en/premium/feature-limits">
    Every tier limit in one table.
  </Card>

  <Card title="Dashboard Watcher" icon="desktop" href="/en/server-management/dashboard-watcher">
    See who changed what before you decide to restore.
  </Card>

  <Card title="Premium overview" icon="crown" href="/en/premium/overview">
    What Max and Black include.
  </Card>
</CardGroup>