...
The cluster should be active
...
Current limitations
- Restoring is possible only if all parts of the snapshot are present in the cluster. Each node looks for a local snapshot data in the configured snapshot path by the given snapshot name and consistent node ID.
- The restore procedure can be applied only to cache groups created by the user.
- Cache groups to be restored from the snapshot must not be present in the cluster. If they are present, they must be link:key-value-api/basic-cache-operations#destroying-caches[ destroyed ] by the user before starting this operation.
- Concurrent restore operations are not allowed. Thus, if one operation has been started, the other can only be started after the first is completed.
...
- The whole cluster allowed only one cluster-wide snapshot operation per time.
- Encrypted caches currently not allowed due to required additional changes to merge cache partition with its delta file.
- The cache stop operation is not allowed during the ongoing cluster snapshot. An exception will be thrown to users on the cache stop attempt.
- The cluster snapshot operation will be stopped if some of the baseline nodes left or fail prior to reporting about their local snapshot completion. Partial local snapshots will be reverted.
- Datastructure and system caches are not included in the snapshot.
Discussion Links
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Hot-cache-backup-td41034.html
...