Saving and Loading Persistence State

The persistence GUI includes a facility to save the content of a persistence service’s stores to a file. When a new persistence service starts, it can load its initial state from that file. You can use this facility for nightly backups, during upgrade migration, or to migrate a persistence cluster to a new physical location.

See the following three subtask topics.

    Procedure
  1. Suspending a Persistence Cluster
  2. Saving the State of a Persistence Service
  3. Restarting a Persistence Cluster with Saved State

Restoring Backups

When restoring from backup files, use only the files created by a backup command. No live persistence files may be present.

The backup command creates a backup file for each persistence service. Rename the backup files and place them in the appropriate data directories before starting the servers.

Before performing a restoral, first identify the desired backup file for each persistence service. Then rename the backup file to <persistence_service_name>.persist and place it in the data directory for that persistence service.

Note the following differences between backups and saving the state of the peristence cluster.

• You use backups only when disk persistence is enabled.
• Unlike saving the state of the persistence cluster (which involves suspending the cluster), backups do not prevent new clients from sending or receiving messages while the backup is in progress.