Re: Moving a Plone installation

Armin Stroß-Radschinski <[email protected]> Wed, 15 Apr 2015 16:05:28 +0200
Newsgroups	gmane.comp.web.zope.plone.user
Message-ID	<[email protected]>
Am 15.04.2015 um 15:48 schrieb Wolfgang Jeltsch <wls580ii-u9ERN231N2QZkvjqreKGLti2O/[email protected]>:

> Am Mittwoch, den 15.04.2015, 12:17 +0100 schrieb Christian Ledermann:
>> On 15 April 2015 at 12:08, Wolfgang Jeltsch <wls580ii-u9ERN231N2QZkvjqreKGLti2O/[email protected]> wrote:
>>> Hi,
>>> 
>>> thanks a lot for this information.
>>> 
>>> I like this “conservative approach”. I just did not know it so far. In
>>> particular, I did not know that it is safe to replace the var directory
>>> with the one from another Plone installation. I guess the Plone versions
>>> of both installations must match for this to work.
>>> Or is it actually
>>> possible to transfer the var directory from of an older Plone to a newer
>>> Plone?
>>> Then I could update my Plone on the way.
>> 
>> yes this is possible. also note that when you update from a plone with
>> python 2.6 to a version with python 2.7 this is the most painless way
> 
> Great!
> 
> What will happen after I start the new Plone with the old var directory?
> Will it walk through the steps of updating the sites to the new
> conventions (new content types, etc.) automatically?

Make a snapshotbackup using the bin/snapshotbackup command (if installed) so you can easily roll back if migration to the new Plone version fails or you do a mistake.

I suggest to start in fg in debugmode. In the ZMI or in the Site-Setup Section of the UI, You will see an advice to start the "in-Place" upgrade procedure . In some cases when the Plone UI is broken, you have to use the ZMI (add /manage to the root URL).

In the migration interface, use the Dry-Run option to check if it will run sane.
If it went fine, then do the actual migration. If it fails, restore the snapshot using bin/snapshotrestore and startover again and make sure everything was right.

Usually if you use nonstandard contenttypes or addons the migration may fail. Then you can look at the logs and try to run the migrations steps by hand one after the other to figure out (see the docs for more). 

In the past other methods than in place migration, seem to work better if these issues occur (transmogrifier, other packages). But if you have a running system and just a minor version jump, I have success most of the time.

Giving it a try is worth the effort.

Sometimes there are fitfalls where you can google easily a solution. e.g. in Plone 4.3+ after removing Kupu there can be a remaining Kupu Tool in the ZMI that makes some trouble until you delete it.

-- Cheers Armin

> 
> All the best,
> Wolfgang
> 
> 
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> Plone-Users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-users

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF

_______________________________________________
Plone-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-users
signature.asc (application/pgp-signature, 496 B)