[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zope
Subject:    Re: [Zope] Fail-safe redundancy policies for Zope
From:       Toby Dickenson <tdickenson () devmail ! geminidataloggers ! co ! uk>
Date:       2004-10-08 8:23:13
Message-ID: 200410080923.13231.tdickenson () devmail ! geminidataloggers ! co ! uk
[Download RAW message or body]

On Wednesday 06 October 2004 21:05, Paul Winkler wrote:

> You could also use DirectoryStorage and frequently replicate to a
> backup storage server.  The backup can't actually serve to ZEO clients
> as long as you're replicating to it, but you might be able to come up with
> some scripts that automatically start a live storage process on
> the backup if the primary fails.  

> Reverting to the primary server might have to be
> a largely manual process.

Maybe, if your backup is read/write. The master maybe contains a few changes 
made just before the outage, and the backup contains the changes made during 
the outage. You need to manually merge those (or more likely, choose one set 
to throw away).

If your secondary is read-only, then whatever heatbeat process switched in the 
backup server should be able to automatically switch it out too.

-- 
Toby Dickenson
_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )
[prev in list] [next in list] [prev in thread] [next in thread]