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/

eZ debug

Timing:	Jan 19 2025 20:10:44
Script start
Timing:	Jan 19 2025 20:10:44
Module start 'layout'
Timing:	Jan 19 2025 20:10:44
Module start 'content'
Timing:	Jan 19 2025 20:10:44
Module end 'content'
Timing:	Jan 19 2025 20:10:44
Script end

Main resources:

Total runtime	0.6987 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	589.1563	152.6250
Module start 'layout'	0.0048	0.0021	741.7813	39.4453
Module start 'content'	0.0070	0.6907	781.2266	590.0781
Module end 'content'	0.6976	0.0011	1,371.3047	12.4766
Script end	0.6987		1,383.7813

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.4346	16	0.0002
Check MTime	0.0012	0.1689	16	0.0001
Mysql Total
Database connection	0.0008	0.1155	1	0.0008
Mysqli_queries	0.6535	93.5304	59	0.0111
Looping result	0.0005	0.0677	57	0.0000
Template Total	0.6745	96.5	2	0.3372
Template load	0.0020	0.2873	2	0.0010
Template processing	0.6724	96.2368	2	0.3362
Template load and register function	0.0001	0.0110	1	0.0001
states
state_id_array	0.0007	0.0996	1	0.0007
state_identifier_array	0.0007	0.1045	2	0.0004
Override
Cache load	0.0017	0.2464	25	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0775	3	0.0002
Fetch class attribute name	0.0009	0.1245	6	0.0001
XML
Image XML parsing	0.0013	0.1921	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0011	6	0.0000
General
dbfile	0.0011	0.1588	29	0.0000
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 17 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs