Results 1 to 5 of 5

Thread: Help for Migration

Hybrid View

  1. #1
    Join Date
    Jul 2007
    Location
    New York, NY
    Posts
    46
    Rep Power
    8

    Default Help for Migration

    I tried to migrate my old system from 4.5.4 GA on CentOS 4.4 32 bits to 4.5.7 GA RHEL 5(64 bits) on cluster. After consulted with professonal ppls, here are the suggestions I have.

    Because 4.5.4 GA doesn't support RHEL 5(64 bits), I can't restore from 4.5.4 GA CentOs(32 bits) full backup to 4.5.4 GA on RHEL 5(64 bits) by following the wiki Network Edition: Moving from 32-bit to 64-bit Server.(not - ZimbraWiki recommanded) After that, I can just perform a 4.5.7 GA upgrade on RHEL 5(64 bits) then. But seems it's a not recommanded way to do.
    The safe way I can perform is "IMAPSYNC" which is I am doing right now.

    My questions are
    1. Is the method provided above(not imapsync) really not working? I should go with imapsync only?
    2. Base on current release Zimbra have, there is no cluster option on RHEL 5. What kind of fail-over/cluster option I can use here? Can I follow someone's post by implemeting heartbeat?

    Thanks
    Chadsel
    Last edited by mmorse; 10-11-2007 at 08:54 PM. Reason: corrupted post - but all good now :)

  2. #2
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Quote Originally Posted by Chadsel Chen View Post
    I tried to migrate my old system from 4.5.4 GA on CentOS 4.4 32 bits to 4.5.7 GA RHEL 5(64 bits) on cluster. After consulted with professonal ppls, here are the suggestions I have.

    Because 4.5.4 GA doesn't support RHEL 5(64 bits), I can't restore from 4.5.4 GA CentOs(32 bits) full backup to 4.5.4 GA on RHEL 5(64 bits) by following the wiki Network Edition: Moving from 32-bit to 64-bit Server.(not - ZimbraWiki recommanded) After that, I can just perform a 4.5.7 GA upgrade on RHEL 5(64 bits) then. But seems it's a not recommanded way to do.
    The safe way I can perform is "IMAPSYNC" which is I am doing right now.

    My questions are
    1. Is the method provided above(not imapsync) really not working? I should go with imapsync only?
    2. Base on current release Zimbra have, there is no cluster option on RHEL 5. What kind of fail-over/cluster option I can use here? Can I follow someone's post by implemeting heartbeat?

    Thanks
    Chadsel
    IMAPSync is by far the easiest route.

  3. #3
    Join Date
    Jul 2007
    Location
    New York, NY
    Posts
    46
    Rep Power
    8

    Default

    Here are my imapsync parameters. "--useheader 'Message-ID' --skipsize" would avoid me to have multiple copies in "Sent" folder if I ran multiple times. But I found out the other serious problem is imapsync doesn't take all the changes from old server to new one. I have some users' messages being left behind or messages deleted on the old server but still not deleted on the new server after I re-run. I think it's something related to imapsync. It's still not 100% reliable.

    imapsync --buffersize 8192000 --noauthmd5 --nosyncacls --syncinternaldates --useheader 'Message-ID' --skipsize --host1 $host1 --user1 "$user" --password1 "$p1" --host2 $host2 --user2 "$user" --password2 "$p1" --exclude Chats --exclude Contacts --exclude Junk --exclude Trash --exclude "Emailed Contacts"

    Hence I still decide to go with full restore. If I have any good news, I will post here to share everyone.

    A clean imapsync from 4.5.4 GA (CentOS 4.4 32bits) to 4.5.7 GA (RHEL 5 64bits) for the same user. The mail box size would be different on both servers. 4.5.7(new) will be larger than 4.5.4(old) even I exclude Junk, Trash....etc That's what I observed. Share here.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •