search for: availibilty

being from a telecoms background, the thought of a single asterisk box solution (even in a low production environment of say <10 phones) worries me slightly! starting from say a base of asterisk@home, you would have several MySQL databases, in addition to numerous config files. I have looked at high availiblity solutions, and from a hardware monitoring point of view, its relitivly straight

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1325788840 -3600 # Node ID 2f5a98692acde9e74d4009f50f83a8aa08296310 # Parent 3a22ed3ec534799b3cab55b0dc0a7380e701ecbe add feature flag to xenstore for XS_RESET_WATCHES Tell guest about availibilty of xenstoreds XS_RESET_WATCHES function. Guests can not issue this command unconditionally because some buggy toolstacks (such as EC2) do not ignore unknown commands properly. Signed-off-by: Olaf Hering <olaf@aepfle.de> diff -r 3a22ed3ec534 -r 2f5a98692acd tools/libxl/libxl_create.c --- a/t...

My mailboxes are on a Dovecot (IMAP) server.On DNS there is an MX record pointing to the server.To read the mail I use Roundcube.If the server is down, I lose the new mail. I would like to do two things, alternatively. First option.1) I keeep the mail on the provider's server, restoring the original MX record.2) Dovecot does not receive the mail, but should go to download it.3) I can access

.../ etc. I am trying to figure out the best way to set things up so that I can run several (eventually) production linux guests (mostly debian stable) on the 2 KVM host systems and be able to migrate them when maintenance is required on their hosts. Performance is of medium importance, stability/availibilty is pretty high priority. A common opinion seems to be that using LVs to hold disk images gives possibly the best IO performance, followed by raw, then qcow2. Would you agree or disagree with this? What evidence can you provide? I am also rather confused about using shared storage, and what op...

...s an issue or if you need something more professional for a business environemnt, then configure a second MX with the same SMTP and dovecot configuration, then configure replication between the two dovecot instances. https://wiki.dovecot.org/Replication HTTP is another topic. If you also need high availibilty of your roundcube frontend, then you'd need a reverse proxy/load balancer in front of your server that can detect the outage and then direct the user to the other frontend on the second MX. HTH, Stefan PS: The text part in you email is broken (no line breaks).