zmslapcat -c command 6.0.x migration

[thunder04]

I am running 6.0.5 and have this problem. I need to move to a new server (32 bit to 64 bit) before I can upgrade to 7 since the OS we were using (Debian 4) is no longer supported.

Would it be possible to do a dummy install somewhere else and copy the good script to my 6.0.5 install? I'm not completely comfortable adding a 6.x upgrade in the mix.

[phoenix]

Originally Posted by thunder04

I'm not completely comfortable adding a 6.x upgrade in the mix.

Why not? It's perfectly straightforward and you should take a backup before any upgrade.

[thunder04]

Well, because I have until noon to get this done and I already set up the config on the new server...

Can I do the upgrade without copying the index and store directores again? We have 200GB of e-mail and it takes HOURS to copy (It's been copying for an hour and 37 GB of it has copied thus far). Having to copy that over AGAIN will blow my timeline and I'll have to abort.

[thunder04]

Also, I can't upgrade the new server while the message store is copying over since it's copying directly into the message store folder....

If this thing is down longer than we planned, I just know our Superintendent (I work for a school district) is going to force us to Google Apps. Maybe I'm wasting my time... *sigh*

[thunder04]

Ohkay,

I upgraded our production server to 6.0.14 plus the patch. Now, when I run

/opt/zimbra/libexec/zmslapcat -c /backup

I get two files:

ldap-config.bak
ldap-config.bak.20111111095640

When following the directions for the 6.0.x and later LDAP setup, I reach a hiccup at letter k.

k. Type /opt/zimbra/openldap/sbin/slapadd -q -b "" -F /opt/zimbra/data/ldap/config -cv -l /backup/ldap.bak.

I do not have a plain "ldap.bak" file.

Upon opening the two files that were generated, they seem to look identical, and they are the same byte size. So, can I simply do step j and step k with the same file??

[thunder04]

Sorry, I'm an idiot! I skipped step 6 under the "Preparing 32-bit Server" instructions because I thought it didn't apply to 6.0.x installs. I realized this is not the case.

D'oh!