Oct 2, 2015, 11:51 AM
105 Posts

Thoughts on server update vs fresh install

  • Category: Administration
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags:
  • Replies: 4

Looks like it's probably time to move from 8.5.3 FP1 to 9.0.1FPcurrent. In the past, we've always spun up a new server, replicated dbs from old to new, downed the old server, and renamed the new server to the old name. It works, it provides a clean fresh install, and we can do it again. We typically did 2 version up-revs (4.6 to 6.5 and 6.5 to 8.5) so this is the first time the revs are close together.

If we opted to do an in-place upgrade, what are the likely disadvantages? I'm thinking that just running the 9.0.1 installer + fix packs might be quicker and require less IP/ini/name manipulation and could be substantially faster and less fuss and require little to know config changes.

Your thoughts?

Thanks for the feedback.

Additional information:

  • We use transaction logging.
  • We don't use Notes for mail, although our apps do send mail to Outlook as part of workflows.
  • We're not 'social', everything is inside the firewall and locally developed apps.
  • Very few web based apps and they all run inside the firewall using straight http.
  • No XPages
  • We're not planning to do client upgrades at this time.
  • We do run server based Oracle to Notes code
  • We also run Integra4Notes and need to install Excel and Word so it works properly.
  • One add-in: AuditManager.nsf with ntrigger.dll for audit trails.
Oct 2, 2015, 2:52 PM
312 Posts
Thoughts

You should be fine in doing in place upgrade.  I take it you tested all the add on products and dbs on the new version?

 

Naturally I would back up everything.

Make sure Notes service (s) are disabled and reboot server before upgrade.  This prevents a file / process in use that can prevent a successful upgrade.

After applying 9.01 start and stop server before apply fix packs hot fixes.

Upgrade the ods to latest version.

 

Oct 7, 2015, 9:18 AM
3 Posts
Try this?

For full version upgrades I normally uninstall Domino, and install the new version, ensuring that I'm pointing the setup files at the existing Domino application and data directories.

I also suggest that you set the Domino windows service to Manual AFTER running the upgrade, prior to rebooting the machine. I've seen systems never come up after upgrade after this, and it's such a pain to fix. Set the service to auto after the first reboot.

Oct 13, 2015, 12:30 PM
13 Posts
For what it's worth...

I recently did this with three Traveler servers.  The changes from 8.5.1 to 9.0.1 are rather large and you would be well advised to perform a clean install of the server code.  There are many schools of thought on this, but you should also be very careful about servers running the HTTP stack.  If you are using the old SSL settings and an old keyring file created using the CERTSERV.NSF database, you will want to create new keyrings before hand using the processes outlined in the documentation for Domino 9.0.1 and TLS.  This is not a trivial matter.  Also, there is a bug in Fix Pack 4, more a memory leak, that is fixed in 9.0.1 Fix Pack 4 Interim Fix 2, that can cause the HTTP stack to crash and take the rest of the Domino server with it.  NOTE: Fix Pack 5 is supposed to be released in November of this year.