I agree, the best solution, if you can, is to just leave the existing data where it is.
The other solutions are messy. The problem with MOVE DATA is that you can't do it by client, but by volume. (Now if you are lucky enough to have your tapes set up so you know there is ONLY data for that client on a volume, then by all means MOVE DATA.) The only other way to do it is to EXPORT the client, delete it from TSM, then IMPORT it again. ************************************************************************ Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert ************************************************************************ -----Original Message----- From: J Bamford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 05, 2001 4:11 AM To: [EMAIL PROTECTED] Subject: Re: Changing Management Class in mid-stream Kevin Although the files will be re-bound to the new mgmt class they will not be moved from their current position. All new data stored will of course go to the new destination. You could simply leave the data that is in the wrong pool where it is. Over time it will expire naturally. Another approach for the future you could consider. If you have chosen to use a different stg pool (and policy maybe) for each customer, why not also create a separate TSM domain for each customer. That way each domain has its own default mgmt classes and stg pools. When you define a new client node to TSM you place that customers machine in the appropriate domain and the defaults are handled for you. This means you don't have to do anything at the client node end. Jason Bamford Tivoli EMEA ----- Original Message ----- From: "Kevin Sawyer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 05, 2001 4:24 AM Subject: Changing Management Class in mid-stream > Hello folks. > > I'm new to the list, but I'm sure I'll become a regular. I will try to help > whenever I can, and as I'm running the first Canadian IBM (TSM based) > Storage Service Provider (SSP) I should have some interesting and unique > challenges, as well as some ordinary ones. > > My first problem is ordinary. I accidentally backed up a customer to the > default management class, when he should have been backed up to a different > one. I've since made the change in the client dsm.opt file (this is on > windows) but I'm wondering at my output when I run "q occ". If I have a > separate storage pool for each management class, will I have to use the > "move data" command to get everything where it should be, or will data be > re-bound and moved automatically? Any information would be helpful. > > Regards, > > Kevin Sawyer > Chief Technical Officer > Storagepipe Solutions Inc. > 416.802.2527 > [EMAIL PROTECTED] --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.303 / Virus Database: 164 - Release Date: 26/11/2001
