Ajcody-Notes-Server-Move: Difference between revisions

Line 32: Line 32:
# On NEWHOST as ROOT: Run the installer with the -s option:  
# On NEWHOST as ROOT: Run the installer with the -s option:  
#: <pre>./install.sh -s</pre>
#: <pre>./install.sh -s</pre>
## This tells the installer to only install the software, and not to configure the installation.
#:* This tells the installer to only install the software, and not to configure the installation.
# On NEWHOST as Root: Remove the dummy install:  
# On NEWHOST as Root: Remove the dummy install:  
#: <pre>rm -rf /opt/zimbra ; mkdir /opt/zimbra</pre>
#: <pre>rm -rf /opt/zimbra ; mkdir /opt/zimbra</pre>
Line 47: Line 47:
## On PROD as Root
## On PROD as Root
##: <pre>nice +19 rsync -avz -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra</pre>
##: <pre>nice +19 rsync -avz -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra</pre>
##:* Do the same with other paths you might have - i.e. secondary volumes.


====The Big Day - PROD Downtime For Switch====
====The Big Day - PROD Downtime For Switch====
Line 58: Line 59:
#* On Prod as ROOT
#* On Prod as ROOT
#*: <pre>nice -20 rsync -avz -e ssh --delete --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra </pre>
#*: <pre>nice -20 rsync -avz -e ssh --delete --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra </pre>
#*:* Do the same with other paths you might have - i.e. secondary volumes.
# Fix permissions on NEWHOST
# Fix permissions on NEWHOST
#* On NEWHOST as ROOT
#* On NEWHOST as ROOT
Line 65: Line 67:
#*: <pre>./install</pre>
#*: <pre>./install</pre>
#** It will detect ZCS already installed, and ask if you want to upgrade. Select Yes.
#** It will detect ZCS already installed, and ask if you want to upgrade. Select Yes.
#** Within the installation script, choose the option that tells Zimbra to NOT automatically start upon completion of upgrade/install.
# Post-Install on NEWHOST
#* Reconfigure any network interface/ip information that you need because of hardware move.
#* 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.


====Reference wiki for instructions====
====Reference wiki for instructions====

Revision as of 15:36, 17 August 2008

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

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

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.

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. Shut down Zimbra on PROD
    • On PROD as ZIMBRA
      su - zimbra
      zmcontrol stop
  2. 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.
  3. Fix permissions on NEWHOST
    • On NEWHOST as ROOT
      run zmfixperms located in /opt/zimbra/libexec
  4. 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, choose the option that tells Zimbra to NOT automatically start upon completion of upgrade/install.
  5. Post-Install on NEWHOST
    • Reconfigure any network interface/ip information that you need because of hardware move.
    • 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.

Reference wiki for instructions

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

Zimbra Domains Into An Existing Zimbra Server

See Zimbra_To_Zimbra_Domain_To_An_Existing_Zimbra_Server.

Jump to: navigation, search