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
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
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
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
The latest amandad.debug file amandad.20100118181046.debug looks like this
amandad: debug 1 pid 25297 ruid 30318 euid 30318: start at Mon Jan 18 18:10:46
2010
Could not open conf file "/etc/amanda/amanda-client.conf": No such file or
directory
amandad: time 0.000: security_getdriver(name=BSD) re
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
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
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 backups of the same directory on
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 ran amrecover, it alwa
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 on the same day.
Hello,
during the amrestore I use settape to force /dev/nst0 instead of 0
(thanks Bernard).
And during recover, I answer no to :
owner/mode for '.'? [yn] n
I'll change the localhost inside the disklist
thanks to all !!
Frederic Medery
System Administrator
LexUM, University of Montreal
Bernard M
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
On Monday 28 June 2004 15:05, 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.0
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: time 0.001: bsd securit
Hi,
I've had the same message yesterday - I suggest you read the
/tmp/Amanda/amidxtaped..debug file and post the contents. In
my case amrecover was being passed a '0' for the tapedev instead of a
suitable tape device. This was because it was picking up my chg-scsi
setup, and mapping the device n
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
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.
>
...
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.
>
> Hi,
>
> Have you add the parameter tapedev "/dev/nrst0", to the amanda.conf ?
No, i´m using the "/dev/nst0" instead. What does this "r" letter stand for?
My version of amanda is amanda-2.4.2p2-9. I downloaded it from redhat.
bruno.
>
> I think my problem is not this. I think my problem
Hi,
Have you add the parameter tapedev "/dev/nrst0", to the amanda.conf ?
I think my problem is not this. I think my problem is the version of
amanda that i'm using ://
Thanks,
Roberto Samarone Araujo
> Hi Roberto,
>
> It´s happening to me also. What I need to avoid
Roberto Samarone Araújo (RSA) wrote:
amrecover Day -s myserver -t myserver -d /dev/st0
You need the nonrewinding device /dev/nst0.
Hi Roberto,
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. Are we missing
som
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
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
>
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
try to
read the tape (or chunk - fsf) with dd
dd
if=/dev/nst0 of=/ bs=1024 count=
where
NNN is greater than your backup job/disk entry
and
see what happens
i
restored some valueable tape (MTF formated) reading this way and putting the
pieces together.
regards,
gregor
On Saturday 19 July 2003 10:46, Freels, James D. wrote:
>Hello I have used amanda for a long time and have used the amrecover
>command to recover files/directories in the past without problems.
>Recently, I accidently deleted a large chunk of my home directory
> (you don't really want to know how t
--On Tuesday, May 27, 2003 10:47:11 -0500 Rebecca Pakish Crum <[EMAIL PROTECTED]> wrote:
Hello,
I setup Amanda for the first time and there is problem with
amrecover. Only some
of the directories and files dumped to the tape are listed in
amrecover. The
index files looks strange:
07664670563/./
0
> Hello,
>
> I setup Amanda for the first time and there is problem with
> amrecover. Only some
> of the directories and files dumped to the tape are listed in
> amrecover. The
> index files looks strange:
>
> 07664670563/./
> 07664670563/./.ICAClient/
> 07664670563/./.acrobat/
> 07664670563/
Hi there,
ive got a Problem with amrecover on an Debian GNU/Linux maschine.
amrecover reports:
No index records for disk for specified date
If date correct, notify system administrator
In debug files in /tmp i cant find any other Informations.Debugfile is
there but the informations are the same s
On Fri, 21 Mar 2003, Jon LaBadie wrote:
> On Thu, Mar 20, 2003 at 05:30:14PM -0800, Stephen Walton wrote:
> > I am trying a test amrestore of some files after amanda has run for a
> > bit on a RedHat 8.0 system with an HP DDS-3 6-tape changer. The backups
> > are fine, as are the automatic tape
On Thu, Mar 20, 2003 at 05:30:14PM -0800, Stephen Walton wrote:
> I am trying a test amrestore of some files after amanda has run for a
> bit on a RedHat 8.0 system with an HP DDS-3 6-tape changer. The backups
> are fine, as are the automatic tape changes; I can get at all of my
> backups manuall
On Wed, Jul 17, 2002 at 05:19:16PM +0100, Mark Snelling wrote:
> I have a problem with amanda. It seems to back up my filesystems ok (except
> for the warning below). When I run amrecover, 2 of the filesystems I can
> browse through, but /mnt/data has the directory structure and NO files?! Has
> a
ier Fernandez
Cc: [EMAIL PROTECTED]
Asunto: Re: Amrecover problem with gtar
On 21 Feb 2002 at 9:17am, [EMAIL PROTECTED] wrote
> Well, i have three machines with amanda, my disklist is
>
> sc01us0105/ user-tar
> sc01us
On 21 Feb 2002 at 9:17am, [EMAIL PROTECTED] wrote
> Well, i have three machines with amanda, my disklist is
>
> sc01us0105/ user-tar
> sc01us0103.cf.jcyl.es / user-tar
> sc01us0103.cf.jcyl.e
Ta works a treat :)
>>> [EMAIL PROTECTED] 02/11/02 15:02 PM >>>
>Exec'ing /sbin/vrestore with arguments:
>restore
>xbf
>2
>-
>...
I assume you're talking about Amanda 2.4.2p2? And if you run vrestore
with the 'b' and '2' args it will work?
I fixed this a while a
>Exec'ing /sbin/vrestore with arguments:
>restore
>xbf
>2
>-
>...
I assume you're talking about Amanda 2.4.2p2? And if you run vrestore
with the 'b' and '2' args it will work?
I fixed this a while ago and I think the following patch will take care
of it for you.
On 18 Jan 2002 at 12:23pm, [EMAIL PROTECTED] wrote
> does anybody know why??
> if i put a 0 in a entry disklist, does Amanda always make full dumps of
> level 0?
>
No. In the disklist, that 4th column is the spindle number, which can
help you control how many dumps run on a particular disk a
In regards to the problem I posted on Wednesday, I've determined that the
permissions/modes didn't get set because the restore did not complete
properly, however amanda did not complain. This happened at the point
amrecover was done reading/recovering all records from tape, and ready to
start on
On Fri, 24 Aug 2001, John W. Price wrote:
> disks, networks, and the like. If there is another disk I should be
> using, by all means let me know.
http://www-internal.alphanet.ch/archives/local/alphanet/divers/patches/amanda/DISASTER_RECOVERY/
supports Amanda recovery with direct (SCSI) or rem
John W. Price <[EMAIL PROTECTED]> wrote:
> amrecover: amandaidx/tcp unknown protocol
something is missing in your /etc/services.
Hi John!
> >extracting files using tapedrive 0 on host fileserver
> Note the "tapedrive 0". That can't possibly the path to your tape drive.
> You probably need to put "-d /dev/whatever" on the amrecover command line.
For security: My NoRewinding device ist /dev/nst0.
Shall i take this device
Am Mittwoch, 20. Juni 2001 22:17 schrieben Sie:
Hi John!
> >For security: My NoRewinding device ist /dev/nst0.
> >Shall i take this device for my changer?
> It should be the tape device name. Whether it is also your changer
> device name depends on your hardware.
> >When i take
> >amrecover -d
>For security: My NoRewinding device ist /dev/nst0.
>Shall i take this device for my changer?
It should be the tape device name. Whether it is also your changer
device name depends on your hardware.
>When i take
>amrecover -d /dev/nst0 or
>amrecover -d /dev/st0
>
>and i become the same error .
>Mar 13 13:23:55 nuthatch inetd[17275]: execv
>/usr/local/libexec/amindexd: No such file or directory
This seems pretty obvious to me. Do you have this file? Are all the
directories down to it searchable by the Amanda user listed in inetd.conf?
>RLE
John R. Jackson, Technical Software Special
"John R. Jackson" a écrit :
>
> >i still have a prob with amrecover in 2.4.2pl1
> >i never have this prob in previous version
> >
> >i run amanda server on a Sun sol 2.6
> >...
> >but when i try amrecover on the server , to restore a file or dir
> >i always have :
> >...
> >error reading tape: Co
>i still have a prob with amrecover in 2.4.2pl1
>i never have this prob in previous version
>
>i run amanda server on a Sun sol 2.6
>...
>but when i try amrecover on the server , to restore a file or dir
>i always have :
>...
>error reading tape: Connection reset by peer
Is there anything of int
>bsd security: remote host stanley.domain.org user root local user amanda
>...
>But on hall the common-src/security program produces the following :
>
>Remote user: amanda
You need to give ./security "root" as the remote user, not "amanda",
then see what it has to say.
I seem to recall seeing so
>I'm unable to see all backed up files while browsing trough the directorys
>via amrecover, but viewing the index-files manualy showed that the files are
>included in the backup...
Please send me (it's probably too big for the whole list) the contents
of the /tmp/amanda/amindexd*debug file that m
Hi Mirko and list,
> We set up a new amanda-2.4.2 backup-server, and right now I'm
> involved in testing
> the backup and recover with the server.
> While testing amrecover, some strange behaviour showed up:
> I'm unable to see all backed up files while browsing trough the
> directorys
> via amre
92 matches
Mail list logo
