ot;
planner:DEFAULT_TAPE_SERVER="localhost"
planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
planner: USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID
HAVE_GZIP
On Mon, 26 Mar 2001, Urban Petry wrote:
Which device driver are you using under Linux? The equivalent of Sun's
'sgen' driver? I am going to try the 'sst' driver supplied with Amanda
today and see if I get a different result. According to the manual, the
factory defaults are ID 0 for the
Hi!
Basically, it's about amanda tells me there is no tape but guys from
company that collocation server told me there is a tape loaded. They check
twice. Also, I'm 100% it's not a joke or something like this, but a serios
situation I don't know how to manage.
[root@server /root]# date
Tue Mar
I think you need to read the amanda documentation. download the source
to amanda, and look in the docs directory.
also read this document: http://www.backupcentral.com/amanda.html
you restore from disk, exactly the same way you restore from tape,
please read the documents on how amanda works,
If "mt" says there is no tape, there isn't any tape.
Amanda has nothing to do with it.
-- Or the tape drive isn't connected to the SCSI bus.
-- Or the power cable isn't plugged in.
-- Or the media is defective.
-- Or the drive needs cleaning.
-- Or the tape drive is buggy.
I see that
I'm getting the following error running ./configure as root:
# ./configure
creating cache ./config.cache
checking host system type... powerpc-ibm-aix4.3.3.0
checking target system type... powerpc-ibm-aix4.3.3.0
checking build system type... powerpc-ibm-aix4.3.3.0
checking cached system tuple...
Hi!
On Tue, 27 Mar 2001, Dan Wilder wrote:
If "mt" says there is no tape, there isn't any tape.
Amanda has nothing to do with it.
Ok.
-- Or the tape drive isn't connected to the SCSI bus.
-- Or the power cable isn't plugged in.
It must be connected because the server is up running
Hi all,
I am setting up the amanda.conf file, and have come to the point where I am setting up
the tape device. I am setting the tpchanger to "chg-multi" so I can take advantage of
the 2 DLTs I have attached to the host. The DLTs are /dev/(n)st0 and /dev/(n)st1. In
reading the
Hi all,
I am setting up the amanda.conf file, and have come to the point where I am setting up
the tape device. I am setting the tpchanger to "chg-multi" so I can take advantage of
the 2 DLTs I have attached to the host. The DLTs are /dev/(n)st0 and /dev/(n)st1. In
reading the
Dan Wilder [EMAIL PROTECTED] writes:
[...]
I see that the drive is an OnStream. Haven't there been
significant problems reported on this list, with those?
According to the SCSI newsgroups they are out of buisness.
Johannes Niess
Several months ago I set up Amanda under Slackware Linux 7.0 (now using
kernel 2.41) and had everything running fine, without issues. A few days
ago, I started getting messages saying Amanda was unable to run..
--
ERROR: /dev/st0: not an amanda tape (expecting a new tape)
--
So I tried
ERROR: /dev/st0: not an amanda tape (expecting a new tape)
That's the wrong device name. It must be /dev/nst0 to get the no-rewind
semantics.
Let me re-iterate, the configuration has not been changed since the day I
installed it and had it working for 3 months. ...
Then you've been damned
Here were my thoughts, and advice is more than welcome:
# cat chg-multi.conf
...
Looks OK to me.
I might have used firstslot 0, lastslot 1 and slot 0, slot 1, but that's
just the C programmer in me :-). Counting from 1 worked for Fortran :-).
John R. Jackson, Technical Software Specialist,
I'm getting the following error running ./configure as root:
First, most people recommend configuring and building as non-root just
in case the process goes weird. The install step is usually the only
thing that has to be done as root.
# ./configure
...
configure: error: *** --with-user=USER
I'm trying to do a full level 0 restore of a directory on our largest
backed up partition. Amanda (2.4.1p1, BSDI 4.1, Seagate DDS4 drive) is
using gtar to back it up because I have to exclude a bunch of stuff. The
problems I've had are as follows.
I successfully used the amrecover technique
FAILURE AND STRANGE DUMP SUMMARY:
kascha sdb2 lev 0 FAILED [disk sdb2 offline on kascha?]
kascha sdb1 lev 0 FAILED [disk sdb1 offline on kascha?]
kascha sda1 lev 0 FAILED [disk sda1 offline on kascha?]
Since these are my boot disk and /usr disk they arnt off
line.
On Tue, 27 Mar 2001, John R. Jackson wrote:
Are you sure the permissions on /dev/nst0 allow read/write access to
the Amanda user? Put another way, make sure they are the same as the
ones on /dev/st0, since that sort of works.
Thanks for the info John. You were right, it was a permissions
OK,
When I changed the disklist on the server to the mount points instead of the
devices (eg. /usr/local instead of hda6 or /dev/hda6), it works fine.
So first of all, thanks a LOT!
Is the reason for this:
a) because the computer we just fixed is running RedHat 7.0 as opposed to
Redhat 6.1
Yes I know this is a popular error message.
# amrecover -C Weekly -s clark -t clark -d /dev/nst0
AMRECOVER Version 2.4.2p1. Contacting server on clark ...
amrecover: Unexpected server end of file
In this case the command was executed on the host "clark"
clark happens to be the amanda server,
I'm trying to do a full level 0 restore of a directory on our largest
backed up partition. ...
I successfully used the amrecover technique to have Amanda restore off of
the level 0 and all of the subsequent days, however I could tell that not
everything got restored. ...
Amrecover is not
Often the response to these posts is,
"What does your /tmp/amanda/amindexd*debug file say?"
This is my fundamental problem. I don't have a amindexd*debug file.
I have all the other debug files:
...
The amindexd is dieing right away, before it can even open the debug
file. What happens if
Hi John -
gtar version:
/usr/local/bin/tar --version
tar (GNU tar) 1.13
Oh well, I'm currently doing a 'gtar -xvf' on the entire image, and there
is that large number in front of everything, but it seems to be restoring
files properly. However I just noticed that it is restoring files I
Here is what I get after I run # su operator -c /usr/lib/amanda/amindexd
amindexd: open debug file "/tmp/amanda/amindexd.debug": Permission denied
Ok Now I opened up permissions on /tmp/amanda.
I re ran the command with the following results
# su operator -c /usr/lib/amanda/amindexd
I have a directory that I must backup sometimes more than once a day... the
problem is that when I try to amrecover it I only get the file list of the
last dump I made ... what can I do to correct this ?
I can think of two things.
You could take over the development project to make Amanda use
"John R. Jackson" wrote:
The amindexd is dieing right away, before it can even open the debug
file. What happens if you do this:
# su operator -c /usr/lib/amanda/amindexd
It should die right away with a message something like this:
amindexd: getpeername: Socket operation on
I just ran into this. On the tape server machine you need to add
clark.xxx.com root
to your .amandahosts file
You also need to verify that the user that runs the service is setup
correctly.
I say this because in your first post you have both amanda and operator as
the users for your services.
Oh well, I'm currently doing a 'gtar -xvf' on the entire image, and there
is that large number in front of everything, but it seems to be restoring
files properly. ...
Really? They are not going into a directory with that big number on
the front?
Whatever. If it's working, you win :-).
unsubscribe
When I changed the disklist on the server to the mount points instead of the
devices (eg. /usr/local instead of hda6 or /dev/hda6), it works fine.
Great!
Is the reason for this:
a) because the computer we just fixed is running RedHat 7.0 as opposed to
Redhat 6.1 on the other
This is my
When I changed the disklist on the server to the mount points instead of the
devices (eg. /usr/local instead of hda6 or /dev/hda6), it works fine.
Great!
Is the reason for this:
a) because the computer we just fixed is running RedHat 7.0 as opposed to
Redhat 6.1 on the other
this
As of firmware upgrade 8ck3v03a (8ch3v03a for HVD
drives), Exabyte have fixed a major problem with
premature EOT errors. I have just upgraded and was
able to do a full level 0 dump for the first time
without getting inconsistent EOTs.
So if you're getting this kind of error, it may be worth
a
* John R. Jackson [EMAIL PROTECTED] (Tue, Mar 27, 2001 at 04:01:42PM -0500)
Or you could just "know" that amrecover lies and whatever tape it
tells you to load, go back to your reports and load the "right" tape.
The amrestore than amidxtaped calls searches for the image by name anyway.
It
32 matches
Mail list logo
