[cobalt-users] High availability/redundancy on Cobalt

[Chip <chip@xxxxxxxxxx>]

Chip wrote:
> I looked into the redundant solution offered by Cobalt, but it
apparently
> involves having the two Raqs close enough to each other that a serial
cable
> can be run between them... which defeats my intended purpose of having
the
> redundant Raqs in different NOCs.

To which  H.P. responded:
aren`t they connected using the second network interface (which could be
routed) ?

Um, don't know... I was told by a Cobalt corporate sales rep that the 
interconnection was via a serial cable that had to run between each 
unit.  I asked if this meant that they had to be physically close to one 
another and he said "yes".

really redundant servers in different nocs are a *really expensive*
project, as you would have to use at least mirroring and monitoring,
using a seperated dedicated line (as you might want redundancy for the
network connection and a safe way to transmit data between the units).

Well, I'm looking at "high availability" rather than "zero down time", with 
the idea being that the slave would ping the master unit, and "wake up" on 
a ping failure after so many seconds.  Obviously it wouldn't be *quite* up 
to date if there were constant database updates, but for our customers, it 
would be a satisfactory solution at much lower cost that 100% redundancy.