> 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/tools/enterprise/control-center/tutorials/gridgain8-management-and-monitoring/backups.md).

# Create GridGain Cluster Backups

Use the GridGain Control Center Snapshots screen to create a cluster backup and restore from it to recover from a data-loss incident.

Before you go into production with GridGain, you need to decide on a cluster backup and recovery strategy. The disk that stores your records does not last forever. A new version of an application might have a bug that corrupts the data. The data center that is running your GridGain-based solution might fail and become unreachable. These examples are just a few of the many problems that can lead to data corruption or make your primary cluster unavailable. You can't eliminate all such events, but if you back up GridGain regularly, you can restore a cluster after a data-loss incident.

In this part of the tutorial, you use the [Snapshots screen](https://mariadb.com/docs/tools/enterprise/control-center/gg8/snapshots/snapshots.md) to create a cluster backup and later use it to resolve a data-corruption incident.

{% hint style="info" %}
**Snapshots require GridGain Ultimate**

Control Center uses the [Snapshots and Recovery feature](https://www.gridgain.com/docs/gridgain8/latest/administrators-guide/snapshots/snapshots-and-recovery) of GridGain Ultimate Edition to create and manage cluster backups. The demo cluster you started in the [first part of the tutorial](https://mariadb.com/docs/tools/enterprise/control-center/tutorials/gridgain8-management-and-monitoring/starting-streaming-demo.md) runs GridGain Ultimate with snapshots enabled, so you can create and restore backups directly. Snapshots are unavailable on GridGain Enterprise clusters and on clusters where snapshot storage has not been configured.
{% endhint %}

## Pause the Application

GridGain can create hot cluster snapshots while applications keep updating records and, later, use the snapshots and WALs to [recover to any point in time](https://www.gridgain.com/docs/gridgain8/latest/administrators-guide/snapshots/point-in-time-recovery). In this tutorial, you simulate a data-loss incident by deleting all of a table's records, then confirm that restoring the cluster brings the record count back to normal. First, stop the tutorial application:

```bash
docker compose -f docker/ignite-streaming-app.yaml stop
```

## Create a Cluster Snapshot

After you pause the application, navigate to the [Snapshots screen](https://mariadb.com/docs/tools/enterprise/control-center/gg8/snapshots/snapshots.md) and create a cluster snapshot:

1. Click `Create snapshot`. In the dialog, keep the default `Full` snapshot type, then click `Create`:

   ![Creating Full GridGain Snapshot](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-1f00a4840740fd2ac7105aac1ed13ebe81b03752%2Fcreate-snapshot.png?alt=media)
2. The new snapshot appears in the `Snapshots` list:

   ![GridGain Snapshots List](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-d944ac82a35de1b04eaea6f5807754fcce7ac7da%2Fsnapshot-created.png?alt=media)

## Corrupt a Cluster Table

After you create a cluster snapshot, open the [Queries screen](https://mariadb.com/docs/tools/enterprise/control-center/gg8/queries/querying.md) and simulate a data-loss incident by removing records from the `Trade` table:

1. Check the number of trades in your cluster by executing the `SELECT count(*) FROM Trade` query. Your record count might not match the number in the following screenshot, because the application may have been running for a different amount of time in your environment.

   ![Trades Count](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-344ecb49464ccb4c44e8701b9bdf6dece424bc9a%2Fcount-before-corruption.png?alt=media)
2. Use the `DELETE FROM Trade` query to remove all the trades.
3. Confirm that the table is empty by running the `SELECT count(*) FROM Trade` query again.

## Restore From the Snapshot

You removed records only from the `Trade` table, so restore just that cache instead of the whole snapshot:

1. On the `Snapshots` screen, click the `⋮` icon in the snapshot's row and select `Restore from snapshot`.
2. In the **Restore snapshot** dialog, select **Include specific**, choose the `Trade` cache from the **Caches** drop-down, and click `Restore`:

   ![Restoring GridGain Cluster from Snapshot](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-8745b6b569adfdc0f79910380b4f38ecf0a3cd02%2Frestore-snapshot.png?alt=media)

   Restoring the full snapshot instead (the default **All** scope) replaces every cache in the cluster and is meant for full disaster recovery on a healthy cluster, not for recovering a single table.
3. After the restore procedure is complete, return to the Queries screen and execute the `SELECT count(*) FROM Trade` query. Confirm that all the records were recovered:

   ![Trades Count](https://2850516351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkuTXWg0NDbRx6XUeYpGD%2Fuploads%2Fgit-blob-344ecb49464ccb4c44e8701b9bdf6dece424bc9a%2Fcount-before-corruption.png?alt=media)

## What's Next

Congratulations! You've finished all the steps of the tutorial. Now you can stop the demo:

* [Part 7: Stop the demo application](https://mariadb.com/docs/tools/enterprise/control-center/tutorials/gridgain8-management-and-monitoring/terminating-streaming-demo.md)

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

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