Q
Get started Bring yourself up to speed with our introductory content.

How did a successful HUB server upgrade to ND6.5.1 turn mutant?

Our global infrastructure is R5.0.11. Two days ago we upgraded our HUB server to ND6.5.1. Generally, we haven't had problems. This afternoon, however, the design became a hybrid of R5/ND6, and we can't work out where this came from. We have checked the obvious replication history, but can't see any reason why the design should become partially overwritten. Any suggestions?
I have no immediate answer without looking at the database in detail. For starters, you can look at the offending design elements. Check the modification dates, last editors, design template and the various design replication options.

Do you have comments on this Ask the Expert Q&A? Let us know.

This was last published in April 2004

Dig Deeper on Lotus Notes Domino Deployment and Migration Advice

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

Search400

  • iSeries tutorials

    Search400.com's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...

SearchDataCenter

SearchContentManagement

Close