Misunderstood multi-versioning
Kim Greene
In a conversation with a new customer this afternoon, I heard a common theme come through; multi-versioning is not well understood. I have had similar conversations with a number of customers over the past few years. The net is that customers do not understand what multi-versioning is and how it can benefit their Domino installations.
Domino on the System i (iSeries, AS/400) has had multi-versioning since releases 6.0.3 and 6.5.0. This support allows more than one version of Lotus Domino to be installed and running on your iSeries at the same time. For example, a single iSeries box or iSeries LPAR could have releases 6.5.6, 7.0.2, 7.0.3, and 8.0.1 installed and running. The main areas of confusion I have found related to this support in my conversations with customers are related to these three areas:
1) how it affects the install process
2) how servers are upgraded to the new release after the new code installation
3) do all servers have to be upgraded at the same time
How it affects the install process
I like to use multi-versioning support to, at a minimum, install the new version of Lotus Domino. With multi-versioning support, I can leave production servers active while installing the new version. This saves about 1/2 hour of downtime for the customer. It also allows the customer the flexibility of installing the new code version during production hours, so they are ready to update their Domino servers whenever is convenient for them.
How do servers get updated after the installation
There is an UPDDOMSVR (Update Domino Server) command that allows you to specify which server you want to take to the new release level. When you are ready to update a Domino server, simply end the server and issue the UPDDOMSVR command. The parameters to the command are the name of the Domino server and the release level you would like to upgrade the server to. It really is that simple.
Do all servers have to be upgraded
This is a very simple answer, no. You can pick and choose which servers to upgrade. For example, if a customer has three servers sitting at releast 6.5.6 and they want to upgrade one of the servers to release 7.0.3, they have that flexibility. Better yet, if a customer wants to check out the new release 8.0.1 that came out yesterday, then can simply install the new code release, configure a test server with this new code release, while leaving their existing servers untouched.
Multi-versioning is really that simple!