Restarting a Persistence Server with Saved State

Adminstrators can restart persistence server using previously saved state.

Prerequisites

The previously suspended server process must no longer exist.

Procedure

  1. Determine which state file or files to load. If needed, copy state files.

    If you saved the state of all the servers, then each one can load its own state file.

    If you saved a subset of the servers, select one state file, and arrange for all the servers to load it.

  2. Start the servers. If needed, supply the --load parameter.

    If the --load parameter specifies a state file, and the server finds that state file, then it loads its initial state from that file. If it cannot load that state file, then the server logs an error and starts with empty state.

    If the --load parameter is absent, then server automatically searches for the default state file in the current directory. If the server finds the default state file, then it loads its initial state from that file. Otherwise, the server starts with empty state.

  3. Verify cluster status in the persistence clusters status table, and server state in the servers list.

Result

Persistence functionality resumes when the servers can form a quorum. For details, see Quorum Conditions General Rule.