R6 migration with mixed R5 servers

I am planning a migration from Domino servers 5.10 and higher on AIX and NT with clusters. We have Quickplace and Sametime server running on Domino overlays as well. I need to able to migrate most of the Domino servers to R6. I need to keep some R5. Besides preventing design of the Domino directory from replicating between R5 and R6, is there any other problems or considerations? Will ST 3.0 and QP 3.0a support R6 or do I need to keep them R5 until supported?

Any help from the trenches is appreciated!!!

Subject: you can migrate the domino directory to D6 in the whole domain

D6 domino directory is designed for coexisting between R4.6.7a, R5 and D6. There are even fields in the D6 design which are not used any more and they are still in there for backward compatibility.

I would start with the HUB servers/Administration Server of the Domino Directory and the new design of the system databases first (to make sure all Adminp Requests for the Domain are properly handled…)

And than it is pretty much your choice what to change next. ST and QP will still bound to specific versions of Domino. I have no clue about the actual releases needed. But they will work fine in a mixed infrastructure.

(nsh)

Subject: RE: you can migrate the domino directory to D6 in the whole domain

Thanks Daniel. Are you saying that it is OK to let the R6 directory design replicate across R5 servers? Or should I prevent design replication of forms, views, and agents between R5 and R6 directories?

Subject: Let it replicate across your domain. It is totally backward compatible with R5.

Subject: RE: Let it replicate across your domain. It is totally backward compatible with R5.

Upgrade Redbook says not to let design replicate on R5 servers for Sametime and Quickplace. I was wondering if the same applied to other R5 mail and app servers. Have you done the upgrade yet with a mixed R5 and R6 environment? Of course I’ll test, just wondering what the rest of you all have experienced.

Thanks!

Subject: RE: Let it replicate across your domain. It is totally backward compatible with R5.

In my experience, I just let the directory replicate across all servers.

I’m running mixed v5 and v6 clusters (for testing purposes - normally you wouldnt want to do this).

The proof, as always, is to construct a test environment and run it there first. Okay, it’ll take some time, but then at least you can demonstrate and test in a non-fatal way. And cover your ass…

:slight_smile:

Typical consultants answer… :slight_smile:

—* Bill

Subject: some more typical consultant stuff … :wink:

How many management consultants does it take to change a light bulb?

Multiple answers:

  1. How many did it take last year?

  2. It depends – how much money is in your budget…?

  3. None. A consultant would recommend replacing the light fixture.

  4. None. Consultants don’t know how to do anything; they can just tell you how you should do it.

  5. One partner. He holds on to the bulb and the whole world revolves around him.

  6. That’s difficult to say. First, we need to do a study to see if you really need light in that area, determine historically why the light burned out, and an analysis to determine whether it’s the right kind of light anyway. Then, maybe, we can recommend appropriate action – although we may need to do additional studies to determine the light sensitivity of employees visiting the area. After that, we can: develop RFPs and RFQs, evaluate the abilities of various maintenance workers to perform the task, recommend personnel selection, and supervise the activity.

  7. Have you thought about rewiring your whole house recently?

And also some info about how software development works in some companies :wink:

Software Development Process

  1. Order the T-shirts for the Development team

  2. Announce availability

  3. Write the code

  4. Write the manual

  5. Hire a Product Manager

  6. Spec the software (writing the specs after the code helps to ensure that the software meets the specifications)

  7. Ship

  8. Test (the customers are a big help here)

  9. Identify bugs as potential enhancements

  10. Announce the upgrade program

Check http://ldd.nashcom.de/nshweb/pages/fun.htm for more jokes :wink:

Daniel Nashed

(ldd@nashcom.de)

Subject: RE: Let it replicate across your domain. It is totally backward compatible with R5.

R6 design has replicated to our D5 sametime and quickplace servers with no noticable problems. Domino.Doc is also D5 at the moment, although we will be upgrading it to D6 shortly.