Enabling Collocation is very simple, you'll just have to be careful how you do it if you have limited tapes. If you are short I'd implement group collocation, put all the nodes in the 1st group. Then gradually move a node at a time out into different groups (along with move nodedata commands)
As for you current retention policies, can you do a "query copygroup f=d" and paste the ones you would like advice on? Steven ego3456 <tsm-fo...@backupcentral.com> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 10/08/2010 18:08 Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] NBU guy in TSM shop and I need help Caterpillar: Confidential Green Retain Until: 09/09/2010 wow, so it really is as clear as mud.. :D my assumption of the retention taking that many tapes was understood by me to be a function of not only the shelf life (retention) but the reclamation (no we don't use collocation, which I'm well aware we should) shotgunning those data bits across a large number of tapes; if all this is true, without a large increase in tape library capacity (we have 252 slots) or a large increase in disk resources, is there an easy way to fix it? If not, I'm inclined to scrap it all and put in NBU for backups going forward. saving the argument on which is better, I'm an NBU guy and a staff of one, and my inclination is if I'm spending buckets of cash, I'm doing it in a way I'm familiar. My first whack though is to try and save this thing so I'm hoping someone out there can provide a panacea or at least an incremental improvement that is free and time efficient. am i spitting in to the wind? +---------------------------------------------------------------------- |This was sent by ericgosn...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +----------------------------------------------------------------------