Re: Previewing Expiration
Also, if you start the GUI and click RESTORE, browse to the files you are interested in, on the FAR RIGHT of the window you will see the management class they backed up to, if you want to check the result of your DIRMC implementation. 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 Alexander Lazarevich Sent: Saturday, September 03, 2005 1:42 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Previewing Expiration On Sat, 3 Sep 2005, David le Blanc wrote: > 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?? Only way I know how to do that is run dsm GUI from the client that has the modified include-exclude (or dsm.opt) file, then proceed to run a manual backup, and see what is red-x'ed out and what isn't, make sure it matches what you think it should do. You don't actually have to run a manual backup to do this though. Alex
Re: Previewing Expiration
On Sat, 3 Sep 2005, David le Blanc wrote: 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?? Only way I know how to do that is run dsm GUI from the client that has the modified include-exclude (or dsm.opt) file, then proceed to run a manual backup, and see what is red-x'ed out and what isn't, make sure it matches what you think it should do. You don't actually have to run a manual backup to do this though. Alex
Re: Previewing Expiration
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David le Blanc >If I make the changes I think need to happen, how can I 'preview' the >expiration process to make certain there are no surprises?? There is no 'preview' for expiration. What kind of surprise are you expecting? >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) You don't even really need that. I usually set up something like vere=1 verd=1 retaine=30 retaino=90 (or however long the longest file retention is for that domain) -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627
