On Wednesday 14 December 2016 20:15:30 Debra S Baddorf wrote:
> > On Dec 14, 2016, at 6:04 PM, Gene Heskett
> > wrote:
> >
> > On Wednesday 14 December 2016 18:25:23 Debra S Baddorf wrote:
> >>> On Dec 14, 2016, at 4:51 PM, Gene Heskett
> >>> wrote:
> >>>
> >>> Greetings all;
> >>>
> >>> I added
> On Dec 14, 2016, at 6:04 PM, Gene Heskett wrote:
>
> On Wednesday 14 December 2016 18:25:23 Debra S Baddorf wrote:
>
>>> On Dec 14, 2016, at 4:51 PM, Gene Heskett
>>> wrote:
>>>
>>> Greetings all;
>>>
>>> I added another machine machine to my disklist about a month back,
>>> and now I need
On Wednesday 14 December 2016 18:25:23 Debra S Baddorf wrote:
> > On Dec 14, 2016, at 4:51 PM, Gene Heskett
> > wrote:
> >
> > Greetings all;
> >
> > I added another machine machine to my disklist about a month back,
> > and now I need to do a full recovery just to see if I've blown a pin
> > on
On Wednesday 14 December 2016 18:25:23 Debra S Baddorf wrote:
> > On Dec 14, 2016, at 4:51 PM, Gene Heskett
> > wrote:
> >
> > Greetings all;
> >
> > I added another machine machine to my disklist about a month back,
> > and now I need to do a full recovery just to see if I've blown a pin
> > on
> On Dec 14, 2016, at 4:51 PM, Gene Heskett wrote:
>
> Greetings all;
>
> I added another machine machine to my disklist about a month back, and
> now I need to do a full recovery just to see if I've blown a pin on its
> gpio.
>
> The machine is a raspberrypi 3b.
>
> But even though I have
Greetings all;
I added another machine machine to my disklist about a month back, and
now I need to do a full recovery just to see if I've blown a pin on its
gpio.
The machine is a raspberrypi 3b.
But even though I have added it to the only_from line in
the /etc/xinetd.d/amanda file, and rest
On Mon, Apr 02, 2012 at 18:36:28 +0800, Yogesh Hasabnis wrote:
> Our AMANDA backup configuration consisted of AMANDA 2.5.2p1 on RHEL3
> as the backup server and AMANDA 2.6.1p2 on RHEL6 as the AMANDA client.
> Recently,the RHEL 3 OS on amanda backup server crashed for some reason
> and I had to inst
On 04/02/2012 09:57 AM, Yogesh Hasabnis wrote:
Hello Jean-Louis,
The log..* files have gone with the older OS that crashed.
Does that mean I wont be able to use "amrecover" for any of my
existing backups ?
You wont be able to use "amrecover" for any of your existing backups.
Henceforward, d
On 04/02/2012 09:38 AM, Yogesh Hasabnis wrote:
Warning: no log files found for tape FULLBACK-19 written 2012-03-12
Warning: no log files found for tape FULLBACK-05 written 2012-02-07
Warning: no log files found for tape FULLBACK-18 written 2012-01-13
Warning: no log files found for tape FULLBACK-
Martineau
To: Yogesh Hasabnis
Cc: "amanda-users@amanda.org"
Sent: Monday, April 2, 2012 6:29 PM
Subject: Re: amrecover problem with amanda 2.6.1p2
Do 'amadmin find' list all dump?
Do the tapelist file list all tapes?
Do you have all the log..* files?
Do 'amch
Do 'amadmin find' list all dump?
Do the tapelist file list all tapes?
Do you have all the log..* files?
Do 'amcheck -s ' print errors or warnings?
Jean-Louis
On 04/02/2012 06:36 AM, Yogesh Hasabnis wrote:
Hi All,
Our AMANDA backup configuration consisted of AMANDA 2.5.2p1 on RHEL3
as the ba
Do 'amadmin find' list all dump?
Do the tapelist file list all tapes?
Do you have all the log..* files?
Do 'amcheck -s ' print errors or warnings?
Jean-Louis
On 04/02/2012 06:36 AM, Yogesh Hasabnis wrote:
Hi All,
Our AMANDA backup configuration consisted of AMANDA 2.5.2p1 on RHEL3
as the ba
Hi All,
Our AMANDA backup configuration consisted of AMANDA 2.5.2p1 on RHEL3 as the
backup server and AMANDA 2.6.1p2 on RHEL6 as the AMANDA client. Recently,the
RHEL 3 OS on amanda backup server crashed for some reason and I had to install
RHEL 5.5 OS on it. I had backed up my original amanda c
On Tue, 2010-03-16 at 14:22 -0500, Dustin J. Mitchell wrote:
> On Tue, Mar 16, 2010 at 1:55 PM, Dustin J. Mitchell wrote:
> > I'm sorry we don't have any good solid answers for you..
>
> Well, I can give a little more detail. I encrypted a backup with
> amcryptsimple, then changed the passphras
On Mon, 2010-03-15 at 14:10 -0500, Dustin J. Mitchell wrote:
> On Fri, Mar 12, 2010 at 5:57 AM, Matt Burkhardt
> wrote:
> > The "bad key" error doesn't mean the passphrase is wrong (that would be
> > "invalid passphrase"). It often means that the file you are decrypting is
> > corrupt. Was
On Tue, Mar 16, 2010 at 1:55 PM, Dustin J. Mitchell wrote:
> I'm sorry we don't have any good solid answers for you..
Well, I can give a little more detail. I encrypted a backup with
amcryptsimple, then changed the passphrase and tried to decrypt it. I
got:
gpg: decryption failed: Bad session
On Tue, Mar 16, 2010 at 9:07 AM, Matt Burkhardt wrote:
> Since it's happened on almost every backup I've tried, I'm assuming I'm
> missing a very important piece of information - so I do think it's a bad key
> or I'm missing the public key. I have another computer that is backed up the
> exact
On Fri, Mar 12, 2010 at 5:57 AM, Matt Burkhardt wrote:
> The "bad key" error doesn't mean the passphrase is wrong (that would be
> "invalid passphrase"). It often means that the file you are decrypting is
> corrupt. Was the file you are decrypting encrypted with a passphrase only or
> with a
On Fri, 2010-03-12 at 08:21 +0100, muessi wrote:
> Dustin J. Mitchell schrieb:
> > I'm not terribly familiar with crypto, but presumably you need the
> > secret key to decrypt. Hopefully that was stored somewhere other than
> > on the old computer?
> >
> > BTW, once you get amfetchdump working,
Dustin J. Mitchell schrieb:
> I'm not terribly familiar with crypto, but presumably you need the
> secret key to decrypt. Hopefully that was stored somewhere other than
> on the old computer?
>
> BTW, once you get amfetchdump working, amrecover will work fine.
> Amrecover just doesn't show error
On Thu, Mar 11, 2010 at 2:52 PM, Matt Burkhardt wrote:
>
> I did amfetchdump and on the first run through it was complaining about
> /var/lib/amanda/.am_passphrase missing, so I created it and put in the
> correct passphrase, now I'm getting this:
>
> amfetchdump: slot 10: time 20100205150231 la
Thanks for being so quick Dustin...
I did amfetchdump and on the first run through it was complaining
about /var/lib/amanda/.am_passphrase missing, so I created it and put in
the correct passphrase, now I'm getting this:
amfetchdump: slot 10: time 20100205150231 label laptops-0010 (exact label m
Amrecover tends to hide the actual error messages, since they occur on
the server.
Try doing a recovery using amfetchdump, instead. I suspect that
there's a missing encryption key or something preventing the recovery.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
It finally happened. My trusty old Toshiba Tecra completely lost it
this morning - just a blinking amber on light, no screen, no prompt, no
beeps. So I'm trying to pull the files off amanda and get them onto my
other PC - a Dell - but I'm running into a problem. I have a feeling
it's because
you for your help.
Thanks a lot,
Yogesh
--- On Mon, 1/18/10, Jean-Louis Martineau wrote:
From: Jean-Louis Martineau
Subject: Re: amrecover problem
To: "Yogesh Hasabnis"
Cc: amanda-users@amanda.org
Date: Monday, January 18, 2010, 8:53 PM
The recover protocol changed, you are still
The recover protocol changed, you are still configured for the old
protocol, you can use it with the 'amoldrecover' command.
But you can also configure the server for the new protocol.
Yogesh Hasabnis wrote:
Hi All,
We are using amanda 2.5.2p1 in our setup. The backup server and the
client ar
ut=0, fromaddr=0xd2dd90)
amrecover: time 0.094: (sockaddr_in *)0xd2dd90 = { 2, 10080, 192.168.100.19 }
amrecover: time 0.094: security_close(handle=0x86c2988, driver=0xd1bcc0 (BSD))
--- On Mon, 1/18/10, Yogesh Hasabnis wrote:
From: Yogesh Hasabnis
Subject: Re: amrecover problem
To: "Yogesh Hasabni
00: security_handleinit(handle=0x83a7210, driver=0xd7ecc0
(BSD))
amandad: time 0.001: accept recv REQ pkt:
<<<<<
SERVICE amindexd
OPTIONS features=9ffe00;auth=bsd;
>>>>>
amandad: time 0.001: amindexd: invalid service
amandad: time 0.001: sending NAK pk
Hi All,
We are using amanda 2.5.2p1 in our setup. The backup server and the client are
the same machine and the OS used RHEL 3. As I am trying to do an "amrecover -s
-t " to recover a backed up folder, I get the following
error:
# amrecover -C tendaily -t -s -d /dev/nst0
AMRECOVER Version
Robert,
Did you configure with --with-maxtapeblocksize? What is the value?
What is your blocksize setting in the tapetype?
Did the tape labeled D5 was written with the same blocksize?
Can you try the attached patch.
Jean-Louis
McGraw, Robert P. wrote:
Jean-Louis,
Here is the amidxta
What's in the amidxtaped.*.debug on the server?
Jean-Louis
McGraw, Robert P. wrote:
My configuration:
build: VERSION="Amanda-2.5.2-20070530"
BUILT_DATE="Thu May 31 09:14:26 EDT 2007"
BUILT_MACH="SunOS zorn.math.purdue.edu 5.10 Generic_118833-03 sun4u
sparc SUNW,Sun-Fire-280R"
CC="/pkgs/g
My configuration:
build: VERSION="Amanda-2.5.2-20070530"
BUILT_DATE="Thu May 31 09:14:26 EDT 2007"
BUILT_MACH="SunOS zorn.math.purdue.edu 5.10 Generic_118833-03 sun4u
sparc SUNW,Sun-Fire-280R"
CC="/pkgs/gcc-3.4.3/bin/gcc"
CONFIGURE_COMMAND="'./configure' 'CC=/pkg
Jean-Louis
There seems to be a problem with solaris 10 /bin/patch. I downloaded the
patch program from sunfreeware and ran the patch and it worked as expected.
I will have to send in a bug report to Sun.
A added the diff file you sent for the amrecover problem and it resolved
this problem
In a few amrecover tests I did yesterday I ran into this problem:
(amanda-2.5.2-20070523) on irix-6.5
amrecover> pwd
/bigdisk
amrecover> add sylvain/Stereopsis/pet/campagna_francois_-BG1_199903260955.mnc
File sylvain/Stereopsis/pet/campagna_francois_-BG1_199903260955.mnc
doesn't exist in directory
The regex library you use is more strict than mine.
Try the attached patch.
Jean-Louis
McGraw, Robert P. wrote:
I am forwarding this from my partner SA. Is this a know problem with a fix
or something newly discovered?
Thanks
Robert
-Original Message-
From: Chapman Flack [mailt
On Wed, May 30, 2007 at 01:41:17PM -0400, McGraw, Robert P. wrote:
> > amrecover> cd jflack
> > amrecover: regex "/jflack/$/": unknown regex error
> >
> > ... and amrecover exits out to the shell.
Interesting -- I get the same regex, but my regex library (in libc) doesn't
complain about it. I ha
I am forwarding this from my partner SA. Is this a know problem with a fix
or something newly discovered?
Thanks
Robert
> -Original Message-
> From: Chapman Flack [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 30, 2007 12:03 PM
> To: Robert McGraw
> Subject: amrecover
>
>
> Robert
On Wednesday 21 March 2007, Jean-Louis Martineau wrote:
>Steven,
>
>It is a known bug, it is already fixed in the CVS tree.
>Try the latest 2.5.1p3 snapshot from
>http://www.zmanda.com/community-builds.php
>
>You can also try to use wildcard: cd Directory?with?space
>
>Jean-Louis
>
>Steven Atkinson
Steven,
It is a known bug, it is already fixed in the CVS tree.
Try the latest 2.5.1p3 snapshot from
http://www.zmanda.com/community-builds.php
You can also try to use wildcard: cd Directory?with?space
Jean-Louis
Steven Atkinson wrote:
Hi,
I am using amanda-2.5.1p3 with DLEs backed up usin
Hi,
I am using amanda-2.5.1p3 with DLEs backed up using tar. When a
directory name contains a space it does not seem possible to cd into
it to recover files. This is a copy of the output received when
trying to change into a directory called "Directory with space".
amrecover> ls
2007-03-21 aman
Jeffrey,
It's a known bug, it was fix on 2007-09-19
You can try the attached patch or upgrade your server to 2.5.1p3.
Jean-Louis
jeffrey d anderson wrote:
I'm running amanda 2.5.0p2 on a RHEL3 server with numerous clients of various
flavors. I recently needed to perform a recover and found a
Jeffrey,
If amrecover doesn't fsf to the correct file, you can disable the fsf by
setting
'amrecover_do_fsf off' in your amanda.conf file.
What is the 'file' reported by 'amadmin find client.lbl.gov
hda1' ? is it 37 or 38?
Could you send me the amrecover.*.debug, amidxtaped.*.debug files?
I'm running amanda 2.5.0p2 on a RHEL3 server with numerous clients of various
flavors. I recently needed to perform a recover and found a problem.
amrecover functions fine. I sethost and setdisk and setdate and it shows me
what appears to be the correct list of available files. It finds the
Eric Doutreleau wrote:
Kevin Till a écrit :
Axel Seguin wrote:
Obviously the client tries to contact the server on port 10080,
shouldn't it try to reach the server on port 10082? How can I change
that?
In ~/.amandahosts on the client I have :
amdump
Any help would be greatly appreciated
Kevin Till a écrit :
Axel Seguin wrote:
Obviously the client tries to contact the server on port 10080,
shouldn't it try to reach the server on port 10082? How can I change
that?
In ~/.amandahosts on the client I have :
amdump
Any help would be greatly appreciated.
Hi,
there is an update
Axel Seguin wrote:
Obviously the client tries to contact the server on port 10080,
shouldn't it try to reach the server on port 10082? How can I change
that?
In ~/.amandahosts on the client I have :
amdump
Any help would be greatly appreciated.
Hi,
there is an update on Amanda 2.5.1. To e
Hi everyone,
I have installed amanda. amchack works fine as well as amdump. When I
try to restore using amrecover I get :
AMRECOVER Version 2.5.1p2. Contacting server on kinshasa ...
[request failed: timeout waiting for ACK]
In the logs on the client
(/tmp/amanda/client/amrecover..de
On Tue, Aug 02, 2005 at 09:46:02AM -0400, Lei Zhong wrote:
> Thanks for the help. Settape only sets the server/device. I read the
> man pages several times. I couldn't find info about how to specify
> which tape you want to restore from in amrecover. Just in case some
> people didn't read my pr
Thanks for the help. Settape only sets the server/device. I read the
man pages several times. I couldn't find info about how to specify
which tape you want to restore from in amrecover. Just in case some
people didn't read my previous emails. Here is what I was trying to do.
I did four full ba
On Mon, Aug 01, 2005 at 08:50:11PM -0400, Gene Heskett wrote:
> On Monday 01 August 2005 17:00, Lei Zhong wrote:
> >Can somebody help me with the amrecover problem I posted earlier? I
> > was testing my amanda config. I don't use tape changer. I did
> > four full bac
On Monday 01 August 2005 17:00, Lei Zhong wrote:
>Can somebody help me with the amrecover problem I posted earlier? I
> was testing my amanda config. I don't use tape changer. I did
> four full backups of the same directory on four different tapes on
> the same day. When I
On Mon, Aug 01, 2005 at 05:00:10PM -0400, Lei Zhong wrote:
> Can somebody help me with the amrecover problem I posted earlier? I was
> testing my amanda config. I don't use tape changer. I did four full
> backups of the same directory on four different tapes o
Can somebody help me with the amrecover problem I posted
earlier? I was testing my amanda config. I don’t use tape
changer. I did four full backups of the same directory on four different tapes
on the same day. When I ran amrecover, it always asked for the first full
backup tape. How
Thanks Alexander and Paul!
it was the bad version of tar. Updating to 1.15.1 fixed everything
and my files are now restored.
Thanks!
Cameron Matheson
On 6/22/05, Paul Bijnens <[EMAIL PROTECTED]> wrote:
> Cam wrote:
> > Hi,
> >
> > On 6/22/05, Paul Bijnens <[EMAIL PROTECTED]> wrote:
> >
> >>Ther
Cam wrote:
Hi,
On 6/22/05, Paul Bijnens <[EMAIL PROTECTED]> wrote:
There should also be a debug file named "amidxtaped.DATETIME.debug"
containing the details of the amrestore command used to extract
the data from the tape.
thanks! i checked that file and it was warning me about the tape bei
Hi,
On 6/22/05, Paul Bijnens <[EMAIL PROTECTED]> wrote:
> There should also be a debug file named "amidxtaped.DATETIME.debug"
> containing the details of the amrestore command used to extract
> the data from the tape.
thanks! i checked that file and it was warning me about the tape being
rewound
Cam wrote:
Extracting files using tape drive /dev/nst0 on host db1.
Load tape DailySet1017 now
Continue [?/Y/n/s/t]? y
EOF, check amidxtaped..debug file on db1.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue
Hi,
so now amrecover works as far as switching the tape is concerned, but
i am still unable to recover files :(. here's the output:
amrecover> extract
Extracting files using tape drive /dev/nst0 on host db1.
The following tapes are needed: DailySet1017
Restoring files into directory /tmp
Continu
Hi,
I'm sure the tape was loaded because I checked it by running amtape and the
files are restored when I comment out the tapedev "0". Please have a look at
the amidxtaped* file attached. It seems that parameter for the tape device argv
[7]="0" is not what amrecover wants.
Thank you very much,
On Thursday 08 July 2004 14:52, Eric Schnoebelen wrote:
> [EMAIL PROTECTED] writes:
> - I've got the following error when I run amrecover:
> -
> - -
> - amrecover> add dumpdates
> - Added /etc/dumpdates
> - amrecover> extract
> -
> - Extracting files using tape drive 0 on host typha.nmsu.ed
[EMAIL PROTECTED] writes:
- I've got the following error when I run amrecover:
-
- -
- amrecover> add dumpdates
- Added /etc/dumpdates
- amrecover> extract
-
- Extracting files using tape drive 0 on host typha.nmsu.edu.
- The following tapes are needed: Biology-1
-
- Restoring files int
Hi,
I've got the following error when I run amrecover:
-
amrecover> add dumpdates
Added /etc/dumpdates
amrecover> extract
Extracting files using tape drive 0 on host typha.nmsu.edu.
The following tapes are needed: Biology-1
Restoring files into directory /home/cngo
Continue [?/Y/n]? y
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Frederic Medery
Sent: 28 June 2004 15:58
To: Mailing List Amanda User
Subject: amrecover problem
Hello,
When I tried to recover a folder called "my folder" (with space
Frederic Medery wrote:
I had the same prob (the 0 problem). But it's still not working (other
reason). Here is my
amidxtaped... :
amidxtaped: debug 1 pid 1566 ruid 33 euid 33: start at Mon Jun 28
13:21:51 2004
amidxtaped: version 2.4.4p1
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: t
ping the device name (0)
>> instead of the device type (/dev/nst0) to amrestore. I worked
>> around this but using the settape /dev/nst0 to pick up the tape
>> device directly and avoid the /dev/sg devices altogether which
>> amrestore couldn't cope with.
>>
>>Reg
vices altogether which amrestore couldn't cope with.
Regards,
Bernard McAuley
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Frederic Medery
Sent: 28 June 2004 15:58
To: Mailing List Amanda User
Subject: amrecover problem
He
; -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
> On Behalf Of Frederic Medery
> Sent: 28 June 2004 15:58
> To: Mailing List Amanda User
> Subject: amrecover problem
>
> Hello,
>
> When I tried to recover a folder called "my folder&
Hello,
When I tried to recover a folder called "my folder" (with space in it, I
don't know if this could be the problem). I have for time to time,
Segment Fault.
and when I try to recover (when I don't receive the error) with the
extract command :
Load tape weekly-05 now
Continue [?/Y/n/s/t]?
Jim Summers wrote:
# unencrypted username/password pairs for authentication.
service amidxtape
{
# flags = REUSE
socket_type = stream
wait= no
user= bin
Add:
group = disk
server = /usr/loca
On Mon, 2003-11-03 at 10:22, Paul Bijnens wrote:
> Jon LaBadie wrote:
>
> > On Mon, Nov 03, 2003 at 09:43:30AM -0500, Joshua Baker-LePain wrote:
> >
> >>On 3 Nov 2003 at 8:37am, Jim Summers wrote
> >>
> >>
> >>>===
> >>>amrestore: could not open /dev/nst0: Permission denied
> >>
> >>What
Jon LaBadie wrote:
On Mon, Nov 03, 2003 at 09:43:30AM -0500, Joshua Baker-LePain wrote:
On 3 Nov 2003 at 8:37am, Jim Summers wrote
===
amrestore: could not open /dev/nst0: Permission denied
What does 'ls -l /dev/nst0' say? And what user and group runs amanda on
the server?
amrecover
On Monday 03 November 2003 09:48, Jim Summers wrote:
>On Mon, 2003-11-03 at 08:43, Joshua Baker-LePain wrote:
>> On 3 Nov 2003 at 8:37am, Jim Summers wrote
>>
>> > ===
>> > amrestore: could not open /dev/nst0: Permission denied
>>
>> What does 'ls -l /dev/nst0' say? And what user and group
On Mon, Nov 03, 2003 at 08:48:46AM -0600, Jim Summers wrote:
> On Mon, 2003-11-03 at 08:43, Joshua Baker-LePain wrote:
> > On 3 Nov 2003 at 8:37am, Jim Summers wrote
> >
> > > ===
> > > amrestore: could not open /dev/nst0: Permission denied
> >
> > What does 'ls -l /dev/nst0' say? And wh
On Monday 03 November 2003 09:37, Jim Summers wrote:
>Hello List,
>
>I am attempting to recover a file using amrecover. I am running
>amrecover on the amanda server and want to recover the file to a
> temp directory and then manually put it back in place. This is
> amanda 2.4.4p1 on a Redhat9 sys
On Mon, Nov 03, 2003 at 09:43:30AM -0500, Joshua Baker-LePain wrote:
> On 3 Nov 2003 at 8:37am, Jim Summers wrote
>
> > ===
> > amrestore: could not open /dev/nst0: Permission denied
>
> What does 'ls -l /dev/nst0' say? And what user and group runs amanda on
> the server?
amrecover, i
On Mon, 2003-11-03 at 08:43, Joshua Baker-LePain wrote:
> On 3 Nov 2003 at 8:37am, Jim Summers wrote
>
> > ===
> > amrestore: could not open /dev/nst0: Permission denied
>
> What does 'ls -l /dev/nst0' say? And what user and group runs amanda on
> the server?
Sorry I forgot to include t
Jim Summers wrote:
Hello List,
I am attempting to recover a file using amrecover. I am running
amrecover on the amanda server and want to recover the file to a temp
directory and then manually put it back in place. This is amanda
2.4.4p1 on a Redhat9 system. I have found references to EOF erro
> amrestore: could not open /dev/nst0: Permission denied
> amidxtaped: time 0.010: amrestore terminated normally with status: 2
> amidxtaped: time 0.010: rewinding tape ...
> amidxtaped: time 0.010: tape_rewind: tape open: /dev/nst0: Permission
> denied
> amidxtaped: time 0.010: pid 31743 finish ti
On 3 Nov 2003 at 8:37am, Jim Summers wrote
> ===
> amrestore: could not open /dev/nst0: Permission denied
What does 'ls -l /dev/nst0' say? And what user and group runs amanda on
the server?
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Hello List,
I am attempting to recover a file using amrecover. I am running
amrecover on the amanda server and want to recover the file to a temp
directory and then manually put it back in place. This is amanda
2.4.4p1 on a Redhat9 system. I have found references to EOF errors but
not anything
Hi Jon,
>
> On Mon, Sep 22, 2003 at 08:42:53AM +0200, Markus Dohmann wrote:
> > Hello amada-users lists,
> >
> > we are using Amanda 2.4.4 (Solaris 8) with GNU tar (1.13.25) and a
> > tape archive (Overland LoaderXpress SDLT). Everything works fine except
> > for the setting of the recovery date
On Mon, Sep 22, 2003 at 08:42:53AM +0200, Markus Dohmann wrote:
> Hello amada-users lists,
>
> we are using Amanda 2.4.4 (Solaris 8) with GNU tar (1.13.25) and a
> tape archive (Overland LoaderXpress SDLT). Everything works fine except
> for the setting of the recovery date of directories.
>
...
Hello amada-users lists,
we are using Amanda 2.4.4 (Solaris 8) with GNU tar (1.13.25) and a
tape archive (Overland LoaderXpress SDLT). Everything works fine except
for the setting of the recovery date of directories.
I restored a directory tree an a client with amrecvoer.
Bruno Negrão wrote:
> It´s happening to me also. What I need to avoid it it, on the server
> machine, run the command mt -f /dev/nst0 rewind
>
> This obligates the tape to rewind itself and makes the backup
> recovering work.
>
> Seriously, I can´t believe that a thing like this should be needed.
>
gt; See, if i want to recover my backup is obvious that the tape should rewind
> itself first, right?
> >
> > Bye,
> > Bruno Negrão.
> >
> > - Original Message -----
> > From: "Roberto Samarone Araújo (RSA)" <[EMAIL PROTECTED]>
> > T
parameter?
> See, if i want to recover my backup is obvious that the tape should rewind
itself first, right?
>
> Bye,
> Bruno Negrão.
>
> - Original Message -
> From: "Roberto Samarone Araújo (RSA)" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
Roberto Samarone Araújo (RSA) wrote:
amrecover Day -s myserver -t myserver -d /dev/st0
You need the nonrewinding device /dev/nst0.
ember 18, 2003 9:06 PM
Subject: amrecover problem
> Hi,
>
>
> I'm using a Red Hat E.S. client and a Debian Linux server. I made a
> backup perfect. I did the backup, I tried to test it but, when I tried the
> command:
>
> amrecover Day -s myserver -t my
Hi,
I'm using a Red Hat E.S. client and a Debian Linux server. I made a
backup perfect. I did the backup, I tried to test it but, when I tried the
command:
amrecover Day -s myserver -t myserver -d /dev/st0
The server returned me:
amrecover: Unexpected server end
Yogish wrote:
> 'amrecover -C normal -s borkerserver'
> 501, no index records for the host brokerserver, Invalid?
> amrecover> sethost localhost
> no index records for host :localhost Invalid?
I would expect another errormessage here:
"No index records for host: %s. Have you enabled indexing?"
I
hi,
when you type amrercover -s borkerserver... it means that borkerserver
is where the index information are.
I saw in your amanda.conf that your index file are stored in
infofile "/var/lib/amanda/normal/curinfo" # database filename
logdir "/var/lib/amanda/normal" # log dir
Hi
The exact commands that I ran were
'amrecover -C normal -s borkerserver'
501, no index records for the host brokerserver,
Invalid?
amrecover> sethost localhost
no index records for host :localhost
Invalid?
Samething for brokerserver also.
I have attached my amanda.conf and disklist. Please
Title: Re: amrecover problem: need help/advice
The problem was my scsi card driver.
Reviewing my kernel configuration files, between 2.4.14 and 2.4.15 (now running 2.4.21), I switched to the new sym53c8xx_2 driver. I recompiled my kernel with the older NCR53c7,8xx driver (there is also an
--On Thursday, July 24, 2003 12:10:28 -0600 Yogish <[EMAIL PROTECTED]> wrote:
> Hi
> I am trying to get into amrecover on the server, but it says the
> connection refused. I typed 'amrecover -C normal -s localhost'. I have
> also entered the name of the host on .amandahosts. Can anyone suggest
>
Hi
I am trying to get into amrecover on the server,
but it says the connection refused. I typed 'amrecover -C normal -s localhost'.
I have also entered the name of the host on .amandahosts. Can anyone suggest why
this problem might be occuring. I am not sure if amanda uses the ethernet
inter
On Sunday 20 July 2003 18:31, Freels, James D. wrote:
>OK. I am learning from this. The number of 1k blocks on the first
>stored file on this tape is actually 384 and not 352. I should have
>looked at the taper output and not the dumper output. I issue the
>following multiple times:
>
>mt rewin
OK. I am learning from this. The number of 1k blocks on the first stored file on this tape is actually 384 and not 352. I should have looked at the taper output and not the dumper output. I issue the following multiple times:
mt rewind
mt -f=/dev/tape_norewind fsf 1
dd if=/dev/tape_norewin
OK. I went to the amdump log file and found that the first file should have 352 1k blocks written to the tape.
Then I issued
mt rewind
mt -f /dev/tape_norewind fsf 1
dd if=/dev/tape_norewind of=./first_file bs=1k count=352
Then the following was received at the console:
dd: reading `/dev/t
Gregor,
Thanks for responding. I also responded back to Gene Heskett with his suggestion and a little more information.
I would like to try this idea. How can I determine from the amanda log files ? Once I output the data from the tape to the drive, how do I conver it back to a .tar f
OK. I can do this. Let me summarize:
I have a tape labeled "fea12". This tape like all the tapes if all filesystems were backed up should contain 40 filesystems + front end + back end.
I issued the command
mt -f /dev/tape_norewind fsf 1
42 times before the end of tape occured and I recei
1 - 100 of 163 matches
Mail list logo
