We asked the same question some weeks ago and got a positive answer back. We have things set up this way now, and are in the process of fixing issues with things that are different when running on the virtual DB as opposed to running directly on postgres. (In our case postgres sequence numbers and ending up in infinite loops in sequoia).
When we have this fully working, at some point we will use (at least) 3 machines to make sure we do not have a single point of failure when we perform maintenance on one of the nodes. Regards - henrik -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Sent: onsdag 17 oktober 2007 15:14 To: Sequoia general mailing list Subject: [Sequoia] sanity check I have two machines that I'd like to run a virtual database on. I want it to neither machine is a single point of failure. So in this situation, the only way to do it that I can see is to have, per machine, a controller and single backend (behind that controller). Then the JDBC url for calling code lists boths those controllers. Does this sound a) workable b) sane? lex _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
