Linux high availability
location: ubuntuforums.com - date: July 13, 2012
I am new to Linux high availability and would like to have a setup that keeps my severs up 99.999% of the time.
This will be servers that will be running Ubuntu 12.04 LTS Server with Apache and PostgresSQL as the database.
I did some reading under the Linux-HA (heartbeat) project but it seems a bit out dated? So I saw a post that said that I should rather use Corrosync as the heartbeat messaging layer.
Is corrosync the answer to use with pacemaker on Ubuntu 12.04?
I am not entirely sure how all the dots connect so here is how I understand it:
To setup a High availability server I need.
* Heartbeat OR corosync
Not sure what openAIS is
* DRBD or some kind of NFS share that syncs. I know rsync is not the best solution for this.
So basically what I what is one IP that switches between 2 - 4 + nodes if the main server fails ( IP failover), The servers must load balance, I DO NOT want to use external storage like
high availability and clustering
location: ubuntuforums.com - date: June 1, 2009
advise suggest and comments what are all possible clustering, high availbility solution available under ubuntu server enviornment.
also can some one point out what are opensource and what are paid/commercial
i found heartbeat(DRBD) and linux-ha
but i have confusion to understand clearly. the first question is it compatible with our ubuntu 8.04 LTS or later on or not. is it certify safe to use
can some one share his own experience testing or production results
we need to make parallel cluster of email server base on ubuntu. which is part of disaster recovery plan. if 1st server get crashed or burn(office premises) so other server come one automaticaly
Linux High Availability Clustering
location: linuxquestions.com - date: March 26, 2012
hi guys, any good software for Linux High Availability Clustering? Tutorials and guides would be great as well.
High Availability Load Balancing and LAMP Servers
location: ubuntuforums.com - date: December 29, 2010
Hello! I figured I would follow this up with what came of my solution search and what we have currently in production We are averaging 1.2m uniques/month and utilize the majority of a 6mb pipe with burst option.
While I was looking for the best of both worlds, it would seem the only easy/free solutions are either live/failover or replication servers, where I was wanting a fully redundant live master/master configuration throughout our entire server system. Reality comes in when you have to start making sacrifices for flexibility or easy of use (I know some hard code *nix monkeys are going to yell at me for that one!).
Old server specs (1 unit):
- 1 x HP DL380 G5 : Dual Xeon 4-core, 8 gig ram, 6 * Cheetah 74gb SAS1 in RAID5, CentOS 5
First hardware specs (all on a gigabit network):
- 2 x SUPERMICRO SYS-5015A-EHF-D525 : Dual Core Atom based 1U servers with 4gb DDR3 memory and a 16gb SSD SLC HDD. Low power, all flash based load balancers. Mobo's feature Intel 82574L LANs!
- 2 x SUPERM
Fencing with VMware ESXi 5.1 (For High Availability)
location: linuxquestions.com - date: January 30, 2014
In the Internet there are nothing about Fencing using luci-ricci (Conga). I have read out many things from Red hat Administration guide and others.But there are just concept and such straight description about the fencing but no proper example or tutorial.
In my lab I have vMware ESXi 5.1 running,
Two Red Hat 6.4 running in the vm.
So can I get any proper instruction/tutorial about doing High Availability using Fencing by the vmware's "fence_vmware_soap" mechanism ?
It will be a great appreciation for any help.
How to install heartbeat(High Availability) in Redhat Linux 6.4 for clustering
location: linuxquestions.com - date: November 29, 2013
what is appropriate packages to install heartbeat in redhat 6.4.
Installation of heartbeat is a commercial
if it is commercial what we need to buy..please give me quick reply
Good setup with Xen for High Availability
location: linuxquestions.com - date: March 19, 2014
We are in the process to ditch our physical servers and move to virtualization. I have tested a few solutions, and we have decided to use Xen - still open between "Linux Xen" or Citrix Xenserver.
We do want HA, even though our servers & applications running are not strictly business critical - downtimes will mainly affect our developers (which of course comes with a cost & annoyance, but no impact for clients). Maybe "automatic" failover is not absolutely necessary, but we must be able to manually shut down one host, one storage server without affecting running guests.
There will be 8-12 guests running (only Linux servers w/o GUI), total storage used today for all is around 100GB.
So, the plan is to have 2 nodes in one pool, my main concern is configuring storage. I'm thinking a Storage repository with 2 physical servers running DRBD here. Any objections?
Looking at the minimal configuration:
2 physical servers as Xen hosts. One 1TB disk each which
High Availability and Failover with Centos 6.3
location: linuxquestions.com - date: July 28, 2012
My aim is to setup a high-availability and failover setup for a webserver. I am a total newbie on this so I had quite a bit to read on this. I also followed a few tutorials/howtos on the web but without 100% success.
Here is my setup:
I have two machines with internal IPs, let's say: node01 192.168.10.82 and node02: 192.168.10.83
node01 also has a virtual IP 192.168.10.81, which is supposed to move between node01 and node02 in case of failover.
I have one external IP let's say: 96.xxx.xxx.xxx NAT'ed to 192.168.10.81
Both nodes have
Centos 6.3 minimal install
Here are the ha config files:
# cat /etc/ha.d/authkeys
2 sha1 test-ha
# cat /etc/ha.d/ha.cf
# cat /etc/ha.d/haresources
node01 192.168.10.81 httpd
If I shutdown heartbeat on node01, httpd automa
Heartbeat high availability with NAMED?
location: linuxquestions.com - date: May 4, 2009
For our network, we have 2 resolving name servers like this for instance:
* Recursive NS - 10.100.1.1
* Recursive NS - 10.100.1.2
We have a few hundred Linux machines with these two IP's in resolv.conf (or worse yet, some machines might only have one of the IP's above.)
So obviously regardless of the state of the two machines, both IP's must always be listening with DNS. How can we make the other automatically take over in the event of a failure?
I've been trying to adopt heartbeat to take on this task. It seems to monitor two severs via serial cable, and has backend scripts to manage starting/stopping the daemon. It seems to have scripts for Oracle, Apache, MySQL; but no script for NameD.
Has anyone had experience in a similar high-availability failover with DNS resolution? We're familiar with BIND and would prefer not to use DJBDNS.
I'd like to hear experiences people have had with heartbeat or other solutions. It really seems simple; but there's been no practic
Redhat 5 High Availability Addon
location: linuxquestions.com - date: October 21, 2012
I have a question about Redhat HA Add-On, how can i setup an Active/Active Cluster using Redhat 5.7 64Bit, with Round-Robin technique.
Each server will run an application and oracle database without RAC.
Page: 1 2 3 4 5 6 7 8 9 10