08-11-2010
HA Cluster solution for Linux - which one to use?
Hi all experts,
I need your kind suggestions or feedback on choice of clustering software for red hat linux nodes running certain applications which I need to make highly available.
Minimum requirement is 2 nodes; all nodes shall be active-active running distinct applications e.g. node 1 runs application ABC and node 2 runs application PQR, node 1 is back up node for PQR and node 2 for ABC. Node 1 and node 2 do not have any shared storage required, they access back end database which is protected by Oracle's dataguard.
I need to have cost-effective HA with minimum downtime. There are various HA solutions available in market - SteelEye, Veritas Cluster, Red Hat cluster suite, IBM HACMP etc. and I have almost narrowed down to Red Hat Cluster(for it being cheaper) vs Veritas (for it being feature rich).
Any experiences with clustering? Any pros and cons of these two cluster software (with references would be appreciated) would be of great help?
Dear mods, if this thread is not suitable for this sub-forum; kindly advise where to post within this forum
5 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear All Experts,
Would like to know the maturity/ stability of Redhat Linux AS 3.0 and Solaris.
My organization need to setup cluster solution. We are well-versed with Veritas Cluster on Solaris.
We are thinking of waiting for certification support of the various ISV like Oracle, Veritas... (3 Replies)
Discussion started by: izy100
3 Replies
2. Linux
All,
I am most familiar with Solaris, and I am in the process of learning Linux (Fedora 5), and one of my tasks is to replace our current NAS solution. We currently use EMC Celerra, but it is way too expensive for what we use it for. So I have looked into Linux.
We mostly we have a Windows... (1 Reply)
Discussion started by: kjbaumann
1 Replies
3. Red Hat
Hi ,
I am a complete newbie to linux, I have been given a job to install a mail solution (postfix if possible) I would like to know how should I go about installing..)
Can any one provide me some steps to go about it..
i have read about postfix and the installation steps, it seems there are... (1 Reply)
Discussion started by: anilhk
1 Replies
4. High Performance Computing
Hi, I am not sure if the term "cluster" fits my situation or not. I have 5 Linux computers, each has different a host-name, and my users have to remember those the computer names to login and find out which computers have free CPUs, so they can run their jobs on those computers have free CPUs.
... (4 Replies)
Discussion started by: hiepng
4 Replies
5. Red Hat
Can some one tell me free cluster solution avaialable for RHEL5 we just want to test the clustering on RHEL. (6 Replies)
Discussion started by: fugitive
6 Replies
LEARN ABOUT OPENSOLARIS
scversions
scversions(1M) System Administration Commands scversions(1M)
NAME
scversions - Sun Cluster version management
SYNOPSIS
scversions [-c]
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
The scversions command commits the cluster to a new level of functionality after a rolling-upgrade to new Sun Cluster software. With no
arguments, the scversions command prints a message indicating whether a commitment is needed.
OPERANDS
The following operands are supported:
-c Commit the set of nodes that are currently active members of the cluster to the highest possible level of functionality.
When you upgrade a node (either through upgrade to a new release of the product or by application of a patch) and boot it back
into the cluster, some of the internal protocols on that node might have to run at lower versions in order to cooperate cor-
rectly with other nodes in the cluster. When the cluster is in this state, some administrative actions might be disabled and
some new functionality introduced in the upgrade might be unavailable.
When you run this command once from any node after all nodes are upgraded, the cluster switches to the highest versions of
internal protocols possible. Assuming that all nodes have the same Sun Cluster software installed at that time, all new func-
tionality becomes available and any administrative restrictions are removed.
If a node that has not been upgraded is an active member of the cluster at the time you run the -c option to scversions, the
command has no effect because the cluster is already running at the highest possible level of functionality.
If a node has not been upgraded and is not an active member of the cluster when you run the -c option to scversions (for exam-
ple, if that node is down for maintenance), the internal protocols of the cluster are upgraded to the highest possible ver-
sions. You might have to upgrade the node that was not an active member of the cluster to enable it to rejoin the cluster.
EXIT STATUS
0 Success
non-zero Failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsczu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
scinstall(1M)
Sun Cluster 3.2 17 Aug 2007 scversions(1M)