ADSM-L

Re: expiration

2002-07-14 13:49:51
Subject: Re: expiration
From: Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Date: Sun, 14 Jul 2002 15:02:13 +0300
if you set copygroup to "very large" values (i.e. all 9's) TSM will count
the versions on every expiration. Better set to nolimit to improve
expiration performance. If we are talking about only one node it might not
be significant. But if someone adds more nodes to that domain or the node
has many-many files ...

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: expiration

Geoff,

Inactive version will be expired from the server according to the
RETEXTRA and RETONLY parameters.  Eventually, only the
active set will remain.

If you want to keep all the inactive versions, you can copy the domain
to a new domain, update the copygroups to have all 9's, activate
the policy set, and then update the node to be in the new domain.

Hope this helps,

Bill
At 12:23 PM 7/11/2002, you wrote:
>The situation is we have a node that is going to have it's daily backups
to
>TSM stopped. They don't want to delete the filespaces at this time. The
>question is, do all the versions remain available since nothing has
>triggered the system to think files were deleted? Or will older version
roll
>off at some point and leave only the latest version of very file on the
>server. Remember the server has only been removed from a daily backup
>schedule.
>
>Thanks for the help.
>
>Geoff Gill
>TSM Administrator
>NT Systems Support Engineer
>SAIC
>E-Mail:    <mailto:gillg AT saic DOT com> gillg AT saic DOT com
>Phone:  (858) 826-4062
>Pager:   (877) 905-7154

----------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge Ma.
<Prev in Thread] Current Thread [Next in Thread>