, 05--2005 01:19, Stefan G. Weichinger
:
Hi, Andrs,
on Montag, 04. April 2005 at 23:01 you wrote to amanda-users:
AFAD Now I have a problem restoring. I tried to use amrestore but it
AFAD returns this to me
AFAD #amrecover
AFAD AMRECOVER Version 2.4.4p4. Contacting server on localhost
Now I have a problem restoring. I tried to use amrestore but it
returns this to me
#amrecover
AMRECOVER Version 2.4.4p4. Contacting server on localhost ...
amrecover: cannot connect to localhost: Connection refused
I have this entry in /etc/hosts
192.168.0.1 localhost.localdomain. localhost
Hi, Andrés,
on Montag, 04. April 2005 at 23:01 you wrote to amanda-users:
AFAD Now I have a problem restoring. I tried to use amrestore but it
AFAD returns this to me
AFAD #amrecover
AFAD AMRECOVER Version 2.4.4p4. Contacting server on localhost ...
AFAD amrecover: cannot connect to localhost:
Stefan,
On Wed, Jan 19, 2005 at 10:48:54PM +0100, Stefan G. Weichinger wrote:
BC Major imporvement though still below the acceptable threshold.
BC Definitely looking like it was never an amanda issue, this looks to
BC be an underlying architecture problem.
I hope that you spot the issue
On Friday 21 January 2005 11:37, Brian Cuttler wrote:
Stefan,
On Wed, Jan 19, 2005 at 10:48:54PM +0100, Stefan G. Weichinger wrote:
BC Major imporvement though still below the acceptable threshold.
BC Definitely looking like it was never an amanda issue, this
looks to BC be an underlying
Info update only.
Ok we've shutdown the Origin 300 and swapped the scsi daisy-chain
around a little.
At this point the SDLT in the shoebox was able to restore a large
tar file without causing a SCSI reset and hanging the system.
I then set the blocksize on the SDLT in the jukebox and
Hi, Brian,
on Mittwoch, 19. Jänner 2005 at 22:02 you wrote to amanda-users:
BC Major imporvement though still below the acceptable threshold.
BC Definitely looking like it was never an amanda issue, this looks to
BC be an underlying architecture problem.
I hope that you spot the issue soon,
On Tuesday 11 January 2005 16:40, Jon LaBadie wrote:
Also, I think that if both types of devices exist on the same bus,
the lower performance one determines the performance of the entire
bus.
In theory, this is *not* the case. One of the (many) selling
points of SCSI over IDE is supposed to be
On Wed, Jan 12, 2005 at 11:18:00AM -0500, Eric Siegerman wrote:
On Tuesday 11 January 2005 16:40, Jon LaBadie wrote:
Also, I think that if both types of devices exist on the same bus,
the lower performance one determines the performance of the entire
bus.
In theory, this is *not* the case.
Google says: voltage standing wave ratio
To many folks forget that a a scsi bus is indeed
an rf transmission line, subject to the usual rules about vswr.
From the context it's pretty clear what vswr means, but what
does it stand for?
/off-topic
Wondered too, as I'm posting
On Wednesday 12 January 2005 14:55, Gene Heskett wrote:
On Wednesday 12 January 2005 12:04, Jon LaBadie wrote:
On Wed, Jan 12, 2005 at 11:18:00AM -0500, Eric Siegerman wrote:
On Tuesday 11 January 2005 16:40, Jon LaBadie wrote:
Also, I think that if both types of devices exist on the same
bus,
Hi, Jon,
on Montag, 10. Jänner 2005 at 22:19 you wrote to amanda-users:
JL In recent versions, amanda can work with blocksizes other than 32k.
JL I forget if it is a configure option needed during the build or
JL a parameter that can be set in amanda.conf. I've never used it.
The parameter
Amanda user list,
I've spoken to Harry at Condre systems and he confirmed what we
where seeing. The jukebox robot is a narrow bus so that are two
changes we need to make.
1) We want to move the jukebox/SDLT to be the last device on
the daisy chain.
2) We want to terminate the jukebox-robot,
Jon,
Recommended buying an additional scsi card more than once to the
system's owners, haven't made the case yet (maybe now). I would
really have liked the raid array on a separate bus from the tape
drives.
I have to trust that the proper cabeling to terminate the additional
lines is present in
On Tuesday 11 January 2005 16:40, Jon LaBadie wrote:
On Tue, Jan 11, 2005 at 03:40:47PM -0500, Brian Cuttler wrote:
Amanda user list,
I've spoken to Harry at Condre systems and he confirmed what we
where seeing. The jukebox robot is a narrow bus so that are two
changes we need to make.
1)
The following (just scripted, with commentary added) is a little long
and rather un-good.
samar 9# script
Script started, file is typescript
Position us at the start of the next volume. This volume has been
relabeled after setting the block size on the tape (last week).
samar 1#
On Mon, Jan 10, 2005 at 11:48:42AM -0500, Brian Cuttler wrote:
The following (just scripted, with commentary added) is a little long
and rather un-good.
...
Probing the drive I find a block size of 32768 again.
samar 25# mt -f /dev/sdlt2 setblksz 131072
samar 26#
Jon,
On Mon, Jan 10, 2005 at 04:19:45PM -0500, Jon LaBadie wrote:
Something that didn't error during the write but did
during the read ?
This is not too surprising to me.
A tape with a blocksize of 132k will accept a write of 32k and
simply pad it to the required size. No errors.
On Fri, Jan 07, 2005 at 03:11:41PM -0500, Jon LaBadie wrote:
That ENOMEM, reported as insufficient memory sometimes used to
throw me for a loop. Here is the situation as I understand it.
To enhance performance dd tries to do unbuffered I/O, meaning the
data goes directly to memory in dd
Apologies for following up my own post.
On Sat, Jan 08, 2005 at 06:20:59PM -0500, Eric Siegerman wrote:
[...] in neither case does [dd] need to copy the data
from one buffer to another. It can just have a single buffer
that's max(ibs,obs) long [...]
Oops; I'm wrong about this. It's only
Hello, Brian,
I thought of your problems this morning ;-)
Just now (on 01/07/2005 at 17:17) you wrote:
BC Oddly trying to dd if=/dev/rmt/tps... read no data
BC samar 85# mt -f /dev/rmt/tps1d4nrns rewind
BC samar 86# dd if=/dev/rmt/tps1d4nrns of=scratch
BC Read error: Invalid argument
Invalid
Stefan,
Yes, will strip more stuff out (didn't realize it had grown so much.
The instruction I was following from Gene where pretty explicite
(not that I follow all that well) and where intended to save the
amanda header, reset the block count, restore the header and flush
the buffers.
Hi, Brian,
on Freitag, 07. Jänner 2005 at 17:59 you wrote to amanda-users:
BC The instruction I was following from Gene where pretty explicite
BC (not that I follow all that well)
;-)
BC and where intended to save the
BC amanda header, reset the block count, restore the header and flush
BC the
On Friday 07 January 2005 11:59, Brian Cuttler wrote:
Stefan,
Yes, will strip more stuff out (didn't realize it had grown so much.
The instruction I was following from Gene where pretty explicite
(not that I follow all that well) and where intended to save the
amanda header, reset the block
Gene,
Humm, are you saying that amlabel works and can read the label
written, but that dd doesn't/cannot? Back to 'man dd' as it exists
on that Irix system would be my next suggestion.
Remembering that I'd set the blocksize on the device and relabeled
yesterday I tried this.
samar 160# mt
Hey Brian,
just now (on 01/07/2005 at 19:20) you wrote:
Humm, are you saying that amlabel works and can read the label
written, but that dd doesn't/cannot? Back to 'man dd' as it exists
on that Irix system would be my next suggestion.
BC Remembering that I'd set the blocksize on the
Stefan,
Good to hear. What size did scratch have?
Much nicer device-name now, BTW, maybe this was the problem ... Do you
use this one (the corresponding non-rewinding device) in amanda.conf
as well ??
I'll have to try to pull it again, I seem to have subsequently
overwritten it with a zero
On Fri, Jan 07, 2005 at 11:59:54AM -0500, Brian Cuttler wrote:
samar 126# which xfsrestore
/sbin/xfsrestore
samar 127# which xfsdump
/usr/sbin/xfsdump
I suppose the theory must be that anyone can do a restore, but
only root can use [xfs]dump.
--
| | /\
|-_|/ Eric Siegerman, Toronto,
On Fri, Jan 07, 2005 at 02:01:26PM -0500, Eric Siegerman wrote:
On Fri, Jan 07, 2005 at 11:17:21AM -0500, Brian Cuttler wrote:
samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch
64+0 records in
1+0 records out
bs block size, obs outpub BS, (there is an IBS also, which I
am afraid of developing
On Fri, Jan 07, 2005 at 01:20:42PM -0500, Brian Cuttler wrote:
samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch
64+0 records in
1+0 records out
bs block size, obs outpub BS, (there is an IBS also, which I
am afraid of developing should this not resolve soon)
Yup, this makes sense. Since
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
samar 6# mt -f /dev/sdlt2 rewind
samar 7# mt -f /dev/sdlt2 fsf 1
samar 8# dd if=/dev/sdlt2
On Fri, Jan 07, 2005 at 03:40:12PM -0500, Brian Cuttler wrote:
samar 24# mt -f /dev/sdlt2 blksize
Recommended tape I/O size: 131072 bytes (256 512-byte blocks)
Minimum block size: 4 byte(s)
Maximum block size: 16777212 bytes
Current block size: Variable
I am using /dev/sdlt2 link
On Friday 07 January 2005 15:40, Brian Cuttler wrote:
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
samar 6# mt -f /dev/sdlt2 rewind
On Fri, Jan 07, 2005 at 03:40:12PM -0500, Brian Cuttler wrote:
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
[likewise with dd
Gene,
Thanks for the tape label sequence, will re-label the next couple
of tapes and see if I don't get different results from the next
amdump run. (commands reproduced below).
If this solves the problem perhaps it should be incorporated into amlabel.
Alexander,
Hadn't realized that the 1st
On Friday 31 December 2004 10:49, Brian Cuttler wrote:
Gene,
Thanks for the tape label sequence, will re-label the next couple
of tapes and see if I don't get different results from the next
amdump run. (commands reproduced below).
If this solves the problem perhaps it should be incorporated
Hi,
on Wednesday 29 December 2004 16:29, Brian Cuttler wrote:
Amanda2.4.4p1-20030716
SGI/IRIX 6.5.19m
mtx 1.3.8
8 Slot jukebox with SDLT 320 (Quantum)
gnutar1.13.25
I suppose this configuration looks familiar to some of you.
I was in the process of writing an email to thank
Gene,
Stefan,
* I'm gonna remove a lot of text from the middle of this.
On Wednesday 29 December 2004 16:29, Brian Cuttler wrote:
## Amanda2.4.4p1-20030716
## SGI/IRIX 6.5.19m
## mtx 1.3.8
## 8 Slot jukebox with SDLT 320 (Quantum)
## gnutar1.13.25
##
## I'm planning to dump 2-3
On Thursday 30 December 2004 14:55, Brian Cuttler wrote:
Gene,
Stefan,
* I'm gonna remove a lot of text from the middle of this.
On Wednesday 29 December 2004 16:29, Brian Cuttler wrote:
## Amanda2.4.4p1-20030716
## SGI/IRIX 6.5.19m
## mtx 1.3.8
## 8 Slot jukebox with SDLT 320
Amanda2.4.4p1-20030716
SGI/IRIX 6.5.19m
mtx 1.3.8
8 Slot jukebox with SDLT 320 (Quantum)
gnutar1.13.25
I suppose this configuration looks familiar to some of you.
I was in the process of writing an email to thank Stefan Weichinger,
Gene Heskett and Eric Siegerman for the terrific
On Wednesday 29 December 2004 16:29, Brian Cuttler wrote:
Amanda2.4.4p1-20030716
SGI/IRIX 6.5.19m
mtx 1.3.8
8 Slot jukebox with SDLT 320 (Quantum)
gnutar1.13.25
I suppose this configuration looks familiar to some of you.
I was in the process of writing an email to thank Stefan
Are you backing up Windows or *nix machines?
Jyrki Hämäläinen [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi all!
I have a problem with amrestore/amrecover.
I managed succesfully backup and tape all filesystems I wanted. When
tried to recover some files I
Adnan Olia wrote:
Are you backing up Windows or *nix machines?
Both machines - backup server and client are linux boxes.
Client machine tar (GNU tar) is version 1.13.19.
Error message amrestore gives indicates OS-level problem but as I told
in previos message I am able to restore stuff
Hi all!
I have a problem with amrestore/amrecover.
I managed succesfully backup and tape all filesystems I wanted. When
tried to recover some files I however encountered problem.
If I got it right amanda reads through tape trying to find right file
and then finds problem with its own headers
Joshua Baker-LePain [EMAIL PROTECTED] writes:
Verifying backups?! Are you insane? You're not supposed to do that until
you *need* them. Sheesh.
Is that so? What's amverify doing in my crontab file, then? ;-)
(That was a rhetorical question. It's there so that ejecting the tape
will be
Hello,
Is there a limit on the length of the path when using amrestore? I
attempted to restore a partition but kept getting errors. When I went
down a few subdirectories the restore worked. Amrestore seems to fail to
restore files when the path is over 80 characters long.
Soo
Tried looking in the FAQ first but didn't come up with anything.
Anyway I have amanda installed on a Linux Redhat 7.2 box, using version
2.4.3b2-20020308
Backup seem to perform normally, but decided to verify by doing a restore
and got the following error:
sh-2.05$ /usr/local/sbin/amrestore
On Thu, 4 Apr 2002 at 9:47am, Davidson, Brian wrote
Backup seem to perform normally, but decided to verify by doing a restore
and got the following error:
Verifying backups?! Are you insane? You're not supposed to do that until
you *need* them. Sheesh.
sh-2.05$
Hi,
use /dev/nst0 as tape-device and you should be fine
Christoph
Davidson, Brian schrieb:
Tried looking in the FAQ first but didn't come up with anything.
Anyway I have amanda installed on a Linux Redhat 7.2 box, using version
2.4.3b2-20020308
Backup seem to perform normally, but
Joshua Baker-LePain [EMAIL PROTECTED] writes:
Verifying backups?! Are you insane? You're not supposed to do that until
you *need* them. Sheesh.
Is that so? What's amverify doing in my crontab file, then? ;-)
(That was a rhetorical question. It's there so that ejecting the tape
will be
On Thu, 4 Apr 2002 at 6:07pm, Arvid Grøtting wrote
Coming to think of it, if amverify were to find a real error, what's
the approperiate procedure for me to follow?
It depends on the error. If the tape is bad, amrmtape it. Amanda will
invalidate the backups on that tape, and catch up on
/nst0. I had just check my BSDI box which uses nrst0
Thanks!
-Original Message-
From: Christoph Scheeder [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 04, 2002 10:34 AM
To: Davidson, Brian
Cc: [EMAIL PROTECTED]
Subject: Re: amrestore problem
Hi,
use /dev/nst0
Hi,
I solved my problem alone.
FYI the problem was that the basename of the machine was not well registred
(baseinstall in /etc/hostname, another name in DNS).
Thank you.
On Wednesday 13 June 2001 11:09, you wrote:
Hi all,
I'm new to Amanda and have a brand new config running. My backup
Hi all,
I'm new to Amanda and have a brand new config running. My backup server and
clients are Debian - i'm using Amanda 2.4.1p1 (precompiled for Debian).
Here's my problem :
I can without problem restore a backup on my backup server :
backup:/var/local/space/test# amrecover -C Normal -s
Hi There!
root@fileserver:/usr/local/sbin ./amrecover Daily
AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ...
220 fileserver AMANDA index server (2.4.2-19991216-beta1) ready.
200 Access OK
Setting restore date to today (2001-03-12)
200 Working date set to
Am Montag, 12. März 2001 09:25 schrieben Sie:
Hi!
Can't determine disk and mount point from $CWD
amrecover
What is wrong?
In short NOTHING. When you start amrecover it assumes that you want to
recover directly into your current working directory. You need to
sethost, then setdisk. So,
Am Freitag, 9. Mrz 2001 16:10 schrieben Sie:
Hi John!
Should i make a
fileserver.medienwerft.de root
king.medienwerft.de root
in the /home/amanda/.amandahosts, too?
Yes. That's exactly what it's telling you.
Thanks, thats good, working of amrecover will be better.
OK, i have
Yes, i changed the lines so you given me.
OK, that´s fine. Amanda finds the Indexfile.
Great! That's good progress.
500 Access not allowed: [access as amanda not allowed from
[EMAIL PROTECTED]] amandahostsauth failed
...
Should i make a
fileserver.medienwerft.de root
king.medienwerft.de
Am Freitag, 9. Mrz 2001 04:48 schrieben Sie:
Hi!
And I also said exactly what I thought was wrong, based on what you
posted. However what you wrote in that letter is not the same as what
Sorry, this mail didn't come to me!
And some mails are more than once by me.
you wrote in this one:
Am Montag, 5. März 2001 09:17 schrieben Sie:
Hi!
vi /etc/services
/amandaidx
amanda 10080/udp
amandaidx 10082/tcp
amidxtape 10083/tcp
Is that correct?
Bye Juergen
--
Dies ist eine Microsoft freie Mail!
amandaidx stream tcp nowait amanda /usr/sbin/tcpd/ usr/local/libexec
amidxtape stream tcp nowait amanda /usr/sbin/tcpd /usr/local/libexe
amanda dgram udp wait amanda /usr/sbin/tcpd /usr/local/libexec
Those cannot be right. First, there is a trailing '/' on "tcpd" for
The result of this run is :
amindexd: debug 1 pid 3228 ruid 560 euid 560 start time Thu Mar 1
09:14:29 2001amindexd: version 2.4.2-19991216-beta1
Is this ok or are you missing some?
There should be a lot more in there.
In /etc/inetd.conf :
[...]
amandaidx stream tcp nowait amanda
On the fileserver (Tapeserver) amrecover give me no output ...
Huh? No output at all???
The file has 0 Bytes :-( ...
What file? The amrecover program?
The first place to look is /tmp/amanda/amindexd*debug on the server.
The result of this run is :
amindexd: debug 1 pid 3228 ruid 560
Hi!
Huh? No output at all???
The file has 0 Bytes :-( ...
What file? The amrecover program?
Yes, and i don't know why amrecover has 0 Byte. Bu i have a copy :-)
The first place to look is /tmp/amanda/amindexd*debug on the server.
The result of this run is :
amindexd: debug 1 pid
Where must i start the recovery? On the Server or on the client?
Typically on the client.
On the fileserver (Tapeserver) amrecover give me no output ...
Huh? No output at all???
and on the client (king) an amrecover gives me:
root@King:/usr/local/sbin ./amrecover -C Daily -s fileserver -t
Hi!
Running with no Problems and give me:
root@fileserver:/usr/local/sbin mt -f/dev/nst0 rewind
root@fileserver:/usr/local/sbin dd if=/dev/nst0 bs=32k count=1
AMANDA: TAPESTART DATE 20010223 TAPE Daily04
The amrestore command is working fine ...
I'm confused. You said it didn't work in
Hi!
But, after rewinding the tape i become another error:
root@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king
amrestore: WARNING: not at start of tape, file numbers will be offset
This was right after a rewind? If so, then that's not an Amanda tape.
Or it cannot be read.
Try this
Running with no Problems and give me:
root@fileserver:/usr/local/sbin mt -f/dev/nst0 rewind
root@fileserver:/usr/local/sbin dd if=/dev/nst0 bs=32k count=1
AMANDA: TAPESTART DATE 20010223 TAPE Daily04
...
The amrestore command is working fine ...
I'm confused. You said it didn't work in
OK, i tested it with this commands:
amanda@fileserver:~ cd /usr/local/sbin/
amanda@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king
amrestore: missing file header block
...
HmWhat´s wrong?
Did you "mt -f /dev/nst0 rewind" first?
Juergen
John R. Jackson, Technical Software
amanda@fileserver:~ cd /usr/local/sbin/
amanda@fileserver:/usr/local/sbin ./amrestore /dev/nst0 king
amrestore: missing file header block
Did you "mt -f /dev/nst0 rewind" first?
i have forgotten :-(
But, after rewinding the tape i become another error:
root@fileserver:/usr/local/sbin
Hi!
root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king
/dev/sg5 is a changer. The tape device is /dev/nst0, and that's what
amrestore wants.
OK, i tested it with this commands:
amanda@fileserver:~ cd /usr/local/sbin/
amanda@fileserver:/usr/local/sbin ./amrestore /dev/nst0
Am Freitag, 16. Februar 2001 20:57 schrieben Sie:
root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king
/dev/sg5 is a changer. The tape device is /dev/nst0, and that's what
amrestore wants.
OK, i will testing at theses day.
Thanks a lot.
Bye Juergen
--
Dies ist eine Microsoft freie
On Feb 16, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king
/dev/sg5 is a changer. The tape device is /dev/nst0, and that's what
amrestore wants.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC
Hi!
I will restore some files from the tape changer, but i become some errors:
root@fileserver:/usr/local/sbin ./amrestore /dev/sg5 king
amrestore: error reading file header: the argument is not correct (Das
Argument ist ungueltig)
In chg-scsi.conf i have
config 0
drivenum
74 matches
Mail list logo
