I'll echo what Richard said and amplify it: TSM requires planning. As it is about 1000000000000000 more powerful and flexible than anything else you might work with, you must think about what your business requirements are before implementing it. Then do the right thing. The next coolest thing about the product is the fact that if you don't do the right thing, with a little thought you can change it! Usually no harm no foul.
Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Wednesday, November 25, 2009 7:38 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Copy Tape pool for a selected set of tapes This is a plan-ahead issue. Nodes which need special handling like that need to be assigned their own storage pool, where your site should have distinct management classes for data having differing requirements. You can define such a storage pool, create a management class & copy group pointing to it, and define a management class for the node to use henceforth. The MOVe NODEdata command can be employed to shift existing data to that separate storage pool, whereafter the desired Backup Stgpool operation can be performed. If the data is static (no new incoming files), another approach could be to define a new stgpool at the bottom of the current storage pool hierarchy, with no migration into it, then MOVe NODEdata into that pool, and do a Backup Stgpool on it. This would avoid the need for a new management class (though you should still pursue that). Richard Sims
