Ajcody-Notes-Server-Move: Difference between revisions
Line 42: | Line 42: | ||
# First initial sync of PROD to NEWHOST | # First initial sync of PROD to NEWHOST | ||
# | #* on PROD as Root | ||
::: <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 mailstores. | ||
# Sync daily until schedule downtime is available | # Sync daily until schedule downtime is available | ||
## On PROD as Root | ## On PROD as Root |
Revision as of 15:11, 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
- Both servers are of the same chip type - 32bit or 64bit.
- Moves to a new chip set require modifications - 32 to 64. Please see:
- 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
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 EXACT version that your PROD is using.
- 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.
Sync PROD Data While PROD Is Still In Production Use
- 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 mailstores.
- Sync daily until schedule downtime is available
- On PROD as Root
nice +19 rsync -avz -e ssh --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
- On PROD as Root
The Big Day - PROD Downtime For Switch
- Shut down Zimbra on PROD
- On PROD as ZIMBRA
- su - zimbra
- zmcontrol stop
- Last rsync of PROD to NEWHOST
- On Prod as ROOT
nice -20 rsync -avz -e ssh --delete --progress /opt/zimbra/ root@NEWHOSTIP:/opt/zimbra
- On Prod as ROOT
# Fix permissions on NEWHOST
- On NEWHOST as ROOT
run zmfixperms located in /opt/zimbra/libexec
- On NEWHOST as ROOT
- 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.
- On NEWHOST as ROOT, rerun the installer without the -s option
Reference wiki for instructions
http://www.zimbrablog.com/blog/archives/2007/10/moving-zcs-to-another-server.html