Re: Reverting failover

2013-04-18 Thread Sven Schwedas
Hi, On 18.04.2013 12:18, Janne Peltonen wrote: > Hi! > > On Thu, Apr 18, 2013 at 11:59:31AM +0200, Sven Schwedas wrote: >>> 1) force syncronisation >>> 3) manually run any remaining synclogs >> >> How do I do that / what's the difference between forced sync and a >> manual sync log run? > > I me

Re: Reverting failover

2013-04-18 Thread Janne Peltonen
Hi! On Thu, Apr 18, 2013 at 11:59:31AM +0200, Sven Schwedas wrote: > > 1) force syncronisation > > 3) manually run any remaining synclogs > > How do I do that / what's the difference between forced sync and a > manual sync log run? I mean that in the first case, you give a list of all your users

Re: Reverting failover

2013-04-18 Thread Sven Schwedas
Hi, On 18.04.2013 11:24, Janne Peltonen wrote: > Hi! > > On Thu, Apr 18, 2013 at 10:45:03AM +0200, Sven Schwedas wrote: >> If I understand correctly, failover is simply done by pointing clients >> to the replica (e.g. moving public IP)? > > More or less. You'll also have to make sure sync_server

Re: Reverting failover

2013-04-18 Thread Janne Peltonen
Hi! On Thu, Apr 18, 2013 at 10:45:03AM +0200, Sven Schwedas wrote: > If I understand correctly, failover is simply done by pointing clients > to the replica (e.g. moving public IP)? More or less. You'll also have to make sure sync_server is no longer running on the replica but all the other relev

Reverting failover

2013-04-18 Thread Sven Schwedas
Hello, If I understand correctly, failover is simply done by pointing clients to the replica (e.g. moving public IP)? We can assume that only one server is ever accessed by clients (both IMAP and SMTP/LMTP), they only have access to the public IP, which is switched over manually. How do I then m

Re: Virtual Domains or not

2013-04-18 Thread Valentin Bud
Hello Marc, Thank you for your answer. I will go with virtual domains and separate mailboxes for now. On 4/16/13 10:51 AM, Marc Patermann wrote: > Valentin, > > Valentin Bud schrieb (16.04.2013 08:19 Uhr): > >> I am trying to figure out what would be a "best practice" when one >> has a couple