Skip to main content

Migrating Zimbra 6 to Zimbra 7

I have a Zimbra 6.0.13 server running on a 32 bit CentOS 4 box. The goal is to migrate it Zimbra 7.1.1 on 64 bit CentOS 6.

I have got a bare installation of Zimbra 7.1.1 running on a CentOS 6 VM. I reused the /opt/zimbra/config.#### file from the old server to do a "kickstart" installation. The config file required a couple of tweaks. First of all, rpm package installs will fail if apache-core is not the first package listed in the set of packages that are to be installed. You also need to switch to a non-upgrade install, and add a quarantine account -- all of that belongs in the config file. You can simply run the installation once, let it fail, but it will create an updated config file. Then grab the config file before it disappears once you uninstall, and tweak with all the new settings now visible.

I have tried the direct migration path using admin console's migration wizard on Zimbra 7. It works great to copy user accounts over, but it uses LDAP and is very lossy when moving mailbox data. Thus I used the wizard to pre-provision user accounts, and then did zmztomig to move individual mailboxes over. This retains most of the things, save for aliases, shared calendars, and such miscellany.

It turns out that the migration-by-updates across 32-to-64 bits and then up the versions is a bit tedious. Our server has been in constant upgrade treadmill since very early Zimbra versions, and there is some cruft in the settings that one has to fight with on every update. It wasn't worth it.

I've ended up copying the account list using the migration system, followed by filters and account contents using export/import.


Popular posts from this blog

Both INCLUDEPATH and DEPENDPATH are usually needed in qmake .pro project files.

qmake, the build tool provided with the Qt toolkit, converts project files written in its own mini-language to platform-specific Makefiles.

This process includes adding necessary dependencies to the Makefile, so that changes in source files trigger rebuilding of the outputs that depend on said sources.

If your project is spread across directories, you'll likely add an INCLUDEPATH line to your .pro file so that the #include directives look sane -- say #include "library/foo.h" instead of #include "../library/foo.h". This can be done by adding INCLUDEPATH += "../" to the .pro project file.

This, by itself, doesn't cause the files in include directories to be treated as dependencies. This is a sane default, since you likely don't want to rebuild your whole project if a system library changes -- assuming, of course, that the library is meant to stay binary compatible between releases!

Thus, if any of your source files references a file from somewhe…

Asterisk 1.8 with SELinux on RHEL 6 / CentOS 6

Asterisk 1.8 is the current long term support (LTS) version of Asterisk. You can find it in the atrpms repository. Using atrpms requires a bit of ingenuity, since you must enable yum priorities. Here's how I've set up my yum priorities and excludes to play well with RHEL (lower priority is higher):

# /etc/yum/pluginconf.d/rhnplugin.conf
priority = 9

# files in /etc/yum/repos.d - current samba and subversion override those of RHEL
sernet-samba - 5
wandisco - 6
rhnplugin - 9
centos-base - 20, includepkgs=xfs* fftw-* glpk-* dell-firmware-repository - 30 dell-omsa-repository - 30 rpmforge-repo - 50, exclude=hdf5*
epel - 60, exclude=dahdi* atrpms - 70
I'm using a bunch of non-redhat packages, including Asterisk, recent subversion, octave, xfs tools, and Dell server management tools.

For Asterisk proper, I'm running an AGI caller id script, and a fax receiving script. The fax script uses cups to print. Those scripts require exceptions to the targeted SELinux policy. Note that the polic…

Details of Migrating Zimbra 6 to Zimbra 8

I have a small Zimbra system that needed to be migrated from 6.0 to 8.0. Generally:
You must update to 6.0.16 on the source system. The account export functionality is broken in versions prior to 6.0.15 and will fail on some accounts.Start with a fresh 8.0 install. On a small system (dozens of users), that seems like the simplest option.Keep the 6.0 system running. Use the migration wizard in 8.0's admin console (Tools & Migration -> Account Migration) to move over account records only.
Set "type of mail server" to Zimbra Collaboration Suite. Set "would you like to import mail" to No.Import from another Zimbra LDAP directory.Set the LDAP Search Base to "dc=foo,dc=com" where would be your domain. This saves work on manually moving accounts between systems.
To move account contents and filter settings between servers, you can do the following on the source server:
su - zimbra      # account to move
DEST=root@destination  # ss…