Difference between revisions of "Ajcody-Notes-Server-Move"

m (Zimbra Domains Into An Existing Zimbra Server)
Line 31: Line 31:
 
</pre>
 
</pre>
  
 +
====Please Note====
 +
<H1> DO NOT USE CRON WHEN SYNCING YOUR SERVER!</H1>
 +
You should always run the rsync command manually.  If you fail to do so, and then complete the migration without removing the cron job that did the sync's, and you leave the old server running, you will lose data.  The sync will then kick off again when cron runs and overwrite your production data!  This will very likely corrupt your installation and leave you with an unstable system!
 +
====Please Note====
 
====Preparing NEWHOST Server====
 
====Preparing NEWHOST Server====
  
Line 47: Line 51:
 
# On NEWHOST, make any other mounts or directories you'll need as to match the PROD server.
 
# On NEWHOST, make any other mounts or directories you'll need as to match the PROD server.
 
#* Secondary mailstores, alternative backup directory paths, etc.
 
#* Secondary mailstores, alternative backup directory paths, etc.
 
+
<hr>
 +
====Please Note====
 +
<H1> DO NOT USE CRON WHEN SYNCING YOUR SERVER!</H1>
 +
You should always run the rsync command manually.  If you fail to do so, and then complete the migration without removing the cron job that did the sync's, and you leave the old server running, you will lose data.  The sync will then kick off again when cron runs and overwrite your production data!  This will very likely corrupt your installation and leave you with an unstable system!
 +
<hr>
 
====Sync PROD Data While PROD Is Still In Production Use====
 
====Sync PROD Data While PROD Is Still In Production Use====
  

Revision as of 20:20, 23 January 2009

Attention.png - This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information.

Server Move Notes

Actual Server Move Home Page

Please see: Ajcody-Notes-Server-Move

Server Move To Same Platform (32/64bit) And OS Type & Version

Reference

Please review the main reference for this page. It will have additional information you should be aware of before following these steps.

http://www.zimbrablog.com/blog/archives/2007/10/moving-zcs-to-another-server.html

Assumptions

  1. Both servers are of the same chip type - 32bit or 64bit.
    1. Moves to a new chip set require modifications - 32 to 64. Please see:
  2. This article makes the assumption your moving to the same OS type & version. For example, your PROD machine is running RHEL4-64bit. So your new machine would be running the same and brought to the same patch level as well.
  3. New server is setup with the same HOSTNAME information as PROD but it will use a different IP until PROD can be shutoff/reconfigured (if needed)
  4. SAME AMOUNT OF MEMORY If your moving from 32bit to 32bit and the new system has more than 4GB of memory and the older one didn't you will most likely need to adjust mailboxd_java_heap_memory_percent . This problem will show up as the mailbox stop starting and /opt/zimbra/log/zmmailboxd.out logging errors about JVM memory heap. Try the following:
su - zimbra
zmlocalconfig -e mailboxd_java_heap_memory_percent=25
zmmailboxdctl restart

Please Note

DO NOT USE CRON WHEN SYNCING YOUR SERVER!

You should always run the rsync command manually. If you fail to do so, and then complete the migration without removing the cron job that did the sync's, and you leave the old server running, you will lose data. The sync will then kick off again when cron runs and overwrite your production data! This will very likely corrupt your installation and leave you with an unstable system!

Please Note

Preparing NEWHOST Server

  1. Install Newer (supported) Operating System that matches PROD
  2. Set up newer ZCS Server’s Hostname as it was on the older server
  3. Configure BIND locally on NEWHOST to handle resolution issues (A, MX, etc.)
    1. On NEWHOST confirm /etc/hosts , /etc/resolv.conf
  4. Download EXACT version that your PROD is using.
  5. On NEWHOST as ROOT: Run the installer with the -s option:
    ./install.sh -s
    • This tells the installer to only install the software, and not to configure the installation.
  6. On NEWHOST as Root: Remove the dummy install:
    rm -rf /opt/zimbra ; mkdir /opt/zimbra
  7. On NEWHOST, make any other mounts or directories you'll need as to match the PROD server.
    • Secondary mailstores, alternative backup directory paths, etc.

Please Note

DO NOT USE CRON WHEN SYNCING YOUR SERVER!

You should always run the rsync command manually. If you fail to do so, and then complete the migration without removing the cron job that did the sync's, and you leave the old server running, you will lose data. The sync will then kick off again when cron runs and overwrite your production data! This will very likely corrupt your installation and leave you with an unstable system!


Sync PROD Data While PROD Is Still In Production Use

  1. First initial sync of PROD to NEWHOST
    • on PROD as Root
      nice +19 rsync -avz -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
      • Do the same with other paths you might have - i.e. secondary volumes.
  2. Sync daily until schedule downtime is available
    1. On PROD as Root
      nice +19 rsync -avz -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
      • Do the same with other paths you might have - i.e. secondary volumes.

The Big Day - PROD Downtime For Switch

  1. Commercial Certificates
    • Are you prepared for the impact this server move has for your commercial certificate? This document doesn't address that.
  2. Block client access to the old server's IP address with firewall rules
    • If your remote, make sure to keep your access port open. We are just trying to prevent any changes to the machines while they are being reconfigured.
  3. Shut down Zimbra on PROD
    • On PROD as ZIMBRA
      su - zimbra
      zmcontrol stop
  4. Last rsync of PROD to NEWHOST
    • On Prod as ROOT
      nice -20 rsync -avz -e ssh --delete --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra 
      • Do the same with other paths you might have - i.e. secondary volumes.
  5. Fix permissions on NEWHOST
    • On NEWHOST as ROOT
      run zmfixperms located in /opt/zimbra/libexec
  6. Turn off PROD and reconfigure NEWHOST
    • This is a good time to turn off PROD.
      • Reconfigure network interfaces so if someone turns on PROD later, it will not use the ip addresses that will now be used on NEWHOST.
      • Reconfigure any mounts (san, nfs, iscsi, etc.) so it will not mount anything that should only be mounted on our NEWHOST. Again, in case the machine is powered on accidentally later.
    • Reconfigure NEWHOST to take over ip addresses of PROD.
      • Make any firewall or other network changes that are necessary.
        • Remember about arp tables.
    • Reconfigure for any mounts that were on PROD that will be needed for NEWHOST.
  7. Install of Zimbra on NEWHOST
    • On NEWHOST as ROOT, rerun the installer without the -s option
      ./install
      • It will detect ZCS already installed, and ask if you want to upgrade. Select Yes.
      • Within the installation script, you might want to choose the option that tells Zimbra to NOT automatically start upon completion of upgrade/install.
  8. Post-Install on NEWHOST
    • This document assumes you were going to get the same hostname and ip address once the final move was done. In case this isn't true, below are some follow up issues you might want to check. You might of done some of these already.
      • Do you need to make adjustments for commercial certificates?
      • Reconfigure any network interface/ip information that you need because of hardware move.
      • Make necessary adjustments you might need because of hostname changes. ( see ZmSetServerName )
      • Adjust any firewall settings
        • If ip address is going to be different, make sure you know the settings you'll need to adjust within Zimbra (if any).
        • If ip address is going to be the same, remember your network will take awhile to see change as the new MAC address gets updated to other devices arp table.
          • If you can, you can speed this along with changes on your switches.
  9. Start zimbra once you think everything is ready.
    • Do some client access tests within your LAN.
    • If testing looks good, the remove any firewall rules you might of done to block access from outside. Then confirm outside access and functionality.
      • Remember to check those mobile devices, certificates, and other access software/devices besides just the Zimbra webclient.

Zimbra Domains Into An Existing Zimbra Server

See Ajcody-Migration-Notes . There's a couple of possibilities being worked out there.

Jump to: navigation, search