Hi,
and the inactive ones will be handeled by the verexists, verdeleted,
retextra and retonly parameters, correct?
regards
michael
-----Urspr�ngliche Nachricht-----
Von: Richard Sims [mailto:[EMAIL PROTECTED]]
Gesendet am: Dienstag, 17. Oktober 2000 15:56
An: [EMAIL PROTECTED]
Betreff: Re: exclude.dir question
> I'm resending this in the hopes someone has a quick answer....
>
> If I backup all the files on a client, and then later decide to implement
> an exclude.dir, what happens to the files that were previously backed up?
> Do they get purged or do they stay forever pinned in ADSM?
Bob - Doing an EXCLUDE or EXCLUDE.FILE or EXCLUDE.DIR has the same effect as
having deleted the specified objects from the client: they will be
expired the next time a backup is performed using those specifications.
As documented in the B/A client manual (Unix), Exclude option note:
1. If you change your include-exclude list so that a previously included
file
is now excluded, any pre-existing backup versions of that file become
inactive the next time an incremental backup is run.
One might extrapolate and think that EXCLUDE.FS would cause the whole
filespace to expire; but in fact it merely causes bakup of the file system
to
be skipped, as though it were not specified on the command line or the
Domain
spec.
The B/A manual could be more clear as to the effects. I'll contact the
documentation people about this.
Richard Sims, BU
