I've just noticed another thing on this 'how to backup Data.fs' issue. Preparing to backup my work, I did a pack, and was then going to archive the resulting Data.fs.old. Because I'd added and deleted a bunch of files earlier today, the Data.fs.old file was 22M in size, and the freshly packed Data.fs was 4M. For example: -rw-r--r-- 1 zope WebAuths 4325257 Jan 18 15:30 Data.fs -rw-r--r-- 1 zope WebAuths 76750 Jan 8 08:43 Data.fs.in -rw-r--r-- 1 zope WebAuths 129950 Jan 17 13:59 Data.fs.index -rw-r--r-- 1 zope WebAuths 4 Jan 9 11:33 Data.fs.lock -rw-r--r-- 1 zope WebAuths 22026222 Jan 17 13:53 Data.fs.old -rw-r--r-- 1 zope WebAuths 188416 Jan 18 15:43 Data.fs.pack -rw-r--r-- 1 zope WebAuths 8656275 Jan 18 15:30 Data.fs.tmp So, I tried running another pack, figuring that the .old file would then be replaced with a copy of the 4M file. But, it remained at 22M. I then deleted the Data.fs.old file, and re-ran the pack. At this point, I noticed that there has been a Data.fs.pack file around, and I don't get a new Data.fs.old. For example: -rw-r--r-- 1 zope WebAuths 4325257 Jan 18 15:30 Data.fs -rw-r--r-- 1 zope WebAuths 76750 Jan 8 08:43 Data.fs.in -rw-r--r-- 1 zope WebAuths 129950 Jan 17 13:59 Data.fs.index -rw-r--r-- 1 zope WebAuths 4 Jan 9 11:33 Data.fs.lock -rw-r--r-- 1 zope WebAuths 4079616 Jan 18 15:43 Data.fs.pack -rw-r--r-- 1 zope WebAuths 8656275 Jan 18 15:30 Data.fs.tmp I'm running 2.2.5, under redhat 7.0. It seems like the idea of running a pack and then archiving Data.fs.old may not always be giving me a valid archive. Should I archive the Data.fs.pack file instead? Oleg Broytmann wrote:
On Thu, 18 Jan 2001, Etienne Labuschagne wrote:
What is the best way to backup Zope's database whithout stopping Zope? When
Pack + backup Data.fs.old.
-- Martin Stitt Chief Software Engineer Esker, Inc. email: marty.stitt@esker.com phone: (608) 273-6000 x331 fax: (608) 273-8227 web: http://www.esker.com