When a management class has no archive copygroup and there's no archive
copygroup defined as a default, then you can't do an archive using this
management class.
So set this management class for a group of files in the dsm.opt of the
client and no archives are created unless another management class is
specified in the archive command.

Attention: When you delete an archive copygroup and do not have a
default archive copygroup, then the grace periods of the policy set are
used after the rebinding. Make sure the values there are large enough...

Regards,
 Michael
--
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

>----------
>Von:   dan thompson[SMTP:thompsod AT USAA DOT COM]
>Gesendet:      Mittwoch, 25. Juni 1997 13:27
>An:    ADSM-L AT VM.MARIST DOT EDU
>Betreff:       Re: Deleting files from backups.
>
(...)
>  Does anyone know if it is possible to define a copygroup or devclass that
>will prevent a
>  file from being stored at all?  (This seems like a perverse ability, but
>it may come in   handy)
>