<div dir="ltr">I am not an expert :) but I can give you what I followed.<div><br></div><div>I initially setup consumers on both new and old data center. Then if you are using a load balancer, create a new VIP to gradually migrate your producers. (you should already have new datacenter members listed under new VIP.) Restarting one (producer) node at a time (after taking the server out of rotation) update the VIP to point to the new data center.</div>
<div><br></div><div>HTH, please let me know if you need more info.</div><div><br></div><div>Thanks!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 19, 2014 at 12:58 PM, Jeetu Jangle <span dir="ltr"><<a href="mailto:firstname.lastname@example.org" target="_blank">email@example.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>We are in process of migrating our services from one data center to another. We have a single instance RabbitMQ (version 2.3.1) (not clustered) running in current data center. We were able to migrate all our applications from 1 data center to another.
We want to migrate RabbitMQ (running 42 exchanges, 232 queues) to another data center with zero or little outage. I would like to ask the experts what steps we can carry to make sure that outage is minimal or zero.</div>
rabbitmq-discuss mailing list<br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>