Create Snapshots using curator

Hi Guys,
New to using curator and have been able to successfully setup and install it. Now when I run it, I'm getting the following error message:

[root@localhost ~]# curator --config /root/config.yml --dry-run snapshot.yml

I'm using the examples at the link below for config file:

https://www.elastic.co/guide/en/elasticsearch/client/curator/current/configfile.html

and for action:

https://www.elastic.co/guide/en/elasticsearch/client/curator/current/actionfile.html

[root@localhost ~]# curator --config /root/config.yml --dry-run snapshot.yml 2017-06-07 15:22:12,615 ERROR Schema error: required key not provided @ data['repository'] Configuration: options: Location: Action ID "1", action "snapshot": Bad Value: "(could not determine)", required key not provided @ data['repository']. Check configuration file.

I've been researching this the whole day and added a filename as well to the name: field. Any help would be much appreciated.

You need to include the name of the repository you created in the repository field.
Following this https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html#_repositories documentation. I named my repository es_backups.

Example:

actions:
  1:
    action: snapshot
    description: >-
      Snapshot  indices older than 0 day (based on index
      creation_date) with the default snapshot name pattern of
      'curator-%Y%m%d%H%M%S'.  Wait for the snapshot to complete.  Do not skip
      the repository filesystem access check.  Use the other options to create
      the snapshot.
    options:
      repository: es_backups
      # Leaving name blank will result in the default 'curator-%Y%m%d%H%M%S'
      name:
      ignore_unavailable: False
      include_global_state: True
      partial: False
      wait_for_completion: True
      skip_repo_fs_check: False
      disable_action: False
    filters:
    - filtertype: age
      source: creation_date
      direction: older
      unit: days
      unit_count: 0
1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.