> My question is about using gnu tar. since tar will be called with the
> --listed-incremental option and the filename does not include the
> configuration I am wondering if there would be an interference of the
> monthly full backups with the daily incremental.
You're right, that looks like a potential problem. But the "real"
fix will not be trivial because clients are not (currently) told what
configuration they are being run for. Also, changing the file name
will introduce a backward incompatibility problem that would have to be
dealt with. I've take a note to investigate this further.
As long as your archive and normal runs do not happen at the same time
(which would be difficult unless you've played with the Amanda port
usage model), there won't be a problem. The listed incremental file is a
temp file until after the run at which point it is renamed to the "real"
name if "record yes" is set. Your archive runs will use the same temp
name as the daily runs, but the file will be thrown away.
One possible workaround (some would say "hack" :-) if the runs might
happen at the same time would be to add a trailing "/." to all the disk
names in your disklist. For instance, if your daily run backs up "/home"
have the archive run do "/home/.". That will do effectively the same
thing but the file names will be different.
I think.
> Alberto
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
