anchor.diff:  
   Only one snapshot process can be executed in the cluster at any time. While snapshot of a particular shard is being
   created this shard cannot be moved to another node, which can interfere with rebalancing process and allocation
  -filtering. Once snapshot of the shard is finished Elasticsearch will be able to move shard to another node according
  -to the current allocation filtering settings and rebalancing algorithm.
  +filtering. Elasticsearch will only be able to move a shard to another node (according to the current allocation
  +filtering settings and rebalancing algorithm) once the snapshot is finished.
   
   Once a snapshot is created information about this snapshot can be obtained using the following command:
   
  
positive.code: [float]
  === Partial restore
  
  By default, entire restore operation will fail if one or more indices participating in the operation don't have
  snapshots of all shards available. It can occur if some shards failed to snapshot for example. It is still possible to
  restore such indices by setting `partial` to `true`. Please note, that only successfully snapshotted shards will be
  restored in this case and all missing shards will be recreated empty.
  
negative.code: `ignore_unavailable` option. Setting it to `true` will cause indices that do not exist to be ignored during snapshot
  creation. By default, when `ignore_unavailable` option is not set and an index is missing the snapshot request will fail.
  By setting `include_global_state` to false it's possible to prevent the cluster global state to be stored as part of
  the snapshot. By default, the entire snapshot will fail if one or more indices participating in the snapshot don't have
  all primary shards available. This behaviour can be changed by setting `partial` to `true`.
  
  The index snapshot process is incremental. In the process of making the index snapshot Elasticsearch analyses
  