Dale,

I added DIRMC = some_disk_space to my existing TSM 4.1 system which had
over time migrated from ADSM 2.

The only wrinkle I hit was during copypool reclamation.  At first I was
using DISK volumes for the directory pool.  Copypool reclamation would sort
of dribble directories off of that pool for hours before ever loading a
source tape for files.  I found an old post in the archives that said that
objects stored on random-access volumes are not aggregated, so there is a
LOT of DB overhead processing those directory objects.  That message went
on to recommend FILE volumes for storing directory objects.

I made that change to my system and restore performance is at least as
good, but copypool reclamation now runs as it should without the hours-long
waits pulling 20 MB of directories off the disk volumes.

Hope this helps.

Tab Trepagnier
TSM Administrator
Laitram Corporation







"Jolliff, Dale" <xjolliff AT TI DOT COM>@VM.MARIST.EDU> on 04/11/2002 08:10:48 
AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Monthly Backups, ...DIRMC


Providing that moving to the use of DIRMC doesn't cause more problems than
it solves,
does anyone have a procedure checklist for creating and implementing DIRMC
on an existing TSM server?

Is there enough of a benefit to warrant altering an existing configuration?