> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/databases/mariadb/overview/backups.md).

# Backups

## How do backups work in MariaDB v2?

<code class="expression">space.vars.ionos\_cloud</code> DBaaS for MariaDB v2 uses configurable backups instead of fixed daily backups. You can set:

* **Location:** The Object Storage region where backups are stored, using the `backup.location` property. For added data safety, use a location different from the cluster's own region.
* **Retention days:** The number of days backups are retained before being automatically deleted, from 1 to 365 days (default: 7), using the `backup.retentionDays` property.

MariaDB v2 continuously archives binary logs and performs periodic full backups, enabling Point-in-Time Recovery (PITR). Backups can be used to restore an existing cluster to a previous point in time, or to initialize a new cluster with data from an existing backup during creation. For more information, see [<mark style="color:blue;">Restore a MariaDB Cluster</mark>](/cloud/databases/mariadb/how-tos/v2/restore-mariadb-cluster.md).

## How do backups work in MariaDB v1?

<code class="expression">space.vars.ionos\_cloud</code> DBaaS for MariaDB v1 supports automatic backups. Automatic backups are created in either of the following instances:

* During the creation of a cluster.
* Upon upgrading the current version of MariaDB to a higher version.
* When a Point-in-Time Recovery operation is conducted.

<code class="expression">space.vars.ionos\_cloud</code> performs automatic full backups that run regularly at a specific hour based on the value set in the DBaaS component. <code class="expression">space.vars.ionos\_cloud</code> maintains backups for the last seven days so that you can recover them for up to a week. You can restore a MariaDB v1 cluster from a backup using either the [<mark style="color:blue;">DCD</mark>](/cloud/databases/mariadb/how-tos/v1/restore-mariadb-cluster-from-backup.md) or the [<mark style="color:blue;">API</mark>](/cloud/databases/mariadb/api/v1-api/restore-mariadb-cluster-from-backup.md).

## Manual backup

<code class="expression">space.vars.ionos\_cloud</code> facilitates the "logical" backup option using `mariadb-dump`. Alternatively, you can also use the `mariadb-dump` client to back up data to a different location. For more information, refer to the [<mark style="color:blue;">MariaDB Documentation</mark>](https://mariadb.com/kb/en/mariadb-dump/).

## Restore benefits

Restoring from a backup, whether through the DCD or the API, offers the following benefits:

* **Point-in-Time Recovery:** You can restore your MariaDB clusters to a specific point in time. For example, you can roll back the cluster to a state before data corruption or accidental deletions.
* **Automated process:** The automated process significantly streamlines and reduces the time and effort required to restore a MariaDB cluster.
* **Data consistency:** It ensures that the restored MariaDB cluster is consistent and matches the data state at the specified point in time, helping maintain data integrity across applications interacting with the cluster.
* **User control:** You have complete control over the restoration process, allowing you to select a specific point in time for the restoration and monitor its progress.


---

# 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.ionos.com/cloud/databases/mariadb/overview/backups.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.