Thanks Christian, the 2 locations are VPN'd together, but have 2 different WAN IPs. I guess I could set up both the routers to port forward to the HA virtual LAN IP, then it wouldn't matter which location the query comes in on, it will always go to the available server.
Wow this has gone so off topic from SOGo, I do apologize. Thanks for all your help, I think I have a general idea of how to set this up, once I get the hardware and start, I may have more questions lol. Carlin On Mon, Oct 29, 2012 at 10:53 AM, Christian Mack < christian.m...@uni-konstanz.de> wrote: > Hello Carlin Hefner > > > On 2012-10-29 14:48, Carlin Hefner wrote: > > Thanks Marc, the problem is we rely on email heavily, so what I mean is > > that we can't have any incoming mail delayed to our inbox. But it's good > > to know that we wont actually loose anything. > > > > Davor, thank you! DRBD looks perfect! > > I'll use that, and a DNS failover to switch incoming requests to the > > backup location/server. > > > > Question, a little off topic but do you know if DRBD or a heartbeat > > service can automatically change DNS entries for failover? > > > > With heartbeat you normally use a service DNS name and IP address. > This IP will be switched to the current running system. > With this you don't need to change DNS at all. > This has the advantage, that your clients will always see the same > service name and IP. > It also has the advantage that you don't have to reduce your DNS TTL for > this entry, in order to switch fast. > > But I don't know, if this is possible for you, as you have two different > locations. > If they use different IP ranges, then it can not work, because you have > to route differently. > > > Kind regards, > Christian Mack > > -- > Christian Mack > Gruppe Informationsdienste > Rechenzentrum Universität Konstanz > -- > users@sogo.nu > https://inverse.ca/sogo/lists > -- users@sogo.nu https://inverse.ca/sogo/lists
