From 139ba6b2ee094541cbb2be664a68ba2ce7e8225b Mon Sep 17 00:00:00 2001 From: Abhradeep Chakraborty Date: Tue, 17 Mar 2026 10:51:21 +0530 Subject: [PATCH 1/2] feat(backup): add doc for cluster backups Signed-off-by: Abhradeep Chakraborty --- docs/cloud/backups.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/cloud/backups.md b/docs/cloud/backups.md index a68172b0..d33fb4bc 100644 --- a/docs/cloud/backups.md +++ b/docs/cloud/backups.md @@ -21,6 +21,9 @@ from a remote storage system is also supported. Existing backups in your Dragonfly Cloud account can be [restored to an active data store](#restoring-from-backup) at any time. +For clustered (multi-shard) data stores, please review the [cluster backup limitations](#cluster-datastore-backups) +before restoring. + ## Manual On-Demand Backups To create a manual on-demand backup, follow the steps below: @@ -63,6 +66,26 @@ To restore a backup in an existing data store, follow the steps below, **with ca - Make **100% sure you select the correct backup** from the dropdown. - Click **Restore**. +## Cluster Datastore Backups + +Dragonfly Cloud supports backups for clustered (multi-shard) data stores. A cluster backup captures +the full dataset distributed across all shards at the point in time the backup was taken. + +### Limitations + +- **Shard count must match on restore**: The target data store must have the same number of shards + as the data store at the time the backup was created. Restoring a cluster backup to a data store + with a different shard count is not supported. +- **Shard distribution is enforced by the backup**: Data is partitioned across shards by hash slot ranges. + When restoring, the slot distribution of the target data store is overwritten to match the shard + distribution recorded in the backup. The target data store will reflect the original slot layout + after the restore completes. +- **Cross-tier restore is not supported**: A backup taken from a clustered data store cannot be + restored to a single-shard (non-clustered) data store, and vice versa. + +***CAUTION: Before initiating a restore, verify that the target data store's shard count and +configuration match the data store that the backup was originally taken from.*** + ## Viewing and Deleting Backups - You can view all backups under the [Account > Backups](https://dragonflydb.cloud/account/backups) tab. From 453406057d399559a749e4f66f8e47b13c3b49c5 Mon Sep 17 00:00:00 2001 From: Abhradeep Chakraborty Date: Wed, 18 Mar 2026 11:21:13 +0530 Subject: [PATCH 2/2] review Signed-off-by: Abhradeep Chakraborty --- docs/cloud/backups.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/docs/cloud/backups.md b/docs/cloud/backups.md index d33fb4bc..9e8d2125 100644 --- a/docs/cloud/backups.md +++ b/docs/cloud/backups.md @@ -21,8 +21,7 @@ from a remote storage system is also supported. Existing backups in your Dragonfly Cloud account can be [restored to an active data store](#restoring-from-backup) at any time. -For clustered (multi-shard) data stores, please review the [cluster backup limitations](#cluster-datastore-backups) -before restoring. +For Swarm (multi-shard) data stores see [cluster backup limitations](#swarm-multi-shard-backups). ## Manual On-Demand Backups @@ -66,10 +65,11 @@ To restore a backup in an existing data store, follow the steps below, **with ca - Make **100% sure you select the correct backup** from the dropdown. - Click **Restore**. -## Cluster Datastore Backups +## Swarm (multi-shard) Backups -Dragonfly Cloud supports backups for clustered (multi-shard) data stores. A cluster backup captures -the full dataset distributed across all shards at the point in time the backup was taken. +Dragonfly Cloud supports backups for Swarm (multi-shard) data stores. A multi shard datastore backup +captures the full dataset distributed across all shards at the point in time the +backup was taken. ### Limitations @@ -80,11 +80,9 @@ the full dataset distributed across all shards at the point in time the backup w When restoring, the slot distribution of the target data store is overwritten to match the shard distribution recorded in the backup. The target data store will reflect the original slot layout after the restore completes. -- **Cross-tier restore is not supported**: A backup taken from a clustered data store cannot be - restored to a single-shard (non-clustered) data store, and vice versa. - -***CAUTION: Before initiating a restore, verify that the target data store's shard count and -configuration match the data store that the backup was originally taken from.*** +- **Swarm backups cannot be restored to a single-shard data store**: A backup taken from a + multi-shard swarm data store cannot be restored to a single-shard (non-clustered) data store. + The reverse is supported — a single-shard backup can be restored to a swarm data store. ## Viewing and Deleting Backups