Sstrutt: /* Post Upgrade Testing */ Typo fix

2012-05-18T05:07:29Z

Post Upgrade Testing: Typo fix

← Older revision		Revision as of 05:07, 18 May 2012
Line 101:		Line 101:
	=== Post Upgrade Testing ===		=== Post Upgrade Testing ===
	* Confirm you can send and receive email through an account on a mobile device		* Confirm you can send and receive email through an account on a mobile device
	* Confirm you can create and delete a task, calendat item and contact on a mobile device and on the server (changes should be		* Confirm you can create and delete a task, calendat item and contact on a mobile device and on the server (changes should be visible on counterpart)

	visible on counterpart)

	[[Category:Z-Push]]		[[Category:Z-Push]]
	[[Category:Zimbra]]		[[Category:Zimbra]]

Sstrutt: Initial creation

2012-05-18T05:06:40Z

Initial creation

New page

== Upgrade Available? ==
To check that an upgrade is available, you need to compare the versions of what you have running against what's available in the SVN repository.

Run <code> svn info </code> against your installation path, and against the repo. When running against your installation path you'll be provided with repo URL. For example...
root@web2:/var/www# svn info z-push/
Path: z-push
URL: svn://svn.berlios.de/z-push/branches/as12.1
Repository Root: svn://svn.berlios.de/z-push
Repository UUID: b7dd7b3b-3a3c-0410-9da9-bee62a6cc5b5
Revision: 1120
Node Kind: directory
Schedule: normal
Last Changed Author: dw2412
Last Changed Rev: 1120
Last Changed Date: 2012-02-07 06:21:29 +0000 (Tue, 07 Feb 2012)

root@web2:/var/www# svn info svn://svn.berlios.de/z-push/branches/as12.1
Path: as12.1
URL: svn://svn.berlios.de/z-push/branches/as12.1
Repository Root: svn://svn.berlios.de/z-push
Repository UUID: b7dd7b3b-3a3c-0410-9da9-bee62a6cc5b5
Revision: 1238
Node Kind: directory
Last Changed Author: dw2412
Last Changed Rev: 1172
Last Changed Date: 2012-03-05 18:19:03 +0000 (Mon, 05 Mar 2012)

Note that you'll need to have installed using SVN in the first place for there to be version tracking in place.

== Procedures ==
=== Create Testing Environment ===
Whether or not you have a large number of users to support it is always a good idea to test the upgrade procedure if at all possible. If you're running from on an Apache webserver this is most easily achieved by creating a copy of your existing Z-Push installation, and then using either a test account on your live Zimbra server, or if you have one, your backup or test server. As a broad overview...

# Create a copy of the Z-Push website
## Create a copy of the files
##* EG <code> cp /var/www/z-push /var/www/z-push-test </code>
## Clear-out any old data
##* EG <code> echo > /var/www/z-push-test/debug.txt </code>
##* EG <code> rm -fr /var/www/z-push-test/state/* </code>
## Create a copy of the site config
##* EG <code> cp /etc/apache2/sites-available/z-push /etc/apache2/sites-available/z-push-test </code>
##* EG <code> cd /etc/apache2/sites-enabled </code>
##* EG <code> vi z-push-test </code> and update site hostname and path (you'll need to update DNS as well)
##* EG <code> apache2ctl -k graceful </code>
# Create a test account on your Zimbra server through the web admin interface
# Copy an account you have access to into the new test account
## Log in to your zimbra server via SSH, and su to the zimbra user
## Export an account to a file...
##* EG <code> zmmailbox -z -m user@domain.com getRestURL "//?fmt=tgz" > /tmp/test-user.tgz </code>
## Import the file into the test account
##* EG <code> zmmailbox -z -m test@domain.com postRestURL "//?fmt=tgz" /tmp/test-user.tgz </code>

=== Upgrade ===
This upgrade procedure assumes the following.
* Path to Z-Push installation: <code>/var/www/z-push</code>
* Path to Z-Push website config: <code>etc/apache2/sites-available/z-push</code>
** Which is enabled by a file link from <code>etc/apache2/sites-enabled/z-push</code>

# Disable Z-Push
#* If Z-Push is the only website running on your server, just stop web service
#** EG <code> apache2ctl stop </code>
#* If Z-Push is on a shared server, disable the site and gracefully restart the web service
#** EG <code> rm /etc/apache2/sites-enabled/z-push</code>
#** EG <code>apache2ctl graceful</code>
# Move the existing site to a backup folder
#* EG <code> mv /var/www/z-push /var/www/z-push-backup </code>
# Recreate the directory for the site
#* EG <code> mkdir /var/www/z-push </code>
# Download the new Z-Push installation
#* EG <code> svn checkout svn://svn.berlios.de/z-push/branches/as12.1 /var/www/z-push </code>
# Download the new Zimbra Active-Sync 12.1 backend branch into a <code>/zimbra</code> folder
#* EG <code> mkdir /var/www/z-push/zimbra </code>
#* EG <code> svn checkout https://zimbrabackend.svn.sourceforge.net/svnroot/zimbrabackend/zimbra-backend/branches/as12.1 /var/www/z-push/zimbra</code>
# Move unrequired files out of <code>backend</code>, leaving only <code>backend.php</code> and <code>diffbackend.php</code>
#* EG <code> mkdir /var/www/z-push/backend-old </code>
#* EG <code> mv /var/www/z-push/backend/* /var/www/z-push/backend-old </code>
#* EG <code> mv /var/www/z-push/backend-old/backend.php /var/www/z-push/backend/ </code>
#* EG <code> mv /var/www/z-push/backend-old/diffbackend.php /var/www/z-push/backend/ </code>
# Move the <code> zimbra.php </code> file into <code>backend</code>
#* EG <code> mv /var/www/z-push/zimbra/zimbra.php /var/www/z-push/backend/ </code>
# Restore the config
#* EG <code> cp /var/www/z-push-backup/config.php /var/www/z-push/ </code>
# Restore the contents of the state folder
#* EG <code> cp -r /var/www/z-push-backup/state/* /var/www/z-push/state/ </code>
# Allow write access to the <code> state </code> folder
#* EG <code> chgrp -R www-data /var/www/z-push/state </code>
#* EG <code> chown -R www-data /var/www/z-push/state </code>
#* EG <code> chmod -R g+w /var/www/z-push/state </code>
# Create file for debug to go to
#* EG <code> touch /var/www/z-push/debug.txt </code>
#* EG <code> chgrp www-data /var/www/z-push/debug.txt </code>
#* EG <code> chmod g+w /var/www/z-push/debug.txt </code>
# Re-enable Z-Push
#* If Z-Push is the only website running on your server, restart the web service
#** EG <code> apache2ctl start </code>
#* If Z-Push is on a shared server, re-enable the site and gracefully restart the web service
#** EG <code> cd /etc/apache2/sites-enabled/ </code>
#** EG <code> ln -s ../sites-available/z-push z-push </code>
#** EG <code>apache2ctl graceful</code>

=== Post Upgrade Testing ===
* Confirm you can send and receive email through an account on a mobile device
* Confirm you can create and delete a task, calendat item and contact on a mobile device and on the server (changes should be

visible on counterpart)

[[Category:Z-Push]]
[[Category:Zimbra]]

Upgrade Z-Push (with Zimbra Backend) - Revision history

Sstrutt: /* Post Upgrade Testing */ Typo fix

Sstrutt: Initial creation