RE: [Zope] Regarding ZOPE backup procedure
Also worth considering: figure out a way to back up your content in a format other than just backing up your ZODB (serialize it and download it via FTP or something). Consider some way to serialize your CMF content into something like plain-text files so that you not only have a backup of your database, but also a neutral (archival) backup of your content as well. For backup of your ZODB, consider use of DirectoryStorage. Sean -----Original Message----- From: Chinku Simon [mailto:Chinku_Simon@infosys.com] Sent: Wednesday, November 13, 2002 1:56 AM To: zope@zope.org Subject: [Zope] Regarding ZOPE backup procedure Hi, I am investigating on methods to back up of a Zope CMF site. What could be the best possible method Thanks in advance Chinku ________________________________________ Chinku Simon Software Engineer, Infosys Technologies Limited, Bangalore. T +91 80 4163889 (Direct) +91 80 8520261 X 50889
Hi, --On Donnerstag, 14. November 2002 12:24 -0800 sean.upton@uniontrib.com wrote:
Also worth considering: figure out a way to back up your content in a format other than just backing up your ZODB (serialize it and download it via FTP or something). Consider some way to serialize your CMF content into something like plain-text files so that you not only have a backup of your database, but also a neutral (archival) backup of your content as well.
Neutral format means without meta information stored in properties? Dont mention filetype problems. If you store your zope versions with regular backups of Data.fs, there is no need to dissemble your object tree in plain files. If you need the data, Data.fs is just as good as a file system it only needs a different "driver" which is the Zope from the time it was stored. Best practice is to store Zope source in a CVS. Data.fs may or may not be stored there as well. Regards Tino
For backup of your ZODB, consider use of DirectoryStorage.
Sean
-----Original Message----- From: Chinku Simon [mailto:Chinku_Simon@infosys.com] Sent: Wednesday, November 13, 2002 1:56 AM To: zope@zope.org Subject: [Zope] Regarding ZOPE backup procedure
Hi,
I am investigating on methods to back up of a Zope CMF site. What could be the best possible method
Thanks in advance Chinku ________________________________________ Chinku Simon Software Engineer, Infosys Technologies Limited, Bangalore. T +91 80 4163889 (Direct) +91 80 8520261 X 50889
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of sean.upton@uniontrib.com Sent: Thursday, November 14, 2002 12:25 PM To: Chinku_Simon@infosys.com; zope@zope.org Subject: RE: [Zope] Regarding ZOPE backup procedure
Also worth considering: figure out a way to back up your content in a format other than just backing up your ZODB (serialize it and download it via FTP or something). Consider some way to serialize your CMF content into something like plain-text files so that you not only have a backup of your database, but also a neutral (archival) backup of your content as well.
For backup of your ZODB, consider use of DirectoryStorage.
I would suggest you never back up with FTP. FTP generally does not present enough metadata to even begin to reassemble a site. For instance, folder properties and SQL method connection data are not in the FTP format. I imagine you would lose all security information as well. FTP is intended primarly for editing object bodies. Otherwise I agrew with Sean. If you are super lazy, you might also want to consider setting up a zsyncer as a quick & ditry backup solution. ZSyncer isn't designed for this purpose but it could be used in this way. This would also let you swap the backup server pretty quickly, though not automatically.
Tino Wildenhain wrote:
If you store your zope versions with regular backups of Data.fs, there is no need to dissemble your object tree in plain files. If you need the data, Data.fs is just as good as a file system it only needs a different "driver" which is the Zope from the time it was stored. Best practice is to store Zope source in a CVS. Data.fs may or may not be stored there as well.
hi Tino, very nice idea to keep the history for the future... Do you have run this "best practice" on a production system? Do I have to shut down my Zope, when I do a nightly "commit"? I don't know how CVS handles a Data.fs which is changed during the commit. I would guess that it should be no problem. Your idea could solve a big problem for me... I'm going to give it a try. thank you, maik
participants (4)
-
Charlie Reiman -
Maik Jablonski -
sean.upton＠uniontrib.com -
Tino Wildenhain