> For the complete documentation index, see [llms.txt](https://docs.drakodevelopment.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drakodevelopment.net/core-features/backup.md).

# Backup

Here’s the basic config you’ll use:

```yaml
Backup:
  Enabled: true          # Turn backups on
  Schedule: 1d           # How often to back up
  MaxBackups: 5          # How many backups to keep
  LogsChannelID: "CHANNEL_ID" # Channel for backup alerts
```

***

### What Each Option Means

* **Enabled**
  * Turns the backup system on or off.
  * Use `true` to activate, `false` to stop it.
* **Schedule**
  * How often backups happen.
  * Examples:
    * `30m` → every 30 minutes
    * `2h` → every 2 hours
    * `1d` → once a day
    * `7d` → once a week
* **MaxBackups**
  * The maximum number of backups saved. Old ones get deleted automatically.
  * Good rule of thumb:
    * Small servers → 3–5 backups
    * Big servers → 2–3 (they take up more space)
* **LogsChannelID**
  * The channel where you’ll see backup notifications.
  * To set this up:
    1. Right-click the channel you want.
    2. Copy its **ID**.
    3. Replace `CHANNEL_ID` with that number.
  * Leave it as `CHANNEL_ID` if you don’t want notifications.

***

Here’s the basic config you’ll use:

```yaml
Backup:
  Enabled: true          # Turn backups on
  Schedule: 1d           # How often to back up
  MaxBackups: 5          # How many backups to keep
  LogsChannelID: 123456789012345678   # Channel for backup alerts
```

***

### What Gets Backed Up?

When backups run, they include:\
✅ All channels & categories\
✅ Permissions & settings\
✅ All roles + permissions\
✅ Members, roles, and nicknames\
✅ Up to **50 messages per channel**

But note:\
❌ Images & attachments\
❌ Voice recordings\
❌ Server boosts, emojis, integrations\
…are **not** saved.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.drakodevelopment.net/core-features/backup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.