Re: Directory storage pools
>As per the TSM redbook at:
>It suggests use of DISKDIRS and OFFDIRS to store directory information
>to avoid restore-time directory reconstruction hits.
>Everything makes sense, including the need to explicitly bind all
>directories on a client to the DISKDIRS management class with DIRMC.
>The next question is... *how* do you select ONLY directories for this
>management class without selecting any files within them, in dsm.opt?
>(Server is 126.96.36.199 on AIX and clients are 188.8.131.52/15 on Windows, Linux,
>Solaris, and AIX.)
Directories cannot be independently selected for a Backup or Archive
operation: they are implicitly backed up or archived along with files
unless you cause files only to be operated upon. Perhaps it would be
helpful if you posted the essence of what you are trying to achieve.
Note that you don't *need* to use DIRMc with Backup: you can use it for
"steering" purposes, but otherwise directories are bound to the management
class with the longest retention period. Note also that you have a mix
of Windows and Unix clients, wherein only the Windows directory info will
typically end up in a storage pool: as the redbook says, "On UNIX clients,
the directory entries are stored directly in the IBM Tivoli Storage Manager
server database" (unless ACLs are involved). With Unix directory info,
the DIRMc effects retention choice, but stgpool choice is not a factor.
I have notes on this stuff in http://people.bu.edu/rbs/ADSM.QuickFacts ,
as an adjunct to the primary IBM reference material.