Difference between revisions of "Upgrade Z-Push v2 (with Zimbra Backend)"

Jump to navigation Jump to search
→‎Go Live: Added "Ver 2.0 To Ver 2.1"
m (→‎Preparation: Corrected SVN path)
(→‎Go Live: Added "Ver 2.0 To Ver 2.1")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
It easiest to perform an upgrade by preparing the files for the website first.  Then once you're confident all is well, switching over is quick and relatively seamless.
It easiest to perform an upgrade by preparing the files for the website in a new folder first.  Then, once you're confident all is well, switch over the old and new folders by renaming.  If something doesn't work as expected its easy to fall back to the previous running version.
 
Whilst it shouldn't be necessary for Active-Sync clients to perform any actions prior to or after an upgrade, its worth making sure that they are syncing properly and don't have any current problems.  Un-synced changes (that exist on phones etc) could get lost, and any existing problems may be exacerbated.


To check your current running versions (assuming you're logging to <code>/var/log/z-push/z-push.log</code>)...
To check your current running versions (assuming you're logging to <code>/var/log/z-push/z-push.log</code>)...
Line 5: Line 7:
** <code>grep "] Version=" /var/log/z-push/z-push.log</code>
** <code>grep "] Version=" /var/log/z-push/z-push.log</code>
* Zimbra backend
* Zimbra backend
** <code>grep "Zimbra Backend version" /var/log/z-push/z-push.log</code>
** See the version indicated in <code> <z-push dir>/backend/zimbra/Release Notes.txt</code>
** If you're running the backend in debug mode (eg <code>define('ZIMBRA_DEBUG',true);</code>) then
*** <code>grep "Zimbra Backend version" /var/log/z-push/z-push.log</code>


Make sure you read the release notes for the new versions of software that you are installing.  You may need to make additional changes as part of the upgrade that are not covered here.
Make sure you read the release notes for the new versions of software that you are installing.  You may need to make additional changes as part of the upgrade that are not covered here.
Line 20: Line 24:
#* EG <code> svn checkout svn://svn.code.sf.net/p/zimbrabackend/code/zimbra-backend/branches/z-push-2 /var/www/z-push-v2.0.6/backend/zimbra</code>
#* EG <code> svn checkout svn://svn.code.sf.net/p/zimbrabackend/code/zimbra-backend/branches/z-push-2 /var/www/z-push-v2.0.6/backend/zimbra</code>
# Copy across the config from your old install  
# Copy across the config from your old install  
#* I tend to do a diff of my existing and the new config files first in order to detect that there are new config settings that I might be wiping out
#* I tend to do a diff of my existing and the new config files first, in order to detect if there are new config settings that I might be wiping out by copying across
#** EG <code> diff /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
#** EG <code> diff /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
#* Also note that ptior to Z-Push v2.0.6, all config was in only file (see [[Z-Push_v2_with_Zimbra#Z-Push Config|Z-Push Config]] for more info)
#* Also note that prior to Z-Push v2.0.6, all config was in only one file (see [[Z-Push_v2_with_Zimbra#Z-Push Config|Z-Push Config]] for more info), since v2.0.6 the backend config has been separated out
#* EG <code> cp /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
#* EG <code> cp /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
#* EG <code> cp /var/www/z-push/backend/zimbra/config.php /var/www/z-push-v2.0.6/backend/zimbra/config.php </code>


== Go Live ==
== Go Live ==
Line 32: Line 37:
# Restart webserver
# Restart webserver
#* <code> apache2ctl -k graceful </code>
#* <code> apache2ctl -k graceful </code>
=== Ver 2.0 To Ver 2.1 ===
As described in the [http://zarafa-deutschland.de/z-push-download/final/2.1/z-push-2.1.0-1750.txt release notes], when upgrading from Version 2.0 to Version 2.1 the data states are not compatible and an upgrade script needs to be run.  Modified go live procedure...
# Move old install out of the way
#* EG <code> mv /var/www/z-push /var/www/z-push-v2.0.7 </code>
# Move new install into place
#* EG <code> mv /var/www/z-push-v2.1 /var/www/z-push </code>
# Restart webserver
#* <code> apache2ctl -k graceful </code>
# Run conversion scipt
#* <code> php /var/www/z-push/tools/migrate-2.0.x-2.1.0.php </code>


== Test ==
== Test ==

Navigation menu