Commit a6deb4a8 authored by Marco Mariani's avatar Marco Mariani

zimbra: fixed BACKUP.txt

parent 370382d1
...@@ -257,8 +257,7 @@ As current proposal, when a new version of Zimbra will be released: ...@@ -257,8 +257,7 @@ As current proposal, when a new version of Zimbra will be released:
by applying the techniques described in README.txt by applying the techniques described in README.txt
- IMPORTANT: adapt the related migration steps in ZimbraBuild/rpmconf/Upgrade/zmupgrade.pm, - IMPORTANT: adapt the related migration steps in ZimbraBuild/rpmconf/Upgrade/zmupgrade.pm,
push the changes to a new branch push the changes to a new branch
- test the migration on a pair of dedicated Zimbra instances (old and new version, - test the migration on a dedicated Zimbra instance, with test data
with test data)
- build the new branch on a separate machine with matching distribution, version, - build the new branch on a separate machine with matching distribution, version,
architecture, $ZIMBRA_HOME, hostname, FQDN, username/UID of the user that runs zimbra architecture, $ZIMBRA_HOME, hostname, FQDN, username/UID of the user that runs zimbra
on the target server. on the target server.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment