anchor.diff:  The previous example shows the snapshot created for the cluster running on the same physical machine. Thus, the whole
   snapshot is located in a single place. While in practice, all the nodes will be running on different machines having the
   snapshot data spread across the cluster. Each node keeps a segment of the snapshot with the data belonging to this particular node.
  -The link:persistence/snapshots#restoring-from-snapshot[restore procedure] explains how to tether together all the segments during recovery.
  +The link:snapshots/snapshots#restoring-from-snapshot[restore procedure] explains how to tether together all the segments during recovery.
   ====
   
   == Configuration
  
positive.code:     - Copy the files belonging to a node with the `{node_id}` from the snapshot into the `$IGNITE_HOME/work/` directory. If the `db/{node_id}` directory is not located under the Ignite `work` dir then you need to copy data files there.
  . Restart the cluster
  
  *Restore On Cluster of Different Topology*
  
  You may want to create a snapshot of an N-node cluster and use it to restore on an M-node cluster. The table below explains what options are supported:
  [cols="1,1",opts="header"]
  |===
  |Condition | Description
  |N == M | The *recommended* case. Create and use the snapshot on clusters of a similar topology.
  |N < M | Start the first N nodes of the M-node cluster and apply the snapshot. Add the rest of the M-cluster nodes to
  the topology and wait while the data gets rebalanced and indexes are rebuilt.
  |N > M | Unsupported.
  |===
  
  === Automatic Snapshot Restore Procedure
  
  The automatic restore procedure allows the user to restore cache groups from a snapshot on an active cluster by using the Java API or link:tools/control-script[command line script].
  
negative.code: commands.
  
  == Restoring From Snapshot
  
  A snapshot can be restored either manually on a stopped cluster or automatically on an active cluster.
  Both procedures are described below, however, it is preferable to use the restore command from Control Script only.
  
  === Manual Snapshot Restore Procedure
  
  The snapshot structure is similar to the layout of the Ignite Native Persistence, so for the manual snapshot restore you must
  do a snapshot restore only on the same cluster with the same node `consistentId` and on the same topology on which a snapshot
  was taken. If you need to restore a snapshot on a different cluster or on a different cluster topology use the
  link:snapshots/snapshots#automatic-snapshot-restore-procedure[Automatic Snapshot Restore Procedure].
  
  In general, stop the cluster, then replace persistence data and other files with the data from the snapshot, and restart the nodes.
  
  The detailed procedure looks as follows:
  
  