Date:  Mon, 10 Dec 2007 19:08:28 -0000
From:  "Jason Ozin at Technica Solutions" <jason (at mark) tec1.co.uk>
Subject:  [coba-e:11391] Re: Project Live? - Updates - Disaster Recovery
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <007b01c83b60$0bdaffa0$2390fee0$ (at mark) co.uk>
In-Reply-To:  <200712101353.58354.bq (at mark) solarspeed.net>
References:  <683F5FB5E2C08E4A8FE8D499A890A3EA0378B7 (at mark) mainserver.mainline.local> <008b01c83a65$79293230$6b7b9690$ (at mark) co.uk> <00b601c83a6f$51871fd0$f4955f70$ (at mark) co.uk> <200712101353.58354.bq (at mark) solarspeed.net>
X-Mail-Count: 11391

Thanks Michael

> The official homepage for the BlueQuartz project is http://bluequartz.org

OK I found that - not that active but thanks.

> The only relevant menu entries in "BlueLinQ" are this:
> "YUM Updater": This is how you update BlueQuartz.
> All other menu entries are more or less deprecated

Thanks for confirming that

> A better approach is to use clustering - for example with DRBD and Heartbeat.
> While a "do it yourself" approach is of course possible, 
> there is also a commercial software available which does this out of the box.

Happy to pay but I'm not convinced such a solution would work with the servers geographically separate and connected via slowish Internet only. What do you think?