# Backups and restore

> Automatic backups of PostgreSQL, MariaDB and Redis, where to see them, and how to start again from a backup.

Source: https://docs.fransys.cloud/en/exploiter/sauvegardes/ Checked against the console on 2026-10-23.

## What's backed up

PostgreSQL, MariaDB and Redis databases are backed up automatically. In the database's **Backups** tab, set the **Backup schedule** and the **Retention (days)**.

Applications themselves have no backups: keep their data in a database, or in external storage.

Backup storage is billed per GB (see [Pricing](https://docs.fransys.cloud/en/budget/grille-tarifaire/)).

## See a database's backups

In the database panel, **Latest backups** lists the most recent ones: the date, the **stored size** (compressed, as the backup is kept), the **raw size** (before compression) and the status. **View all backups** shows them page by page.

## Start again from a backup

Set **On first start** to **From a backup**. A database's **Restore from** setting chooses where it starts from:
- **This service itself**: its latest backup is restored when it restarts (when it's brought back online);
- **another database with the same engine**, in this project or another: search for it by its name or its project's name.

Then the **Backup to restore**: the most recent one, or a specific backup. **Restore up to** sets a point in time (local time); left empty, everything the backup contains is restored.

> **When the restore happens**
> The backup is restored when the database starts: when it's created, or when it's brought back online. The data already there is then replaced.

To recover data without touching the live database, add a new database with the same engine and choose the original database as its source.

With no source chosen, a database starts empty.

## Before taking it offline

Taking a project or a cluster offline erases the databases' data. First set **Restore from** to **This service itself**: when it comes back online, each database will start from its latest backup.