[opencms-dev] Backup complete OC-structure

[Claus Priisholm]

If you can afford a minor stop of the service you can halt the 
application (or tomcat), dump the database using  whatever tools you 
have for it - e.g. mysqlhotcopy if you run MySQL and wrap up the 
appropriate web-app dir. The database dump along with the web-app dir 
gives all you need.
The app must be stopped to ensure a consistent backup such that the db 
and the web-app dir shares the same view of the world (not sure if the 
built-in export actually guarantees that on a running application - 
haven't looked into it).


On 15/3-2004, at 9.59, Thorsten K. Zeiller wrote:

> Hi list,
>
> we manage a huge site via OC (Tomcat 4.0.3, jdk 1.4.0). Backups were 
> made up
> to now via the export-function. Now the site is so big, that sometimes 
> the
> memory of the jvm is not enough, the writing of the .zip-file stops and
> leaves a corrupted file. The CATALINA_OPTS mem options are set to 
> -Xmx256m.
>
> We can not upgrade memory in short time so we are searching for an
> alternative way to backup system and content data. Our approach would 
> be to
> dump the whole database. Does anybody use a method like this? What else
> would we need to restore data from a db-dump if necessary (obviously 
> the
> "manifest.xml")?
>
> Help or hints would be appreciated,
>
> regards
> Thorsten K. Zeiller
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please 
> visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>
>
--
Claus Priisholm, CodeDroids ApS
+45 48 22 46 46
cpr (you-know-what) interlet.dk - cpr (you-know-what) codedroids.com
http://www.interlet.dk - http://www.codedroids.com