Backup - from a EE point of view

[Matteo Pelucco]

Hi all.
Me and my collegues are evaluating the possibility to have daily backups
for every site hosted in a Magnolia Instance (we have more than one..).

We are using Enterprise Edition and I think that the main options are 3:

1) Custom command
It will produce SV-XML of a list of path / workspace following site bk
configuration. Generic, but absoutely custom.
PROs: freedom of a custom implementation
CONs: no Magnolia foundation, no I/O facilities... almost all to be done.

2) Extending backup module
At the moment, backup module will backup the entire workspaces, without
taking care of sites inside.
A custom command that extends the BackupCommand would be nice.
But then we will have also the duty of re-import them in a custom import
job...
PROs: backup module is powerful, scheduled, binary output (small size)
CONs: import job to implement, custom backup commands to take care of a
multisite environment

3) Using Packager module
This seems to be the most effective solution, because we can define
"visually" the package / backup path for every site, call from a
scheduler (we will only have to implement a custom command that calls
Packager backup methods).
The only thing to take care is to rename the backup for being able to
re-upload on the same instance that produce it, otherwise the definition
will be overwritten.
PROs: visual definition of backup task, several recovery options
(rollback / install).
CONs: i see almost no cons..

I would only ask to community which options would you follow, and which
pros / cons you can see.

Matteo

PS: JSP / magnolia-tools are not taken into consideration.


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Zdenek Skodik]

If you are looking for the partial backups and wouldn't like to
use the backup/restore jsp scripts then as the best approach
seems to me to use the packager features calling from scheduler.
In general the functionality of jsp scripts was replaced by the backup
and packager modules since Magnolia 3.6. The packages can contain
whatever you need so the restore is very quick and instance independent.
I think this fit your needs so any cons appear. So in conclusion
for EE users is best to use the mentioned modules, for CE users
I can recommend the jsp scripts.  


-  
Best regards,

Zdenek Skodik
Magnolia International Ltd.

Magnolia®  - Simple Open-Source Content Management


On Út, 2009-09-15 at 12:33 +0200, Matteo Pelucco wrote:

> Hi all.
> Me and my collegues are evaluating the possibility to have daily backups
> for every site hosted in a Magnolia Instance (we have more than one..).
>
> We are using Enterprise Edition and I think that the main options are 3:
>
> 1) Custom command
> It will produce SV-XML of a list of path / workspace following site bk
> configuration. Generic, but absoutely custom.
> PROs: freedom of a custom implementation
> CONs: no Magnolia foundation, no I/O facilities... almost all to be done.
>
> 2) Extending backup module
> At the moment, backup module will backup the entire workspaces, without
> taking care of sites inside.
> A custom command that extends the BackupCommand would be nice.
> But then we will have also the duty of re-import them in a custom import
> job...
> PROs: backup module is powerful, scheduled, binary output (small size)
> CONs: import job to implement, custom backup commands to take care of a
> multisite environment
>
> 3) Using Packager module
> This seems to be the most effective solution, because we can define
> "visually" the package / backup path for every site, call from a
> scheduler (we will only have to implement a custom command that calls
> Packager backup methods).
> The only thing to take care is to rename the backup for being able to
> re-upload on the same instance that produce it, otherwise the definition
> will be overwritten.
> PROs: visual definition of backup task, several recovery options
> (rollback / install).
> CONs: i see almost no cons..
>
> I would only ask to community which options would you follow, and which
> pros / cons you can see.
>
> Matteo
>
> PS: JSP / magnolia-tools are not taken into consideration.
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Matteo Pelucco]

Thanks Zdenek for your point of view.
Matteo

Zdenek Skodik ha scritto:
>
> If you are looking for...


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Ralf Hirning-2]

Hi Matteo,

do you know that Packager has a remote interface so you can call the
backup funtionality for example by a script executed by cron:

 http://[server]/[rootContext]/pack/.pack/backupPackage/[name]?mgnlPath=[packagePath]

And you can create folders in the packages repository. So you can upload
the package in a different folder

Ralf


Matteo Pelucco schrieb:

>
> Thanks Zdenek for your point of view.
> Matteo
>
> Zdenek Skodik ha scritto:
>>
>> If you are looking for...
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Matteo Pelucco]

Ralf Hirning ha scritto:
>
> Hi Matteo,
>
> do you know that Packager has a remote interface so you can call the
> backup funtionality for example by a script executed by cron:
>
> http://[server]/[rootContext]/pack/.pack/backupPackage/[name]?mgnlPath=[packagePath]

Hi Ralf, yes I knew this but we decided to run backups only on the same
instance, with a cron and the usage of Packager API.

> And you can create folders in the packages repository. So you can upload
> the package in a different folder

Oh, this is a good idea.
For now we decided to rename temporarily the package so that we can
safely upload on other Magnolia instances.

E.g.:
package: bk_mySite

rename to: bk_mySite_20090920-0340
export executed
rename to: bk_mySite

In this way the exported package has a "unique" name, so that we can
import on other instances without name collision.

But the folders are anyway a good idea.
Matteo


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------