Hi,
OS: Solaris8,
Hardware: Sunfire V120
amanda backup is failing regularly.
Following is the report generated.
These dumps were to tape ARCH_DE2_003.
*** A TAPE ERROR OCCURRED: [[writing file: Bad file
number]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to
Sal Sharief wrote:
FAILURE AND STRANGE DUMP SUMMARY:
jafar2 /home/host lev 0 FAILED [out of tape]
It says out of tape, but a tape error is more likely.
...
Tape Size (GB)... 4.71
Tape Used (%) 9.65
Filesystems Taped 6
Am I correct that your tapesize is
--- Paul Bijnens [EMAIL PROTECTED] wrote:
Sal Sharief wrote:
FAILURE AND STRANGE DUMP SUMMARY:
jafar2 /home/host lev 0 FAILED [out of tape]
It says out of tape, but a tape error is more
likely.
Tape Size (GB)... 4.71
Tape Used (%) 9.65
On Saturday 27 July 2002 01:52, Michael Perry wrote:
I decided to focus on getting smbclient backups working with
amanda so read the docs/samba stuff and added relevant entries to
my disklist file and also ran amcheck a few times. I am running
amanda on a Debian Unstable system with a very
I decided to focus on getting smbclient backups working with amanda so
read the docs/samba stuff and added relevant entries to my disklist file
and also ran amcheck a few times. I am running amanda on a Debian
Unstable system with a very recent CVS version of Samba that is in the
unstable tree
Hi, thanks for all your help. I broke down and recompiled/reinstalled the
amanda client and that seems to have cleared up the problem, amcheck no
longer reports any errors. I'll find out if the backups run tonight.
Thanks Again!
-Josh
Hi there.
I'm having a problem getting Amanda to backup one of our servers. When
running amcheck I get the following error:
ERROR: nushtel: [access as operator not allowed from operator@backupservername]
I found the faq-o-matic entry for this issue and checked all of my
settings against the
Looking at /tmp/amanda/amandad.debug on the server I'm trying to backup I
see somethings that concern me, namely:
the BUILT_MACH line lists the wrong hostname ...
That's just documentation about where Amanda was built. It's not used
for anything.
... The other bit that bugs me is that it
On Mon, 10 Sep 2001, John R. Jackson wrote:
What's in ~operator/.amandahosts? It should be:
backupservername operator
Here's what's in .amandahosts:
console.corecom.net operator
console is the name of the backupserver, here is the exact verbage of the
amcheck error:
ERROR: nushtel:
Here's what's in .amandahosts: ...
OK, that looks right.
We are using version 2.4.1p1. ...
OK, that version does not report anything else useful.
What does the following say:
ls -ld ~operator/.amandahosts
ls -ld ~operator
ls -ld ~operator/..
ls -ld ~operator/../..
John R. Jackson,
OK, then here are a couple of other things to try. Is the .amandahosts
file being accessed when you do amcheck? For instance, does ls -lu
show a time change?
Note that ls only shows things to the minute, so if you have some
other utility that shows more accurate atime output, that would be
On Mon, 10 Sep 2001, John R. Jackson wrote:
What does the following say:
ls -ld ~operator/.amandahosts
-r 1 operator operator 28 Sep 10 14:14 /usr/local/amanda/.amandahosts
ls -ld ~operator
drwxrwxr-x 2 operator wheel 512 Sep 10 14:14 /usr/local/amanda
ls -ld
12 matches
Mail list logo
