On Tue, Jan 8, 2013 at 11:56 AM, Todd Nine wrote:
> Our current production
> cluster is still on 1.0.x, so we can either fire up a 1.0.x cluster, then
> upgrade every node to accomplish this, or just use the script.
No 1.0 cluster is required to restore 1.0 directory structure to a 1.1
cluster an
Our use case is for testing migrations in our data, as well as stress testing
outside our production environment. To do this, we load our backups into a
fresh cluster, then perform our testing. Our current production cluster is
still on 1.0.x, so we can either fire up a 1.0.x cluster, then upg
I thought this was to load between separate clusters not to upgrade within the
same cluster. No?
On Jan 8, 2013, at 11:29 AM, "Rob Coli" wrote:
> On Tue, Jan 8, 2013 at 8:41 AM, Todd Nine wrote:
>> I have recently been trying to restore backups from a v1.0.x cluster we
>> have into a 1.1.7 cl
On Tue, Jan 8, 2013 at 8:41 AM, Todd Nine wrote:
> I have recently been trying to restore backups from a v1.0.x cluster we
> have into a 1.1.7 cluster. This has not been as trivial as I expected, and
> I've had a lot of help from the IRC channel in tackling this problem. As a
> way of saying t
Hi all,
I have recently been trying to restore backups from a v1.0.x cluster we
have into a 1.1.7 cluster. This has not been as trivial as I expected, and
I've had a lot of help from the IRC channel in tackling this problem. As a
way of saying thanks, I'd like to contribute the updated ruby scr
