Index: [Article Count Order] [Thread]

Date:  Mon, 19 Jun 2006 19:40:37 +0100
From:  "Colin Jack" <colin (at mark) mainline.co.uk>
Subject:  [coba-e:05803] Re: Redundancy
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <F07DD4D0940AFF41A207BE85479D2AFF180D5C (at mark) server.mainline.local>
X-Mail-Count: 05803

A friend had this running like this before, but ran into performance
issues. Maybe worth revisiting?

Regards

Colin 

> -----Original Message-----
> From: Richard Siddall [mailto:cobalt (at mark) elirion.net] 
> Sent: 19 June 2006 18:30
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:05800] Re: Redundancy
> 
> Colin Jack wrote:
> > I am not an linux expert, but was wondering whether in 
> principal the 
> > following is 'do-able' ...
> > 
> > Have CMU backup to an FTP server every night and then have another 
> > backup server running cmuImport every night on a cronjob to 
> duplicate 
> > the other server. Then if the primary goes down we could have some 
> > sort of heartbeat monitor that switches across to the backup. Yes, 
> > users may get some dupe mail, but apart from that everything should 
> > carry on before ... or am I being na$B}W(Be here?
> > 
> > Colin
> > 
> 
> Colin,
> 
> We've done something like this, except that we really only 
> used CMU to back up the configuration of the server.  We used 
> rsync to copy over all the vsite files and e-mail.
> 
> Regards,
> 
> 	Richard Siddall
> 
> 
>