Lotus Domino Server hardware refresh

T-cko
T-cko used Ask the Experts™
on
Dear experts,

I would like to ask for help, resp. advice.

For our customer is planned a hardware refresh of Domino Server running on Solaris
Current situation is:
server1 and server2 in a cluster, planned is to install new server3 and server4 also in a cluster. In the test period will run old and new servers concurrently. What would be the "best practise" for that?
I plan following steps:
1. register new servers in domino directory on server1 (create IDs)
2. make a clean installation of server3
3. copy the data folder from server1
4. configure the server3 and start it
5. the same with server4

Please note, that the old and new servers are not on the same network, so replication between the old and new environment is not possible. The servers act as web servers.

Thank you for your comments
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Sjef BosmanGroupware Consultant

Commented:
I can agree with the hardware refresh plan you added above.

When the new servers are to be accessible for the same users as the old servers, make sure the new servers have different names than the old ones, also their network names, otherwise you'll have some serious network problems.

> They are not on the same network...
Will they be 2 clusters of 2 servers, or 1 cluster of 4? In either case, you might have consistency issues with mainly the mail database (if any), because only one server or cluster will receive mail. How do you plan to replicate incoming mail?
The requirement for the old and new servers to be completely separated will generate a lot of extra work, as well as the occurrence of an outage, because mail the mail connection must be stopped in order to migrate.

If you build a new cluster first, and then gradually migrate users using built in tools, you will have a much easier ride, and no outage

Commented:
Are these just web servers as opposed to user connected mail/application servers?  And is the test just a closed test, i.e.not live to users/the world?

If there is no overlap period then yes just install two new servers ready, for the test period take a copy of the data directory and notes.ini from the old two servers to the two new ones (with the old server down during the copy) and run them as server1 and server2 still.

At the changeover point, down the old two, recopy the data directories and bring the new two up.

If there could be comms between them of any sort - only needs specific port 1352 firewalled connection say - then it would be much easier and could be transparent to the usersas you could add the new servers to the cluster, or remove server2, rebuild it on the new box but still in the cluster then do the same for server1.

So can you fill us in on some more of the details?

Steve
Announcing the Winners!

The results are in for the 15th Annual Expert Awards! Congratulations to the winners, and thank you to everyone who participated in the nominations. We are so grateful for the valuable contributions experts make on a daily basis. Click to read more about this year’s recipients!

Author

Commented:
Dear all,

thank you for your quick answers/advices. There is no mail routing enabled on the servers, they act only as a web server - accessible from the internet. During the overlap period will new servers be tested internally, by the customer. For testing will be used data from a backup, the final data migration is planned as following: shutdown server 1 (www still accessible on server2), copy all *.nsf and *.html to the new server3 (offline copy), start server3 and push the replication to server4. After GO LIVE decision the DNS entry for affected URLs will be changed.

Do you see any "weak point" here?

Have a nice day
M.
Commented:
Well personally I would suggest:

Offline server 1, 3, and 4

Give server 1 a different IP, and server 3 the old Server 1 IP
copy data to server"3" and bring it up as SERVER1

Offline server 2
Give server 2 a different IP and server 4 the old server 2 IP

copy data to server "4" and bring it up as server2

Back as you were before.

Then there is no DNS caching delay etc.

If these are internally located on private addresses but connected to from the internet then you could re-point your firewalls to the new servers instead of swapping IP's around.
Sjef BosmanGroupware Consultant

Commented:
Agree with dragon-it.

I'd also consider two virtual machines (next time), on two different real machines. The VMs running Linux or so. Whenever you have to upgrade again, you add processors and memory, and worst case you move the whole VM to a different server. The server's databases could even be stored on a SAN or NAS.

Commented:
Thanks for the points / answer.  Did you get it all going OK in the end ?

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial