View source for Network Edition Moving from Open Source to Network Edition ZCS

{{BC|Certified}}
__FORCETOC__
<div class="col-md-12 ibox-content">
=Moving from Open Source Edition to Network Edition=
{{KB|{{ZC}}|{{ZCS 8.0}}|{{ZCS 7.0}}|}}
{{WIP}}
This article describes the steps to move from Open Source ZCS to Network Edition ZCS.

==Official In-Place Edition Switch ==

'''This is is an official recommendation for ZCS 7.x and greater.'''

* '''Warning''' [[Backup_and_Restore_Articles | Take a backup first!]]

This first method deals with in-place Open Source to Network Edition switches/conversions; meaning no server hardware or operating system platform changes, just the ZCS edition. [[Backup_and_Restore_Articles | Remember to take a backup first]]. Then just run the NE .install.sh over your FOSS instance, with a purchased license handy. You should choose the same version of NE as you are currently running on FOSS for this transition to minimize other variables. (Upgrading version & edition switch at the same time between some minor releases is technically possible, but harder to troubleshoot later.)

Note, this process essentially works in reverse as well.

==Official Certified Edition Move==

* '''Important'''<nowiki>: The ZCS release version number you install on the network edition server </nowiki>'''must be the same release''' as installed on the open source edition server. 

The server can have a different operating system. Thus the following can apply with (or without) hardware and/or operating system platform changes taking place. This guide assumes a 2 server scenario; If using only one, be sure that your data is backed up. (Entire /opt/zimbra directory for starters.)

===Migrating from Open Source ZCS to Network Edition ZCS===

On the open source server, you perform the following steps:

* Block client access to the old server's IP address with firewall rules
* Create an LDAP dump directory
* Backup the LDAP data
* Export the MySQL data

For the network edition server, you do the following:

* Prepare the new server
* Copy the backup files from the open source server to the network edition server
* Restore the LDAP data
* Import the MySQL data
* Edit the localconfig.xml file to update the MySQL password values to be the same as those on the old server.
* Copy various files from the open source server to the network edition server
* Prepare and run a new backup on the network edition server

====Preparing the Open Source Server====

# Block client access to the server IP address with firewall rules.
# Create an LDAP dump directory. As root, type 
#: a. '' mkdir /backup''
#: b.  '' chown zimbra:zimbra /backup''
# Backup the LDAP data, as zimbra, type <br />'' /opt/zimbra/libexec/zmslapcat /backup''
# Export MySQL data. Before you start, make sure that '' /backup '' is large enough to hold all the data. Depending on the original database size, this can be very large. If you have large configuration, you may want to run this command with '' nohup'' so that the session does not terminate. Type <br />'' mysqldump -f -S /opt/zimbra/db/mysql.sock \ <br /> -u zimbra --password=`zmlocalconfig -s -m nokey \ <br /> zimbra_mysql_password` --all-databases --single-transaction \<br /> > /backup/mysql.sql''
# Stop the open source 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 Network Edition Server====
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.


The ZCS installation on the network edition server must be configured exactly as the ZCS configuration on the open source server. You go through the complete menu driven installation process, making changes to the configuration setting to match the settings on the original server. Before you begin to install ZCS, note the information you need from the old server including: admin account name and password, spam training and non-spam training user account names, exact domain name, and the global document account name.

'''Note''': The following commands are run as zimbra user.

# 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.
#: '''Important'''<nowiki>: Before you start, make sure that your ZCSLicense.xml file is copied 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.</nowiki>
#: a. Zimbra LDAP Server - For Domain to create - identify the same default domain as on the original server.
#: b. 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.
#: c. Change any other settings on the new server to match the configuration on the original server.
# Stop the ZCS services, type '' zmcontrol stop'' .
# Copy over '' /backup/* '' from the open source server to the network edition server. The files should be readable as zimbra user.
# Restore the LDAP data to the network edition server.
#: For 5.0.x and previous:
#:: a. Type '' rm -rf /opt/zimbra/openldap-data/*''
#:: b. Type '' /opt/zimbra/openldap/sbin/slapadd \<br /> -f /opt/zimbra/conf/slapd.conf -qcv \<br /> -l /backup/ldap.bak''
#: For 6.0.x and later:
#:: a. Type '' rm -rf /opt/zimbra/data/ldap/hdb/db/* /opt/zimbra/data/ldap/hdb/logs/*''
#:: b. Type '' /opt/zimbra/openldap/slapadd \<br /> -F /opt/zimbra/data/ldap/config -qcv \<br /> -l /backup/ldap.bak''
# Start MySQL, import the MySQL data, and stop the mySQL service. Type
#: a. '' mysql.server start''
#: b. '' mysql -f zimbra < /backup/mysql.sql<br />'' If you have large configuration, you may want to run this command with '' nohup'' so that the session does not terminate.
#:c. '' mysql.server stop''
# Edit '' /opt/zimbra/conf/localconfig.xml'' to update the following password values to the values from the localconfig.xml file on the open source server:
#:*MySQL password values:
#:**zimbra_mysql_password
#:**mysql_root_password
#:*LDAP password values:
#:**ldap_amavis_password
#:**ldap_nginx_password
#:**ldap_postfix_password
#:**ldap_replication_password
#:**ldap_root_password
#:**zimbra_ldap_password

====Moving the email store & index====
# Copy the following files from the open source server to the network edition server. Make sure that you preserve file ownership and permissions on the copied files.
#* /opt/zimbra/store/*
#* /opt/zimbra/index/*
#* Any other volumes that were set up on the open source server.
# For a clean backup, remove the redologs. Type<br />'' rm -rf /opt/zimbra/redolog/*''
# 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.

--------------------------------------------------------------------------------

==Related Articles==
For server and/or OS platform changes see also [[http://www.zimbrablog.com/blog/archives/2007/10/moving-zcs-to-another-server.html install.sh -s method]]

[[Network_Edition:_Moving_from_32-bit_to_64-bit_Server]]

[[Moving_ZCS_to_New_Server]]

<br> Keywords: ''moving'' "64 bit" "32 bit" 

{{Article Footer|Zimbra Collaboration Suite 8.0, 7.0|7/1/2007}}

[[Category: Installation]]
[[Category: Certified]]
[[Category: Pending Certification]]