I have searched the forum and the install guides and have not found this specific scenario addressed.
Customer wants to move existing Domino server from one physical machine to another without change of server name, certifier, etc. and upgrade from 6.5 (on old) to R7 on new. The plan is to copy all Domino files from old machine to new (without actually installing anything on new machine) and THEN run the R7 install. Is there any reason this would not work or should not be done?
thanks,
Dieter
(I tried this post earlier so if it appears twice, my apologies)
Subject: Moving Domino server from one physical machine to another without name/cert change
Here are the steps that have worked for me numerous times. I got it from here somewhere, so I take no credit for it, I just know it works like a charm! And does work for 6.x server moves.
"The following procedure can be used when you need to move an existing Domino server to new hardware (i.e. when upgrading to a new server) without any disruption to your users. The procedure is based on a number of postings to notes.net and our own recent experience moving a R5.05 Domino server to new hardware. The basic idea is simple: install the same version of the server on the new box (but don’t configure it), then move the data directory & ini file from the old machine.
If possible, obtain the install media for the release of Domino currently running on the server you want to move - lets call it DEV1. If this is unavailable, upgrade DEV1 to the version you DO have available. It is vital that you install the release of Domino currently running on the old machine on the new hardware. If you only have the install media for 5.07, and DEV1 is currently running 5.05, you must upgrade DEV1 to 5.07 prior to the move.
Note: It is preferable to avoid upgrading the server prior to moving it, if possible - that way you can be sure that any problems encountered after the move are not due to problems with the upgrade.
If the server is one of several in a Notes Domain, replicate the Domino Directory (names.nsf) with another server in the domain to ensure an up to date copy.
Disable replication and access to the old server (to ensure we get a frozen snapshot of the server and its data). Replication and access via Notes clients can be disabled by simply taking the Domino server down. On an NT box, as an extra precaution you can remove any shares and stop the netlogon service (this must be restarted before data can be copied to the new box).
Do a full backup of the old server.
Install Domino on the new hardware, but don’t configure it.
Copy the data directory and the notes.ini file from the old server to the new box, replacing the data directory & ini file created during the Domino install on the new machine (if you stopped the netlogon service in step 3. you’ll need to restart it so you can connect to the new server). (Note: If you have any 3rd party Domino software installed on your server, you may also need some DLLs from the program directory; it safest to just reinstall the 3rd party software)
If the path of the data directory on the new machine is different to the old, you need to modify the directory= line in the notes.ini file to specify the correct location of the data directory on the new machine.
Disconnect the old box from the network.
Update the DNS to resolve the server name “DEV1” to the IP address of the new server (the NT server name doesn’t need to be the same as the old machine). (Note: If you’re using NetBIOS for name resolution, you also have to purge the NetBIOS cache or the other machines will not find the new machine)
Bring the new server up, test Notes and the DNS change
Do a full backup of the new server
If you need to reconnect the old machine to the network, make sure you trash the Domino server installation prior to reconnection to prevent conflicts with the new server.
You’re done - your server should now run happily on the new hardware with no disruption to your users."
I then bring the new server up check that it comes up, replicates with other servers, sends and receives internal and SMTP mail. Then I do the upgrade.
Subject: RE: Moving Domino server from one physical machine to another without name/cert change
The only thing I don’t like about this procedure is that by copying the data directory intact, you miss out on the opportunity to start with “clean” replicas of all databases. OTOH, it’s much faster this way, and making fresh replicas is subject to possible problems with access control. If there’s not an extreme hurry, though, I think the benefit of clean replicas is worth the trouble.