Head in a blender

Fine tuning the interpretation of the upgrade steps

Andy Pedisich  June 3 2008 11:22:14 AM
I've been re-reading the article called Steps for migrating from Notes/Domino 7.x to Notes/Domino 8.x trying to get my small brain around the sticky parts of the technote.

The sticky part, of course, is having to run Fixup/Compact/Updall prior to upgrading.  To quote the note:

1. Ensure that database clean-up is completed by doing the following on the Domino 7.x server to help avoid database and/or view corruption. It is recommended to run the commands with the server down.


The wording seems a little ambiguous about the need for doing these before you upgrade.  It says to "help avoid" issues.  I'm sure it's not something that your required to do in all situations.  It probably only needs to be done if you are very cautious and have the time, or if you know that your databases are having corruption issues.

It's a fact that databases need cleaning up during the lead-up time to any upgrade.  Believe it or not, I've run into shops that don't do system maintenance tasks on a regular basis.  Folks like that would be well advised to take the server down and do some scrubbing.

I can't imagine a requirement for upgrading that would make you get a window to shut down a server and run pre and post maintenance on all of the databases on a server.  Nobody's going to get a window that big.  This is a new technote.  Maybe the wording will be fine tuned.

I've talked to some folks who like doing a FCU on system databases like NAMES.NSF, ADMIN4.NSF, EVENTS4.NSF and DDM.NSF off-line with the server down, prior to upgrading a server.  Personally, I have never done this, but these are smart people and obviously feel like it's more insurance that things will go well after the upgrade.  I certainly FCU them after the server upgrade, but before the server is re-started.

A wise old buddy of mine from Lotus once told me a while back that you want to make sure that the outage you take for upgrades doesn't get blamed when Domino corrects existing problems.  And each Release of Domino seems to be better at detecting issues.

Over time I've learned there are a lot of technique variations, many of which are founded on paranoia which is based on unpleasant experiences.  Sometime the cause for that paranoia has been fixed, but we keep on doing what we do anyway.

-Andy
Comments

1Dan Soares  6/3/2008 8:34:13 PM  Fine tuning the interpretation of the upgrade steps

"Believe it or not, I've run into shops that don't do system maintenance tasks on a regular basis"

Andy

For the benefit of the new admins who read your blog would you elaborate on what "system maintenance tasks" need to be done on a Domino server on a regular basis?

Thanks!

Dan

2Fred Janssen  6/4/2008 9:01:00 AM  Fine tuning the interpretation of the upgrade steps

I would advise run a (bi)weekly/monthly fixup, compact and updall on all servers on the following databases:

names.nsf, admin4.nsf, events4.nsf, statrep.nsf, ddm.nsf.

Create and IND file with these filenames (enabling me to easily add other database when deemed necessary).

Then create a script to:

1. End the Domino server

2. Run the maintenance from the OS

3. Restart the machine (if dedicated for Domino).

Fred

3andy pedisich  6/4/2008 10:09:43 AM  Fine tuning the interpretation of the upgrade steps

@Fred - I like that, but the best way to run maintenance on those files is when the server is down.

- Andy

4Fred Janssen  6/5/2008 10:41:25 AM  Fine tuning the interpretation of the upgrade steps

@Andy

Please refer to step 1 in my 3 step plan ;-)

It should off-course be scheduled sometime during the weekend...

5Andy Pedisich  6/5/2008 10:44:38 AM  Fine tuning the interpretation of the upgrade steps

@Fred - Darn! If only I knew how to read before I wrote!

"Test"