Details
-
Bug
-
Resolution: Won't Do
-
Neutral
-
None
-
1.0.2
-
None
-
MacOS X 10.6.8, Derby, Magnolia 3.6.8
Description
I am trying to use the Magnolia Backup module (v1.0.2) to sync all content from our production environment running Oracle as database to a local machine running Derby as database.
I understand from this discussion and from the documentation of the module that this should be possible?
I have tried to do this using the following steps:
- Export from the authoring production environment using the Magnolia backup module. This resulted in a backup of 3GB, mainly due to the BLOBs which we store on the file system (on production).
- Change the repoConfig.gz by replacing all instances of the Oracle persistence manager by the (default) Derby persistence manager.
- Install an empty Tomcat 6 on my local machine.
- Deploy our customized Magnolia WAR including our custom module. This is identical to the version running on production except that locally we use Derby instead of Oracle.
- Start the server once and perform the installation.
- Stop the server and remove the repositories folder.
- Import the backup locally into the magnoliaAuthor instance using ./restore -backup 20111019_magnolia_backup_production_derby -webapp /Applications/Dev/apache-tomcat-6.0.32/webapps/magnoliaAuthor
However this fails with the mentioned error. See the attached log file for details.
Any ideas?
I also ran into out of memory issues regarding the heap space but fixed that by increasing -Xmx to 1024M in the restore script.
Another thing I noticed is that that Magnolia backup tool does not seem to recognize that for the magnoliaAuthor instance we do not use the default/magnolia.properties but instead magnoliaAuthor/magnolia.properties:
Loading configuration at /Applications/Dev/apache-tomcat-6.0.32/webapps/magnoliaAuthor/WEB-INF/config/default/magnolia.properties
But I fixed that by manually re-arranging some stuff for the import.