As mentioned before, you can force the active files off by performance
reclamation on the volumes.  That being said, the smaller the volumes are,
the less reclamation you have to do, but the larger they are, the less
volume management the TSM DB has to do.
A few years ago, we had 2GB file volumes and the TSM DB response was
pretty horrible.  After we moved to larger/fewer file volumes TSM
magically started to return queries in a reasonable amount of time and
everything was just generally faster.

It's a balance you need to find that best fits your TSM DB performance and
all the hardware supporting it.

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
warbogas AT INDIANA DOT EDU

Sent by: ADSM-L AT VM.MARIST DOT EDU
03/10/2011 04:43 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] Does Move Data recover space on virtual volumes?






Shawn,
Your mention of the 50 GB MAXCAP on the device class was a jolt. Ours is 1
TB, and I see that could be exacerbating the problem. The bigger virtual
volumes are, the more space they lock and the greater chance they contain
active files, which results in longer lifespans for them.

What rule of thumb works best to set MAXCAPACITY?

Thank you,
Keith



This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.