I'm running an amanda 3.3.1 server, using the default bsdtcp auth method.
I'm running amrecover as just:
amrecover DailySet
Once I've added files to be restored and type extract I get the following
error:
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug
Running amanda 3.2.0 on a Sun Solaris 10 server.
./amrecover archive
AMRECOVER Version 3.2.0. Contacting server on hertz ...
[request failed: timeout waiting for ACK]
123][r...@hertz]:amanda/client/archive# cat amrecover.20101210142059.debug
Fri Dec 10 14:20:59 2010: amrecover: pid 275 ruid 0
amrecover get a timeout, you must check why the server did not respond.
Do hertz (128.210.3.201) in the name of the amanda server?
What's the inetd config for the amanda service on hertz?
What's in the amandad.*.debug file on hertz?
Any error in syslog?
Jean-Louis
McGraw, Robert P wrote:
Robert
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Friday, December 10, 2010 2:57 PM
To: McGraw, Robert P
Cc: 'amanda-users@amanda.org'
Subject: Re: having problem with amrecover under 3.2.0
amrecover get a timeout, you must check why
amanda-client.conf is not required. Maybe you added some config in it?
Jean-Louis
McGraw, Robert P wrote:
After a little more searching I found the problem.
Even thought the debug files did not say, it seem that I needed an
amanda-client.conf file in ~amandabackup/etc/amanda. Once I added
Hello,
I was surprised by the messahe from amrecover :
No index records for disk for specified date
If date correct, notify system administrator
I look in the debuf files on the server machine and I found the problem
but not the solution. The file amindexd.20070226214504.debug contains
the
Hello,
I lost today a disk at 18:30 containing my home directory ... I think,
the last save was at 13:00 I will restore it .
But I encounter a little problem with amrecover, here is the
screencopy :
AMRECOVER Version 2.5.1p3
hi i have some problems with the new framework of security of amanda
my server and my client is in the version 2.5.1p2
the amanda-client.conf on the client is this one
conf int # your config name
index_server backup # your amindexd server
tape_server backup # your amidxtaped server
#tapedev #
* Eric Doutreleau [EMAIL PROTECTED] [20070123 09:23]:
hi i have some problems with the new framework of security of amanda
my server and my client is in the version 2.5.1p2
the amanda-client.conf on the client is this one
conf int # your config name
index_server backup # your amindexd
Jean-Francois Malouin a écrit :
* Eric Doutreleau [EMAIL PROTECTED] [20070123 09:23]:
hi i have some problems with the new framework of security of amanda
my server and my client is in the version 2.5.1p2
the amanda-client.conf on the client is this one
conf int # your config name
* Eric Doutreleau [EMAIL PROTECTED] [20070123 11:48]:
Jean-Francois Malouin a écrit :
* Eric Doutreleau [EMAIL PROTECTED] [20070123 09:23]:
hi i have some problems with the new framework of security of amanda
my server and my client is in the version 2.5.1p2
the amanda-client.conf on
Gene Heskett a écrit :
On Thursday 27 April 2006 07:56, Thomas Ginestet wrote:
[...]
501 Could not read config file /etc/amanda/DailySet/amanda.conf!
I've checked amindexd logs:
backup:/var/log/amanda# vi amindexd.20060426132954.debug
amindexd: debug 1 pid 12531 ruid 34 euid 34: start
On Friday 28 April 2006 05:31, Thomas Ginestet wrote:
Gene Heskett a écrit :
Thanks a lot Gene (and you too Matt ;-) ), your script is such a good
idea. Using the x bit was better ;-). But I have others problems like
the generated tapelist with owner amanda and group amanda (and
restricted
Hi list,
Thanks to your help, I've successful launched amcheck and amdump :-)
I've tried amrecover to check recovery too but some new problems occured.
After playing with access not allowed error, I'm still stuck on the
following one:
backup:/# amrecover DailySet
AMRECOVER Version 2.5.0.
On Wednesday 26 April 2006 08:38, Thomas Ginestet wrote:
Hi list,
Thanks to your help, I've successful launched amcheck and amdump :-)
I've tried amrecover to check recovery too but some new problems
occured.
After playing with access not allowed error, I'm still stuck on the
following one:
I am trying to restore a file on a machine other than the amanda server as
one part of our website was hacked on the weekend.
Here are the server details:
Server
NetBSD/i386 v2.0.2
Amanda 2.4.4p4
HP Surestore DAT24x6 (amanda tapes 1-5,
I have resolved this issue by adding:
amrecover_do_fsf yes
to my amanda.conf file.
I guess because amanda uses the no-rewind device the fsf is required to
correctly position the drive when multiple DLE's are on one tape.
Scott...
Scott R. Burns
NETCON Technologies Inc.
Suite 135 - 4474 Blakie
Whil using amrecover, if I don an ls in the amrecover shell, even if
there are only 2 lines, I have to press q to get rid of a pager
(END) prompt. Is this normal ? Is there a way to tell the pager that
my terminal has y lines ? If so, what is the correct way on solaris
AND on Linux.
Thanks !
Guy Dallaire wrote:
Whil using amrecover, if I don an ls in the amrecover shell, even if
there are only 2 lines, I have to press q to get rid of a pager
(END) prompt. Is this normal ? Is there a way to tell the pager that
my terminal has y lines ? If so, what is the correct way on solaris
AND on
On Wed, May 18, 2005 at 03:48:20PM +0200, Paul Bijnens wrote:
Guy Dallaire wrote:
Whil using amrecover, if I don an ls in the amrecover shell, even if
there are only 2 lines, I have to press q to get rid of a pager
(END) prompt. Is this normal ? Is there a way to tell the pager that
my
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On Sat, Jan 22, 2005 at 02:45:40PM +0100, Sören Edzen wrote:
Hi!
I have problem using amrecover. I get the following output:
amidxtaped: time 0.002: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv
On Fri, Feb 04, 2005 at 11:21:07AM -, soed2003 wrote:
--- In [EMAIL PROTECTED], Jon LaBadie [EMAIL PROTECTED] wrote:
On Sat, Jan 22, 2005 at 02:45:40PM +0100, Sören Edzen wrote:
Hi!
I have problem using amrecover. I get the following output:
amidxtaped: time 0.002: Ready
Hi!
I have problem using amrecover. I get the following output:
--Start output amrecover ---
[EMAIL PROTECTED]:/dist/tmp/amrecover amrecover zampo
AMRECOVER Version 2.4.4p4. Contacting server on zampo ...
220 zampo AMANDA index server (2.4.4p4) ready.
200 Access OK
Setting
Hi,
On Saturday 22 January 2005 14:45, Sören Edzen wrote:
I have problem using amrecover. I get the following output:
[...]
Extracting files using tape drive /dev/nst0 on host zampo.edzen.net.
Load tape zampo103 now
Continue [?/Y/n/s/t]?
EOF, check amidxtaped.timestamp.debug file
On Saturday 22 January 2005 15:07, Andreas Putzo wrote:
Hi,
On Saturday 22 January 2005 14:45, Sören Edzen wrote:
I have problem using amrecover. I get the following output:
Try mt -f /dev/rmt0 rewind before using amrecover or use
/dev/st0. I even tried to rewind the tape with mt before
On Sat, Jan 22, 2005 at 02:45:40PM +0100, Sören Edzen wrote:
Hi!
I have problem using amrecover. I get the following output:
amidxtaped: time 0.002: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = amrestore
argv[1] = -p
argv[2] = -h
argv[3] = /dev/nst0
argv[4
Hi,
i got a Problem with amrecover.
If I try to connect to the backupserver I got this error:
AMRECOVER Version 2.4.4p4. Contacting server on 192.168.10.95 ...
amrecover: cannot connect to 192.168.10.95: Connection refused
hosts on server looks like this:
127.0.0.1 backup
On Fri, 26 Nov 2004 at 1:45pm, Sebastian Kösters wrote
Hi,
i got a Problem with amrecover.
If I try to connect to the backupserver I got this error:
AMRECOVER Version 2.4.4p4. Contacting server on 192.168.10.95 ...
amrecover: cannot connect to 192.168.10.95: Connection refused
Are you
Joshua Baker-LePain
Gesendet: Freitag, 26. November 2004 13:50
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: Problem with amrecover
On Fri, 26 Nov 2004 at 1:45pm, Sebastian Kösters wrote
Hi,
i got a Problem with amrecover.
If I try to connect to the backupserver I got this error
On Fri, 26 Nov 2004 at 1:58pm, Sebastian Kösters wrote
Hi and thanks,
new .amandahosts entry on Server now looks like this:
localhost amanda
localhost.localdomain amanda
backup amanda
client1 root
what must an entry in /etc/hosts.allow look like?
amindexd, amidxtaped:
: Problem with amrecover
On Fri, 26 Nov 2004 at 1:58pm, Sebastian Kösters wrote
Hi and thanks,
new .amandahosts entry on Server now looks like this:
localhost amanda
localhost.localdomain amanda
backup amanda
client1 root
what must an entry in /etc/hosts.allow look like?
amindexd
On Fri, 26 Nov 2004 at 2:10pm, Sebastian Kösters wrote
I even got the same error ;(
host.allow:
amindexd, amidxtaped: 192.168.10.22
host.deny is empty
Those should both be hosts (/etc/hosts.allow, /etc/hosts.deny). Also,
check your firewall settings.
--
Joshua Baker-LePain
: Re: AW: AW: Problem with amrecover
On Fri, 26 Nov 2004 at 2:10pm, Sebastian Kösters wrote
I even got the same error ;(
host.allow:
amindexd, amidxtaped: 192.168.10.22
host.deny is empty
Those should both be hosts (/etc/hosts.allow, /etc/hosts.deny). Also,
check your firewall
Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im
Auftrag von Joshua Baker-LePain
Gesendet: Freitag, 26. November 2004 14:22
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: Problem with amrecover
On Fri, 26 Nov 2004 at 2:20pm, Sebastian Kösters wrote
On Fri, 26 Nov 2004 at 2:48pm, Sebastian Kösters wrote
Iptables is disabled on both.
/tmp/amanda on Server is empty
On Client there are 1260 files namend
Amandad.xxx.debug
Amrecover.xx.debug
Runtar.xxx.debug
Selfcheck._dir.x.debug
Sendbackup.xx.debug
: Problem with amrecover
On Fri, 26 Nov 2004 at 2:48pm, Sebastian Kösters wrote
Iptables is disabled on both.
/tmp/amanda on Server is empty
On Client there are 1260 files namend
Amandad.xxx.debug
Amrecover.xx.debug
Runtar.xxx.debug
Selfcheck._dir.x.debug
On Fri, 26 Nov 2004 at 3:39pm, Sebastian Kösters wrote
[EMAIL PROTECTED] data]# amrecover -C config -s 192.168.10.95 -t
192.168.10.95
AMRECOVER Version 2.4.3. Contacting server on 192.168.10.95 ...
220 backup AMANDA index server (2.4.4p4) ready.
200 Access OK
Setting restore date to today
...this Directory is empty.
-Ursprüngliche Nachricht-
Von: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 26. November 2004 15:42
An: Sebastian Kösters
Cc: [EMAIL PROTECTED]
Betreff: Re: AW: AW: AW: AW: AW: Problem with amrecover
On Fri, 26 Nov 2004 at 3:39pm, Sebastian Kösters
--On Wednesday, August 04, 2004 05:53:22 +0100 Alvaro Rosales [EMAIL PROTECTED]
wrote:
Hi guys,
I finally had been able to make backups with mi amanda sever, but when I try to run
amrecover I get this error:
amindexd: time 0.093: check failed: [access as operator not allowed from [EMAIL
Hi guys,
I finally had been able to make backups with mi amanda sever, but when I try to run
amrecover I get this error:
amindexd: time 0.093: check failed: [access as operator not allowed from [EMAIL
PROTECTED]
lim951-2.pe.yr.com.] amandahostsauth failed
My client .amandahosts file list the
Pascal,
I recall a similar error when the chg-disk changer wasn't setting the
data sym-link to the correct tape slot. Try using the command:
settape chg-disk
before doing the extract. It also worked if I manually ran the command:
amtape config slot N
in another window before doing the
Hi,
we are doing backups on hard drives, this part works fine, but when I
try to do a recover, I get this error EOF, check amidxtaped.debug
file. This is a except from my session:
[EMAIL PROTECTED] /]# /usr/sbin/amrecover -s .xx.cesart.com -t
.xx.cesart.com -C Hosting
AMRECOVER
On Tuesday 24 February 2004 15:36, Stefan G. Weichinger wrote:
Hi, Bram Metsch,
on Dienstag, 24. Februar 2004 at 15:19 you wrote to amanda-users:
the archive. Or am I too naive to assume they would read the docs?
I'm afraid you are right ;-)
Uwe.
Hi amanda-users,
I'm trying to do an amrecover as root (because amanda tells me to do so as
root... ) to recover files on the amanda-server itself, but I just get the
following error-message:
500 Access not allowed: [access as amanda not allowed from
[EMAIL PROTECTED] amandahostsauth failed
On Tue, 24 Feb 2004 15:09:52 +0100
[EMAIL PROTECTED] wrote:
Hi amanda-users,
I'm trying to do an amrecover as root (because amanda tells me to do so as
root... ) to recover files on the amanda-server itself, but I just get the
following error-message:
500 Access not allowed: [access as
Hi, Bram Metsch,
on Dienstag, 24. Februar 2004 at 15:19 you wrote to amanda-users:
BM On Tue, 24 Feb 2004 15:09:52 +0100
BM [EMAIL PROTECTED] wrote:
500 Access not allowed: [access as amanda not allowed from
[EMAIL PROTECTED] amandahostsauth failed
What am I doing wrong?
BM Hello Henning,
interface to the archives?
Regards,
Jack Parker
-Original Message-
From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 24, 2004 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem with amrecover
Hi, Bram Metsch,
on Dienstag, 24. Februar 2004 at 15:19 you
Hi, Jack,
on Dienstag, 24. Februar 2004 at 16:02 you wrote to amanda-users:
JP Personally, trying to browse the archives was rather difficult, I had to
JP visit each month's worth of posts and search within it - each time I
JP would find a dozen or more matches for my samba query, none of which
.
Regards,
Jack Parker
-Original Message-
From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 24, 2004 10:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem with amrecover
Hi, Jack,
on Dienstag, 24. Februar 2004 at 16:02 you wrote to amanda-users:
JP
On Tue, Feb 24, 2004 at 03:09:52PM +0100, [EMAIL PROTECTED] wrote:
Hi amanda-users,
I'm trying to do an amrecover as root (because amanda tells me to do so as
root... ) to recover files on the amanda-server itself, but I just get the
following error-message:
500 Access not allowed:
/aruseruntitled0375.htm,v
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0376.htm,v
4. and now the problem
amrecover pwd
/export/home/aotto/.REPOSITORY
amrecover ls
2003-10-10 TTWOS.CVS/
question? why does I not see the TacClient directory
mfg
aotto
Andreas Otto wrote:
07741131644/./aotto/.REPOSITORY/TacClient/etc/help/contents/aruseruntitled0368.htm,v
Symptom of tar version 1.13. Bad, very bad.
You need tar.1.13.19 at least, or better yet 1.13.25.
Get it from:
ftp://alpha.gnu.org/gnu/tar/tar-1.13.25.tar.gz
You can fix your indexes
Hi Nicki and others that replied.
Eventually found the problem after running strace amrecover which
indicated that it was refused connection to port 10082 (amandaidx). On
closer inspection I found that amandaidx (/etc/xinetd.d/amandaidx) was
actually disabled and this led to my problems.
If i am not mistaken, then .amandahosts must contain all of the
users machines that need access to that machine. So edit the
.amandahosts file on the BACKUP server and add lines to allow you to
access from the host recover-host with user root:
recover-host root
recover-host.domain root
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bartho Saaiman wrote:
I am trying to restore from a tape using amrecover. If I use
amrecover DailyBackup it says:
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
amrecover: cannot connect to localhost: Connection refused
This
Are backup and localhost different machines?
On Thursday 27 March 2003 10:17 pm, Bartho Saaiman wrote:
Hi All :)
I am trying to restore from a tape using amrecover. If I use
amrecover DailyBackup it says:
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
amrecover: cannot
Hi All :)
I am trying to restore from a tape using amrecover. If I use
amrecover DailyBackup it says:
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
amrecover: cannot connect to localhost: Connection refused
If I use the -s backup and/or -t backup I also get the same:
AMRECOVER
Joshua Baker-LePain schrieb:
Is the kernel to old?
Well, given that current is 2.4.20... It's also not a release kernel
(note the pre). I know nothing about Debian, but I'd strongly recommend
upgrading at least to a released 2.2 series kernel (it's actually still
maintained -- 2.2.25 just
Jon LaBadie wrote:
On Wed, Mar 19, 2003 at 02:18:21PM -0800, bao wrote:
As a followup to my previous mail.
I have repeatedly tried amrecover with different disks in my config. The
small disk (with original 760 MB, after backup ~380 MB) seems to let me
recover. The bigger disk (original ~ 18
On Thursday 20 March 2003 01:50 pm, bao wrote:
Jon, I have done some search for Linux file size. It says:
For ext2/3 and kernel 2.4.x, file size: ~ 4TB, filesystem size: ~ 1TB.
Obviously, it can't be the kernel that imposes this limit. Morever, I
was able to get a dump, using tar, of size 9
Hi list,
I'm experiencing the same problem.
My linux dist. is RH 8.0 kernel 2.4.18-19.8.0.
tar 1.13.25-8.
amdump was ok. amverify OK.
But when I ran amrecover, everything went fine until the extract step.
amanda seems to freeze.
Here's the result of amidxtaped and amrecover, respectively:
As a followup to my previous mail.
I have repeatedly tried amrecover with different disks in my config. The
small disk (with original 760 MB, after backup ~380 MB) seems to let me
recover. The bigger disk (original ~ 18 GB, after backup ~9 MB) always
hangs or reboots the server itself. No
On Wed, Mar 19, 2003 at 02:18:21PM -0800, bao wrote:
As a followup to my previous mail.
I have repeatedly tried amrecover with different disks in my config. The
small disk (with original 760 MB, after backup ~380 MB) seems to let me
recover. The bigger disk (original ~ 18 GB, after backup
Hi,
I try to recover files from a backup that I made a few minutes ago. Now
I get this error:
Load tape SkillDealBackupFull01 now
Continue? [Y/n]: y
EOF, check amidxtaped.debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
On Tue, 18 Mar 2003 at 4:17pm, Rainer Wiener wrote
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = /dev/nst0
argv[4] = ha-node01.berlin.skilldeal.com
argv[5] = ^hda2$
argv[6] = 20030317
amrestore: 0: skipping start of tape: date
On Tue, Mar 18, 2003 at 04:17:54PM +0100, Rainer Wiener wrote:
ha-node01.berlin.skilldeal.com.hda1.20030317.0
amrestore: strange amanda header: AMANDA: DILE 00030317
It should be: AMANDA: FILE 00030317 ...
^
I suspect a memory error on your tape server.
--
skilldeal - Ihr Partner für IT-Projekte
Rainer Wiener
skilldeal AG
Gitschiner Str. 94
D-10969 Berlin
Tel: +49 (0) 30 61 6558 -65/ -60
Fax: +49 (0) 30 61 6558 -66
E-Mail: [EMAIL PROTECTED]
Internet: http://www.skilldeal.com
This message may contain confidential and/or privileged
Hi,
when I try to recover files with am recover, I get a strange messages saying
that the directory / file I'm trying to restore is not in archive..
---
I'm using the following dump type in amanda.conf:
define
I'm guessing here, but it looks like the file name doesn't have a leading
slash in the archive, so you shouldn't put one in your 'add' command. Try
amrecover add lib
^ no slash here
and see what happens.
Good luck!
--Steve Lane /\
Doudna Lab \
On Thu, 19 Dec 2002 at 10:27am, John Oliver wrote
On Wed, Dec 18, 2002 at 07:39:48PM -0600, C. Bensend wrote:
Hey John,
Notice that the error message didn't say:
[access as amanda not allowed from root@backup]
or
[access as amanda not allowed from [EMAIL PROTECTED]] ?
On Thu, Dec 19, 2002 at 02:06:27PM -0500, Joshua Baker-LePain wrote:
Since you must run amrecover as root, .amandahosts needs an entry for that
as well as the entry for amanda for amdumps. You can leave them both in
there, so no need to edit the file every time.
So I can:
localhost root
You have to do everthing as the amanda user. But If you want to
restore something you have to be root. So you have to have access to
the client as root.
Ben
John Oliver wrote:
On Wed, Dec 18, 2002 at 07:39:48PM -0600, C. Bensend wrote:
Hey John,
Notice that the error message didn't
On Thu, 19 Dec 2002 at 11:08am, John Oliver wrote
On Thu, Dec 19, 2002 at 02:06:27PM -0500, Joshua Baker-LePain wrote:
Since you must run amrecover as root, .amandahosts needs an entry for that
as well as the entry for amanda for amdumps. You can leave them both in
there, so no need to
[root@backup DailySet1]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 backup AMANDA index server (2.4.2p2) ready.
500 Access not allowed: [access as amanda not allowed from
root@localhost] amandahostsauth failed
[root@backup DailySet1]# uname -a
Linux
On Wed, Dec 18, 2002 at 04:49:28PM -0800, John Oliver wrote:
[root@backup DailySet1]# amrecover
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 backup AMANDA index server (2.4.2p2) ready.
500 Access not allowed: [access as amanda not allowed from
root@localhost]
I've been trying to use amrecover to restore some files on my machine
(imagine that!), but so far
each time I try, I get this error on my amidxtaped.XX.debug file:
path = /usr/local/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = /dev/nst0
argv[4] = my.system.com
amrestore: 0: skipping start of tape: date 20020411 label Daily3
amrestore: 1: restoring my.system._usr.20020411.0
gzip: stdout: Connection timed out
...
I see that there is obviously some time out values concerning gzip, but I
don't know really what I am looking for.
Any suggestions?
This
On Thursday 09 August 2001 06:32, you wrote:
Extracting files using tape drive /dev/null on host backup.
Ummm, did you put the tape into the /dev/null device? No, I didn't
think so :-).
You need to use the -d flag on amrecover.
now why didnt i notice this right from the start i'm
On Tue, 7 Aug 2001 at 5:21pm, Arne Hueggenberg wrote
so as of late im running amanda to make nice shiny backups of all my servers.
Now ive tried for the first time to actually recover soemthing and lo and
behold, im running into problems.
Of course. I mean, what are you trying to do,
Extracting files using tape drive /dev/null on host backup.
Ummm, did you put the tape into the /dev/null device? No, I didn't
think so :-).
You need to use the -d flag on amrecover.
Arne Hueggenberg
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Hi,
so as of late im running amanda to make nice shiny backups of all my servers.
Now ive tried for the first time to actually recover soemthing and lo and
behold, im running into problems.
what im trying to do is recover a few files of one of the partitions i back up
whats happening is the
I keep getting the following error when I try to recover a file with
amrecover:
tcsh /usr/local/sbin/amrecover -C WeeklySet1 -d /dev/nst1 -s redbaron.physics.s
c.edu
AMRECOVER Version 2.4.2p1. Contacting server on
I keep getting the following error when I try to recover a file with
amrecover:
...
tar: Unexpected EOF on archive file
...
amrestore: 0: skipping start of tape: date 20010315 label WeeklySet112
amrestore: 1: skipping beauty._etc.20010315.0
amrestore: 2: restoring
83 matches
Mail list logo
