Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Migration

Welcome to the Zimbra - Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 06-21-2009, 09:28 AM
Advanced Member
 
Posts: 180
Exclamation from sun java communication suite to zimbra

Hi all,
I am using the imapsync to migrate the data from sun java communication suite to zimbra.
In sun suite I have 2400 messages in my inbox, but migrated data shows only 1400 messages.
The total number of message in my inbox, sent and in some different folders are 4800 but in the logs of imapsync I have seen that the tranfered messages is 5624, any info or help.
Moreover, any smooth strategy OR any other tool instead of imapsync for migrating 700+ users from sun suite to zimbra, I have mailboxes which have 1 to 2 lac of messages

Regards
Adeel
Reply With Quote
  #2 (permalink)  
Old 06-25-2009, 12:36 AM
Trained Alumni
 
Posts: 21
Default

We completed migrating 2800+ accounts from iplanet 5.2 to zimbra this week using imapsync. It was a bit slow (10days for 2TB), but went fairly well. A full imapsync was run followed by additional syncs using the "maxage" option. A maxage of 5 with 2800 accounts finished in 4 hours.

The imapsync was staged on a third host and we used proxy accounts on sun and zimbra to access the end users account. Our config allowed for about 8 simultaneous imapsyncs.

After the account was fully converted into zimbra, we used Sun's ims "deliver" command to drop one final message in the old account, informing the user their email account now existed at a different host. This was important for pop and imap clients that still pointed to the old server.

Guide to imapsync - Zimbra :: Wiki
Reply With Quote
  #3 (permalink)  
Old 06-25-2009, 01:28 AM
Advanced Member
 
Posts: 180
Exclamation

THX,
actually I was viewing the messages in conversation mode (VIEW), when turn into message mode the right number of messages were shown.

Did you automate the script, if yes then how did you manage the usernames and password of old mail server and for the new mail server in the script.

I think I have to manually enter it in the scripts.
Please share your strategy for the migrating the passwords. Did you use the ldapmodify?

Regards
Adeel
Reply With Quote
  #4 (permalink)  
Old 06-25-2009, 02:17 PM
Trained Alumni
 
Posts: 21
Default

Quote:
Originally Posted by adeelarifbhatti View Post
THX,
Did you automate the script, if yes then how did you manage the usernames and password of old mail server and for the new mail server in the script.
It was fairly automated. A few perl scripts were used to create the zimbra accounts, added aliases, transfer the personal address book entries (PAB) and imapsync their email.

We are using an external ldap server for authentication so we did not need to transfer their password into zimbra and created the account like:
Code:
  zmprov ca someuser@mydomain.com  "" givenname "firstName" sn "lastName" cn "firstName lastName" displayName "firstName lastName"
If you are importing the passwords into zimbra's openldap server, then maybe run ldapsearch on sun's directory server and retrieve the 'userpassword' value for the user and include the result in the zmprov command. You should also be able to grab the cn, sn, mail, mailalternateaddress, etc values from sun's directory server and use it to build the appropriate zmprov command.

Code:
  zmprov ca someuser@mydomain.com  {ssha}sdkfgjksdfjksajfdskaf givenname "firstName" sn "lastName" cn "firstName lastName" displayName "firstName lastName"

  zmprov aaa someuser@mydomain.com theiralias@mydomain.com
On the sun side, a "message store administrator" was established. Store admins can have imap proxy rights to individual accounts. You will not need to know the user's password to transfer their email into zimbra. Same is true on the zimbra side.

We did something similar to this:
Code:
foreach $user (@listofusers){
        $user1 = $user2 = $user;

        $cmd = "/usr/bin/imapsync --buffersize 8192000 --nosyncacls " .
                  "--subscribe --syncinternaldates --host1 $oldserver " .
                  "--user1 $user1 --authuser1 $sunproxyauthuser1 --authmech1 PLAIN " .
                  "--passfile1 $passfile1 --port1 143 --host2 $newserver " .
                  "--user2 $user2 --authuser2 $zimbraproxyauthuser2 --authmech2 PLAIN " .
                  "--passfile2 $passfile2 --port2 143 --noauthmd5";
       system ($cmd);
}
Reply With Quote
  #5 (permalink)  
Old 06-25-2009, 10:14 PM
Advanced Member
 
Posts: 180
Exclamation

Well, Thanks but any explaination of the following.

--authuser1 $sunproxyauthuser1

--authuser2 $zimbraproxyauthuser2

Regards
Adeel
Reply With Quote
  #6 (permalink)  
Old 06-27-2009, 09:24 PM
Trained Alumni
 
Posts: 21
Default

Quote:
Originally Posted by adeelarifbhatti View Post
Well, Thanks but any explanation of the following.
--authuser1 $sunproxyauthuser1
It is described here.
Specifying Administrator Access to the Message Store - Sun Java Communications Suite - wikis.sun.com

1. from the sun messaging server command line, run:
Code:
configutil -o store.admins
2. Add to the list of admins, preserving any values from step 1:
Code:
configutil -o store.admins -v "admin,jnorton,frankf,ted"
3. Run an ldap search to locate service admins. This is sun's directory server, not zimbras, openldap server.
Code:
ldapsearch -D 'cn=directory manager' ... -b 'dc=host,dc=com' 'cn=Service Administrators' dn
4. Ldapmodify the dn from step three, to include the dn of the admin from step 2.
Code:
ldapmodify ....
dn: cn=Service Administrators, ou=Groups, dc=host,dc=com
changetype: modify
add: uniqueMember
uniqueMember: uid=ted, ou=accounting, dc=host,dc=com
5. ldapmodify the dn of the new admin to include the service admin of value from step 3
Code:
ldapmodify ....
dn: uid=ted, ou=accounting, dc=host,dc=com
changetype: modify
add: memberOf
memberOf: cn=Service Administrators, ou=Groups, dc=host,dc=com
6. restart sun's messaging server imapd process.


The zimbra side is more simple.
Quote:
--authuser2 $zimbraproxyauthuser2
From the command line on your zimbra server, run:
Code:
 zmprov gaaa
That is the list of users that can auth on behalf of others to perform tasks like imapsync. One might be "admin".

Using the examples above, I would use "ted" on the sun side and maybe "admin" from the zimbra side to perform the syncs, like:

Code:
       $cmd = "/usr/bin/imapsync --buffersize 8192000 --nosyncacls " .
                  "--subscribe --syncinternaldates --host1 $oldserver " .
                  "--user1 $user1 --authuser1 ted --authmech1 PLAIN " .
                  "--passfile1 $passfile1 --port1 143 --host2 $newserver " .
                  "--user2 $user2 --authuser2 admin --authmech2 PLAIN " .
                  "--passfile2 $passfile2 --port2 143 --noauthmd5";
The $passfile1 and $passfile2 should point to a file containing the password for authuser1 and authuser2.
Reply With Quote
  #7 (permalink)  
Old 12-28-2009, 01:42 AM
Starter Member
 
Posts: 1
Default PAB Migration perl script to zimbra

Hi Folwer,

Appreciate if you could provide us the script you used for migrating personal address book from SUN IMS to Zimbra.

Thanks

Vijay
systems@mailman.aus.edu
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

Zimbrablog.com