>What I would like to do is, for a given set of sensitive file systems, keep
>the last Level 0, level 1 etc.. on the holding disk ...
>Is it the case of RTFM, or does Amanda not support this type of arrangement?
It does not support this, although it's probably a good idea. I've added
it to the TODO list.
In addition to the ideas Jason had, the following patch goes into
the code where the holding disk files are normally unlinked (removed)
and links them into a hard coded different directory (in the same file
system) first. Only the last chunks of any given backup level are kept.
It's a definite hack, but might do what you want.
You will want to change the directory name and maybe look at the file
being linked to only pick ones you're interested in. Adjust as needed :-).
I did some minimal testing, but handle with care.
You should also think about how you'll actually use this with restores.
Amrestore (and amrecover, for that matter) know how to look in a holding
disk for images, but the "save area" won't look right because it is
not listed as a holding disk and does not have the proper datestamp in
the name.
I think enough symlinks would make this work :-), or even some tricks
like defining this as a real holding disk with "use" set to zero and
changing the patch to create the datestamp directory (or symlink)
in the right place in the save area. You could extend the patch to
take care of some of that for you or handle it after the amdump run.
Depends on how much work you want to put into it now vs. just dealing
with it when it's time to actually do a restore.
>Srdjan Nikolic
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
save-holding.diff
