Hi All,
One of my customers has a large (21GB) production zodb which they back
up onto a contingency server using repozo and rsync. The process is
roughly as follows:
1. pack the production database to 3 days once a day.
2. create a full backup with repozo and rsync this to the contingency
Chris Withers wrote at 2006-10-4 15:06 +0100:
...
The interesting thing is that it looks like the transactions where the
time appears to go backwards are duplicates of earlier transactions:
position in file tid time from tid
310253762330x03689abb582f1311 2006-10-03
Dieter Maurer wrote:
3. If repozo is not to blame, what could be?
One possibility would be a bad call.
A bad call?
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist
Chris Withers wrote at 2006-10-4 18:23 +0100:
Dieter Maurer wrote:
3. If repozo is not to blame, what could be?
One possibility would be a bad call.
A bad call?
You should read my messages carefully!
E.g. a call where the same incremental backup file
is presented more than onces to
