[rabbitmq-discuss] Portability of the RabbitMQ database

Mon Jun 21 12:15:30 BST 2010

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthew Sackman wrote:
> On Mon, Jun 21, 2010 at 12:45:30PM +0200, Andreas Jung wrote:
>> I am playing over with replication and fail-over scenarios with RabbitMQ. So
>> I copied over the database directory
>> of production RabbitMQ server to a different machine and tried to restart
>> the RabbitMQ server with the database
>> of the production server. The production machine is running Linux and the
>> destination machines are Linux + MacOSX.
>>
>> The startup fails on both server...isn't the database portable across
>> different machine?
> 
> The database captures the nodename. You'll need to ensure that both
> machines have the same nodename. Setting the nodename to
> "rabbit at localhost" is the simplest way of achieving that. Other ideas
> are suggested in our HA pacemaker guide at
> http://www.rabbitmq.com/pacemaker.html

You can not use rabbit at localhost for a RabbitMQ cluster since you need
distinct node names..how would you move a database from a cluster node
to another server?

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwfSdIACgkQCJIWIbr9KYwTmwCfTjvdyHms8tqX8M7Vb21GaAbX
8xkAn205rMdC+PKXdI2aXD9xtMWqqDqm
=xsTc
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lists.vcf
Type: text/x-vcard
Size: 316 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100621/ee6d9ee4/attachment.vcf>