Migrate from Zimbra 6.0.10 on MacOSX to Zimbra 7.1.3 on Ubuntu 10.04 LTS
Hi, we have a single server installation (with a single domain) running MacOSX Server 10.4 with Zimbra 6.0.10_GA_2692.MACOSXx86 Network Edition and we must migrate on a new server Linux with Ubuntu 10.04 LTS. We wish at the same time upgrading to current 7.1.3 Zimbra release. What steps must be followed so that all go wrong? Thank you for your help.
Move Zimbra from OSX to 64bit Ubuntu
Not too long ago, we had the same situation..
We were running Zimbra 5.x on MAC OSX and needed to move to 64bit to get better performance (and to upgrade to Zimbra 7.x along the way)...
Here's what we did:
1. The "new" server was setup as a single Zimbra domain, with a second domain to alias all users into. This way, we did not have the @mail.fake.com showing in email messages, just @fake.com addresses. The second domain alias allows us to route email to the Zimbra server from the front-end mail server (running a serious spam filer).
2. The new server is NOT named the same as the old server (different IP address also)
3. Gave-up on 'migration' as discussed all over on the forums. We wanted to be able to extract a user account on the old server and import it into the new server. Some pieces change, but most settings can be moved over. I ended up writing scripts to do this. The script can do the export of the user account (including all the settings for the user), fix any settings that need fixing, and import them into the new server. Then the mailbox is backed-up from the old server and restored on the new server. Once user(s) are run through the script, the old server is set to forward any incoming email to the new server account (using the email alias).
Some parts get messy;
- We had users on ZCS 5.x that used the "Notebook". That does not move to the new server. (export or save contents from old server.)
- The user "email signature" did not move easily so we let them set signatures on the new server themselves.
- using the Backup / Restore of the "emailed contacts" gets messy. You end up with @oldserver.fake.com addresses in the new server user accounts. I am working on a cleanup script to sanitize the address books prior to shutting-down the old zimbra server.
- We had many "shared calendars" on the old server. These don't move to the new server and remain working. (mostly due to the internal IDs not matching up.) Easiest way we handled this was to delete the shared calendars and re-push the shares out to users. (to clarify: we have many shared calendars for multiple buildings that we automatically share into the user accounts. The process is invisible to the user-- they are automatically 'subscribed' to the shared resource.) If you do not have many large-scale shared resources, this may not be a problem to you.
I can't think of more at the moment. If you are doing the move yourself, give yourself plenty of time. If you do it like we did and leave both servers online, you will be able to move one or two accounts to actually see what you are up against.
I want to say it was several days to get the 850+ accounts moved and setup with their shares, etc.