,
I have been using amanda for some years without problems on Debian
systems using Debian packages of amanda. Now I found a problem. Most
probably because I changed to amgtar instead of normal gnu tar.
When restoring using amrecover, the add command is no longer
recursive. If I tag a directory
On Thursday, August 20, 2015 03:25:04 PM you wrote:
Hi,
I have been using amanda for some years without problems on Debian
systems using Debian packages of amanda. Now I found a problem. Most
probably because I changed to amgtar instead of normal gnu tar.
When restoring using amrecover
Hi,
I have been using amanda for some years without problems on Debian
systems using Debian packages of amanda. Now I found a problem. Most
probably because I changed to amgtar instead of normal gnu tar.
When restoring using amrecover, the add command is no longer
recursive. If I tag
to amgtar instead of normal gnu tar.
When restoring using amrecover, the add command is no longer
recursive. If I tag a directory, it only extracts the directory, not
is contents and children. For what I found until now, the amrecover
calls after a chain of calls, tar xcf - --files-from
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
I'm on the AMANDA backup server (v2.6.1p2), as root, in a working dir
with lots and lots of space. I was going to start by extracting some
files, (that were backed up from an AMANDA client,) to my working
directory on the server. I'm using vtapes if that matters.
When I run amrecover
On Mon, Apr 19, 2010 at 8:50 AM, Craig Constantine cr...@blkbx.com wrote:
AMRECOVER Version 2.6.1p2. Contacting server on localhost ...
I'd recommend just using auth local if you're communicating within
the localhost. BSDTCP is just too annoying to get right.
Dustin
--
Open Source Storage
Hi,
I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error message
when trying to extract files.
Could the reason be that I did the dumps before setting amrecover_changer ?
Here is my amanda.conf:
==
Jean-Louis Martineau wrote:
Andreas Kuntzagk wrote:
Hi,
I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error
message when trying to extract files.
Could the reason be that I did the dumps before setting
amrecover_changer
Edit chg-lib.sh and set MTX to the full path:
MTX=/opt/csw/sbin/mtx
Jean-Louis
Andreas Kuntzagk wrote:
Jean-Louis Martineau wrote:
Andreas Kuntzagk wrote:
Hi,
I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error
message
Andreas Kuntzagk wrote:
Hi,
I'm trying to do a (test) recovery using our SL24 changer.
I set amrecover_changer and use setdevice but still get an error
message when trying to extract files.
Could the reason be that I did the dumps before setting
amrecover_changer ?
no.
Look for message in
Hello list,
my English is bad, so I want your amnesty.
I used
-
CentOS release 5 (Final)
build: VERSION=Amanda-2.6.1b2
--
and I set the chg-disk in the amanda.conf.
First of all, I get the next error during extract on amrecover.
Yoshihiro Ishikawa wrote:
[r...@centos32 recover-src]# diff -uNr extract_list.c.o extract_list.c
--- extract_list.c.o2008-12-13 02:59:47.0 +0900
+++ extract_list.c 2009-02-06 12:40:52.0 +0900
@@ -1755,6 +1755,10 @@
if (file.program != NULL) {
if
On Fri, Sep 30, 2005 at 03:43:41PM -0700, Steve H wrote:
Ok, new error. I was going to use dd to get the image off, and try to restore
it in other ways. Unfortunately, that didn't work, I received this error:
[EMAIL PROTECTED] restore]# dd conv=noerror if=/dev/nst0 bs=32 skip=1
Steve H wrote:
One more item to note. I attempted to use amrestore instead of amrecover, and
after specifying the command:
amrestore -p /dev/nst0 host.domain /home/public | restore -ivf -
I got this error:
Input block size is 32
restore: Tape is not a dump tape
Error 32 (Broken pipe) offset
Steve H wrote:
in checking the Index files, I noticed that the actual
files had a different date on them (august 5th) while all the directories have
august 11th. This is bothering me because that shouldn't happen. Would Amanda
backup only the directories if the tape becomes full?
Actually,
Steve H wrote:
This time, I put the necessary tape in, and run amrecover and it will only
restore the directories. The files will not restore, and I keep getting the
error:
./laptopBackups/Documents and Settings/My Documents/
tar: Unexpected EOF in archive
tar: Error is not recoverable:
I have tried to restore other disks on that tape, and other tapes now. I can
use amrestore to pull files off the tape, but for some reason, when I try to
use restore on those files, it throws the error tape is not a dump tape. Any
idea what is causing this?
Also, I keep getting expected EOF
Ok, new error. I was going to use dd to get the image off, and try to restore
it in other ways. Unfortunately, that didn't work, I received this error:
[EMAIL PROTECTED] restore]# dd conv=noerror if=/dev/nst0 bs=32 skip=1
of=./restoreimage
dd: warning: working around lseek kernel bug for file
Guys,
I would appreciate some help with this one, as it's freaking me out. I have
been getting backups for a while now of a particular host and file system. I
have tested the recovery before and it worked great.
This time, I put the necessary tape in, and run amrecover and it will only
or reinstall it from sources
- Original Message -
From: Steve H [EMAIL PROTECTED]
To: amanda-users@amanda.org
Sent: Thursday, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one, as it's freaking me out. I
have
been
-users@amanda.org
Sent: Thursday, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one, as it's freaking me out. I
have
been getting backups for a while now of a particular host and file system.
I
have tested
, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one, as it's freaking me out. I
have
been getting backups for a while now of a particular host and file system.
I
have tested the recovery before and it worked great
Sent: Thursday, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one, as it's freaking me
out. I have
been getting backups for a while now of a particular host and file
system. I
have tested the recovery before
your tar RPM or reinstall it from sources
- Original Message -
From: Steve H [EMAIL PROTECTED]
To: amanda-users@amanda.org
Sent: Thursday, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one, as it's freaking me
out. I have
been getting backups for a while now of a particular host and
file system. I
have tested the recovery before and it worked great.
This time, I
: Steve H [EMAIL PROTECTED]
To: amanda-users@amanda.org
Sent: Thursday, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys,
I would appreciate some help with this one, as it's freaking me
out. I have
been getting backups for a while now
One more item to note. I attempted to use amrestore instead of amrecover, and
after specifying the command:
amrestore -p /dev/nst0 host.domain /home/public | restore -ivf -
I got this error:
Input block size is 32
restore: Tape is not a dump tape
Error 32 (Broken pipe) offset 32768+32768,
happens at the
tar point, then simple upgrade your tar RPM or reinstall it
from sources
- Original Message -
From: Steve H [EMAIL PROTECTED]
To: amanda-users@amanda.org
Sent: Thursday, September 29, 2005 5:42 PM
Subject: Using amrecover - strange happenings
Guys
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
Hi
I am backing up my linux servers with confirmed good backups onto
Amanda via Solaris 8, using L20 Tape device. Unfortunately I am quite
a few errors in the retore of files:
amrecover extract
Extracting files using tape drive /dev/rmt/0n on host insight.
The following tapes are needed:
TJ wrote:
warning: restore program for /sbin/dump not available.
amrecover couldn't exec: No such file or directory
problem executing restore
I have no experience whatsoever with backup type DUMP, but I'd venture
that message meant you don't have the corresponding restore program on
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
agora:/usr/local/sbin # amrecover -C DailySet1 -d /dev/nst0
AMRECOVER Version 2.4.4p2. Contacting server on agora ...
amrecover: Unexpected end of file, check amindexd*debug on server agora
is what I'm getting, when trying to recover files
Thorsten Bremer wrote:
schatten:/etc# amrecover Weekly
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date set to 2004-05-27.
Moin Paul,
Your localhost is actually called schatten, and I guess that a
dns lookup of schatten does not result in localhost, nor in 127.0.0.1.
Hmm... you're right :-)
Don't use localhost in disklist. It will bit you.
If you don't believe me, just just got bitten...
OK, I begin to
Thorsten Bremer wrote:
schatten:~# amrecover Weekly -s schatten.magnus
AMRECOVER Version 2.4.2p2. Contacting server on schatten.magnus ...
220 schatten AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2004-05-27)
200 Working date set to 2004-05-27.
200 Working date
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
I am using amanda server 2.4.2p2-1 to backup a remote
solaris system. Backups of the remote client appear to
be running properly - index records for the remote
host reflect a complete list of directories/files. The
amount of data backed up (for full backups)
corresponds with directory sizes on
Hello everyone!
I am having a bit of trouble using amrecover and am hoping that someone can
see what is going wrong.
As root, I run amrecover, then select a few files to test restoring. This
is what I get:
sbs|amvr: /home/amv amrecover Gemini
AMRECOVER Version 2.4.2p2. Contacting server
What do you get if you do this:
gzip -dc /var/amanda/daily/index/santafe/_opv_rnd/20010522_1.gz | head
If you get a list of names and each line starts with a large number
rather than a directory path, you've got a broken version of GNU tar.
What version are you using? Anything other than
Hi
I having problems using `amrecover` to find files to restore:
on one of my client machines (santafe) I have a filesystem mounted
on '/opv'. The actual backup directory is one of the subdirectories
below '/opv/rnd'. When I start `amrecover` on santafe woth $CWD being
'/opv/rnd' I get
root@sundev1:/etc# amrecover
AMRECOVER Version 2.4.1p1. Contacting server on sundev1.corp.walid.com ...
220 sundev1 AMANDA index server (2.4.1p1) ready.
200 Access OK
Setting restore date to today (2000-11-07)
200 Working date set to 2000-11-07.
200 Config set to daily.
501 No index
44 matches
Mail list logo
