[asterisk-users] High Availability with Asterisk

[Michelle Dupuis]

Some food for thought:

If you use DRBD, then you will mirror corruption from one system to another.  You also cannot selectively pick files in a folder to mirror (you will mirror a lot!)  As well, DRBD struggles as peers are set further apart (latency) or number of changes increases.

A lot of HA tools don't look deeper into Asterisk to see if/how it has failed (they only detected catastrophic failures).  What happens when the Asterisk process is alive but no longer bridging calls?

If asterisk/host processes mess up an consume huge amounts of system resources, most HA tools cannot respond.

As a biased recommendation, take a look at HAAst at www.generationd.com  It takes care of moving a shared IP between hosts as well as other features.

Michelle


(I work for Generationd :)


________________________________________
From: asterisk-users-bounces at lists.digium.com <asterisk-users-bounces at lists.digium.com> on behalf of Thorolf Godawa <nospam at godawa.de>
Sent: Thursday, March 6, 2014 10:21 AM
To: Asterisk Users List
Subject: [asterisk-users] High Availability with Asterisk

Hi everybody,

what are the current options to get an Asterisk-system high available?


Using two servers as active/passive with DRBD, Pacemaker/Corosync works
very good, there are no quality issues of the voice quality, even not on
high loaded servers and no problems with a lot of small packages.

But for this you need two systems for every Asterisk-system, what is not
"economic" in any way.


Using (para-)virtualization with Xen could be an other option, on
systems with low load this works reliable, but what happens on systems
with high load? Are there any issues known about problems with the
realtime, packet loss etc. because it runs in a VM?

The idea would be having a HA-cluster of two servers with Xen, each of
them runs one instance of an Asterisk-system in a single VM and on a
failure the VM will be restarted on the other node.

This might result in a much higher load on this node, because is runs
two VMs, but for a short period, until the other node comes back again,
it might be tolerable.


Are there other options running two Asterisk-instances parallel on one
system, each binded on it's own IP, maybe s.th. with chroot or similar?


Thanks a lot,
--

kind regards,

Thorolf

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users