Saving the State of a Persistence Service

Administrators can save the state of suspended persistence services.

1. Open the services list.

   You may save all the services, or only a subset. The choice depends on available disk space, network speed and bandwidth. If you save only a subset, ensure that you save the quorum leader or the service with the latest history numbers.

2. Locate the service to save, and click the Save icon in the corresponding row. Confirm.
3. Wait for the service to finish saving, and verify success.

   When the save operation is complete, the Disk column will indicate the value Saved. Alternatively, you can verify the save operation by checking the service log messages and the timestamp on the saved state file.

   A save operation could fail if the disk is full, for example.

   If a save operation fails, take corrective action and save again.

   Note: The save operation includes only replicated state. If replication is not enabled for a store, then the save operation excludes the content of that store from the state file.

   Note: The state file name is service_name.state.


   Note: If the state file already exists, the save operation renames it to service_name.state.backup before writing a new state file.
4. Optional. Repeat steps 2 and 3 for other services.
   Alternatively, you can save the state of all the services with one command. Click the Save icon in the cluster row.