In theory you could use a script bring down cce gracefully, tar the =
essential stuff and copy somewhere at like midnight or so and then bring =
it back up and copy to an alternate location. There are a lot of file =
to be concern, but should be possible. In the event of a crash you will =
need to untar on top of an existing server and will recreate the =
environment. cce will take a few seconds to copy so the server should =
not be down for more than maybe 10 seconds or so, the rest is simple =
copy of files.
----- Original Message -----=20
From: Colin Jack=20
To: coba-e (at mark) bluequartz.org=20
Sent: Monday, June 19, 2006 12:56 PM
Subject: [coba-e:05799] Re: Redundancy
Already got that ... but not going to help if the PSU blows and takes =
the motherboard out!
I need a virtually seamless changeover in the case of a disaster. This =
stuff is colocoed 2 hours drive away!
Colin
-------------------------------------------------------------------------=
---
From: Support [mailto:support (at mark) domain-nameit.net]=20
Sent: 19 June 2006 16:39
To: Colin Jack
Subject: Re: [coba-e:05797] Redundancy
use RAID-1
Colin Jack <colin (at mark) mainline.co.uk> 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=EFve here?
Colin
5801_2.html (attatchment)