TrePium Technologies

IBM Lotus Domino 8.5 to IBM Lotus Domino 9.0 Migration cut over plan

When you upgrade users' mail files to the Notes 9.0 mail template or to the Lotus iNotes (9.0) template, you can upgrade one file at a time or use the mail conversion utility to automate upgrading the design. Be sure that you have already upgraded the Domino server that hosts the mail files and the Notes clients that access those files, or users will not be able to use the features in the new design. Upgrade mail files at a time when users won't be accessing them -- for example, early mornings or over a weekend. Notify users that their mail files will be unavailable during the upgrade.

Migration Steps :

· 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 on all databases and perform another health check on new Domino servers.

· Check the connectivity of domino server to other domino servers.

· Update the IP address of 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 server listed. This is to ensure there is no adverse impact on the other environments.

· Business Testing

· Failover Testing between the Prod servers by bringing down the PROD server.

· Check whether all users are fail over to DR server.

· On successful fail over, 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 Team 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