Linux Replicated High Availability Manager 1.4.2 (DRBD 8.2 based branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Linux Replicated High Availability Manager 1.4.2 (DRBD 8.2 based branch)
# 1  
Old 04-15-2008
Linux Replicated High Availability Manager 1.4.2 (DRBD 8.2 based branch)

The Linux Replicated High Availability Manager (Linuxha.net) allows the creation of clusters for application high availability through data replication. Currently, clusters are limited to two nodes, but multiple applications can be hosted and failed-over between the nodes. The software uses DRBD to provide the data replication facillity. License: GNU General Public License v2 Changes:
Many minor and major bugs have been fixed. The administrators guide documentation has been updated to reflect these changes and several other improvements.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

High availability of a process between two Linux servers

Hello, I would like to create a script that will maintain HA/failover of a process between two servers. I wanted to send a continuous heartbeat message through a script to another server when everything is working fine, if a process has gone down then the same message should be sent another... (4 Replies)
Discussion started by: Mahesh_RPM
4 Replies

2. Red Hat

Samba High Availability issue using luci (HA Manager) on CentOS

Hello, I am working on to setup a Samba High availability on CentOS using luci (HA Manager) and GFS2 using 2 nodes cluster. I am successfully able to configure GFS HA and VIP HA using luci but when trying to add samba server HA, i am in trouble and not able to figure out what is the issue.... (1 Reply)
Discussion started by: sunnysthakur
1 Replies
Login or Register to Ask a Question
clusters(4)						     Sun Cluster File Formats						       clusters(4)

NAME
clusters - cluster names database SYNOPSIS
/etc/clusters DESCRIPTION
The clusters file contains information regarding the known clusters in the local naming domain. For each cluster a single line should be present with the following information: clustername whitespace-delimited list of hosts Expansion is recursive if a name on the right hand side is tagged with the expansion marker: ``*''. Items are separated by any number of blanks and/or TAB characters. A `#' indicates the beginning of a comment. Characters up to the end of the line are not interpreted by routines which search the file. Cluster names may contain any printable character other than an upper case character, a field delimiter, NEWLINE, or comment character. The maximum length of a cluster name is 32 characters. This information is used by Sun Cluster system administration tools, like cconsole(1M) to specify a group of nodes to administer. The names used in this database must be host names, as used in the hosts database. The database is available from either NIS or NIS+ maps or a local file. Lookup order can be specified in the /etc/nsswitch.conf file. The default order is nis files. EXAMPLES
Example 1 A Sample /etc/clusters File Here is a typical /etc/clusters file: bothclusters *planets *wine planets mercury venus wine zinfandel merlot chardonnay riesling Here is a typical /etc/nsswitch.conf entry: clusters: nis files FILES
/etc/clusters /etc/nsswitch.conf ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
cconsole(1M), chosts(1M), serialports(4), nsswitch.conf(4), attributes(5) Sun Cluster 3.2 26 Jun 2006 clusters(4)