Re: QTOFARQRY

I think I could put a *NOMAX on the save and it wouldn't work - until I 
dropped the Domino servers.  And, even if it did get a lock on it when the 
data queue was in the process of being passed from one Domino server to 
another, I would bet that the Domino server jobs would get ill.  I'll just 
skip saving the object.

Big save, preceded by RCLSTG, every 8 weeks.  PTF's and IPL follows.

- Get software vendor keys.  IBM gives you 70 days - so no big deal.  But 
those third party ap's may not cut you any slack.  Question:  In a real 
disaster, how long would it take you to get running keys?  We've found 
that some vendors will only let you talk to the Smiling Jack the sales 
guy, who happens to be on vacation this week.  Document this key process 
in your recovery instructions.  I wonder if DR plans should be in every 
bid proposal?

- We've found that a save after a restore is about the only truly reliable 
method of determining objects that may have become damaged.  For example, 
even though we run a RCLSTG immediately prior to the full system save, we 
still occasionally have a backup hurl because of damaged objects.  The 
backing up of an object is what sets the 'damaged' flag on the object, if 
it's damaged.  I think Barsa recommends the save also.  This also gets you 
a new SAVSYS in case you have to restore to the new machine.  Not much of 
a concern in a DR test weekend for sure.

Rob Berendt