Data Snapshots and Recovery

To create a full snapshot, use the cluster snapshot create CLI command. In the command, you can specify the list of fully qualified table names to create snapshots of, or specify the --all option to create a snapshot of all tables. For example:

The command above creates a full snapshot of a table Person at a specified destination path (see Defining Snapshot Paths for the latter).

When creating incremental snapshots, successive copies of the data contain only the changes since the last full or incremental snapshot. The base snapshot for incremental snapshots must be a full snapshot, but all subsequent ones can be incremental. The latest valid snapshot will be found for the tables you have specified, and an incremental snapshot based on it will be created.

Here is how you can create an incremental snapshot based on the full snapshot created above:

You cannot add more tables to the snapshot when creating an incremental snapshot. You need to have the same tables in it as in the base snapshot created before.

You can also make a snapshot for the specific cluster state in the past, for example:

The timestamp must be specified in ISO format.

To restore snapshots, you can use the cluster snapshot restore command.

To make sure your snapshot is restored correctly, follow these guidelines:

When you are prepared to restore data to the cluster, run the restore command. For example:

The command above restores all tables in the snapshot with the specified ID, from the specified source path (see Defining Snapshot Paths for the latter). You can also choose to only restore specific tables stored in the snapshot, instead of all of them. In this case, specify the fully qualified table names of the tables to restore, for example:

You define snapshot paths in the cluster configuration.

You then define the snapshot path for a specific command (--destination when creating a snapshot, --source when restoring from a snapshot).

The destinations and sources can be defined as either LOCAL or REMOTE.

For absolute LOCAL path, snapshot with ID 1 would be created in the /absolute-path/node-1/snapshot-1 directory. For absolute REMOTE path, the same snapshot would be created in the /absolute-path/snapshot-1 directory. For relative REMOTE and LOCAL paths, the same snapshot would be created in the {GRIDGAIN_HOME}/relative-path/snapshot-1 directory.

Incremental snapshot destination must have the same URI and type as all parents' snapshots. The path name could be different from that of the parents.

The snapshot restore operations must point to the same URI with the same type (LOCAL or REMOTE) that were used when creating that snapshot.

You can check the status of all snapshots by using the cluster snapshot status command. By default, this command provides information about all snapshots in the cluster.

You can narrow information down by providing the snapshot ID. If you do, you can also use the --all-nodes option to see information about the snapshot on each specific node in the cluster. For example:

The command above returns information about all operations with the snapshots per node.

The following information is provided:

You can delete a snapshot using the delete command.

Where: id is the snapshot’s ID and url (optional) is the cluster’s URL.

For example: