If you want cheap and reliable, then Sun Cluster for free seems to be a pretty good option. Of course one should always choose the option that works best for them.
On 5/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:
Yet in the past, the only way you could get ahold of or run sun cluster,
was if you sent personnel to the cluster class, then bought the package,
and paid maintenance on it.
Depending on the user's budget, that wasn't always the way to go.
I fully understand that you now get the cluster software for free, but if
you have problems, aside from the OpenSolaris community, you're on your own
unless you buy support. I haven't seen anything that states whether or
not training on the product is a requisite for getting support on Sun
Cluster, so I would assume that it is still a requirement, but I would hope
that I am wrong in that regard.
If you wanted to do something on the cheap, without all the overhead, this
works very well.
====================================================
Larry Becke
Sr. Technical Analyst
Mid-Range Operations, UNIX
Marsh Affinity Group Services
A Service of Seabury & Smith
====================================================
Only the individual sender is responsible for the content of the
message, and the message does not necessarily reflect the
position or policy of the Marsh Incorporated or its affiliates.
====================================================
"David Burge"
<[EMAIL PROTECTED]
ail.com> To
"Larry Becke"
05/17/2006 01:03 <[EMAIL PROTECTED]>
PM cc
opensolaris-discuss@opensolaris.org
Subject
Re: [osol-discuss] Re: Distributed
File System for Solaris
What you describe is what Sun Cluster provides as well as the ability to
access the data concurrently from both systems.
On 5/17/06, Larry Becke < [EMAIL PROTECTED]> wrote:
Not sure if it's been considered or not.
If you have disk that can be physically shared between two hosts, either
via SCSI, iSCSI or FC or some other mechanism, why not just create a
metaset out of the disk, share the metaset to the 2nd box.
Now, this doesn't allow full R/W + R/W on both boxes, however, if you set
up box b to monitor box a, if box a goes down, box b forces a takeover of
the metaset, mounts the filesystem (performs fsck if necessary), starts
the mail service on the *backup* server.
Then you aren't having to worry about continuously synchronizing filesets
over and over again.
It's simple to implement, and if you have something at the front end that
can intelligently route the mail traffic - possibly even configure a
virtual NIC that uses the same IP address as the primary server, so that
it comes up just prior to re-enabling the service.
Just a thought...
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
