Andrew BOGECHO wrote:
>
> My main worry is that small change done to one small file, hence a
> very tiny level 1, that gets dumped, written to tape, and removed from
> the holding disk, before it ever shows up in the amdump log.
Why don't you keep it simple? Here's what I do here and it works
perfectly: I just don't put any tape in the drive. The backup images go
thus all to the holding disk. In my backup script, immediately after the
"amdump ..." command, I have a "cp -av ..." ;-). So after AMANDA is
finished, the backup images are copied from the holding disk to my MO
disk, which is patiently waiting there. Next day I check if everything
went well and I do an "amflush ...". I thus get AMANDA backups on
removable MO disks with the added feature of tape copies ;-) (you see,
it all depends on how you see the world).
In place of my MO disks, you would use a large part of your hard disks,
large enough to accomodate 7 days's worth of data. Your holding disk
should be separate from this and also large enough to hold one day's
backup images. Try it, "It works with AMANDA (TM)" :-)
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
