On 28/10/2007 Sam Stainsby wrote:
We use the repozo backup (and restore) tool that comes with Zope and
include the backup repository in our normal backup regime (which uses
backuppc).
zopeinstalldir/bin/repozo.py
Read inside the file for the doco. This tool is designed to work with
On Mon, 29 Oct 2007 15:15:51 +0100, Jonas Meurer wrote:
From what others said, a local copy of the 'live Data.fs' is safe as
well, as zope appends new transactions to the end of Data.fs.
To quote Andreas Jung:
An inconsistent copy of the Data.fs is not the problem since
On 29/10/2007 Sam Stainsby wrote:
To quote Andreas Jung:
An inconsistent copy of the Data.fs is not the problem since
invalid transaction entries will be discarded by the ZODB.
That's the theory. But why trust a higher risk strategy, when there is a
perfectly good tool
On Sun, 28 Oct 2007 20:15:27 +0100, Jonas Meurer wrote:
i'll change that to backup a local copy of the Data.fs instead in
future. a simple solution would be to run 'cp Data.fs Data.fs.safe' for
every instance just before backuppc starts the rsync process.
We use the repozo backup (and
