On Fri, 2012-03-16 at 09:05 -0400, Berkay Mollamustafaoglu wrote:
Right, there is no built-in mechanism to do that. You'd have to write
code that reads from one and writes to the other yourself.
And here's some code:
Copying the files should have worked, not sure what that problem is.
There has been some discussions about this in the list. If you search
for "backup" in mailing list archive you should be able to find the
mberkay on yahoo, google and skype
On Fri, Mar 16, 2012 at 8:58 AM, Pulkit Singhal
So since its tougher to answer a question when something
actually cannot happen, I take it that there is no way to
start a local ES instance and perform an async replication of
the data from the cloud over to my machine?
On Thu, Mar 15, 2012 at 12:57 PM, Pulkit Singhal
Unfortunately the SCP command to get the data
directory runs into problems early on:
Sending file modes: C0664 51257065 _5kr.fdt
Sink: C0664 51257065 _5kr.fdt
_5kr.fdt 46% 23MB 0.0KB/s - stalled -
So I guess that's not a good route to go.
On Thu, Mar 15, 2012 at 12:39 PM, Pulkit Singhal
The following thread doesn't really answer my
question (may be because I don't get how to
set it up):
But Shay's comment, "copy of the data
directory of each production cluster, and move
it to development" makes sense. I'll try that
out but in the mean time any other direct
answers to my question would be most welcome.
On Thu, Mar 15, 2012 at 12:21 PM, gearond
Want to know this also. Posting to
View this message in context:
Sent from the ElasticSearch Users
mailing list archive at Nabble.com.