It's been a while since I've "moved" a repository from one host to another. IIRC, the Node must be updated manually in that case.
Just do it through a normal transaction. Open the repository with a local session, #begin, update the node the hostname and port the primary will be running on, then #commit. If you want to do HA, make a #fullBackup AFTER you start primary and copy those backup files to your secondary host and start it up (you may rename the repository directory in the target if you wish - Magma doesn't care). That secondary will look into the persistent Node to know where to connect to the primary to receive updates.
I run all my my repositories HA, but my environment and processes have been stable for a couple of years now - so it's been a while since I've been in the HA code - so please forgive my going by memory here. Let me know if you have any troubles.
- Chris
On Fri, Aug 12, 2011 at 10:05 AM, Milan Mimica milan.mimica@gmail.com wrote:
Chris Muller wrote:
Yes, the Node is a persistent object in the database and the server commits its hostname - using NetNameResolver localHostName. See MagmaServerConsole>>#thisLocation and you can browse senders from there if you're interested. It sounds like you need to set up a hostname for your machine.
Now that's some useful info. I have transfered the database from my machine to a dedicated server. By transfered I mean plain file copy. So the remote database now has the wrong Node written, with "localhost" in it. How do I fix?
-- Milan Mimica http://sparklet.sf.net