amanda 2.4.1p1
...
driver: result time 963.054 from dumper0: FAILED 01-6 [taper port
open: No such file or directory]
i'm rather confused:( . .sorry . .any help?
That message is caused by the Amanda routine stream_client failing.
Unfortunately, at 2.4.1p1, errno was not properly protected
Hi all, new to the group! :-)
Welcome!
I have a 400GIG RAID array on an Sun E3500 and a new Exabyte 110L tape
library to back it up.
OK.
Also, the 110L has scsi mode and sequential mode, not sure which one would
be best.
I'm not sure what sequential mode is, but given the choice, I'd go
Ok, I have a system on a different network I want to back up. I can't
access it directly from my amanda server because of IP masquerading.
So my thought was that I would have the gateway system that sits
between these two nets nfs-mount the filesystems from the system I
want to back up. amanda
hello everyone,
i think i've almost got amanda configured to work with my changer 100%. i
can load and unload tapes via the amtape command. specifying which slot i
want to load also works flawlessly. however, if i try and run an `amtape
conf show`, i get errors as it tries to read each tape
Quoting Paul Lussier ([EMAIL PROTECTED]):
In a message dated: Wed, 11 Jul 2001 13:40:13 +0200
Vicente Vives said:
My problem is very 'simple'...
I have to dump 13 GB using 2 GB tapes.
Can i do this?
How ?
You can, you just need to be creative in how you do it. There are
several
Quoting John R. Jackson ([EMAIL PROTECTED]):
Hi all, new to the group! :-)
Welcome!
I have a 400GIG RAID array on an Sun E3500 and a new Exabyte 110L tape
library to back it up.
OK.
Also, the 110L has scsi mode and sequential mode, not sure which one would
be best.
I'm not
1.) DMEG on my Dell 4400 server gives me:
Vendor: BNCHMARKModel: DLT1Rev: 3213
Type: Sequential Access
2.) I have been using a tapetype I modified from the samples, i.e:
DLT
length 4 mbytes
filemark 2000 kbytes
speed 1536 kbytes
Being a
On Thu, 12 Jul 2001 at 10:35pm, Philip J. Hollenback wrote
So my thought was that I would have the gateway system that sits
between these two nets nfs-mount the filesystems from the system I
want to back up. amanda could then back up the nfs dirs. Any problem
with that?
I think this
Below is the report, as mailed by my Amanda server.
Until the last few days, Amanda was running the backups with no problems. However, it
has sent me this for the last three, with active dump processes running on the client.
The server: RH7.1 w/ a generic load of Amanda 2.4.2p2
client: RH 7.0
In a message dated: Fri, 13 Jul 2001 09:41:24 +0200
Kris Boulez said:
Isn't there an option since amanda 2.2 to use multiple tapes for one
dump (see docs/MULTITAPE ). Is this just a 'would be nice to have' or
are people using this in production.
Good question, I don't know. It's been some
Title: unsubscribe
Unsubscribe
~~~
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized.
If you are not the
On Fri, 13 Jul 2001 at 8:39am, Joshua Baker-LePain wrote
Not a d*mn thing, because he hit 'CTRL-X Y' instead of 'CTRL-C Y'. Sorry
about that. What he decided not to write was...
On Thu, 12 Jul 2001 at 10:35pm, Philip J. Hollenback wrote
So my thought was that I would have the gateway
Hi
I'm trying to recover som data from a backup, but it does't really work.
Here's a cut of the session:
--- CUT ---
AMRECOVER Version 2.4.2. Contacting server on afs1.eos.dk ...
220 afs1 AMANDA index server (2.4.2) ready.
200 Access OK
Setting restore date to today (2001-07-13)
200 Working
Hi folks,
when using amrecover on localhost, I get [names edited]:
# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on backups.my.domain ...
220 backups AMANDA index server (2.4.2p2) ready.
500 Access not allowed: [access as operator not allowed from
[EMAIL PROTECTED]] open of
500 Access not allowed: [access as operator not allowed from
[EMAIL PROTECTED]] open of /usr/home/operator/.amandahosts failed
# whoami
root
Running tests as root is cheating :-). Try running them as operator.
# pwd
/usr/home/operator
# ls -alF
-rw--- 1 operator operator69 Jul 13
I'm trying to install amanda on IRIX 6.1 systems, but I keep getting this
error message while running amcheck
Amanda Backup Client Hosts Check
WARNING: spindletop: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.038 seconds, 1 problem
On Fri, 13 Jul 2001, John R. Jackson wrote:
Hi John
Then first things first. If amrecover is giving you grief, and you
really, really need that file back now, don't use it. Amrecover was
able to tell you the right tape, so mount it by hand and do the amrestore
piped into smbclient (or
I have had amanda running nicely for a little while now. Backing up about 20
Linux boxes. On two machines that I recently added to the backup procedure
two of the disklist entries are failing.
abbreviated disklist:
--
wilder /home
Is amrestore supposed to take a really long time to exit after a quit
command? Everything is copacetic with my amrestore sessions, until this
point. I end up having to do a ^C to get out of it (after waiting 20 or 30
minutes), which doesn't seem to hurt anything, other than my pride...
I'm on
Okay, I've finally got amanda working enough on aix 4.3.3 so that amcheck works. Now,
as to the disklist... dump on aix does NOT dump a filesystem. If I don't want to use
gnutar for the backup, what do I set the dumptypes to in the amanda.conf?
--
... dump on aix does NOT dump a filesystem. ...
The backup program does, and that's what Amanda will call.
The term DUMP in the dumptype means pick the appropriate dump-like
program on the client. In some cases, there are even multiple dump-like
programs to choose from, based on the file
What happens if you run this by hand **as root** on the client:
/bin/gtar --create \
--file /dev/null \
--directory /home \
--one-file-system \
--listed-incremental /dev/null \
--sparse \
--ignore-failed-read \
Is amrestore supposed to take a really long time to exit after a quit
command? ...
Not sure what you mean by a quit command to amrestore. Did you mean
amrecover?
It could be cause by three things:
* amrestore might still be shipping the image to the restore program.
If you've already
I've checked pretty much every possible reason for getting this message,
but nothing seems to work as yet.
Did you go through these FAQ items:
http://amanda.sourceforge.net/fom-serve/cache/16.html
http://amanda.sourceforge.net/fom-serve/cache/140.html
I also checked out amandad and I get
BTW I'm using Amanda 2.4.2p2 on all of the systems in my backup procedure.
on 'wilder' when i run the command this is the output:
[root@wilder /home]# /bin/gtar --version
tar (GNU tar) 1.13.17
Copyright 2000 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent
BTW I'm using Amanda 2.4.2p2 on all of the systems in my backup procedure.
OK.
Total bytes written: 558479360 (533MB, ?B/s)
It appears to get the size correctly ...
Yup, that looks good.
Go to /tmp/amanda on wilder and find an amandad that is starting the
sendsize service. Take the OPTIONS
client: RH 7.0 w/ a generic load of Amanda 2.4.2p2
What version of dump are you using? I think the last time this came up,
the person upgraded to the latest (and/or restore as well) and things
started working.
Basically the error is saying dumper on the tape server waited half an
hour and
i think i've almost got amanda configured to work with my changer 100%. ...
What version of Amanda?
amtape miami show
amtape: scanning all 7 slots in tape-changer rack:
slot /dev/nst0:: no tape online
What's in /tmp/amanda/changer.debug*? You may want to empty it out,
then try the command to
I have this constant recurrant error, that every day the amcheck is
failing just after a succesfull amdump.
I don't understand. Do you really mean you're running amcheck **after**
you run amdump? Why? Usually it's run **before** amdump so any problems
it finds can be fixed before the run.
Thanks to you, and all that pointed this out.
The strange thing about it, is that our exclusion worked fine until we
upgraded our gnutar from 1.12.? to 1.13.19
So the problems with restoring with 1.13 alluded to on the amanda-patches
page are pretty well obsolete by .19 ?
John R. Jackson
So the problems with restoring with 1.13 alluded to on the amanda-patches
page are pretty well obsolete by .19 ?
I'm not sure what problems that refers to, but I don't recall any restore
problems being reported on this list due to GNU tar for I don't know how
long (or, put a different way, any
Nice! That's just the kind of solution I was looking for. I have it
configured, now let's see how it works...
P.
On Prickle-Prickle, the 48th of Confusion, Joshua Baker-LePain spake:
On Fri, 13 Jul 2001 at 8:39am, Joshua Baker-LePain wrote
Not a d*mn thing, because he hit 'CTRL-X Y'
Hi @ all!
I have a general question about amanda-tapecycles: How does that cycling
work?
I.e. if i tell amanda that I want a 10 days backup-cycle with
incremental backup every day, using 20 tapes - when does amanda use
which tape? Does it cycle until all the tapes have been used one time
and
... Does it cycle until all the tapes have been used one time
and then start again ...
Yes. It's a simple least recently used algorith (the oldest tape is
the one that will be used next).
Volker
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
34 matches
Mail list logo