SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
STRANGE: AMANDA MAIL REPORT FOR November 11, 2010
Author Message
Post STRANGE: AMANDA MAIL REPORT FOR November 11, 2010 
Hi

I am getting STRANGE reports about every other day from amanda 3.1.3


STRANGE DUMP DETAILS:
/-- amanda.ruf.ch / lev 1 STRANGE
sendbackup: start [amanda.ruf.ch:/ level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
sendbackup: info end
? /bin/tar: ./etc/amanda/DailySet1/index/srvx-lx01-afa.ruf.group/_usr/20101111010001_1.gz.tmp: Warning: Cannot stat: No such file or directory
| Total bytes written: 2754560 (2.7MiB, 3.4MiB/s)
sendbackup: size 2690
sendbackup: end
--------
STRANGE DUMP DETAILS:
/-- amanda.ruf.ch / lev 1 STRANGE
sendbackup: start [amanda.ruf.ch:/ level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
sendbackup: info end
? /bin/tar: ./etc/amanda/DailySet1/index/srvx-lx01-afa.ruf.group/_usr/20101110010001_1.gz.tmp: Warning: Cannot stat: No such file or directory
| Total bytes written: 2560000 (2.5MiB, 3.1MiB/s)
sendbackup: size 2500
sendbackup: end
--------
STRANGE DUMP DETAILS:
/-- amanda.ruf.ch / lev 0 STRANGE
sendbackup: start [amanda.ruf.ch:/ level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
sendbackup: info end
? /bin/tar: ./etc/amanda/DailySet1/index/subversion.ruf.ch/_data/20101105010003_1.gz.tmp: Warning: Cannot stat: No such file or directory
| Total bytes written: 152627200 (146MiB, 3.9MiB/s)
sendbackup: size 149050
sendbackup: end
--------
It looks like it has a problem with compressing the index. Any ideas?
Thanks
Erich Titl

Post STRANGE: AMANDA MAIL REPORT FOR November 11, 2010 
On Thu, Nov 11, 2010 at 08:28:44AM +0100, Titl Erich wrote:
Hi

I am getting STRANGE reports about every other day from amanda 3.1.3

STRANGE DUMP DETAILS:

/-- amanda.ruf.ch / lev 1 STRANGE

sendbackup: start [amanda.ruf.ch:/ level 1]

sendbackup: info BACKUP=/bin/tar

sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...

sendbackup: info end

? /bin/tar:
./etc/amanda/DailySet1/index/srvx-lx01-afa.ruf.group/_usr/20101111010001_1.g
z.tmp: Warning: Cannot stat: No such file or directory

| Total bytes written: 2754560 (2.7MiB, 3.4MiB/s)

sendbackup: size 2690

sendbackup: end

\--------
[ snip ]

It looks like it has a problem with compressing the index. Any ideas?


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".

jl
--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)

Post STRANGE: AMANDA MAIL REPORT FOR November 11, 2010 
Hi

-----Original Message-----
From: owner-amanda-users < at > amanda.org
...


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

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB