Well, the straightforward TSM way to keep files in a diskpool, is to
remove the NEXTSTGPOOL value from the definition of the storage pool (so
that the files have no place to migrate to), or set the HIGHMIG stgpool
pool property to 100%, so that migration will never start.
The most practical way to do that, is to split your storage pools so
that the client data you want to stay to disk all goes to one disk pool,
and the other clients go to another pool that DOES migrate.
You can split the clients up by putting them in different domains, or by
using management classes.
If you don't want to do that, but you want to know when your disk pool
is getting full, you can use TSM Operational Reporter.
You can add a line to the custom summary to tell you the disk pool
utilization, based on a select statement:
select pct_utilized from stgpools where stgpool_name='BACKUPDISK'
And you can set a threshold for that value so that TOR runs every nn
minutes, and sends you an email if pct_utilized is greater than, say,
90%.
Hope some of that is what you are looking for...
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kurt Buff
Sent: Wednesday, June 08, 2005 6:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Keeping files in diskpools
All,
First time poster, fairly new to the whole thing, so help much
appreciated.
We've got a TSM server on which we've just upgraded the disk array, from
1TB
to 2TB. It also has a Spectralogic Treefrog unit with two AIT2 drives
and a
15-slot robot.
We're looking to keep the current generation of files from our main file
server in the diskpools, so that we (in the event of a meltdown of the
fileserver) won't have to resort to tape. The amount of storage on the
file
server is roughly 1TB - the other servers are only a small fraction of
that.
We've kept the old diskpools, and created new ones to catch new data.
The file server currently has its storage divided into two partitions.
I'm
reconfiguring the array on the file server to add space, and I'm going
to
switch to a single large partition, and change the drive letter so that
the
TSM server will pick up all of the files on the reconfigured array as
new.
(I've got a copy of the data on a test machine, done with robocopy, to
retain all of the ACL information, and will be copying the data back
after
the production file server is reconfigured.)
Is there some way 1) to fix those files in their diskpools, or 2) get
notification if they start to migrate to tape and/or 3) get notification
if
space in the diskpools is such that files from the file server are
likely to
migrate to tape?
The version for TSM shown at the CLI interface is "Version 5, Release 1,
Level 5.0".
Thanks,
Kurt Buff
Sr. Network Administrator
Zetron, Inc.
kbuff AT zetron DOT com
|
