Amanda-specific information
Preventable strange results
During the backup process Amanda will create some temporary files. These files can cause strange results on the Amanda server:
? gtar: ./etc/amanda/DailySet1/index/hostname/_/20101206010001_0.gz.tmp: Warning: Cannot stat: No such file or directory
And if an Amanda client has multiple DLEs on different spindles this can appear in the results:
? gtar: ./var/lib/amanda/gnutar-lists/hostname_path_0.new: Warning: Cannot stat: No such file or directory
Backing up these temporary files is not useful, so you can add them to the exclude list. This is the exclude list for Amanda servers:
/etc/amanda/DailySet1/index/*.gz.tmp
On Amanda clients these files can be excluded:
/var/lib/amanda/gnutar-lists/*.new
If your Amanda server is also a client combine the two lists:
/etc/amanda/DailySet1/index/*.gz.tmp /var/lib/amanda/gnutar-lists/*.new
Other strange results
You can also see the following files in the results:
? gtar: ./var/log/amanda/server/DailySet1/chunker.20101211010541.debug: Warning: Cannot stat: No such file or directory
This happens because Amanda is deleting old files after a couple of days. The files are useful during troubleshooting so cannot be added to the exclude list. As of Amanda 2.6.1 you can ignore these results by using amgtar.