Amanda-specific information: Difference between revisions

From wiki.zmanda.com
Jump to navigation Jump to search
(Added information about temporary index files)
 
(Added debug files that get deleted on the clients during backups.)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
During the backup process Amanda will create some temporary files. These files can cause ''strange'' results:
= Preventable ''strange'' results =
 
During the backup process Amanda will create some temporary files. These files can cause ''strange'' results on the Amanda server:
<pre>? gtar: ./etc/amanda/DailySet1/index/hostname/_/20101206010001_0.gz.tmp: Warning: Cannot stat: No such file or directory</pre>
<pre>? gtar: ./etc/amanda/DailySet1/index/hostname/_/20101206010001_0.gz.tmp: Warning: Cannot stat: No such file or directory</pre>
And if an Amanda client has multiple DLEs on different spindles this can appear in the results:
<pre>? gtar: ./var/lib/amanda/gnutar-lists/hostname_path_0.new: Warning: Cannot stat: No such file or directory</pre>
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:
<pre>/etc/amanda/DailySet1/index/*.gz.tmp</pre>
On Amanda clients these files can be excluded:
<pre>/var/lib/amanda/gnutar-lists/*.new</pre>
If your Amanda server is also a client combine the two lists:
<pre>/etc/amanda/DailySet1/index/*.gz.tmp
/var/lib/amanda/gnutar-lists/*.new</pre>
= Other ''strange'' results =
You can also see the following files in the results:
<pre>? gtar: ./var/log/amanda/server/DailySet1/chunker.20101211010541.debug: Warning: Cannot stat: No such file or directory
? gtar: ./var/log/amanda/amandad/amandad.20101227010453.debug: Warning: Cannot stat: No such file or directory
? gtar: ./var/log/amanda/client/DailySet1/runtar.20101227010453.debug: Warning: Cannot stat: No such file or directory
? gtar: ./var/log/amanda/client/DailySet1/sendbackup.20101227010453.debug: Warning: Cannot stat: No such file or directory</pre>


Backing up these temporary files is not useful, so you can add them to the exclude list: /etc/amanda/DailySet1/index/*.gz.tmp
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 [http://wiki.zmanda.com/man/amgtar.8.html amgtar].

Latest revision as of 08:49, 31 December 2010

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
? gtar: ./var/log/amanda/amandad/amandad.20101227010453.debug: Warning: Cannot stat: No such file or directory
? gtar: ./var/log/amanda/client/DailySet1/runtar.20101227010453.debug: Warning: Cannot stat: No such file or directory
? gtar: ./var/log/amanda/client/DailySet1/sendbackup.20101227010453.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.