This still puzzles me then,,,,, how can I get that scenerio to play?  The
situation is that we want a limited set of files/directories to be
incrementally backed-up during the week,,,, but those same files and
several other large directories (these are to large to be backedup during
the week to meet the processing window, thus the decision to NOT do them
during the week).

BTW Andy, this particular server is HARTCT1-APP. You may remember their
processing requirements.

----------
> From: Andy Raibeck <araibeck AT VNET.IBM DOT COM>
> From: Andy Raibeck <araibeck AT VNET.IBM DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Different includes/excludes
> Date: Tuesday, February 18, 1997 3:11 PM
>
> Dave Sanders asks:
>
> > A client would like to have a seperate include/exclude list during the
week
> > vs. during the weekend.  I know there have been discussions about this
in
> > the past,,, but could someone refresh the topic??
>
> Some issues/problems you can run into:
>
> - Backup versions of files that were included but are subsequently
excluded
>   will be expired the next time incremental backup runs. In other words,
the
>   exclusion is for all backup versions, not just for any that might have
been
>   created while using that version of the include/exclude list.
>
> - If you change the management class on an INCLUDE statement, all
existing
>   backup versions of files affected by that INCLUDE will be re-bound to
that
>   management class (i.e. you can't have Monday - Friday's backups bound
to
>   one management class, and Saturday's backup bound to another -- all
backup
>   versions of the same file must be bound to the same management class).
>
> In general, I wouldn't recommend flip-flopping include/exclude lists
around,
> although I don't have the specifics of your particular situation.
>
> Andy Raibeck
> ADSM Level 2 Support