[MGNLEE-111] Backup facility Created: 28/Jul/05  Updated: 23/Jun/14  Resolved: 27/Jun/08

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 3.6

Type: New Feature Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1504 dev tool: scheduled exports Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Spontaneously i had the following idea:

  • define a period parameter
  • a task saves an export to the filesystem depending on this parameter
  • the export gets zipped

This allows a backup to the filesystem. This would be helpful since repositories can crash and backing up the repository files itself is not the best solution.

This is very easy to do and would help hosting magnolia.

Hm, this brings me back to the scheduler But we do not need a sofisticated scheduler to realize this.



 Comments   
Comment by Sameer Charles [ 28/Jul/05 ]

Zip exporter is already available under i.m.cms.core.ie package
you are right it should be straight forward to write import and will be very helpful

just wondering if we should make this as a separate app independent of magnolia since its a simple backup
of a repository and could also be used by other systems as well. what you think?

Comment by Boris Kraft [ 28/Jul/05 ]

I agree that a separate app would be useful; not so much because its useful somewhere else (I assume its simple enough to write so that its not worth the dependency) but to use as a cron target. Once its external, its simple enough to add an internal method that uses the same class.

While we talk about import/export I propose that we not only make system view but also document view available. The latter is much more concise und useful in other places.

Comment by Sameer Charles [ 28/Jul/05 ]

Once we figure out how to handle references we can work on this.

right, Its important to have a document view export so you can also edit it manualy if needed.
Only problem - "The document view is designed to be more human-readable than the system view, though it achieves this at the expense of completeness." and jackrabbit skips all data type information.

Comment by Philipp Bracher [ 29/Jul/05 ]

talking about backup i think more for a system view since a 1:1 restoring is the goal. A separete app is more useful for system admins and so far a must.

If we use the jcr system view export we should not loose the references then. Do we realy need an other format?

The exporting got more configuration parameters in the last view days, but as a lot of other stuff this is not dokumented yet!

Comment by Magnolia International [ 07/Apr/08 ]

This will be realized - in one way or another - with the backup features planned for 3.6

Comment by Jan Haderka [ 27/Jun/08 ]

Backup module of 3.6 EE allows for scheduled backups to be performed.

Generated at Mon Feb 12 05:26:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.