It is the full Erlang node name that is stashed in the mnesia structures. This is set either via the -name (uses full hostname) or -sname (use only local machine name) erl command line option. So it'll depend a bit on what your rabbit configuration/startup scripts say.<br>
<br>One way of making a particular Erlang node with mnesia easily relocatable is to specify -sname myname@localhost, explicitly overriding the local machine name by using localhost. This obviously only works if you're not doing anything distributed, like clustering.<br>
<br>Robby<br><br><br><div class="gmail_quote">On Fri, Apr 15, 2011 at 11:35 AM, Alext0 <span dir="ltr"><<a href="mailto:althomas@maninvestments.com">althomas@maninvestments.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Thanks Simon, that's good news.<br>
<br>
This did come from a reputable source (!) - perhaps it applies to clusters?<br>
I mentioned mnesia, but of course we don't want any file to be "pinned".<br>
<br>
We'll probably ask for some confirmation that this is the case (and will<br>
hold for future releases) via official channels so that we have confidence<br>
our disaster recovery plan is valid.<br>
<br>
cheers<br>
Alex<br>
<div><div></div><div class="h5"><br>
<br>
Simon MacMullen-2 wrote:<br>
><br>
> On 11/04/11 15:18, Alext0 wrote:<br>
>> OK, a query with almost the same subject was posted a while ago!<br>
>><br>
>> But that concerned clustering, DRBD etc, and our scenario is much<br>
>> simpler...<br>
>><br>
>> We want to migrate an RMQ instance from one machine to another by<br>
>> stopping<br>
>> it, transferring the data files and restarting it at the destination.<br>
>><br>
>> Externally, the DNS hostname is migrated from one IP address to the<br>
>> other.<br>
>> Our RMQ nodename will use the DNS name (e.g. RMQ1 - not a FQDN) so this<br>
>> won't need to change.<br>
>><br>
>> Despite this, we heard there might be references to the IP address in<br>
>> mnesia<br>
>> files and hence migrating the IP address too would be required (i.e. we<br>
>> need<br>
>> a VIP) - can we get away without this?<br>
><br>
> I don't believe Mnesia embeds IP addresses (where did you hear that?).<br>
> You should be fine.<br>
><br>
> Cheers, Simon<br>
><br>
> --<br>
> Simon MacMullen<br>
> Staff Engineer, RabbitMQ<br>
> SpringSource, a division of VMware<br>
><br>
> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><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>
><br>
><br>
<br>
</div></div><font color="#888888">--<br>
View this message in context: <a href="http://old.nabble.com/Portability-of-mnesia-and-other-data-between-IP-addresses-tp31370661p31404585.html" target="_blank">http://old.nabble.com/Portability-of-mnesia-and-other-data-between-IP-addresses-tp31370661p31404585.html</a><br>
</font><div class="im">Sent from the RabbitMQ mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><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>
</div></div></blockquote></div><br>