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.
Thanks
Rick
From: Ian Smith <ian.smith AT OUCS.OX.AC DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 11/14/2011 06:47 AM
Subject: Re: Dev Class type FILE with multiple directories
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Keith,
the difference is that you are using pre-defined volumes - which the doc
says will be used in alphabetical order - see the worked example at the
bottom of the technote (steps 1 - 8 ). The true round-robin across
directories only works when using scratch volumes (that are auto-created
on demand).
Ian Smith
Oxford University.
On 12/11/11 15:33, Arbogast, Warren K wrote:
> Rick,
> I am just getting started with FILE deviceclass storage pools, so take
the following with ample grains of salt. However, my experience
contradicts swg21497567. Or, I might misunderstand that Technote.
>
> This is a TSM 6.2 RHEL5 server. The file deviceclass has fourteen 2 TB
filesystems on raid10 ldevs. Volumes were predefined to the storage pool
with 'wait=yes', so they were created one at a time in round-robin order
across the filesystems.
>
> A small amount of client backups are being written to the file pool at
this time, so it is clear how volumes are being used. Client backup files
are written to the storage pool in volume name order, not in filesystem
name sort order. Today I see one full volume in each directory, and many
empty volumes. If the Technote applied, all full volumes would be in the
first directory.
>
> Ås far as I know,
> Keith
-----------------------------------------
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.
|
