Triggering Hot Backups
You can trigger a hot backup to save a snapshot of the persistence store. Hot backups are useful when you wish to bring up a new cluster with the same data or parts of the data. The new cluster can then be used to share load with the original cluster, perform testing, or reproduce an issue, using production data.
Clusters must have a directory set in the
backup-dir configuration option. See Backing Up the Persistence Store in the Platform documentation.
This page is available only to admin users.
Go to Administration > Cluster State and select
PASSIVEfrom the dropdown menu.
Backups may be initiated during membership changes, partition table changes, or during normal data updates. As a result, some members may have outdated versions of the persistence store before they start the backup process. By putting your cluster in a
PASSIVEstate, you can stop the cluster from making changes to the persistence store.
Go to the Persistence tab and click Hot Backup.
The backup process will start asynchronously in the background.
Go to the Cluster State tab select
ACTIVEfrom the dropdown menu.
Monitor the backup process in the the Last Hot Backup Task Status field.
When the Status field of each member is Success, the backup process completed successfully.
To learn more about changing cluster states, see Changing the Cluster State.