Author: Debbie Bassler <Deborah_Bassler AT PAPAJOHNS DOT COM>
Date: Wed, 8 Jun 2005 15:55:58 -0400
A couple of weeks ago I was given the opportunity to take on the TSM admin role :-) I was wondering if anyone reclaims copy storage pools. Currently, we execute a schedule to reclaim space from our c
Author: Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Date: Wed, 8 Jun 2005 16:13:55 -0400
DEFINITION OF BACKUP RULES: VEREXISTS: # of versions to keep while file exists (adjusted by RETEXTRA) VERDELETED: # of versions to keep on TSM when file is deleted from client RETEXTRA: # of DAYS to
Author: Debbie Bassler <Deborah_Bassler AT PAPAJOHNS DOT COM>
Date: Wed, 8 Jun 2005 16:15:45 -0400
Thanks to all....I had a brain block...I was thinking our copy storage pool was collocated, as are our primary pools,,,,,,boy, it's hard to get back in the saddle (and stay on),,,, :-) Lawrence Clark
I suspect when you say "that doesn't work" you mean that setting recl=100 doesn't kill any ongoing reclamation process (but that it does set the reclamation threshhold back to 100%)? If so, then that
Author: "Warren, Matthew (Retail)" <Matthew.Warren AT POWERGEN.CO DOT UK>
Date: Thu, 9 Jun 2005 12:43:35 +0100
Hmm, Are the explanation of the retention parms here correct? I thought it went like so; VEREXISTS: max number of versions to keep for a file that exists on the client VERDELETED: max number of versi