Hi Adam, You need to restore the backup on the second controller. The general flow is as follows:
1.) Initialize first backend. 2.) Dump backend contents. This creates a dump with an associated checkpoint. You can enable the backend at this time. 3.) Transfer log and dump to second controller. This gets the controllers syncrhonized. 4.) Load the dump on the second backend. 5.) Enable the second backend. At this point your cluster is up and running. Cheers, Robert On 7/7/08 12:27 PM, "Adam Purkiss" <[EMAIL PROTECTED]> wrote: That was the reason it did not start up. I will see if this fixes things Can I confirm that if I use this then when I restore backend DB1 on controller 1 do I need to restore the same backup on controller 2 or do I just enable it. From: [EMAIL PROTECTED] To: [email protected] Date: Mon, 7 Jul 2008 11:54:09 -0700 Subject: Re: [Sequoia] DB failover does not seem to be working Hi Adam, Can you check your hedera.properties file and look at the JGroups config file name? If it is sequencer.xml, you have just hit a configuration problem that is logged as sequoia-1102, which is fixed in the codeline. The problem is that the jgroups-all.jar file also contains a sequencer.xml file with a bad IP address. It picks this up before the Sequoia version. To correct the problem, rename config/sequencer.xml to config/sequoia_sequencer.xml and adjust the name accordingly in the Hedera properties file referenced by your virtual database. Thanks, Robert -- Robert Hodges, CTO, Continuent, Inc. Email: [EMAIL PROTECTED] Mobile: +1-510-501-3728 Skype: hodgesrm
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
