Thanks for the Reply, Just one Question regarding your Process: The backup files you've mentioned, are those the XML exports, or did you manage to run MySQL Scripts?
I ask because I would like to go with a Mysql restore rather than XML exports, because the XML exports are brutally slow on our server and produce a 100% load on the productive server for more than an hour. Regards Claudio ******************************************** IPH Informatik AG Herr Claudio Greuter Lagerhausstrasse 9 8400 Winterthur Switzerland Tel: +41 (0)52 203 26 72 Fax: +41 (0)52 233 94 71 Email: [EMAIL PROTECTED] ******************************************** -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 7. November 2007 16:28 To: [email protected] Subject: Re: [magnolia-user] Migration from 3.0.1 to 3.0.5 We've migrated 2 sites so far. We did start with a plain vanilla Mag 3.0.5 WAR, switched from Derby to BDB and upgraded to Jackrabbit 1.3.3 first (see http://www.magnolia.info/wiki/Wiki.jsp? page=Magnolia_3.0.5_Jackrabbit_1.3.3_BDB). Then we kicked the repository and let Magnolia bootstrap with the backup files from the old version. This worked flawlessly for us and we have not experienced any problems so far with the new system. Regards, Will On 07.11.2007, at 16:21, Claudio Greuter wrote: > Hi Again > > I am still looking for information about a migration path from > 3.0.1 to > 3.0.5, however I did not find any information so far. Did I miss some > documentation on the Web or has anybody migrated to 3.0.5? > > Regards > > Claudio > > ******************************************** > IPH Informatik AG > Herr Claudio Greuter > Lagerhausstrasse 9 > 8400 Winterthur > Switzerland > Tel: +41 (0)52 203 26 72 > Fax: +41 (0)52 233 94 71 > Email: [EMAIL PROTECTED] > ******************************************** > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: Freitag, 2. November 2007 15:55 > To: [email protected] > Subject: [magnolia-user] Migration from 3.0.1 to 3.0.5 > > Hi Folks. > > Because we're planning the relocation of our magnolia 3.0.1 > installation, I am checking if its worth to migrate to a newer > magnolia > version during this process. > > I'd like to know if it's ok to just replace the existing Jars with the > new ones, or if it's necessary to make a full bootstrap. > > Exporting and Importing takes quite long, I would like migrate with > the > following approach: > > 1. Create a MYSQL backup of the Database > 2. Move all Files from the "olde" instances to their new Server > 3. Patch the New Server by replacing the JARs and whatever else is > needed. > 4. Restore the MYSQL-backup to the databases on the new Server > > In this way I don't have to deal with exporting the settings, > Templates > and contents from the old version. > > > Will this work for a migration from 3.0.1 to 3.0.5 or have database > structures changed meanwhile? > > Many thanks for your opinions > > Claudio > > > > ******************************************** > IPH Informatik AG > Herr Claudio Greuter > Lagerhausstrasse 9 > 8400 Winterthur > Switzerland > Tel: +41 (0)52 203 26 72 > Fax: +41 (0)52 233 94 71 > Email: [EMAIL PROTECTED] > ******************************************** > > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
