anchor.diff:  `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, entire snapshot will fail if one or more indices participating in the snapshot don't have
  +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
  
positive.code: }'
  -----------------------------------
  
  Once repository is registered, its information can be obtained using the following command:
  
  [source,js]
  -----------------------------------
  
negative.code: changed since the last snapshot. That allows multiple snapshots to be preserved in the repository in a compact form.
  Snapshotting process is executed in non-blocking fashion. All indexing and searching operation can continue to be
  executed against the index that is being snapshotted. However, a snapshot represents the point-in-time view of the index
  at the moment when snapshot was created, so no records that were added to the index after the snapshot process was started
  will be present in the snapshot. The snapshot process starts immediately for the primary shards that has been started
  and are not relocating at the moment. Before version 1.2.0, the snapshot operation fails if the cluster has any relocating or
  initializing primaries of indices participating in the snapshot. Starting with version 1.2.0, Elasticsearch waits for
  