From fd0bc63fa6d6a938bfa01283f8d273ac88eb9a61 Mon Sep 17 00:00:00 2001 From: Marco Mariani <marco.mariani@nexedi.com> Date: Mon, 8 Jul 2013 12:11:31 +0200 Subject: [PATCH] zimbra docs: added reference to http://blog.spanger.org/?p=1168 --- software/zimbra/BACKUP.txt | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/software/zimbra/BACKUP.txt b/software/zimbra/BACKUP.txt index 1e68dcdbe..d7d8ee434 100644 --- a/software/zimbra/BACKUP.txt +++ b/software/zimbra/BACKUP.txt @@ -238,7 +238,11 @@ When a new version of Zimbra is released, it can be installed with: Moving to another server and upgrading Zimbra version can NOT be done at the same time. The application must be migrated to the new server, -then the new version can be installed. +then the new version can be installed. A more complex procedure to both +update the version and move to a server with possibly different architecture +is described in + + http://blog.spanger.org/?p=1168 @@ -278,3 +282,9 @@ As current proposal, when a new version of Zimbra will be released: parameters, and can then be deployed on the target server as described above. +The procedure described in + + http://blog.spanger.org/?p=1168 + +could also be adapted to the Buildout Edition. + -- 2.30.9