so is the new Data.fs.index regenerated when Zope is restarted? ps - i've migrated Data.fs successfully and repeatedly between a netbsd 2.0 install a linux server with no issues. (and i didn't copy the .index file, only the Data.fs) tariq -----Original Message----- From: Tim Peters [mailto:tim.peters@gmail.com] Sent: 14 January 2005 14:41 To: zope@zope.org Subject: Re: [Zope] Copying Data.fs [John Poltorak]
Would there be any problem in copying Data.fs from one system to another and being able to use it?
You can even move it across operating systems (the FileStorage format is platform-independent). You take a small risk if you try to copy a Data.fs *while* it's in active use, because it's in a temporarily non-sane state during the time a transaction is being committed. More here: http://zope.org/Wikis/ZODB/FileStorageBackup _______________________________________________ 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 )
[Tariq Rashid]
so is the new Data.fs.index regenerated when Zope is restarted?
If you copy over the .fs file but not the .index file too, then it's best practice to delete the stale .index file (if any) on the destination machine. ZODB uses some heuristic checks to try to detect a mismatching .index file, and they're pretty strong heuristics, but it's possible they could fail to detect a mismatch.
ps - i've migrated Data.fs successfully and repeatedly between a netbsd 2.0 install a linux server withand i didn't copy the .index file,only the Data.fs)
It's always OK to delete an .index file. ZODB creates an .index file if none exists. Leaving behind a stale .index file is a little risky. I expect it's much riskier to leave stale persistent ZEO cache files in place, if the destination machine is being used as a ZEO server.
participants (2)
-
Tariq Rashid -
Tim Peters