ok, thanks...

it makes sens to me now..

I have some work to do to change it all !

Mike

>
____________________________________________________________________________
_______
> Michael REGELIN
> Ingénieur Informatique - O.S.O.
> Groupware & Messagerie
> Centre des Technologies de l'Information (CTI)
> Route des Acacias 82
> CP149 - 1211 Genève 8
> Tél. + 41 22 3274322  -  Fax + 41 22 3275499
> Mailto:michael.regelin AT etat.ge DOT ch 
> http://intraCTI.etat-ge.ch/services_complementaires/messagerie.html
> __________________________________________________________
> 


-----Message d'origine-----
De : Don France (TSMnews) [mailto:DFrance-TSM AT ATT DOT NET]
De : Don France (TSMnews) [mailto:DFrance-TSM AT ATT DOT NET]
Envoyé : vendredi, 3. mai 2002 23:22
À : ADSM-L AT VM.MARIST DOT EDU
Objet : Re: Help Understanding Mgmt classes


Michael,

The rules I described apply universally to backup objects with the same name
owned by a given node in backup storage.

With TDP products, in some cases, the backup objects are given different,
unique names every time a backup occurs -- you must review the Install &
User's Guide for the TDP you are using.  For example, TDP v1 for Exchange
creates unique names for every backup, so retention/expiration must be done
manually;  in v2 of this TDP, objects stored in backup storage are given the
same name, so their retention/expiration becomes "automated" like for files
backed up by the b/a-client -- and the management class rules, as I
described, will apply.

Hope this helps.