can
see for it to do that. The ONLY backup that was defined to go direct to tape
is localhost:/data1.
markh
-Original Message-
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 5:16 PM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help
index tee cannot write [Broken pipe]
...
Where does the tee come into play so I can tell what application failed? ...
The tee is caused by having indexing turned on. The dumper terminated
for some reason and there was nothing on the other end of that file
descriptor to write to any more, which
:16 PM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help figuring out why these don't complete
index tee cannot write [Broken pipe]
...
Where does the tee come into play so I can tell what application failed?
...
The tee is caused by having indexing turned on. The dumper terminated
... I'll go fight the amandad busy and dumper died messages later, but why
am I getting all the dump to tape failed ...
You'll need to fight the dumper died messages first. They triggered
the dump to tape failed.
The place to start is the amdump.1 file (or whichever one matches
this run).
You
I have not reset the chunksize from it's default so it is still at whatever
the default is. I'll explicitly set it to 1Gb and try again. ...
The default is already 1 GByte, so that's not it (and you don't need
to change it). And I can see in the log you sent that it's still using
that value.
. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 3:16 PM
To: Mark Holm
Cc: '[EMAIL PROTECTED]'
Subject: Re: Need help figuring out why these don't complete
I have not reset the chunksize from it's default so it is still at whatever
the default is. I'll explicitly set
Attached is the Amanda report from the backup that I just completed, which
should have been a Full Backup forced by a dumpcycle of 0 and runspercycle
of 1. I'll go fight the amandad busy and dumper died messages later, but why
am I getting all the dump to tape failed which pair up with the No
Hi everybody:
I start to use the tape cleaner but I have had some problems. When i run amcheck all the time I got the error
amcheck-server: slot 5: rewinding tape: No medium found
amcheck-server: fatal slot 6: mtx: Cleaning Cartridge Installed and Ejected
ERROR: label miro_daily-5 or new tape
---
Von: Radu Filip [mailto:[EMAIL PROTECTED]]
Gesendet: Samstag, 7. April 2001 15:14
An: [EMAIL PROTECTED]
Betreff: Need help on recover
Wichtigkeit: Hoch
Hi!
First at all, I'm not in situation of need for real to
restore from tapes,
but I'm the stage where I want to verify that I can
On Mon, 9 Apr 2001 [EMAIL PROTECTED] wrote:
No, I don't solve the problem, yet. - I slow down the Bus-Speed in the
Controller-BIOS for the LVD-Connector from 40 to 20MB/sec. - With this
change, the write-process (backup) now works - but restoring fails...
Oh, I see. For me there was no
On Sat, Apr 07, 2001 at 04:13:32PM +0300, Radu Filip wrote:
amrestore: 0: skipping start of tape: date 20010407 label bak_tape_3
amrestore: fast-forward: Input/output error
this was the error I was searched for on this list archive
amidxtaped: amrestore terminated
Thank you, Jean-Loius. Your answer leads me to a succesfull restore of an
entire subirectory. Anyway, driver hang out several times and also I had
to manually rewind the tape before running amrecover.
Mersi,
Radu Filip
P.S. Based on my experience until now, *don't* buy OnStream tape drives!
On Wed, 14 Mar 2001, John R. Jackson wrote:
... I am encrypting the backups with gnupg and using tar. ...
Huh? How are you doing the encryption? Amanda doesn't support that.
Check out this url: http://security.uchicago.edu/tools/gpg-amanda
Pretty easy to get going. Just uses a wraper
So what I am hearing is that amanda can backup no partition larger then
the size of the tape drive + whatever compression is in use.
Correct, for the moment. I'm trying to fix that (literally) as I'm
writing this.
OK. One last question how do you specify to use hardware or sofware
Hello,
I am new to amanda so please excuse the lay questions. I have searched
the archives but did not find what I was looking for. I have two servers.
The backup server has a SONY SDT 7000 4/8gig drive. I have everything
setup, labeled the tapes and ran amcheck with no errors. I am
... I am encrypting the backups with gnupg and using tar. ...
Huh? How are you doing the encryption? Amanda doesn't support that.
When I run amdump I get
the error "dump larger then tape, but cannot incremental dump new disk"
This says the estimated dump size Amanda got is larger than
"John" == John R Jackson [EMAIL PROTECTED] writes:
John You must have some kind of hostname lookup problem, which is unrelated
John to Amanda. Amanda tried to look up "master" and "localhost" and got
John an error. Start checking your DNS configuration, /etc/resolv.conf,
John
I wonder if Amanada needs a ``TROUBLESHOOTING'' file like that which
appears in the Samba distribtion? ...
How about we call it FAQ? And then we could put a link to it on the
web page.
Oh, wait. Never mind. :-)
Not that I have time to volunteer, unfortunately.
And I should get into the
amrestore: fast-forward: Errore di input/output
Assuming I can translate this properly :-), this means the drive reported
an I/O error to the OS (who reported it to Amanda who logged it).
In other words, the tape could not be read.
But all may not be lost. Here are some things to try:
*
Hi all..
I'm having a lot of troubles in restoring amanda backups...
I have an HP's T20i Travan Tape in a Linux 2.2.14-5.0 kernel box...
When I run:
/usr/sbin/amrecover -C DailyBack -d /dev/nst0
I select the file I want to restore, I start the 'extract' command and
I obtain:
"
...
Hi,
I'd *really* like to fix this before the holidays... ;)
My tapehost can't seem to back itself up. Last night's report indicates
"request timed out", as does a subsequent amcheck. I've consulted the
FAQ for amcheck, and since /tmp/amanda/amandad.debug had not been
rewritten since the
Hi,
Nevermind folks, I figured it out. Guess I just panicked because it was
the Friday before Christmas... ;)
The problem was large filesystems that were all scheduled for level 0
dumps. Amanda was timing out before dump was finished estimating the
sizes. Increasing "etimeout" in amanda.conf
101 - 122 of 122 matches
Mail list logo
