Recover Partitions from a Remote Cluster
Data recovery from remote clusters requires XDCR and enough memory and disk space.
If more nodes in a cluster catastrophically fail than the number of replicas, data partitions in that cluster will no longer be available. For example, if you have a four-node cluster with one replica and two nodes fail and are unrecoverable, some data shards will no longer be available.
Data recovery from remote clusters requires an XDCR environment and adequate amount of memory and disk space to support the workload and recovered data.
To recover the missing data partition in case of node failure and when vBuckets are unavailable, follow these steps.
For each failed node, click on.
You will see whether data is unavailable and which vBuckets are unavailable. If you do not have enough replicas for the number of the failed-over nodes, some vBuckets will no longer be available:
Add new functioning nodes to replace the failed nodes.
Do not rebalance after you add new nodes to a cluster. Typically, you will rebalance after adding nodes to the cluster, but in this scenario the rebalance will destroy the information about the missing vBuckets and you cannot recover it.
In this example, two nodes failed in a three-node cluster and a new node at
10.3.3.61was added. If you are certain that your cluster can easily handle the workload and recovered data, you may choose to skip this step.
Run cbrecovery to recover data from your backup cluster. In the Server Panel, the Stop Recovery button appears.
After the recovery completes, this button disappears.
Rebalance your cluster.
Once the recovery is completed, you can rebalance your cluster. Rebalancing will recreate replica vBuckets and redistribute them evenly across the cluster.