How to do/trigger archiving

Next topic

Author	Message
Marco Zinn	Monday 18 October 2004 1:33:33 pm Currently, ezPublish "drops" (deletes) data of object versions, that are older than 10 versions (for articles) than the published version. In other words, it keeps about 10 versions of an object in the DB, not more. Sometimes, you may want to "archive" (do "record-copies"... i don't know the perfect word) of "archived versions", when you deleted them from the DB (or maybe as soon as you publish a new version). I guess, this would need: - a trigger (somewhere in the "publish" function) - a smart way to serialize the object (XML, okay, but think of files and images)... maybe the package system would be good - some "output destination" like a file (Text, binary, PDF, whatever) - Some concept of how to "get rid of" these "record copies": Writing them to tapes, DVDs or the like Did anyone do something like this? Marco http://www.hyperroad-design.com
Norman Leutner	Monday 18 October 2004 10:58:45 pm I`m using sql-dumps to backup the database every night. The storage directory is also copied and written on tapes every night. The sql-dumps and files are archived with HP Omniback. Mit freundlichen Grüßen Best regards Norman Leutner ____________________________________________________________ eZ Publish Platinum Partner - http://www.all2e.com http://ez.no/partners/worldwide_partners/all2e_gmbh
Björn Dieding@xrow.de	Tuesday 19 October 2004 4:52:41 pm I think you are on the right track... My idea - Do a before publish workflow. - that workflow should take care that the ezcontentobject package gets created without class information and just one version. - Store this package somewhere on the disk. I have already done similar things. It is not that hard. Though not all Datatypes support serializing :-( Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/

Author

Message

Monday 18 October 2004 1:33:33 pm

Currently, ezPublish "drops" (deletes) data of object versions, that are older than 10 versions (for articles) than the published version. In other words, it keeps about 10 versions of an object in the DB, not more.
Sometimes, you may want to "archive" (do "record-copies"... i don't know the perfect word) of "archived versions", when you deleted them from the DB (or maybe as soon as you publish a new version).

I guess, this would need:
- a trigger (somewhere in the "publish" function)
- a smart way to serialize the object (XML, okay, but think of files and images)... maybe the package system would be good
- some "output destination" like a file (Text, binary, PDF, whatever)
- Some concept of how to "get rid of" these "record copies": Writing them to tapes, DVDs or the like

Did anyone do something like this?

Marco
http://www.hyperroad-design.com

Norman Leutner

Monday 18 October 2004 10:58:45 pm

I`m using sql-dumps to backup the database every night.
The storage directory is also copied and written on tapes every night.
The sql-dumps and files are archived with HP Omniback.

Mit freundlichen Grüßen
Best regards

Norman Leutner

____________________________________________________________
eZ Publish Platinum Partner - http://www.all2e.com
http://ez.no/partners/worldwide_partners/all2e_gmbh

Björn Dieding@xrow.de

Tuesday 19 October 2004 4:52:41 pm

I think you are on the right track...

My idea
- Do a before publish workflow.
- that workflow should take care that the ezcontentobject package gets created without class information and just one version.
- Store this package somewhere on the disk.

I have already done similar things. It is not that hard. Though not all Datatypes support serializing :-(

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/