The files previously backed-up stay pinned in *SM. "Forever" is a long
time though. How long they are maintained in *SM will depend on the
effective policy(ies) for each files (ie. review your versions data exists,
versions data deleted, and retain extra versions parameters). Up to two
backup versions of the excluded files will remain kept in *SM's storage:
The most recent backup version is retained as long as the original file
exists on the client file system. By default, and when a file is no longer
associated to a policy, all other versions are retained for up to 30 days
after they become inactive (30 days = backup retention default grace period
- Make that 365 days for the default archive grace period).
I have doubts about what Steven suggests as to whether it would actually
work.... I never tried. I would be curious to know if it does work. Do
let us know how you fared on this one. If I may suggest, I would think you
would have better luck if you renamed the directory, excluded the renamed
directory, ran an incremental (which would make believe to *SM the files
were removed, initiating an expiration of the files previously backed-up),
then return your directory to the desired name, and making sure your
excludes are set to your desired directory structure. The expired files
will disappear from *SM's DB when the grace period has elapsed (see "q
domain f=d" for the backup retention grace period applicable to your
environment)
Hope this helps.
Serge Gaudet, CMI
Consultant
Steven P Roder
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
FFALO.EDU> cc:
Sent by: "ADSM: Dist Subject: Re: exclude.dir question
Stor Manager"
<[EMAIL PROTECTED]>
16/10/2000 05:14 PM
Please respond to
"ADSM: Dist Stor
Manager"
> 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?
Well, if they are not expired the first backup after adding the
exclude.dir, then they will stay in the DB. A way around this would be to
first exclude them via "exclude /pathto/.../*", and running a backup to
expire the files. Then, convert that to exclude.dir.
The above is the empiracl method. My guess is that they will stay
pinned, as exclude.dir says to not look any further in the tree...
Let us know how it turns out.
Steve Roder, University at Buffalo
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
ADSM Administrator
([EMAIL PROTECTED] | (716)645-3564 |
http://ubvm.cc.buffalo.edu/~tkssteve)
