[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] StaQWare [RaQ 3]
- Subject: Re: [cobalt-users] StaQWare [RaQ 3]
- From: "Kevin D" <kdlists@xxxxxxxxxxxxxxx>
- Date: Tue Jul 17 23:43:43 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
From: "Sean Chester" <seanc@xxxxxxxxxxxxxxxxxxxxxx>
> Is anyone using StaQWare on a RaQ 3
No, but I've looked at it.
> 1) Does it work on a RaQ3 ? All the reviews i read mention the RaQ3i, is
> there much difference between a raq3 and a 3i ?
I don't believe the raq3 has a second NIC, and your raq needs 2 NICs to use
staqware (both the primary and backup raqs are connected using the second
nic).
> 2) Does it takeover a failed server quite seemlessly ? (ie. do you notice
> when it takes over? how quick does it do it?)
No, I believe it can take up to 12 minutes to failover, as the backup raq
must restart before it can take over for the primary raq.
> 3) If my main server is hacked? is the backup (clustered) server hacked
to?
> (does it mirror continuesly?)
Not necessarily but possibly. It depends on how the server gets hacked and
what gets mirrored. I'm not entirely sure of the staqware details, but I
would imagine that the the config files as well as the /home partition must
get mirrored. Thus, it is possible for your backup raq to be hacked after
reboot.
Personally, I don't like staqware because you have an entire raq sitting on
deck doing absolutely nothing, except waiting. The failover time not being
immediate is also a big drawback. What I'd like to see with staqware is a
clustering solution, like what the dell powerEdge systems use. That way,
your backup raq acts as an actual backup, yet it can actually do something
besides waiting for your primary server to fail. Failover in a cluster is
immediate. You don't necessarily need a second NIC when using a cluster.
You can set this up yourself on cobalt raqs, but you'll need to do some
research and a lot of telnetting :)
Kevin