Hi > -----Original Message----- > From: [email protected] ... > > > No, I do not think it is having a problem. Notice your files > are named XYZ".gz.tmp". The ".tmp" indicates it is a > temporary file, possibly existing for only a short time. In > this case, when the index is completed, the file is renamed > without the ".tmp". > > The message you are receiving arises because of the way tar works. > A list of files to be backed up is generated and then the > backup is done. On an active directory tree, it is not > uncommon for changes to occur between generating the list and > actually backing up the specific files in the list. > Certainly, the Amanda directory tree is "active" during an > amdump run!! So such messages should be expected. Another > "strange dump" message you may see is "file changed as we > backed it up".
The message is quite disconcerting though.
Based on your analysis I intoduced a new dumptype which should exclude the
temporary index files to be backed up.
define dumptype root-tar-no-index-temp {
root-tar
program "GNUTAR"
comment "root partitions dumped with tar excluding temp files"
exclude "./etc/amanda/DailySet1/index/*/*/*.tmp"
}
I am using this dumptype now for the amanda server root partition which
holds /etc/amanda, we'll see.
Thanks
Erich
smime.p7s
Description: S/MIME cryptographic signature
