Difference between revisions of "Network Edition: Moving from 32-bit to 64-bit Server"

(Preparing the 64-bit Server)
(Redirected page to ZCS to ZCS rsync Migration)
(21 intermediate revisions by 4 users not shown)
Line 1: Line 1:
#REDIRECT [[ZCS_to_ZCS_rsync_Migration|ZCS to ZCS rsync Migration]]
This article describes the steps to move network edition ZCS accounts from a 32-bit server to a 64-bit server.
'''''IMPORTANT''': The ZCS release you install on the 64-bit server must be the same release as installed on the 32-bit server. The server can have a different operating system.''
The new server hardware must meet the requirements described in the Installation Prerequisites section of the ZCS Single Server Installation Guide. Install the new operating systems, making any necessary OS configuration modifications as described in the installation guide.
==32-bit to 64-Bit Migration==
For the migration, you do the following on the 32-bit server:
* Block client access to the old server's IP address with firewall rules
* Create an LDAP dump directory
* Backup the LDAP data
You do the following on the 64-bit server:
* Prepare the new server
* Restore the LDAP data
* Edit the localconfig.xml file to update the MySQL and LDAP password values to be the same as those configured on the old server
* Copy the latest backup files from the 32-bit server to the 64-bit server
* Delete the MySQL data that is set up in the initial installation of ZCS
* Copy various files from the 32-bit server to the 64-bit server
* Prepare and run a new backup for the 64-bit server
==Preparing the 32-bit Server==
# Block client access to the server's IP address with firewall rules.
# Create an LDAP dump directory. As root, type '''mkdir /backup'''.
# As root, type '''chown zimbra:zimbra /backup'''.
# Backup the LDAP data, as zimbra, type '''/opt/zimbra/libexec/zmslapcat /backup'''
# Stop the 32-bit server, type '''zmcontrol stop'''.
# Change the hostname and IP address on the old server to something else. Do not turn off the server.
==Preparing the 64-bit Server==
# Prepare the 64-bit server and install ZCS.
::The ZCS installation on the new server must be configured exactly as the ZCS configuration on the original server. You go through the complete menu driven installation process, making changes to the configuration setting to match the settings on the original server.
:: a. Copy your ZCSLicense.xml file to a directory on the new server. You will not be able to complete the ZCS installation if the license is not on the new server.
:: b. Follow the directions in the ZCS single server installation guide to install ZCS. Make sure that you configure the same domain, hostname, passwords as on the old server. During ZCS install, the following settings must be changed to match the original server settings:
::* Zimbra LDAP Server - For Domain to create - identify the same default domain as on the original server.
::* Zimbra Mailbox Server - An administrator's account is automatically created.
:::* Make sure that the account name for '''Admin user to create''' is the same name as on the original server.
:::* Set the admin password.
:::* Change the '''Spam training user''' and the '''Non-spam (HAM) training user''' account names to be the same as the spam account names on the original server.
:::* '''Global Document Account''' - This account name is automatically generated. Change the Global Document Account name to be the same account name as on the original server.
::* Change any other settings on the new server to match the configuration on the original server.
ZCS is installed. To continue:
# Stop the ZCS services, type '''zmcontrol stop'''.
# Restore the LDAP data to the 64-bit server. As zimbra, type
#:: a. rm -rf /opt/zimbra/openldap-data/*
#:: b. Copy the file '''/opt/zimbra/openldap-data/DB_CONFIG''' from the 32-bit server to '''/opt/zimbra/openldap-data/''' on the 64-bit server. '''''Note:''' If this file does not exist, or is empty, creating it may improve ldap performance; see the [[Performance_Tuning_Guidelines_for_Large_Deployments|Performance Tuning Guide]] for more information.''
#:: c. Create the necessary directory structure.  Type '''mkdir -p /opt/zimbra/openldap-data/logs /opt/zimbra/openldap-data/accesslog/db /opt/zimbra/openldap-data/accesslog/logs'''  Type '''chown -R zimbra:zimbra /opt/zimbra/openldap-data'''
#:: d. Copy from the 32-bit server to the 64-bit server the '''/backup/ldap.bak''' file.
#:: e. For 5.0.x or previous, type '''/opt/zimbra/openldap/sbin/slapadd -q -b "" -f /opt/zimbra/conf/slapd.conf -cv  -l /backup/ldap.bak'''.  For 6.0.x and later, type '''/opt/zimbra/openldap/sbin/slapadd -q -b "" -F /opt/zimbra/data/ldap/config -cv  -l /backup/ldap.bak'''.
# Edit '''/opt/zimbra/conf/localconfig.xml''' to update the zimbra_mysql_password, mysql_root_password, zimbra_ldap_password and the ldap_root_password values to the values from the localconfig.xml file on the 32-bit server.
# You may also need to update ldap_postfix_password and ldap_amavis_password from old localconfig.cml to avoid issues ldap not being able to connect postfix/amavis.
# Delete the MySQL data on the 64-bit server and copy the MySQL data from the 32-bit server.
#:: a. Type '''rm -rf /opt/zimbra/db/data/*'''
#:: b. Copy the '''/opt/zimbra/db/data/*''' from the 32-bit server to the 64-bit server.
# Copy the following files from the 32-bit server to the 64-bit server
#:* '''/opt/zimbra/store/*'''
#:* '''/opt/zimbra/index/*'''
#:* Any other volumes that were set up on the 32-bit server such as HSM.
# If the original server was running with [[:Category:Certificates|commercial certificates]], copy those over as well.
#:* The tomcat keystore (http, pop, and imap) is '''/opt/zimbra/tomcat/conf/keystore.''' (In 5.0.x, the jetty keystore (http, pop, and imap) is '''/opt/zimbra/mailboxd/etc/keystore.''')
#:* When transferring the keystore file, be sure to transfer the keystore password to the new system otherwise the mailbox server will not start.
#: Run on old system
#: <pre>zmlocalconfig -s mailboxd_keystore_password</pre>
#: On new system
#: <pre>zmlocalconfig -e mailboxd_keystore_password=thepassword</pre>
#:* If any root certificates were added to the cacerts keystore, that is '''/opt/zimbra/java/jre/lib/security/cacerts''' on linux or '''/System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/lib/security/cacerts''' on Mac OS X, copy cacerts to the new server.
#:* The postfix certificates (smtp) are '''/opt/zimbra/conf/smtpd.crt''' and '''smtpd.key'''. If you are using the certificates for nginx, perdition, or ldap (slapd) they are also in '''/opt/zimbra/conf/'''; they should normally be identical to the postfix certificate files.
# Remove any old backup sessions because these sessions are no longer needed. Type '''rm -rf /opt/zimbra/redolog/*'''
# As root, run '''/opt/zimbra/libexec/zmfixperms''' to repair any potential permissions problems with files under /opt/zimbra.
# Start ZCS, type '''zmcontrol start'''.
# Now run a full backup, type '''zmbackup -f -a all'''.
# Remove the firewall rules and allow client access to the new server.
Keywords: ''Migration, migrating, 32bit, 64bit, architecture, moving''
{{Article Footer|Zimbra Collaboration Suite 4.5.6|7/5/2007}}
[[Category: Installation ]]

Latest revision as of 13:37, 31 March 2015

Jump to: navigation, search