Backing Up ES

Yes, you will always be able to upgrade to a newer version without needing
to reindex. A multi node cluster backup simplest option is to backup each
node data location.

On Mon, Mar 19, 2012 at 11:13 AM, Kristian Jörg krjg@devo.se wrote:

Regarding backup. Since I am using ES sort of as a noSQL database it will
not be possible to reindex from scratch after updates has been done to the
documents.
Is it guaranteed that it will always be possible to import an index to a
newer version of ES without need of reindexing it?

Second question. How do you backup shards that are not on the local node?
I am not there yet, but I might be in future...

/Kristian

Shay Banon skrev 2012-03-14 13:05:

Yes, assuming you have 1 replica, and 2 machines, you only need to copy

one machine over. And the restore process you mentioned is good.

On Tuesday, March 13, 2012 at 5:24 AM, Eugene Strokin wrote:

Hello, I'm planning to use very nice script by Karussell

https://gist.github.com/**1074906 https://gist.github.com/1074906
for backing up my ES.
But I have a cluster of currently 2 machines running the ES.
I want to make sure, that this is enough to copy the files just from one
machine, because after flush they are the same on both server boxes.
And to restore, I just need to restore files on one machine, run ES, and
on another I'd just run empty ES server with my custom mappings, and the
second machine would pick the data up from the first.
Am I correct, or my assumption is mistaken?

Thank you,
Eugene S.

--
Med vänlig hälsning
Kristian Jörg

Devo IT AB
Tel: 054 - 22 14 58, 0709 - 15 83 42
E-post: kristian.jorg@devo.se
Webb: http://www.devo.se