Re: Keeping files in diskpools
Not sure if this what you can use.. in TSM for stgpool there is an option called Migration Delay. Basically it allow you to control how long the data to remain in the storage pool before data migrates. I am thinking this could save you some time during "meltdown." It's in the Admin manual Chapter 9. Managing Storage Pools and Volumes if you would like to look up. Migration Delay (primary storage pools only) The minimum number of days that a file must remain in a storage pool before the server can migrate the file to the next storage pool. For a disk storage pool, the days are counted from the time that the file was stored in the storage pool or last retrieved by a client. For a sequential access storage pool, the days are counted from the time that the file was stored in the storage pool. Thanks, Sung Y. Lee "ADSM: Dist Stor Manager" wrote on 06/08/2005 06:59:03 PM: > 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. > [EMAIL PROTECTED]
Re: Keeping files in diskpools
Wanda Prather said... > 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. That's a possible but unlikely strategy, unless I can arrange to get that data to tape in an alternate fashion for offsite storage. > 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. Seems like segregating the storage pools by client is a good thing to do regardless. > You can split the clients up by putting them in different > domains, or by > using management classes. Something to learn - I'll peruse the docs for that. I don't believe that we're doing anything like that at the moment. > 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%. This does sound promising - more docs to read! > Hope some of that is what you are looking for... Definitely > Wanda Prather > "I/O, I/O, It's all about I/O" -(me) Thanks very much for taking the time. I'm sure I'll have more questions later Kurt
Re: Keeping files in diskpools
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:[EMAIL PROTECTED] On Behalf Of Kurt Buff Sent: Wednesday, June 08, 2005 6:59 PM To: ADSM-L@VM.MARIST.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. [EMAIL PROTECTED]
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. [EMAIL PROTECTED]
