ZCS to ZCS rsync Migration: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
{{ZC}}{{Article Infobox|{{admin}}|{{ZCS 8.0}} | {{ZC}}{{Article Infobox|{{admin}}|{{ZCS 8.0}} {{ZCS 7.0}}|}} | ||
= ZCS to ZCS rsync Migration = | = ZCS to ZCS rsync Migration = | ||
Line 6: | Line 6: | ||
# Migrating from a 32-bit server to a 64-bit server - reference [[Network_Edition:_Moving_from_32-bit_to_64-bit_Server|Moving from 32-bit to 64-bit Server]] for a previous version of this guide | # Migrating from a 32-bit server to a 64-bit server - reference [[Network_Edition:_Moving_from_32-bit_to_64-bit_Server|Moving from 32-bit to 64-bit Server]] for a previous version of this guide | ||
# Abandoning an old system because it is damaged, corrupted, broken, etc. | # Abandoning an old system because it is damaged, corrupted, broken, etc. | ||
# Running continuous rsync copies of a ZCS mailstore for DR purposes | |||
# Moving from an Operating System that is EOL to one that is current, for example: | # Moving from an Operating System that is EOL to one that is current, for example: | ||
* Moving from RHEL 4 to RHEL 5 | * Moving from RHEL 4 to RHEL 5 | ||
Line 39: | Line 40: | ||
* Restore the LDAP data | * 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 | * 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 | * Copy the latest backup files from the Old Server to the New Server | ||
* Delete the MySQL data that is set up in the initial installation of ZCS | * Delete the MySQL data that is set up in the initial installation of ZCS | ||
* Copy various files from the | * Copy various files from the Old Server to the New Server | ||
* Prepare and run a new backup for the | * Prepare and run a new backup for the New Server | ||
==Preparing the | ==Preparing the Old Server== | ||
# Block client access to the server's IP address with firewall rules. | # Block client access to the server's IP address with firewall rules. | ||
# Create an LDAP dump directory. As root, type '''mkdir /backup'''. | # Create an LDAP dump directory. As root, type '''mkdir /backup'''. | ||
# As root, type '''chown zimbra:zimbra /backup'''. | # As root, type '''chown zimbra:zimbra /backup'''. | ||
# Stop the | # Stop the Old Server, type '''zmcontrol stop'''. | ||
# On ZCS 6.0 and later, backup the LDAP config database, as zimbra, type '''/opt/zimbra/libexec/zmslapcat -c /backup''' | # On ZCS 6.0 and later, backup the LDAP config database, as zimbra, type '''/opt/zimbra/libexec/zmslapcat -c /backup''' | ||
# Backup the LDAP data, as zimbra, type '''/opt/zimbra/libexec/zmslapcat /backup''' | # Backup the LDAP data, as zimbra, type '''/opt/zimbra/libexec/zmslapcat /backup''' | ||
Line 75: | Line 76: | ||
# Restore the LDAP data to the 64-bit server. As zimbra, type | # Restore the LDAP data to the 64-bit server. As zimbra, type | ||
#:: a. '''rm -rf /opt/zimbra/openldap-data/*''' | #:: a. '''rm -rf /opt/zimbra/openldap-data/*''' | ||
#:: b. Copy the file '''/opt/zimbra/openldap-data/DB_CONFIG''' from the | #:: b. Copy the file '''/opt/zimbra/openldap-data/DB_CONFIG''' from the Old Server to '''/opt/zimbra/openldap-data/''' on the New 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''' | #:: 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 | #:: d. Copy from the Old Server to the New Server the '''/backup/ldap.bak''' file. | ||
#:: e. Type '''/opt/zimbra/openldap/sbin/slapadd -q -b "" -f /opt/zimbra/conf/slapd.conf -cv -l /backup/ldap.bak'''. | #:: e. Type '''/opt/zimbra/openldap/sbin/slapadd -q -b "" -f /opt/zimbra/conf/slapd.conf -cv -l /backup/ldap.bak'''. | ||
6.0.x and later LDAP setup: | 6.0.x and later LDAP setup: | ||
# Restore the LDAP data to the | # Restore the LDAP data to the New Server. As zimbra, type | ||
#:: a. '''rm -rf /opt/zimbra/data/ldap/config/*''' | #:: a. '''rm -rf /opt/zimbra/data/ldap/config/*''' | ||
#:: b. '''rm -rf /opt/zimbra/data/ldap/hdb/*''' | #:: b. '''rm -rf /opt/zimbra/data/ldap/hdb/*''' | ||
Line 88: | Line 89: | ||
#:: d. '''mkdir -p /opt/zimbra/data/ldap/hdb/db /opt/zimbra/data/ldap/hdb/logs''' | #:: d. '''mkdir -p /opt/zimbra/data/ldap/hdb/db /opt/zimbra/data/ldap/hdb/logs''' | ||
#:: e. If this is an ldap master with replicas: '''mkdir -p /opt/zimbra/data/ldap/accesslog/db /opt/zimbra/data/ldap/accesslog/logs''' | #:: e. If this is an ldap master with replicas: '''mkdir -p /opt/zimbra/data/ldap/accesslog/db /opt/zimbra/data/ldap/accesslog/logs''' | ||
#:: f. Copy the file '''/opt/zimbra/data/ldap/hdb/db/DB_CONFIG''' from the | #:: f. Copy the file '''/opt/zimbra/data/ldap/hdb/db/DB_CONFIG''' from the Old Server to '''/opt/zimbra/data/ldap/hdb/db''' on the New 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.'' | ||
#:: g. Type '''chown -R zimbra:zimbra /opt/zimbra/data/ldap''' | #:: g. Type '''chown -R zimbra:zimbra /opt/zimbra/data/ldap''' | ||
#:: h. Copy from the | #:: h. Copy from the Old Server to the New Server the '''/backup/ldap-config.bak''' file. | ||
#:: i. Copy from the | #:: i. Copy from the Old Server server to the New Server the '''/backup/ldap.bak''' file. | ||
#:: j. Type '''/opt/zimbra/openldap/sbin/slapadd -q -n 0 -F /opt/zimbra/data/ldap/config -cv -l /backup/ldap-config.bak'''. | #:: j. Type '''/opt/zimbra/openldap/sbin/slapadd -q -n 0 -F /opt/zimbra/data/ldap/config -cv -l /backup/ldap-config.bak'''. | ||
#:: k. Type '''/opt/zimbra/openldap/sbin/slapadd -q -b "" -F /opt/zimbra/data/ldap/config -cv -l /backup/ldap.bak'''. | #:: k. Type '''/opt/zimbra/openldap/sbin/slapadd -q -b "" -F /opt/zimbra/data/ldap/config -cv -l /backup/ldap.bak'''. | ||
Line 97: | Line 98: | ||
For all versions: | For all versions: | ||
# Edit '''/opt/zimbra/conf/localconfig.xml''' to update the following with the values from the localconfig.xml file on the | # Edit '''/opt/zimbra/conf/localconfig.xml''' to update the following with the values from the localconfig.xml file on the Old Server: | ||
#:: a. zimbra_mysql_password | #:: a. zimbra_mysql_password | ||
#:: b. mysql_root_password | #:: b. mysql_root_password | ||
#:: c. zimbra_logger_mysql_password ''(Note: Transfer/copy this value to the | #:: c. zimbra_logger_mysql_password ''(Note: Transfer/copy this value to the New Server only if available from the old Old Server.)'' | ||
#:: d. mailboxd_keystore_password ''(Note: Transfer/copy this value to the | #:: d. mailboxd_keystore_password ''(Note: Transfer/copy this value to the New Server only if available from the old Old Server.)'' | ||
#:: e. mailboxd_truststore_password | #:: e. mailboxd_truststore_password | ||
#:: f. mailboxd_keystore_base_password | #:: f. mailboxd_keystore_base_password | ||
Line 110: | Line 111: | ||
#:: k. ldap_nginx_password | #:: k. ldap_nginx_password | ||
#:: l. ldap_replication_password | #:: l. ldap_replication_password | ||
# Delete the MySQL data on the | # Delete the MySQL data on the New Server and copy the MySQL data from the Old Server. | ||
#:: a. Type '''rm -rf /opt/zimbra/db/data/*''' | #:: a. Type '''rm -rf /opt/zimbra/db/data/*''' | ||
#:: b. Copy the '''/opt/zimbra/db/data/*''' from the | #:: b. Copy the '''/opt/zimbra/db/data/*''' from the Old Server to the New Server. | ||
# Copy the following files from the | # Copy the following files from the Old Server to the New Server | ||
#:* '''/opt/zimbra/store/*''' | #:* '''/opt/zimbra/store/*''' | ||
#:* '''/opt/zimbra/index/*''' | #:* '''/opt/zimbra/index/*''' | ||
#:* Any other volumes that were set up on the | #:* Any other volumes that were set up on the Old Server such as HSM. | ||
# If the original server was running with [[:Category:Certificates|commercial certificates]], copy those over as well. | # 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.''') | #:* 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.''') | ||
Line 141: | Line 142: | ||
{{Article Footer|Zimbra Collaboration Server | {{Article Footer|Zimbra Collaboration Server 8.0|01/18/2014}} | ||
[[Category:Installation]] | [[Category:Installation]] | ||
[[Category:Certified]] | [[Category:Certified]] | ||
[[Category:ZCS 8.0]] | |||
[[Category:ZCS 7.0]] | [[Category:ZCS 7.0]] | ||
Revision as of 15:48, 1 February 2014
Article Information |
---|
This article applies to the following ZCS versions.
ZCS 7.0 {{{4}}}|}
ZCS to ZCS rsync MigrationUsing rsync to migrate from an old ZCS mailstore to a new ZCS mailstore can be required for multiple reasons:
For the purposes of this documentation, we will call the two platforms the "Old Server" and the "New Server". RequirementsIMPORTANT: The ZCS release you install on the New Server must be the same ZCS Version as installed on the Old Server. The server can have a different operating system, but the ZCS Version must be identical. 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. Please note too: this method is not required for ancillary systems, such as LDAP nodes, MTAs, or Proxies - all of these nodes can have new systems added while the old system is still running, and therefore do not require the rsync methods described here. Use Rolling Upgrade methods for non-mailstores systems. This rsync method is specifically for ZCS mailstores. Migration StepsFor the migration, you would perform the following high-level steps to minimize downtime: New Server:
Old Server:
You do the following on the New Server:
Preparing the Old Server
Preparing the 64-bit Server
ZCS is installed. To continue:
5.0.x or previous LDAP setup:
6.0.x and later LDAP setup:
For all versions:
Reference Documentation
Keywords: Migration, migrating, 32bit, 64bit, architecture, moving
|