> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/analytics/mariadb-columnstore/management/column-store-backup-and-restore/backup-and-restore-with-mariadb-enterprise-columnstore.md).

# Backup and Restore Overview

## Overview

MariaDB ColumnStore supports backup and restore.

## System of Record

Before you determine a backup strategy for your ColumnStore deployment, it is a good idea to determine the **system of record** for your ColumnStore data.

A system of record is the authoritative data source for a given piece of information. Organizations often store duplicate information in several systems, but only a single system can be the authoritative data source.

ColumnStore is designed to handle analytical processing for OLAP, data warehousing, DSS, and hybrid workloads on very large data sets. Analytical processing does not generally happen on the system of record. Instead, analytical processing generally occurs on a specialized database that is loaded with data from the separate system of record. Additionally, very large data sets can be difficult to back up. Therefore, it may be beneficial to only backup the system of record.

If ColumnStore is not acting as the system of record for your data, you should determine how the system of record affects your backup plan:

* If your system of record is another database server, you should ensure that the other database server is properly backed up and that your organization has procedures to reload ColumnStore from the other database server.
* If your system of record is a set of data files, you should ensure that the set of data files is properly backed up and that your organization has procedures to reload ColumnStore from the set of data files.

## Full Backup and Restore

MariaDB ColumnStore supports full backup and restore for all storage types. A full backup includes:

* ColumnStore's data and metadata

With S3: an S3 snapshot of the [S3-compatible object storage](/docs/analytics/mariadb-columnstore/architecture/columnstore-architectural-overview.md#s3-compatible-object-storage-1) and a file system snapshot or copy of the [Storage Manager directory](/docs/analytics/mariadb-columnstore/architecture/columnstore-storage-architecture.md#storage-manager-directory) Without S3: a file system snapshot or copy of the [DB Root directories](/docs/analytics/mariadb-columnstore/architecture/columnstore-storage-architecture.md#db-root-directories).

* The MariaDB data directory from the primary node

To see the procedure to perform a full backup and restore, choose the storage type:

| Storage Type                                                                                                                                                                               | Diagram                                                 |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- |
| [ColumnStore with Object Storage](/docs/analytics/mariadb-columnstore/management/column-store-backup-and-restore/mariadb-enterprise-columnstore-backup-and-restore-with-object-storage.md) | ![columnstore-topology-s3](/files/cqMDrSA3ZNWBhcKBf76l) |
| [ColumnStore with Shared Local Storage](/docs/analytics/mariadb-columnstore/architecture/columnstore-architectural-overview.md#enterprise-columnstore-with-shared-local-storage)           | ![columnstore-topology](/files/Xe609DeZrCnURxk1aBrz)    |

<sub>*This page is: Copyright © 2025 MariaDB. All rights reserved.*</sub>

{% @marketo/form formId="4316" %}


---

# 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://mariadb.com/docs/analytics/mariadb-columnstore/management/column-store-backup-and-restore/backup-and-restore-with-mariadb-enterprise-columnstore.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.
