We are swapping out an old Notes server (8.5.3) with a new server running 9.0.1, and are looking to minimize downtime. The idea we have is to set up the new server in a cluster, let it replicate while the old (current) server is up and running, disconnect all users and do one last replication, then take the old server down. We would then rename the new server with all the old server data/IP address and make it the primary server. These seems like it would call for significantly less downtime than taking down the old server and then manually copying over 1 TB worth of databases
Would this method work? I don’t have any experience with clusters, so any help would be appreciated. Thanks.
Subject: Renameing a Domino Server
That process would work. Here is a technote on how to rename the Domino Server:
Procedures for renaming a Domino server / migrating to a new Domino server
http://www-01.ibm.com/support/docview.wss?uid=swg21102494 http://www-01.ibm.com/support/docview.wss?uid=swg21102494
Subject: A section in the Upgrade Cookbook
Upgrade Cookbook
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/UC1_TableofContents.htm http://www-10.lotus.com/ldd/dominowiki.nsf/dx/UC1_TableofContents.htm
Pertinent Section
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Page_1_Planning_the_Domino_Server_85x_deployment#newormove http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Page_1_Planning_the_Domino_Server_85x_deployment#newormove
Option 3 - Install New Domino servers (Inherit Identities)
- Build new server independently
- Create a new temporary server identity
- Permits change of underlying hardware and operating system
- Permits testing of the configured state before cut-over
- Create replicas on temporary server and keep in synch with server to be replaced via replication
- At desired time, switch server host, network and Domino server identities
- Change is transparent to clients
- If clustered…
-repeat process for each server
-do not add temporary Domino server into cluster
One thing I’ll add is make sure your databases on Remote Server are not Encrypted and you also have to make sure that if you are using DAOS on the new Server you have to make sure the .NLO files are not encrypted either as you will be switching Domino ID files…
To be honest, and I know it’s a lot of data, I find it much easier to use option 2
Option 2 - Move existing Domino Server to new hardware
Note: It is not recommended that you upgrade the hardware and Domino at the same time. You should upgrade the hardware before or after the Domino upgrade, but not at the same time unless you have no other choice. Upgrading them separately makes it much easier to troubleshoot when problems arise, isolating the issue to the hardware upgrade versus the Domino upgrade.
The server identity remains the same, but will be moved to a new machine:
- Bring down the current server
- Move all data to the new hardware to the same position (same file locations and directory structure) as the old hardware.
- Domino program directory
- Domino data directory
- Domino transactional logs
- Domino DAOS files (only if upgrading from 8.5 to 8.5.1)
Note: If you are changing file locations and directory structure during this move, refer to the wiki article: Changing directory locations when moving a Domino Server to new hardware http://www.lotus.com/ldd/dominowiki.nsf/dx/Changing_directory_locations_when_moving_a_Domino_Server_to_new_hardware for more information.
- Rerun install of the current version of the Domino server and point to all of the same file locations to mirror your previous configurations
- Once you start the copy of data to the new hardware, you should never bring up the server on the old machine
- Before bringing up the server for the first time, switch the server host and network identities to that of the old server
- Run this configuration for a few days to make sure everything runs correctly. If so, then you can safely upgrade this Domino server
Regards,
John Pag
jpaganet@us.ibm.com