Ajcody-Notes-Server-Move
- 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
- Both servers are of the same chip type - 32bit or 64bit.
- Update : We believe this steps listed on this page will work even with a 32 to 64 server will work. I will leave the references below though for historical reasons.
- Moves to a new chip set require modifications - 32 to 64. Please see:
- Update : We believe this steps listed on this page will work even with a 32 to 64 server will work. I will leave the references below though for historical reasons.
- 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.
- 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)
- 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
Preparing NEWHOST Server
- Install Newer (supported) Operating System that matches PROD
- Set up newer ZCS Server’s Hostname as it was on the older server
- Configure BIND locally on NEWHOST to handle resolution issues (A, MX, etc.)
- On NEWHOST confirm /etc/hosts , /etc/resolv.conf
- Download the EXACT version that your PROD is using.
- ZIMBRA User And UID Match
- On OLDHOST as ZIMBRA:
zmlocalconfig zimbra_uid
- On OLDHOST, note the zimbra entry in /etc/passwd and /etc/group.
- On NEWHOST configure the /etc/passwd to be the same UID for zimbra as the OLDHOST had.
- On NEWHOST configure the entry for zimbra in the OLDHOST's /etc/group to match for zimbra as well.
- On OLDHOST as ZIMBRA:
- 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.
- On NEWHOST as Root: Remove the dummy install:
rm -rf /opt/zimbra ; mkdir /opt/zimbra
- 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
Sync PROD Data While PROD Is Still In Production Use
UPDATE : I've added the -H option to the rsync command to preserve hard links.
- First initial sync of PROD to NEWHOST
- on PROD as Root
nice +19 rsync -avzH -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
- Do the same with other paths you might have - i.e. secondary volumes.
- on PROD as Root
- Sync daily until schedule downtime is available
- On PROD as Root
nice +19 rsync -avzH -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
- Do the same with other paths you might have - i.e. secondary volumes.
- On PROD as Root
The Big Day - PROD Downtime For Switch
- Commercial Certificates
- Are you prepared for the impact this server move has for your commercial certificate? This document doesn't address that.
- 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.
- Shut down Zimbra on PROD
- On PROD as ZIMBRA
- su - zimbra
- zmcontrol stop
- On PROD as ZIMBRA
- Last rsync of PROD to NEWHOST
- On Prod as ROOT
nice -20 rsync -avzH -e ssh --delete --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
- UPDATE : I've added the -H option to the rsync command to preserve hard links.
- Do the same with other paths you might have - i.e. secondary volumes.
- On Prod as ROOT
- Fix permissions on NEWHOST
- On NEWHOST as ROOT
run zmfixperms located in /opt/zimbra/libexec
- On NEWHOST as ROOT
- 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.
- Make any firewall or other network changes that are necessary.
- Reconfigure for any mounts that were on PROD that will be needed for NEWHOST.
- This is a good time to turn off PROD.
- Install of Zimbra on NEWHOST
- If you have a Split DNS install or use private LAN addresses on the server with a firewall front-ending the public addresses, you'll want to verify logical hostname resolution and hostname resolution
- In some cases, you can move Zimbra to another server with a different hostname but keep the logical hostname the same. The logical hostname is what users know this server as, and it doesn't necessarily have to match the actual hostname.
- For example, you might have "mail.mydomain.com" as the DNS name for the server, but the hostname is "web11233"
- You need to have the server itself resolve the logical hostname, the old hostname and the new hostname as the internal private LAN address.
host `hostname`
host (logical hostname)
nslookup `hostname`
nslookup (logical hostname)
nslookup (old hostname)
nslookup (old hostname)
- You want all these to look the same. You can follow instructions at Split_dns. Essentially what that does is have a local copy of bind (named) running that resolves just those names and forwards all other lookups to your normal DNS servers.
- In some cases, you can move Zimbra to another server with a different hostname but keep the logical hostname the same. The logical hostname is what users know this server as, and it doesn't necessarily have to match the actual hostname.
- On NEWHOST as ROOT, rerun the installer without the -s option
./install.sh
- 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.
- If you have a Split DNS install or use private LAN addresses on the server with a firewall front-ending the public addresses, you'll want to verify logical hostname resolution and hostname resolution
- 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.
- 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.
- 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.