Migration from Lotus Domino 9

Looking to migrate to ZCS? Ask here. Got a great tip or script that helped you migrate? Post it here.
atanski
Posts: 1
Joined: Tue Oct 23, 2018 11:31 am

Migration from Lotus Domino 9

Postby atanski » Wed Oct 31, 2018 12:28 pm

Hi,

I'm trying to migrate from Lotus Domino 9 to Zimbra.

First of all ZCS Migration Tool gives an log output:

Code: Select all

 ProductName: Zimbra Migration Wizard for IBM Lotus Domino  Product Version:8.7.1.1661
 RPC Error:- WinHttpSendRequest failed. The RPC request is logged as C:\Users\DOMINO~1\AppData\Local\Temp\ZCSDominoMigrationWizard\1-RPCErrorRequest.xml
 RPC Error: One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server.
Continue with the invalid certificate?
 strSvrVersion: 8.7.11_GA_1854 20170531151956 20170531-1523 NETWORK
 dSvrMajorVer: 8.700000
 dProdMajorVersion: 8.700000
 wProdMinorVersion: 1661
 Server Minor: 11
 BaseDN: o=our_domain
 cn=admin system/o=our_domain -- admin@our_domain.pl
 cn=user/o=our_domain -- user@our_domain.pl
  ldap_result returned no LDAP_RES_SEARCH_ENTRY. Success, 101
 ldap_result returned no LDAP_RES_SEARCH_ENTRY. Parameter Error, -1
 DN Map Creation sucessfully done.
 database opened successfully.
 database opened successfully.
 Picking Objects
 Failed to execute query. No match found
 Failed to get field value Incorrect item type specified
 Failed to get field value Incorrect item type specified
 Failed to get field value Incorrect item type specified
 Failed to get field value Incorrect item type specified
 Failed to get field value Incorrect item type specified
 Failed to get field value Incorrect item type specified
 Failed to get field value Incorrect item type specified
 database opened successfully.

but account list is empty.

Second try was standalone NSFMigration-8.7.1.1661.exe:

Code: Select all

 31-10-2018 13:25:16 [7800]: ProductName: Zimbra Import Wizard for NSF Files  Product Version:8.7.1.1661
31-10-2018 13:25:16 [2376]: PopulateDominoUserIDMap: Start
31-10-2018 13:25:19 [7800]: Creating / starting worker thread
31-10-2018 13:25:19 [7800]: Dispatching work to worker thread
31-10-2018 13:25:19 [5336]: Worker thread started
31-10-2018 13:25:23 [5336]: Work arrived...C:\Users\atanski\Desktop\atanski.nsf atanski@zimbra.our_domain.pl
31-10-2018 13:25:23 [5336]: Logging on to zimbra server (zimbra.our_domain.pl:443)
31-10-2018 13:25:23 [5336]: Replicating folder hierarchy
31-10-2018 13:25:23 [5336]: Iterating through special folders
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to get view folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Iterating through user-defined folders
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified
31-10-2018 13:25:23 [5336]: Failed to process folder. Incorrect note type specified


I tried also imapsync - its great tool but slow and has timeouts...

Can anybody help? Someone migrated from Lotus 9 ?


User avatar
audriga
Posts: 5
Joined: Fri Nov 02, 2018 3:45 pm
Location: Karlsruhe, Germany
Contact:

Re: Migration from Lotus Domino 9

Postby audriga » Wed May 22, 2019 12:12 pm

Hi atanski,

even though this post is a little older, a short comment on this:

* We can support Notes=>Zimbra migrations under the cooperation described at https://zimbra.audriga.com
* This can include mails, contacts, calendars, tasks, eventually notes
* Our system can migrate many mailboxes in parallel which should increase speed. However, of course the Notes and Zimbra server and their internet connection need to be sufficient

Best,
Hans-Jörg (audriga)
Lewis-H
Posts: 34
Joined: Wed Jan 01, 2020 11:28 am
Contact:

Re: Migration from Lotus Domino 9

Postby Lewis-H » Wed Apr 01, 2020 12:51 pm

Put 2003 servers in Permanent/ Long term Maintenance Mode
· Log-on to Win2K3 server and stop the Lotus Domino services
· Take backup of Existing Server by Coping all the databases from Win2K3 to Win2K8 servers.
· log-on to Win2K8 server and Install the Domino 8.5.2 FP4 software on Win2K8 VM.
· Run the Domino server setup and follow the on-screen instruction
· Copy the domino system databases, Server ID file and notes.ini file from win2k3 to win2k8 server.
· Make the necessary changes in the notes.ini (update the program and data path) and configure the domino server on Win2k8 server
· Start the domino server services on Win2K8 And Perform the health check on the new Domino servers.
· Copy all databases from win2k3 to win2k8 server on their respective path
· Rename 2003 PROD/DR servers at the end of the migration server-old,
· Shutdown 2003 PROD Servers (server-old )
· Start the domino server services on Win2K8
· Perform the maintenance of all databases and perform another health check on new Domino servers.
· Check the connectivity of the domino server to other domino servers.
· Update the IP address of the win2k8 box in the allow list of SMTP servers.
· Coordinate with DNS team to map the domino alias to IP address of Win2K8 server
· Handover to the Application Team
· Application team to do detailed Application checks
· Do Replication Health Check to ensure the links are up and replication is occurring as scheduled with all services listed. This is to ensure there is no adverse impact on other environments.
· Business Testing
· Failover Testing between the Prod servers by bringing down the PROD server.
· Check whether all users are failover to the DR server.
· On successful failover, bring the PROD server back online
· Business Sign-Off
· Take 2008 servers out of Maintenance Mode and into Monitoring mode
· Follow the VM Rename SOP for server-old
· Email verification to the users that migration is complete and successful
· Email to the Stakeholders re status of the migration
· Email these Teams to advise which servers have been shut down and should not be powered back on.
· Submit an SR to the Backup to request the backup jobs be disabled for the list of servers.

Return to “Migration”

Who is online

Users browsing this forum: No registered users and 3 guests