Hello,

instead of excluding files (not supported by archive), you can include them
to a special management class that does not exist. You will then get an
error message and the files will not be archived. Not elegant, but...

We do not use this bypass, but regurlarly make manual deletes in the archive
packages (for big Essbase files).

Regards,

Rene Lambelet
Nestec SA - 55, Av. Nestle - CH-1800 Vevey
Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
E-Mail: rene.lambelet AT nestle DOT com



> -----Original Message-----
> From: ROBERT OTT [SMTP:Robert.Ott AT TLC.STATE.TX DOT US]
> Sent: Thursday, April 15, 1999 1:53 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Archiving vs. Backup
>
> ADSM'ers,
>
> Currently our shop is using backups for all of our clients.  It is now
> time to implement archiving for some of these boxes.  We will want to
> exclude some of the files that are currently backed from the archival
> process.  I don't have the option of allowing users to initiate archives
> or to explicitly include files or extensions of files to be archived.
>
> My problem:  How do I filter out the files I don't want archived?
> Separate dsm.opt?  Another nodename?
>
> Any suggestions and or solutions would be greatly appreciated.
>
> Thanks,
>
> Robert