ADSM-L

Re: Expiration/inactive node

2005-02-20 02:25:10
Subject: Re: Expiration/inactive node
From: "Lambelet,Rene,VEVEY,GLOBE Center CSC" <Rene.Lambelet AT NESTLE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 20 Feb 2005 08:24:24 +0100
Hi,

you could also export this node to tape, and use relative timing if import 
needed for the audit

                René LAMBELET
                NESTEC  SA
                GLOBE - Global Business Excellence
                GC-Central Support Center
                SD-IT
                Av. Nestlé 55  CH-1800 Vevey (Switzerland) 
                tél +41 (0)21 924'35'43  fax +41 (0)21 703'30'17  local BUS-10 
119
                mailto:rene.lambelet AT nestle DOT com

>       This e-mail message is confidential and for the use of the intended 
> recipient(s) only. 
>       Unauthorized use or treatment of all or part of this message is 
> strictly prohibited. 
>       Unintended recipients: please notify the sender and delete the original 
> message, 
>       any attachments and any copies from your computer and back-up system 
> immediately. 
>       Thank you.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Bob Booth - CITES
Sent: Saturday,19. February 2005 19:38
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Expiration/inactive node


On Sat, Feb 19, 2005 at 10:26:33AM -0800, Sam Sheppard wrote:
> Due to a legal investigation, I have been asked to 'freeze' the backups
> on one of my client machines.  We removed the client from the schedule
> and changed the NODENAME parm in the dsm.opt file to specify a new
> name.
>
> My question regards expiration processing for the 'frozen' node.  My
> understanding is that, as long as the client doesn't connect to the TSM
> server, no expiration will take place.  Is this indeed the case or is
> there still some expiration of files on this system that will take
> place during expire inventory processing?  Will a subsequent backup be
> the only way to trigger expiration?

Expiration will still 'delete' inactive items based on the policy domain
mgmtclass (copy group) settings.  If you truly need to freeze all activity
for this node, including not removing files/directories that have been
marked inactive, you may have to create a new domain with unlimited
retention for all copies inactive.

It is true however, that if another backup isn't performed, the files that
are now marked as active, will stay that way, until the administrator
deletes them with a delete filespace command.

hth,

bob

<Prev in Thread] Current Thread [Next in Thread>