Etienne,

If you spread your volumes over multiple disks like I do, you might want
to define private FILE volumes for the disk pool (that is, zero scratch
volumes).  That gives me full control over where the volume files are
located.   Otherwise TSM will allocate all volumes from the first drive in
the set until that drive fills up.

In addition, you have to think of the number of simultaneous mounts.  In
my case, twelve mounts is adequate to support a total of about 120 nodes
during the entire backup window.  At this writing, six of those volumes
are in "filling" status so I assume there have never been more than six
mounted at any one point.

Otherwise, no special consideration.  It just works.

Tab






Etienne Brodeur <ebrodeur AT SERTI DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/05/2002 09:15 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Reclaiming LTO Tapes


Hi Tab,

        What are the impact o fusing a FILE rather than a DISK devclass
other than faster reclamation of copypool?

Thanks for the info.

Etienne





Jack,

It's been mentioned before, but if you use a disk pool for directories,
you should make the disk pool a FILE devclass.

When my directory disk pool was DISK devclass, copypool reclamation would
launch and eight hours later I would have reclaimed a few tens of MBs.

I rebuilt the directory disk pool as FILE devclass, and copy pool
reclamation proceeds at full speed from the start.

Tab Trepagnier
TSM Administrator
Laitram Corporation






"Coats, Jack" <Jack.Coats AT BANKSTERLING DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/03/2002 03:35 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Reclaiming LTO Tapes


I cannot find out how to speed me up either!  Mine is slower than sin,
on reclaiming my offsite copypools especially.