---
title: "Back up a Database Cluster"
component: "tigergraph-server"
version: "4.3"
module: "backup-and-restore"
html_url: "/tigergraph-server/4.3/backup-and-restore/backup-cluster"
canonical_url: "https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/backup-cluster"
markdown_url: "https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/backup-cluster.md"
---

[View as HTML](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/backup-cluster)

# Back up a Database Cluster

> [!NOTE]
> In TigerGraph DB Community Edition, backup and restore are not supported. Use [database export and import](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/database-import-export.md) instead.

This page walks you through the steps to back up your database cluster. The process also applies to single-server instances.

Backing up a cluster is an online operation. Your database remains available during the backup.

While database reads and writes can take place during backup, the system enforces **locking** among other cluster critical operations ( cluster resizing, `CONFIG APPLY` and upgrade). One operation will be granted the lock and others will be rejected or canceled.

Consult [the gadmin Command Glossary](https://www.tigergraph.com/docs/tigergraph-server/4.3/system-management/management-commands.md) to view the help files for the `gadmin backup` commands.

## 1\. Prerequisites

* You have access to the TigerGraph Linux user account on your cluster. All commands must be run from the TigerGraph Linux user.
* You have provided valid [configurations for database backup](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/configurations.md).

## 2\. Procedure

### 2.1\. Data backup

To back up a database cluster, run the following command:

```console
$ gadmin backup create <tag>
```

Replace `<tag>` with a custom tag for the backup. A timestamp is suffixed to the tag you provided to form the full tag of the backup. If no tag is provided, the system uses the default `backup` followed by the timestamp when the backup is created as the tag for the backup.

For example, run the following command to create a backup for a database cluster:

```console
$ gadmin backup create weekly
```

This creates a backup named `weekly-<timestamp>` at the [backup location you configured](https://www.tigergraph.com/docs/tigergraph-server/4.3/backup-and-restore/configurations.md).

You can also make `weekly` the entire tag by using the flag `--custom-tag`:

$ gadmin backup create weekly --custom-tag

This creates a backup named `weekly` without the `-<timestamp>` suffix.
