Backup snapshot using curator older than 30days

Elastic Stack Elasticsearch
1

Hi,

Kindly correct this command

curator --host localhost --port 9200 snapshot indices --skip-repo-validation --repository backups --time-unit days --older-than 30 --timestring '%Y.%m.%d'
Usage: curator snapshot [OPTIONS] COMMAND [ARGS]...

Take snapshots of indices (Backup)

Options:
--repository TEXT Repository name.
--name TEXT Override default name.
--prefix TEXT Override default prefix.
--wait_for_completion BOOLEAN Wait for snapshot to complete before
returning. [default: True]
--ignore_unavailable Ignore unavailable shards/indices.
--include_global_state BOOLEAN Store cluster global state with snapshot.
[default: True]
--partial Do not fail if primary shard is unavailable.
--request_timeout INTEGER Allow this many seconds before the
transaction times out. [default: 21600]
--skip-repo-validation Skip repository access validation.
--help Show this message and exit.

Commands:
indices Index selection.
2017-02-22 21:46:03,920 ERROR Missing required parameter --repository

2

curator --dry-run --host elasticsearch.******.com snapshot --skip-repo-validation --repository backups indices --older-than 30 --time-unit days --timestring '%Y.%m.%d'

remove the --dry-run to actually do it.

3

Thank you for your reply, i tried your command . ERROR No indices provided.

$ curator --host localhost snapshot --skip-repo-validation --repository backups indices --older-than 30 --time-unit days --timestring '%Y.%m.%d'
2017-02-21 23:33:47,860 INFO Job starting: snapshot indices
2017-02-21 23:33:47,860 INFO Overriding default connection timeout for snapshot action. New timeout: 21600
2017-02-21 23:33:48,099 INFO Action snapshot will be performed on the following indices: [u'topbeat-2016.12.07', u'topbeat-2016.12.09', u'topbeat-2016.12.10', u'topbeat-2016.12.11', u'topbeat-2016.12.12', u'topbeat-2016.12.15', u'topbeat-2016.12.16', u'topbeat-2016.12.17', u'topbeat-2016.12.18', u'topbeat-2016.12.19', u'topbeat-2016.12.20', u'topbeat-2016.12.21', u'topbeat-2016.12.22', u'topbeat-2016.12.23', u'topbeat-2016.12.24', u'topbeat-2016.12.25', u'topbeat-2016.12.26', u'topbeat-2016.12.27', u'topbeat-2016.12.28', u'topbeat-2016.12.29', u'topbeat-2016.12.30', u'topbeat-2016.12.31', u'topbeat-2017.01.01', u'topbeat-2017.01.02', u'topbeat-2017.01.03', u'topbeat-2017.01.04', u'topbeat-2017.01.05', u'topbeat-2017.01.06', u'topbeat-2017.01.07', u'topbeat-2017.01.08', u'topbeat-2017.01.09', u'topbeat-2017.01.10', u'topbeat-2017.01.11', u'topbeat-2017.01.12', u'topbeat-2017.01.13', u'topbeat-2017.01.14', u'topbeat-2017.01.15', u'topbeat-2017.01.16', u'topbeat-2017.01.17', u'topbeat-2017.01.18', u'topbeat-2017.01.19', u'topbeat-2017.01.20', u'topbeat-2017.01.21', u'topbeat-2017.01.22', u'topbeat-2017.01.23']
2017-02-21 23:33:48,273 ERROR No indices provided.
2017-02-21 23:33:48,273 WARNING Job did not complete successfully.

kindly help me, We are using using curator 3.5.1, Elasticsearch version 2.3.1

5

All indices starting this name type :

ccsd-
cloudtrail-
filebeat-
packetbeat-
syslog-
tbng-
topbeat-

6

2017-02-23 06:15:00,373 INFO Job starting: snapshot indices
2017-02-23 06:15:00,373 INFO Overriding default connection timeout for snapshot action. New timeout: 21600
2017-02-23 06:15:00,475 INFO Action snapshot will be performed on the following indices: [u'topbeat-2016.12.07', u'topbeat-2016.12.09', u'topbeat-2016.12.10', u'topbeat-2016.12.11', u'topbeat-2016.12.12', u'topbeat-2016.12.15', u'topbeat-2016.12.16', u'topbeat-2016.12.17', u'topbeat-2016.12.18', u'topbeat-2016.12.19', u'topbeat-2016.12.20', u'topbeat-2016.12.21', u'topbeat-2016.12.22', u'topbeat-2016.12.23', u'topbeat-2016.12.24', u'topbeat-2016.12.25', u'topbeat-2016.12.26', u'topbeat-2016.12.27', u'topbeat-2016.12.28', u'topbeat-2016.12.29', u'topbeat-2016.12.30', u'topbeat-2016.12.31', u'topbeat-2017.01.01', u'topbeat-2017.01.02', u'topbeat-2017.01.03', u'topbeat-2017.01.04', u'topbeat-2017.01.05', u'topbeat-2017.01.06', u'topbeat-2017.01.07', u'topbeat-2017.01.08', u'topbeat-2017.01.09', u'topbeat-2017.01.10', u'topbeat-2017.01.11', u'topbeat-2017.01.12', u'topbeat-2017.01.13', u'topbeat-2017.01.14', u'topbeat-2017.01.15', u'topbeat-2017.01.16', u'topbeat-2017.01.17', u'topbeat-2017.01.18', u'topbeat-2017.01.19', u'topbeat-2017.01.20', u'topbeat-2017.01.21', u'topbeat-2017.01.22', u'topbeat-2017.01.23', u'topbeat-2017.01.24']
2017-02-23 06:15:00,642 ERROR No indices provided.
2017-02-23 06:15:00,642 WARNING Job did not complete successfully.
[root@elk-i-1b426dc3 backups]# curator --host elasticsearch.******.com snapshot --repository backups indices --prefix topbeat- --older-than 30 --time-unit days --timestring '%Y.%m.%d'

correct this command please

7

Hi,

I am also seeing this issue, If I run the command with Dry-Run option is displays the Indices that will be snapshooted, but then when I run the command without --dry-run, it says no indices provided..
[root@ElasticSearch2 curator]# curator --host 127.0.0.1 snapshot --repository ElasticSearch2-Repo-S3 indices --older-than 53 --time-unit days --timestring '%Y.%m.%d'
2017-03-07 15:54:48,815 INFO Job starting: snapshot indices
2017-03-07 15:54:48,816 INFO Overriding default connection timeout for snapshot action. New timeout: 21600
2017-03-07 15:54:48,902 INFO Action snapshot will be performed on the following indices: [u'applogs-2017.01.13', u'latencymetrics-2017.01.13', u'preadvicemetrics-2017.01.13']
2017-03-07 15:54:48,917 ERROR No indices provided.
2017-03-07 15:54:48,917 WARNING Job did not complete successfully.

8

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