Log server repository permission

[jolson]

Update: I spoke with swilkerson about this, and closed indices cannot currently be backed up. In a future version of Elasticsearch, this might be a possibility - but for now it is not possible. Thank you!

[OptimusB]

Thanks for checking this. This means that the maintenance task should really run after the backup task? If the maintenance task runs and closes the indices then it won't get captured by backups?

I also tested the command by reopening an index manually then running the backup command, which works. So I guess I can backup everything that was missed manually.

Thanks again!

Code: Select all

[root@localhost]# curator snapshot --prefix logstash-2015.12.31 --repository "Test Repo" --most-recent 1
2015-03-10 08:56:13,219 INFO      Job starting...
2015-03-10 08:56:13,219 INFO      Default timeout of 30 seconds is too low for command SNAPSHOT.  Overriding to 21,600 seconds (6 hours).
2015-03-10 08:56:13,222 INFO      Beginning SNAPSHOT operations...
2015-03-10 08:56:13,228 INFO      Attempting to create snapshot for logstash-2015.12.31...
2015-03-10 08:56:14,162 INFO      Snapshot operation for index logstash-2015.12.31 succeeded.
2015-03-10 08:56:14,162 INFO      Snapshot 'latest' 1 indices operations completed.
2015-03-10 08:56:14,162 INFO      Done in 0:00:00.955550.

[jolson]

Typically, you will have your 'close indices after X days' setting set to something like '10 days' for instance. If you are backing up every day, it should not matter which order the processes run in, as backup task should have backed up any indices that are going to be closed. I am not sure why it was designed this way - perhaps to save you a little bit of backup space. Does that answer your question?

If all is good here, would it be alright if I closed this thread? Thanks!

[OptimusB]

Yes and thanks again. This can be closed. Cheers.