I had said:

>Here's another NFS based dedup box question . . .
>Taking a NFS based dedup box down would require taking the NFS share
offline (unmounting it).
>What would you do in TSM to stop it from  accessing the FILE dev based
stgpool?
>The only thing I can see is a "update stgpool x access=unavailable".
>For tape we take the drives and/or paths offline when we take a lib down.
 Just wondering what the equivalent is for a FILE based stgpool.

We had to replace a memory dimm in our DD yesterday.  The DD had reported
that a replacement was needed, but the DD was running just fine.  We did
not want to take TSM all the way down, so I used this procedure:

updated the stgpools to access=unavailable
killed several processes using those stgpools
unmounted the NFS share
<emc fixed the DD>
mounted the NFS share
updated the stgpools to access=readw

This worked perfectly.  Immediately after bringing the stgpool back to
access=readw several reclamation jobs kicked in.


Rick


-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.