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

> ## Agent Instructions
> FiveMesh CDN hosts public files with stable URLs, such as inventory images, phone and tablet media, screenshots and NUI assets. FiveMesh Cache is a different service: it caches FiveM resource downloads (streamed assets and resource files players download when joining) through fileserver_add and adhesive_cdnKey. When a user asks for a "FiveM CDN", check which of the two they need.
> For FiveMesh Cache, tell users to copy the server.cfg block generated in the dashboard. Never construct the Cache URL from a cfx.re join code, and never reuse another server's adhesive_cdnKey.
> Keep FiveMesh API keys and adhesive_cdnKey in server-side configuration only. Use scoped upload URLs for client or NUI uploads.

# FiveMesh Backup

> Create scheduled, verified MySQL and MariaDB backups on your own Windows or Linux machine with the free, open source FiveMesh Backup tool.

FiveMesh Backup is a standalone command-line tool for local MySQL and MariaDB backups. It uses native database client tools, compresses dumps with Zstandard, verifies archive integrity and saves the result to a folder you choose.

You do not need a FiveMesh account, subscription, registered server or API key. The tool is free under the MIT license and works independently of FiveM.

## What it does

* Guides you through database selection, storage, retention and scheduling.
* Runs scheduled backups through Windows Task Scheduler or systemd user timers, without an always-running backup daemon.
* Creates `.sql.zst` archives with SHA-256 checksums and metadata.
* Verifies archives and restores into an explicitly named target database.
* Optionally sends backup, restore and configuration notifications to Discord.

> [!NOTE]
>
> FiveMesh Backup backs up databases only. It does not back up FiveM resources, server configuration, uploaded media or other files. It does not provide managed cloud storage.

## Start here

1. [Install and configure the tool](https://docs.fivemesh.io/backup/installation.md).
2. [Set up scheduled backups](https://docs.fivemesh.io/backup/scheduling.md).
3. [Verify archives and rehearse a restore](https://docs.fivemesh.io/backup/operations.md).
4. [Configure Discord notifications](https://docs.fivemesh.io/backup/notifications.md).
5. [Review retention, credentials and troubleshooting](https://docs.fivemesh.io/backup/configuration.md).

## What stays local

Configuration, database credentials, run history and archives stay on your machine. There is no telemetry. Optional Discord notifications send operational details to the channel you configure; they do not upload database archives.

A local backup does not protect against losing the machine or disk that holds it. Keep a separate off-machine copy when you need that protection. Archive verification checks integrity; a restore rehearsal checks whether the data works for your application.

## Source and releases

Read the [source code](https://github.com/FiveMesh/fivemesh-backup), download [release files](https://github.com/FiveMesh/fivemesh-backup/releases/latest), or [report an issue](https://github.com/FiveMesh/fivemesh-backup/issues). Report security vulnerabilities using the repository's [security policy](https://github.com/FiveMesh/fivemesh-backup/blob/main/SECURITY.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.