Hi enlightened list members,
I have a number of policy changes to make, including the implementation of an client optionset containing a 'DIRMC' to redirect directories globally to a disk storage pool with lowered retention. The problem I have is the database appeared to grow more quickly than anticipated and I've finally clicked that TSM has made an unfortunate choice for DIRMC, where it has selected a management class set up for a TDP with 60day archives... Whoever set it up made the (otherwise unused) backup copygroup nolimit for all parameters. As you could imagine, we now have likely a billion versions of a billion directories across the enterprise. If I make the changes I think need to happen, how can I 'preview' the expiration process to make certain there are no surprises?? Also, whats a good policy for directory retention? I've taken a stab in the dark, and kept only a very few versions, with verdel=1 and retonly=7 years (which is pretty much the standard for data being too old to be useful to anyone but a lawyer) Dave
