Re: amrecover problem

[Gene Heskett]

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 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 restarted xinetd, and verified
> >>> that all the server_args=bsdtcp, this machine is still rejecting
> >>> the connection from amrecover on the pi:
> >>>
> >>> pi@raspberrypi:/ $ sudo amrecover -s coyote.coyote.den -t
> >>> coyote.coyote.den -d /amandatapes -C Daily
> >>> AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den
> >>> ... [request failed: EOF on read from coyote.coyote.den]
> >>>
> >>> What does this tell me I need to do next?
> >>>
> >>> Thank you all.
> >>>
> >>> Cheers, Gene Heskett
> >>> --
> >>> "There are four boxes to be used in defense of liberty:
> >>> soap, ballot, jury, and ammo. Please use in that order."
> >>> -Ed Howdershelt (Author)
> >>> Genes Web page 
> >>
> >> For an easy starter question:  does your server  (coyote, I take
> >> it?) include the PI node’s name in the  .amandahosts   file?   
> >> (And .k5amandahosts,  but I doubt if you use kerberos).
> >>
> >> Sample client line:
> >> .amandahosts:PI.my.domainroot amindexd amidxtaped
> >
> > Now I am between 2 other rocks
> > pi@raspberrypi:~ $ sudo amrecover -s coyote.coyote.den -t
> > coyote.coyote.den -C Daily
> > AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
> > NAK: user root from raspberrypi.coyote.den is not allowed to execute
> > the service amindexd: Please add the line "raspberrypi.coyote.den
> > root amindexd amidxtaped" to /home/amanda/.amandahosts on the server
> > pi@raspberrypi:~
>
> Well,  this one is what we just did.   However,  the file is rather
> picky about its permissions: (operator  is my backup account).  Oh, 
> and make sure the line reads exactly as requested, above. -rw--- 
> 1 operator root  2875 Aug 29 14:09 .amandahosts
>
> > $ amrecover -s coyote.coyote.den -t coyote.coyote.den -C
> > Daily
> > amrecover: critical (fatal): create debug
> > directory "/var/log/amanda/client/": Permission denied
> > amrecover: create debug directory "/var/log/amanda/client/":
> > Permission denied
> >
> > but the directory exists, with these permissions:
> > pi@raspberrypi:/var/log $ sudo ls -l amanda
> > total 8
> > drwx-- 2 backup backup 4096 Dec 14 03:03 amandad
> > drwx-- 3 backup backup 4096 Dec 14 18:50 client
> > Those perms don't look kosher, but thats what installing
> > amanda-common and amanda-client left me with.
>
> I gather these are where your logs are supposed to go?   (the default
> value is  /tmp/amanda,  I think) My permissions are,  where OPERATOR 
> is my backup  account.
>
> drwxr-xr-x.  7 operator root 4096 Dec 14 07:00 amanda
>
> What’s the permission on your  “/var/log”   itself  ?   If you don’t
> want *IT*  to be owned by  “backup” you may need to specify a
> directory under it./var/log/amanda  perhaps. Though,  if your
> backups are currently working,
> it’s probably okay.   It’s just the recover   that isn’t going,  right
> now.
>
> directories under that are created at need,  i think,  and come up
> with drwx--  2 operator root 4096 Dec 14 17:30 amandad
> drwx--  5 operator root 4096 Dec 14 17:30 client
> drwx--  2 operator root 4096 Dec 14 04:47 log.error
> drwx--  5 operator root 4096 Dec 14 17:30 server
> (you won’t get all until needed)
>   Those match yours.
>
> So, maybe I haven’t added anything new?Or did this prompt a
> change, above? Deb
>
> > Next?
> >
> > Thanks Deb.
> >
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page 

That one I did get sorted, I needed to put a "root" line in .amandahosts.

So I set it up to do a bare metal recovery of /.  But it crashed before 
even getting a good start. So now I have a trashed boot card, which is 
actually a 32Gb u-sd card about the size of a fingernail. I have the 
stuff here to rebuild it, or more cards.  But I am convinced I've blown 
a gpio pin on this pi, so I just ordered two more from MCM. $35 a copy. 
I've been beating my head on the floor over some crappy hookup jumpers 
that probably caused the blown pin, so if Digi-Key or the mailman, ever 
gets off the pot, I'll make me up a special jumper assembly that should 
stop the interconnect problem that started all this, once and for all. 
But not going to worry about it for a day o

Re: amrecover problem

[Debra S Baddorf]

> 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 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 restarted xinetd, and verified
>>> that all the server_args=bsdtcp, this machine is still rejecting the
>>> connection from amrecover on the pi:
>>> 
>>> pi@raspberrypi:/ $ sudo amrecover -s coyote.coyote.den -t
>>> coyote.coyote.den -d /amandatapes -C Daily
>>> AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
>>> [request failed: EOF on read from coyote.coyote.den]
>>> 
>>> What does this tell me I need to do next?
>>> 
>>> Thank you all.
>>> 
>>> Cheers, Gene Heskett
>>> --
>>> "There are four boxes to be used in defense of liberty:
>>> soap, ballot, jury, and ammo. Please use in that order."
>>> -Ed Howdershelt (Author)
>>> Genes Web page 
>> 
>> For an easy starter question:  does your server  (coyote, I take it?)
>> include the PI node’s name in the  .amandahosts   file?(And 
>> .k5amandahosts,  but I doubt if you use kerberos).
>> 
>> Sample client line:
>> .amandahosts:PI.my.domainroot amindexd amidxtaped
> 
> Now I am between 2 other rocks
> pi@raspberrypi:~ $ sudo amrecover -s coyote.coyote.den -t 
> coyote.coyote.den -C Daily 
> AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
> NAK: user root from raspberrypi.coyote.den is not allowed to execute the 
> service amindexd: Please add the line "raspberrypi.coyote.den root 
> amindexd amidxtaped" to /home/amanda/.amandahosts on the server
> pi@raspberrypi:~


Well,  this one is what we just did.   However,  the file is rather picky about 
its permissions:
   (operator  is my backup account).  Oh,  and make sure the line reads exactly 
as requested, above.
-rw---  1 operator root  2875 Aug 29 14:09 .amandahosts


> $ amrecover -s coyote.coyote.den -t coyote.coyote.den -C 
> Daily 
> amrecover: critical (fatal): create debug 
> directory "/var/log/amanda/client/": Permission denied
> amrecover: create debug directory "/var/log/amanda/client/": Permission 
> denied
> 
> but the directory exists, with these permissions:
> pi@raspberrypi:/var/log $ sudo ls -l amanda
> total 8
> drwx-- 2 backup backup 4096 Dec 14 03:03 amandad
> drwx-- 3 backup backup 4096 Dec 14 18:50 client
> Those perms don't look kosher, but thats what installing amanda-common 
> and amanda-client left me with.
> 

I gather these are where your logs are supposed to go?   (the default value is  
/tmp/amanda,  I think)
My permissions are,  where OPERATOR  is my backup  account.

drwxr-xr-x.  7 operator root 4096 Dec 14 07:00 amanda

What’s the permission on your  “/var/log”   itself  ?   If you don’t want *IT*  
to be owned by  “backup”
you may need to specify a directory under it./var/log/amanda  perhaps.
Though,  if your backups are currently working,
it’s probably okay.   It’s just the recover   that isn’t going,  right now.

directories under that are created at need,  i think,  and come up with
drwx--  2 operator root 4096 Dec 14 17:30 amandad
drwx--  5 operator root 4096 Dec 14 17:30 client
drwx--  2 operator root 4096 Dec 14 04:47 log.error
drwx--  5 operator root 4096 Dec 14 17:30 server
(you won’t get all until needed)
  Those match yours.

So, maybe I haven’t added anything new?Or did this prompt a change, above?
Deb


> Next?
> 
> Thanks Deb.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 
> 

Re: amrecover problem

[Gene Heskett]

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 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 restarted xinetd, and verified
> > that all the server_args=bsdtcp, this machine is still rejecting the
> > connection from amrecover on the pi:
> >
> > pi@raspberrypi:/ $ sudo amrecover -s coyote.coyote.den -t
> > coyote.coyote.den -d /amandatapes -C Daily
> > AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
> > [request failed: EOF on read from coyote.coyote.den]
> >
> > What does this tell me I need to do next?
> >
> > Thank you all.
> >
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page 
>
> For an easy starter question:  does your server  (coyote, I take it?)
> include the PI node’s name in the  .amandahosts   file?(And 
> .k5amandahosts,  but I doubt if you use kerberos).
>
> Sample client line:
> .amandahosts:PI.my.domainroot amindexd amidxtaped

Now I am between 2 other rocks
pi@raspberrypi:~ $ sudo amrecover -s coyote.coyote.den -t 
coyote.coyote.den -C Daily 
AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
NAK: user root from raspberrypi.coyote.den is not allowed to execute the 
service amindexd: Please add the line "raspberrypi.coyote.den root 
amindexd amidxtaped" to /home/amanda/.amandahosts on the server
pi@raspberrypi:~ $ amrecover -s coyote.coyote.den -t coyote.coyote.den -C 
Daily 
amrecover: critical (fatal): create debug 
directory "/var/log/amanda/client/": Permission denied
amrecover: create debug directory "/var/log/amanda/client/": Permission 
denied

but the directory exists, with these permissions:
pi@raspberrypi:/var/log $ sudo ls -l amanda
total 8
drwx-- 2 backup backup 4096 Dec 14 03:03 amandad
drwx-- 3 backup backup 4096 Dec 14 18:50 client
Those perms don't look kosher, but thats what installing amanda-common 
and amanda-client left me with.

Next?

Thanks Deb.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: amrecover problem

[Gene Heskett]

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 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 restarted xinetd, and verified
> > that all the server_args=bsdtcp, this machine is still rejecting the
> > connection from amrecover on the pi:
> >
> > pi@raspberrypi:/ $ sudo amrecover -s coyote.coyote.den -t
> > coyote.coyote.den -d /amandatapes -C Daily
> > AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
> > [request failed: EOF on read from coyote.coyote.den]
> >
> > What does this tell me I need to do next?
> >
> > Thank you all.
> >
> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> > soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page 
>
> For an easy starter question:  does your server  (coyote, I take it?)
> include the PI node’s name in the  .amandahosts   file?(And 
> .k5amandahosts,  but I doubt if you use kerberos).
>
It does now, thanks Deb. I'll be back if that doesn't work. :)

> Sample client line:
> .amandahosts:PI.my.domainroot amindexd amidxtaped


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: amrecover problem

[Debra S Baddorf]

> 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 added it to the only_from line in 
> the /etc/xinetd.d/amanda file, and restarted xinetd, and verified that 
> all the server_args=bsdtcp, this machine is still rejecting the 
> connection from amrecover on the pi:
> 
> pi@raspberrypi:/ $ sudo amrecover -s coyote.coyote.den -t 
> coyote.coyote.den -d /amandatapes -C Daily 
> AMRECOVER Version 3.3.6. Contacting server on coyote.coyote.den ...
> [request failed: EOF on read from coyote.coyote.den]
> 
> What does this tell me I need to do next?
> 
> Thank you all.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 


For an easy starter question:  does your server  (coyote, I take it?)
include the PI node’s name in the  .amandahosts   file?(And  
.k5amandahosts,  but I doubt if you use kerberos).

Sample client line:
.amandahosts:PI.my.domainroot amindexd amidxtaped

Re: amrecover problem with amanda 2.6.1p2

[Nathan Stratton Treadway]

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 install RHEL 5.5 OS on it. I had backed up my original

On Mon, Apr 02, 2012 at 10:24:45 -0400, Jean-Louis Martineau wrote:
> On 04/02/2012 09:57 AM, Yogesh Hasabnis wrote:
> >Any workaround to handle the current situation which allows  me to
> >use "amrecover" ?
> You must recreate the log.* files.
> You can write a tool that read the tapes and create the log.* files.

Do you happen to have on tape a backup of the log files from your Amanda
server before it crashed?  If so, you could you use amrestore to
retrieve the log files (at least up through the day before that last
tape) and then install them into place on current server installation.

(I'm not sure about Red Hat, but on Debian/Ubuntu the Amanda log files
get stored under /var/log/amanda/[CONFIG]/, so as long as the /var
partition/directory tree was covered by your backups you should be able
to find the amanda log files on the tape)

Good luck.

Nathan




Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Re: amrecover problem with amanda 2.6.1p2

[Jean-Louis Martineau]

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, do I need to back up "log..*" files as well 
along with the /etc/amanda/* and /var/lib/amanda/*  to take care of 
such situations which may occur in the future ?


Isn't obvious when I wrote that they are required?
Beside the tapes, they are the more important part of the amanda database.

Any workaround to handle the current situation which allows  me to use 
"amrecover" ?

You must recreate the log.* files.
You can write a tool that read the tapes and create the log.* files.

Jean-Louis

Re: amrecover problem with amanda 2.6.1p2

[Jean-Louis Martineau]

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-17 written 2011-12-09
Warning: no log files found for tape FULLBACK-16 written 2011-11-04
Warning: no log files found for tape FULLBACK-01 written 2011-09-30
Warning: no log files found for tape FULLBACK-15 written 2011-08-31
Warning: no log files found for tape FULLBACK-11 written 2011-08-01
Warning: no log files found for tape FULLBACK-10 written 2011-06-30
Warning: no log files found for tape FULLBACK-08 written 2011-06-02
Warning: no log files found for tape FULLBACK-07 written 2011-05-02
Warning: no log files found for tape FULLBACK-04 written 2011-04-12



Where are the log..* files? They are required.
They must be in 'amgetconf  logdir'.

Without them, amanda do not know what is on the tapes.

You can use amrestore to read the tape and do a manual recovery.

Jean-Louis

Re: amrecover problem with amanda 2.6.1p2

[Yogesh Hasabnis]

Hello Jean-Louis,

Thanks for the reply.

The output of 'amadmin  find' is as follows:

$ amadmin fullback find
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-17 written 2011-12-09
Warning: no log files found for tape FULLBACK-16 written 2011-11-04
Warning: no log files found for tape FULLBACK-01 written 2011-09-30
Warning: no log files found for tape FULLBACK-15 written 2011-08-31
Warning: no log files found for tape FULLBACK-11 written 2011-08-01
Warning: no log files found for tape FULLBACK-10 written 2011-06-30
Warning: no log files found for tape FULLBACK-08 written 2011-06-02
Warning: no log files found for tape FULLBACK-07 written 2011-05-02
Warning: no log files found for tape FULLBACK-04 written 2011-04-12
Warning: no log files found for tape FULLBACK-14 written 2011-04-06
Warning: no log files found for tape FULLBACK-06 written 2011-04-06
Warning: no log files found for tape FULLBACK-03 written 2011-03-03
Warning: no log files found for tape FULLBACK-02 written 2010-12-14
Warning: no log files found for tape FULLBACK-13 written 2009-12-02
Warning: no log files found for tape FULLBACK-12 written 2008-08-05
Warning: no log files found for tape FULLBACK-09 written 2007-10-31

No dump to list

Yes the tapelist file does list all the tapes.
I don't have the log..* files

The 'amcheck -s ' prints something similar to what is given below:

$ amcheck -s 
"/etc/amanda//amanda.conf", line 82: warning: Keyword tapebufs is 
deprecated.
Amanda Tape Server Host Check
-
Holding disk /var/tmp/amanda: 122302464 KB disk space available, using 512 
KB as requested
read label `-15', date `20120214'.
NOTE: skipping tape-writable test
Tape -15 label ok
Server check took 0.210 seconds

(brought to you by Amanda 2.6.1p2)

Thanks in advance,
Yogesh




 From: Jean-Louis 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 '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 
> 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 configuration 
> directories under /etc/amanda and also the contents of the /var/lib/amanda 
> directory which contained the index data, before the OS reinstallation. I 
> have installed AMANDA 2.6.1p2 on this new OS on the backup server and 
> reconfigured it. I have also copied the directories containing the index data 
> under the appropriate directories (/var/lib/amanda).
> 
> Now when I try to use the command (from my AMANDA client)
> 
> # amrecover -C  -s  -t 
> 
> and use the proper "sethost", "setdisk" and "setdate" commands, I get the 
> error "No index records for disk for specified date".   The contents of the 
> amindexd*.debug under the /var/log/amanda/server/ are roughly as 
> follows:
> 
> 157832.225922: amindexd: > DATE 2012-04-02
> 157832.226013: amindexd: < 200 Working date set to 2012-04-02.
> 157832.226299: amindexd: > OISD /
> 157832.226341: amindexd: < 500 No dumps available on or before date 
> "2012-04-02"
> 
> Kindly suggest about what needs to be done to make the amrecover command work.
> 
> Thanks in advance,
> Yogesh Hasabnsi

Re: amrecover problem with amanda 2.6.1p2

[Jean-Louis Martineau]

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 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 configuration directories under /etc/amanda and also the 
contents of the /var/lib/amanda directory which contained the index 
data, before the OS reinstallation. I have installed AMANDA 2.6.1p2 on 
this new OS on the backup server and reconfigured it. I have also 
copied the directories containing the index data under the appropriate 
directories (/var/lib/amanda).


Now when I try to use the command (from my AMANDA client)

# amrecover -C  -s  -t 

and use the proper "sethost", "setdisk" and "setdate" commands, I get 
the error "No index records for disk for specified date".   The 
contents of the amindexd*.debug under the 
/var/log/amanda/server/ are roughly as follows:


157832.225922: amindexd: > DATE 2012-04-02
157832.226013: amindexd: < 200 Working date set to 2012-04-02.
157832.226299: amindexd: > OISD /
157832.226341: amindexd: < 500 No dumps available on or before 
date "2012-04-02"


Kindly suggest about what needs to be done to make the amrecover 
command work.


Thanks in advance,
Yogesh Hasabnsi

Re: amrecover problem with amanda 2.6.1p2

[Jean-Louis Martineau]

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 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 configuration directories under /etc/amanda and also the 
contents of the /var/lib/amanda directory which contained the index 
data, before the OS reinstallation. I have installed AMANDA 2.6.1p2 on 
this new OS on the backup server and reconfigured it. I have also 
copied the directories containing the index data under the appropriate 
directories (/var/lib/amanda).


Now when I try to use the command (from my AMANDA client)

# amrecover -C  -s  -t 

and use the proper "sethost", "setdisk" and "setdate" commands, I get 
the error "No index records for disk for specified date".   The 
contents of the amindexd*.debug under the 
/var/log/amanda/server/ are roughly as follows:


157832.225922: amindexd: > DATE 2012-04-02
157832.226013: amindexd: < 200 Working date set to 2012-04-02.
157832.226299: amindexd: > OISD /
157832.226341: amindexd: < 500 No dumps available on or before 
date "2012-04-02"


Kindly suggest about what needs to be done to make the amrecover 
command work.


Thanks in advance,
Yogesh Hasabnsi

Re: Amrecover problem - tar: This does not look like a tar archive

[Matt Burkhardt]

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 passphrase and tried to decrypt it.  I
> got:
> 
> gpg: decryption failed: Bad session key
> 
> Incidentally:
> Tue Mar 16 14:12:47 2010: amfetchdump: :
> process exited with status 0
> which makes it hard for amfetchdump (or amidxtaped, behind the scenes
> for amrecover) to know anything has gone wrong.  I suppose we should
> special-case a zero-length output as "failed"..
> 
> Some scribbling on the dumpfile on my vtape got gpg to say:
> 
> gpg: [don't know]: invalid packet (ctb=39)
> gpg: [don't know]: invalid packet (ctb=5d)
> gpg: [don't know]: invalid packet (ctb=2a)
> 
> which also doesn't match the error you saw.
> 
> dus...@euclid ~/code/amanda/t/amanda [master] $ gpg --version
> gpg (GnuPG) 2.0.11
> libgcrypt 1.4.4
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> Dustin
> 

I tried using the -l option on amfetchdump, but it still wants to be
able to decrypt the file before it dumps it


amfetchdump: slot 16: time 20100302090001 label laptops-0016 (exact label match)
Scanning volume laptops-0016 (slot 16)
amfetchdump: 1: restoring FILE: date 20100302090001 host 
mlb-laptop.imparisystems.local disk /home/mlb/ImpariSystems lev 1 comp .gz 
program /bin/tar crypt enc client_encrypt /usr/sbin/amcryptsimple 
client_decrypt_option -d
gpg: decryption failed: bad key


I'm working back through the files just to see if one of these hits - I
can't imagine using a separate passphrase on this set than on any other
groups.

Thanks for all the help

Matt Burkhardt
Impari Systems, Inc.

m...@imparisystems.com
http://www.imparisystems.com 
http://www.linkedin.com/in/mlburkhardt 
502 Fairview Avenue
Frederick, MD  21701
work (301) 682-7901
cell   (301) 802-3235

Re: Amrecover problem - tar: This does not look like a tar archive

[Matt Burkhardt]

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 the file you are decrypting encrypted with a passphrase only 
> > or with a public key?
> 
> What was the answer to this question?
> 
> Dustin
> 
> --
> Open Source Storage Engineer
> http://www.zmanda.com
> 

Dustin - thanks for checking up on me!

I've been trying to get an older version by getting the history and
selecting a full backup - so I do 


history
200- Dump history for config "laptops" host "mlb-laptop.imparisystems.local" 
disk /home/mlb/ImpariSystems
201- 2010-03-10-09-15-33 1 laptops-0004:5
201- 2010-03-09-10-40-06 1 laptops-0003:1
201- 2010-03-08-17-27-03 0 laptops-0002:2
201- 2010-03-06-12-03-37 0 laptops-0001:3
201- 2010-03-05-11-46-08 1 laptops-0020:2
201- 2010-03-05-09-57-36 0 laptops-0019:3
201- 2010-03-04-10-23-20 0 laptops-0018:4
201- 2010-03-03-09-00-02 1 laptops-0017:4
201- 2010-03-02-09-00-01 1 laptops-0016:1
201- 2010-02-28-12-13-07 1 laptops-0015:2
201- 2010-02-28-09-00-01 0 laptops-0014:4
201- 2010-02-25-09-00-01 1 laptops-0013:2
201- 2010-02-24-13-25-46 1 laptops-0012:2
201- 2010-02-24-09-00-02 0 laptops-0011:3
201- 2010-02-23-09-00-02 1 laptops-0007:2
201- 2010-02-11-09-00-02 0 laptops-0005:4
201- 2010-02-08-12-02-50 1 laptops-0006:4
201- 2010-02-07-09-00-02 1 laptops-0008:4
201- 2010-02-05-15-02-31 1 laptops-0010:4


In this example, I set the date to 2010-03-06 because I'm assuming that
0 means a full backup - and then I try to extract it and I get:


amrecover> setdate 2010-03-06
200 Working date set to 2010-03-06.
amrecover> ls
2010-03-06-12-03-37 YorkInvoice.txt.2008022237.log
2010-03-06-12-03-37 YorkInvoice.txt.2008022236.log
2010-03-06-12-03-37 YorkInvoice
2010-03-06-12-03-37 Q3IncomeStatement.20090222151410.log
2010-03-06-12-03-37 Q3IncomeStatement.20090222151409.xac
2010-03-06-12-03-37 Q3IncomeStatement.20090222150138.log
2010-03-06-12-03-37 Q3IncomeStatement.20090220101929.log
2010-03-06-12-03-37 Q3IncomeStatement.20090220101928.log
2010-03-06-12-03-37 Q3IncomeStatement
2010-03-06-12-03-37 OC_Beta_V4.0.pdf
2010-03-06-12-03-37 ImpariSystems.20100228163356.log
2010-03-06-12-03-37 ImpariSystems.20100228163355.xac
2010-03-06-12-03-37 ImpariSystems.20100228163244.log
2010-03-06-12-03-37 ImpariSystems.20100223123458.log
2010-03-06-12-03-37 ImpariSystems.20100223123457.xac
2010-03-06-12-03-37 ImpariSystems.20100223122643.log
2010-03-06-12-03-37 ImpariSystems.20100223122642.xac
2010-03-06-12-03-37 ImpariSystems.20100223121705.xac
2010-03-06-12-03-37 ImpariSystems.20100223121705.log
2010-03-06-12-03-37 ImpariSystems.20100223121146.log
2010-03-06-12-03-37 ImpariSystems.20100223121145.xac
2010-03-06-12-03-37 ImpariSystems.20100223120132.xac
2010-03-06-12-03-37 ImpariSystems.20100223120132.log
2010-03-06-12-03-37 ImpariSystems.20100223115324.log
2010-03-06-12-03-37 ImpariSystems.20100208164001.log
2010-03-06-12-03-37 ImpariSystems.20100208120210.log
2010-03-06-12-03-37 ImpariSystems.20100208120209.xac
2010-03-06-12-03-37 ImpariSystems.20100208115934.log
2010-03-06-12-03-37 ImpariSystems.20100207143430.log
2010-03-06-12-03-37 ImpariSystems.20100207143429.xac
2010-03-06-12-03-37 ImpariSystems.20100207142854.log
2010-03-06-12-03-37 ImpariSystems.20100207142853.xac
2010-03-06-12-03-37 ImpariSystems.20100207142327.log
2010-03-06-12-03-37 ImpariSystems.20100202141328.xac
2010-03-06-12-03-37 ImpariSystems.20100202141328.log
2010-03-06-12-03-37 ImpariSystems.20100202140825.log
2010-03-06-12-03-37 ImpariSystems.20100202140824.xac
2010-03-06-12-03-37 ImpariSystems.20100202135209.log
2010-03-06-12-03-37 ImpariSystems.20100202135208.xac
2010-03-06-12-03-37 ImpariSystems.20100202134629.log
2010-03-06-12-03-37 ImpariSystems
2010-03-06-12-03-37 Financials.20070602144258.log
2010-03-06-12-03-37 Financials.20070524123205.log
2010-03-06-12-03-37 Financials.20070524123203.log
2010-03-06-12-03-37 Financials
2010-03-06-12-03-37 EasyCom.pdf
2010-03-06-12-03-37 "Demo Site/"
2010-03-06-12-03-37 Backup.20090222151812.log
2010-03-06-12-03-37 Backup.20090222151811.log
2010-03-06-12-03-37 Backup
2010-03-06-12-03-37 2007msrsmfinal1.pdf
2010-03-06-12-03-37 .
amrecover> add ImpariSystems
Added file /ImpariSystems
amrecover> extract

Extracting files using tape drive changer on host ubuntu.imparisystems.local.
The following tapes are needed: laptops-0001

Restoring files into directory /home/mlb
Continue [?/Y/n]? y

Extracting files using tape drive changer on host ubuntu.imparisystems.local.
Load tape laptops-0001 now
Continue [?/Y/n/s/d]? y
tar: This does not look like a tar archive
tar: ./ImpariSystems: Not found in archive
tar: Exiting with failure status due to previous errors
Extractor child exited with status 2
amrecover> 


So I tried to retrieve an older version using amfetchdump - so 


amfetchdum

Re: Amrecover problem - tar: This does not look like a tar archive

[Dustin J. Mitchell]

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 key

Incidentally:
Tue Mar 16 14:12:47 2010: amfetchdump: :
process exited with status 0
which makes it hard for amfetchdump (or amidxtaped, behind the scenes
for amrecover) to know anything has gone wrong.  I suppose we should
special-case a zero-length output as "failed"..

Some scribbling on the dumpfile on my vtape got gpg to say:

gpg: [don't know]: invalid packet (ctb=39)
gpg: [don't know]: invalid packet (ctb=5d)
gpg: [don't know]: invalid packet (ctb=2a)

which also doesn't match the error you saw.

dus...@euclid ~/code/amanda/t/amanda [master] $ gpg --version
gpg (GnuPG) 2.0.11
libgcrypt 1.4.4
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: Amrecover problem - tar: This does not look like a tar archive

[Dustin J. Mitchell]

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 same way and I've had no problems recovering files for that one.

Hmm, so the first thing to figure out is, does an incorrect passphrase
generate that error?  If so, then I suspect that you've been
encrypting with a different passphrase than you're using for
decryption.  That this works for other systems points strongly in this
direction.

One thing you might do is amfetchdump's -l option, and then try
various manual invocations of gpg to decrypt it.  Maybe there are
other passphrases available?  You might also try stracing the gpg run.
 If it reads most of the way to the end before bailing out, then it is
more likely to be a corrupt file.  If it bails out at the very
beginning, then it's more likely to be a settings problem.

I'm sorry we don't have any good solid answers for you..

Dustin

--
Open Source Storage Engineer
http://www.zmanda.com

Re: Amrecover problem - tar: This does not look like a tar archive

[Dustin J. Mitchell]

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 public key?

What was the answer to this question?

Dustin

--
Open Source Storage Engineer
http://www.zmanda.com

Re: Amrecover problem - tar: This does not look like a tar archive

[Matt Burkhardt]

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, amrecover will work fine.
> > Amrecover just doesn't show error messages very well.  For example,
> > the message regarding am_passphrase was buried in the amidxtaped
> > logfile.
> > 
> 
> Well, I'm not quite sure we're talking bout the same thing, but when I use
> encryption, I get something like this in the dumpfiles:
> 
> To restore, position tape at start of file and run:
>   dd if= bs=32k skip=1 | /usr/sbin/amcrypt-ossl-asym -d | /bin/gzip 
> -dc |
> /bin/tar -xpGf - ...
> 
> 
> So far, having to restore something encrypted, I did use the above commands 
> and
> it worked just fine.
> 
> /Michael
> 

I'm using amcryptsimple instead of the encryption methodology that
you're using - but thanks for the feedback.

I'm also working with the gnupg folks and they've given me this feedback
- just also wanted to check and make sure that I'm reading the code
correctly.  I'll keep everyone in the loop



> > Long story short, I use amanda for my backups and I've been using
> encryptsimple for my backups.  My PC died completely, and I'm trying
> to get the backups onto another machine.  I've stepped through the
> programs and have found that it's calling gpg with 
> > 
> > gpg --batch --quiet --no-mdc-warning --decrypt --passphrase-fd 3
> 3 > 
> > I was under the impression that the passphrase (.am_passphrase) was
> just a clear text secret phrase.  However, the gpg call errors out
> with:
> > 
> > gpg: decryption failed: bad key
> 
> 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 public key? 


Here's the code that calls gpg for the encryption:


gpg --batch --no-secmem-warning --disable-mdc --symmetric --cipher-algo AES256 
--passphrase-fd 3  3http://www.imparisystems.com 
http://www.linkedin.com/in/mlburkhardt 
502 Fairview Avenue
Frederick, MD  21701
work (301) 682-7901
cell   (301) 802-3235

Re: Amrecover problem - tar: This does not look like a tar archive

[muessi]

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 messages very well.  For example,
> the message regarding am_passphrase was buried in the amidxtaped
> logfile.
> 

Well, I'm not quite sure we're talking bout the same thing, but when I use
encryption, I get something like this in the dumpfiles:

To restore, position tape at start of file and run:
dd if= bs=32k skip=1 | /usr/sbin/amcrypt-ossl-asym -d | /bin/gzip 
-dc |
/bin/tar -xpGf - ...


So far, having to restore something encrypted, I did use the above commands and
it worked just fine.

/Michael

-- 
Michael Müskens

Rule #18: It's better to seek forgiveness than ask permission.




signature.asc
Description: OpenPGP digital signature

Re: Amrecover problem - tar: This does not look like a tar archive

[Dustin J. Mitchell]

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 label laptops-0010 (exact label 
> match)
> Scanning volume laptops-0010 (slot 10)
> amfetchdump: 1: restoring FILE: date 20100205150231 host 
> mlb-laptop.imparisystems.local disk /home/mlb/Documents lev 1 comp .gz 
> program /bin/tar crypt enc client_encrypt /usr/sbin/amcryptsimple 
> client_decrypt_option -d
> gpg: decryption failed: bad key
>
> So I'm hunting around for the next steps - can I create a new key file 
> without the old computer?

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 messages very well.  For example,
the message regarding am_passphrase was buried in the amidxtaped
logfile.

Dustin

--
Open Source Storage Engineer
http://www.zmanda.com

Re: Amrecover problem - tar: This does not look like a tar archive

[Matt Burkhardt]

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 match)
Scanning volume laptops-0010 (slot 10)
amfetchdump: 1: restoring FILE: date 20100205150231 host 
mlb-laptop.imparisystems.local disk /home/mlb/Documents lev 1 comp .gz program 
/bin/tar crypt enc client_encrypt /usr/sbin/amcryptsimple client_decrypt_option 
-d
gpg: decryption failed: bad key


So I'm hunting around for the next steps - can I create a new key file
without the old computer?

On Thu, 2010-03-11 at 13:22 -0600, Dustin J. Mitchell wrote:

> 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



Matt Burkhardt
Impari Systems, Inc.

Customer Relationship Management Systems
We help you find and keep your best customers
m...@imparisystems.com
http://www.imparisystems.com 
http://www.linkedin.com/in/mlburkhardt 
502 Fairview Avenue
Frederick, MD  21701
work (301) 682-7901
cell   (301) 802-3235

Re: Amrecover problem - tar: This does not look like a tar archive

[Dustin J. Mitchell]

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

Re: amrecover problem

[Yogesh Hasabnis]

Hello Jean-Louis,
 
Thanks for the reply. I tried the amoldrecover command and it seems to be 
working. I will work on configuring the server to the new recover protocol as 
per your suggestion when I reach office tomorrow (I just tried the amoldrecover 
from my home) .
 
I am very grateful to 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 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 
> 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 2.5.2p1. Contacting server on  ...
> NAK: amindexd: invalid service, add 'amindexd' as argument to amandad
> 
Did you tried what it told you?
Add: server_args = -auth=bsd amdump amindexd amidxtaped
To the amanda service in xinetd

You can remove the amandaidx and amidxtaped service.
> 
> I had a amrecover a few months ago and it had worked very well. The only 
> thing that has changed recently is the amanda version. My 
> /etc/xinetd.d/amanda file looks as follows:
> service amanda
> {
>     disable     = no
>     socket_type = dgram
>     protocol    = udp
>     wait        = yes
>     user        = amandabackup
>     group       = disk
>     groups      = yes
>     server      = /usr/lib/amanda/amandad
> }
> service amandaidx
> {
>     disable     = no
>     socket_type = stream
>     protocol    = tcp
>     wait        = no
>     user        = amandabackup
>     group       = disk
>     groups      = yes
>     server      = /usr/lib/amanda/amindexd
> }
> 
> service amidxtape
> {
>     disable     = no
>     socket_type = stream
>     protocol    = tcp
>     wait        = no
>     user        = amandabackup
>     group       = disk
>     groups      = yes
>     server      = /usr/lib/amanda/amidxtaped
> }
> 
> Can I get suggestions about what could be the problem ?
> 
> Thanks in advance,
> Yogesh
> 
> 
Jean-Louis



  

Re: amrecover problem

[Jean-Louis Martineau]

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 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 2.5.2p1. Contacting server on  ...
NAK: amindexd: invalid service, add 'amindexd' as argument to amandad


Did you tried what it told you?
Add: server_args = -auth=bsd amdump amindexd amidxtaped
To the amanda service in xinetd

You can remove the amandaidx and amidxtaped service.


I had a amrecover a few months ago and it had worked very well. The 
only thing that has changed recently is the amanda version. My 
/etc/xinetd.d/amanda file looks as follows:

service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group   = disk
groups  = yes
server  = /usr/lib/amanda/amandad
}
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group   = disk
groups  = yes
server  = /usr/lib/amanda/amindexd
}

service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group   = disk
groups  = yes
server  = /usr/lib/amanda/amidxtaped
}

Can I get suggestions about what could be the problem ?

Thanks in advance,
Yogesh



Jean-Louis

Re: amrecover problem

[Yogesh Hasabnis]

And the latest amrecover.debug file reads as follows:


amrecover: debug 1 pid 24885 ruid 0 euid 0: start at Mon Jan 18 18:03:32 2010
Could not open conf file "/etc/amanda/amanda-client.conf": No such file or 
directory
Could not open conf file "/etc/amanda/tendaily/amanda-client.conf": No such 
file or directory
amrecover: debug 1 pid 24885 ruid 0 euid 0: rename at Mon Jan 18 18:03:32 2010
amrecover: time 0.001: security_getdriver(name=bsd) returns 0xd1bcc0
amrecover: time 0.001: security_handleinit(handle=0x86c2988, driver=0xd1bcc0 
(BSD))
amrecover: time 0.002: bind_portrange2: Skip port 593: Owned by http-rpc-epmap.
amrecover: time 0.002: bind_portrange2: Skip port 594: Owned by tpip.
amrecover: time 0.003:
 bind_portrange2: Skip port 595: Owned by cab-protocol.
amrecover: time 0.003: bind_portrange2: Skip port 596: Owned by smsd.
amrecover: time 0.003: bind_portrange2: Skip port 597: Owned by ptcnameservice.
amrecover: time 0.004: bind_portrange2: Skip port 598: Owned by sco-websrvrmg3.
amrecover: time 0.004: bind_portrange2: Skip port 599: Owned by acp.
amrecover: time 0.005: bind_portrange2: Skip port 600: Owned by ipcserver.
amrecover: time 0.005: bind_portrange2: Skip port 601: Owned by syslog-conn.
amrecover: time 0.006: bind_portrange2: Skip port 602: Owned by xmlrpc-beep.
amrecover: time 0.006: bind_portrange2: Skip port 603: Owned by idxp.
amrecover: time 0.006: bind_portrange2: Skip port 604: Owned by tunnel.
amrecover: time 0.007: bind_portrange2: Skip port 605: Owned by soap-beep.
amrecover: time 0.007: bind_portrange2: Skip port 606: Owned by urm.
amrecover: time 0.008: bind_portrange2: Skip port 607: Owned
 by nqs.
amrecover: time 0.008: bind_portrange2: Skip port 608: Owned by sift-uft.
amrecover: time 0.008: bind_portrange2: Skip port 609: Owned by npmp-trap.
amrecover: time 0.009: bind_portrange2: Skip port 610: Owned by npmp-local.
amrecover: time 0.009: bind_portrange2: Skip port 611: Owned by npmp-gui.
amrecover: time 0.009: bind_portrange2: Skip port 612: Owned by hmmp-ind.
amrecover: time 0.009: bind_portrange2: Skip port 613: Owned by hmmp-op.
amrecover: time 0.010: bind_portrange2: Skip port 614: Owned by sshell.
amrecover: time 0.010: bind_portrange2: Skip port 615: Owned by sco-inetmgr.
amrecover: time 0.079: bind_portrange2: Try  port 616: Available   - Success
amrecover: time 0.079: dgram_bind: socket 3 bound to 0.0.0.0.616
amrecover: time 0.080: dgram_send_addr(addr=0x86c29a8, dgram=0xd1dda4)
amrecover: time 0.080: (sockaddr_in *)0x86c29a8 = { 2, 10080, 192.168.100.19 }
amrecover: time
 0.080: dgram_send_addr: 0xd1dda4->socket = 3
amrecover: time 0.094: dgram_recv(dgram=0xd1dda4, timeout=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 Hasabnis" 
Date: Monday, January 18, 2010, 6:41 PM

And the latest amrecover.debug file reads as follows:


amrecover: debug 1 pid 24885 ruid 0 euid 0: start at Mon Jan 18 18:03:32 2010
Could not open conf file "/etc/amanda/amanda-client.conf": No such file or 
directory
Could not open conf file "/etc/amanda/tendaily/amanda-client.conf": No such 
file or directory
amrecover: debug 1 pid 24885 ruid 0 euid 0: rename at Mon Jan 18 18:03:32 2010
amrecover: time 0.001: security_getdriver(name=bsd) returns 0xd1bcc0
amrecover: time 0.001: security_handleinit(handle=0x86c2988, driver=0xd1bcc0 
(BSD))
amrecover: time 0.002: bind_portrange2: Skip port 593: Owned by http-rpc-epmap.
amrecover: time 0.002: bind_portrange2: Skip port 594: Owned by tpip.
amrecover: time 0.003:
 bind_portrange2: Skip port 595: Owned by cab-protocol.
amrecover: time 0.003: bind_portrange2: Skip port 596: Owned by smsd.
amrecover: time 0.003: bind_portrange2: Skip port 597: Owned by ptcnameservice.
amrecover: time 0.004: bind_portrange2: Skip port 598: Owned by sco-websrvrmg3.
amrecover: time 0.004: bind_portrange2: Skip port 599: Owned by acp.
amrecover: time 0.005: bind_portrange2: Skip port 600: Owned by ipcserver.
amrecover: time 0.005: bind_portrange2: Skip port 601: Owned by syslog-conn.
amrecover: time 0.006: bind_portrange2: Skip port 602: Owned by xmlrpc-beep.
amrecover: time 0.006: bind_portrange2: Skip port 603: Owned by idxp.
amrecover: time 0.006: bind_portrange2: Skip port 604: Owned by tunnel.
amrecover: time 0.007: bind_portrange2: Skip port 605: Owned by soap-beep.
amrecover: time 0.007: bind_portrange2: Skip port 606: Owned by urm.
amrecover: time 0.008: bind_portrange2: Skip port 607: Owned
 by nqs.
amrecover: time 0.008: bind_portrange2: Skip port 608: Owned by sift-uft.
amrecover: time 0.008: bind_portrange2: Skip port 609: Owned by npmp-trap.
amrecover: time 0.009: bind_portrange2: Skip port 610: Owned by npmp-local.
amrecover: time 0.009: bind_portrange2: Sk

Re: amrecover problem

[Yogesh Hasabnis]

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) returns 0xd7ecc0
amandad: version 2.5.2p1
amandad: time 0.000: build: VERSION="Amanda-2.5.2p1"
amandad: time 0.000:    BUILT_DATE="Wed Jun 6 19:55:12 PDT 2007"
amandad: time 0.000:    BUILT_MACH="Linux rhel3 2.4.21-40.EL #1 Thu Feb 2 
22:32:00 EST 2006 i686 athlon i386 GNU/Linux"
amandad: time 0.000:    CC="gcc"
amandad:
time 0.000:    CONFIGURE_COMMAND="'./configure'
'--build=i386-redhat-linux' '--prefix=/usr' '--bindir=/usr/bin'
'--sbindir=/usr/sbin' '--libexecdir=/usr/lib/amanda' '-
-datadir=/usr/share'
'--sysconfdir=/etc' '--sharedstatedir=/var/lib/amanda'
'--localstatedir=/var/lib/amanda' '--libdir=/usr/lib'
'--includedir=/usr/include' '--infodir=/usr/info' 
'--mandir=/usr/share/man'
'--with-gnutar=/bin/tar'
'--with-gnutar-listdir=/var/lib/amanda/gnutar-lists'
'--with-dumperdir=/usr/lib/amanda' '--with-index-server=localhost'
'--with-t
ape-server=localhost' '--with-user=amandabackup'
'--with-group=disk' '--with-owner=paddy' '--with-fqdn'
'--with-bsd-security' '--with-bsdtcp-security' '--with-bsdudp-security'
'--w
ith-ssh-security' '--with-assertions'"
amandad: time 0.000: paths: bindir="/usr/bin" sbindir="/usr/sbin"
amandad: time 0.000:    libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
amandad: time
 0.000:    AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
amandad: time 0.000:    CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
amandad: time 0.000:    RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
amandad: time 0.000:    RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF
amandad: time 0.000:    XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF 
VXRESTORE=UNDEF
amandad: time 0.000:    SAMBA_CLIENT="/usr/bin/smbclient" GNUTAR="/bin/tar"
amandad: time 0.000:    COMPRESS_PATH="/bin/gzip" 
UNCOMPRESS_PATH="/bin/gzip"
amandad: time 0.000:    LPRCMD="/usr/bin/lpr" MAILER="/usr/bin/Mail"
amandad: time
 0.000:    listed_incr_dir="/var/lib/amanda/gnutar-lists"
amandad: time 0.000: defs:  DEFAULT_SERVER="localhost" 
DEFAULT_CONFIG="DailySet1"
amandad: time 0.000:    DEFAULT_TAPE_SERVER="localhost" HAVE_MMAP 
NEED_STRSTR
amandad: time 0.000:    HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID 
ASSERTIONS
amandad: time 0.000:    DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY 
RSH_SECURITY
amandad: time 0.000:    USE_AMANDAHOSTS CLIENT_LOGIN="amandabackup" 
FORCE_USERID
amandad: time 0.000:    HAVE_GZIP COMPRESS_SUFFIX=".gz" 
COMPRESS_FAST_OPT="--fast"
amandad: time 0.000:    COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
amandad: time 0.000: dgram_recv(dgram=0xd80da4,
 timeout=0, fromaddr=0xd90d90)
amandad: time 0.000: (sockaddr_in *)0xd90d90 = { 2, 925, 192.168.100.19 }
amandad: time 0.000: 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 pkt:
<
ERROR amindexd: invalid service, add 'amindexd' as argument to amandad
>
amandad: time 0.001: dgram_send_addr(addr=0x83a7230, dgram=0xd80da4)
amandad: time 0.001: (sockaddr_in *)0x83a7230 = { 2, 925, 192.168.100.19 }
amandad: time 0.001: dgram_send_addr: 0xd80da4->socket = 0
amandad: time 0.001: security_close(handle=0x83a7210, driver=0xd7ecc0 (BSD))
amandad: time 29.998: pid 25297 finish time Mon Jan 18 18:11:16 2010


--- On Mon, 1/18/10, Yogesh Hasabnis  wrote:

From: Yogesh Hasabnis 
Subject: amrecover problem
To: amanda-users@amanda.org
Date: Monday, January 18, 2010, 6:03 PM

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 2.5.2p1. Contacting server on  ...
NAK: amindexd: invalid service, add 'amindexd' as argument to amandad

I had a amrecover a few months ago and it had worked very well. The only thing 
that has changed recently is the amanda version. My /etc/xinetd.d/amanda file 
looks as follows:
service amanda
{
    disable = no
    socket_type = dgram
    protocol    =
 udp
    wait    = yes
    user    = amandabackup
    group   = disk
    groups  = yes
    server  = /usr/lib/amanda/amandad
}
service amandaidx
{
    disable = no
    socket_type = stream
    protocol    = tcp
    wait    = no
    user    = amandabackup
    group   = disk
    groups  = yes
    server  =
 /usr/lib/amanda/amindexd
}

service amidxtape
{
    disable = no
    socket_type = stream
    protocol    = tcp
    w

Re: amrecover problem with spaces in directory names

[Gene Heskett]

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 wrote:
>> 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 amanda-2.5.1p2.tar.gz
>> 2007-03-21 "Directory with space/"
>> 2007-03-21 .ssh/
>> amrecover> cd "Directory with space/"
>> Invalid directory - "Directory with space/"
>> amrecover> cd "Directory with space"
>> Invalid directory - "Directory with space"
>> amrecover> cd Directory with space
>> Invalid directory - Directory
>> syntax error
>> amrecover> cd Directory\ with\ space
>> "Directory\" is not a valid shell wildcard pattern: trailing backslash
>> (\)
>> syntax error
>>
>> It is possible to add and extract the directory. This makes the
>> problem inconvenient rather than crippling.
>>
>> amrecover> add "Directory with space"
>> Added dir "/atn/Directory with space/" at date 2007-03-21
>> amrecover> extract
>>
>> Extracting files using tape drive /dev/nst0 on host
>> backup-01.fhs.local. The following tapes are needed: Archive02-002
>>
>> Restoring files into directory /var/spool/amanda/tmp
>> Continue [?/Y/n]? Y
>>
>> Extracting files using tape drive /dev/nst0 on host
>> backup-01.fhs.local. Load tape Archive02-002 now
>> Continue [?/Y/n/s/t]? Y
>>
>> Does anyone have any pointers as to where to start looking to fix this
>> issue.
>>
>> Thanks
>> Steve Atkinson
>>
>> --
>> Deputy Network Manager
>> Fallibroome High School
>> UK.

Have you moved the snapshot location?  I've been getting mine from your 
umontreal site since forever...  But I notice a 'low level of activity' 
there in recent weeks.



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Newlan's Truism:
An "acceptable" level of unemployment means that the 
government economist to whom it is acceptable still has a job.

Re: amrecover problem with spaces in directory names

[Jean-Louis Martineau]

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 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 amanda-2.5.1p2.tar.gz
2007-03-21 "Directory with space/"
2007-03-21 .ssh/
amrecover> cd "Directory with space/"
Invalid directory - "Directory with space/"
amrecover> cd "Directory with space"
Invalid directory - "Directory with space"
amrecover> cd Directory with space
Invalid directory - Directory
syntax error
amrecover> cd Directory\ with\ space
"Directory\" is not a valid shell wildcard pattern: trailing backslash 
(\)

syntax error

It is possible to add and extract the directory. This makes the
problem inconvenient rather than crippling.

amrecover> add "Directory with space"
Added dir "/atn/Directory with space/" at date 2007-03-21
amrecover> extract

Extracting files using tape drive /dev/nst0 on host backup-01.fhs.local.
The following tapes are needed: Archive02-002

Restoring files into directory /var/spool/amanda/tmp
Continue [?/Y/n]? Y

Extracting files using tape drive /dev/nst0 on host backup-01.fhs.local.
Load tape Archive02-002 now
Continue [?/Y/n/s/t]? Y

Does anyone have any pointers as to where to start looking to fix this 
issue.


Thanks
Steve Atkinson

--
Deputy Network Manager
Fallibroome High School
UK.

Re: amrecover problem

[Kevin Till]

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.



Hi,
there is an update on Amanda 2.5.1. To enable different auth 
mechanism, amandad needs to run on the server. And it will start 
amindexd and amidxtaped accordingly.


Please see 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication 





well i have seen that but i have a lot of old amanda configuration and i 
would like to use "amoldrecover".


amoldrecover will try to connect to port 10082 on the server. This particular server must 
run amindexd and amidxtaped in the Amanda 2.5.0 format.


See:
http://wiki.zmanda.com/index.php/Quick_start#Configuring_xinetd_on_server

Hope this helps.
--
Thank you!
Kevin Till

Amanda documentation: http://wiki.zmanda.com
Amanda forums:http://forums.zmanda.com

Re: amrecover problem

[Eric Doutreleau]

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 on Amanda 2.5.1. To enable different auth 
mechanism, amandad needs to run on the server. And it will start 
amindexd and amidxtaped accordingly.


Please see 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication 





well i have seen that but i have a lot of old amanda configuration and i 
would like to use "amoldrecover".


when i use that on a remote i got the following message on the 
amidxtaped.debug

more amidxtaped.20070125103831.debug
amidxtaped: debug 1 pid 9307 ruid 33 euid 33: start at Thu Jan 25 
10:38:31 2007

amidxtaped: version 2.5.1p2
amidxtaped: time 0.000: read error: No such file or directory
amidxtaped: time 0.000: pid 9307 finish time Thu Jan 25 10:38:32 2007

on the backup server it works well

Re: amrecover problem

[Kevin Till]

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 enable different auth mechanism, amandad needs to 
run on the server. And it will start amindexd and amidxtaped accordingly.


Please see 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication



--
Thank you!
Kevin Till

Amanda documentation: http://wiki.zmanda.com
Amanda forums:http://forums.zmanda.com

Re: amrecover problem

[Jon LaBadie]

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 previous emails.  Here is what I was trying to do.
> I did four full backups on the same day.  When I tried to restore using
> amrecover, it always asked for the first backup tape.  How can I change
> to a different backup tape?

You don't.  There is no functionallity "in amrecover" for the
operator to specify the tape.  amrecover is designed to look
at the index files and based on the parameters pick a tape
for you.  As amanda was not designed with a consideration of
multiple runs on the same date, the selection process of amrecover
doesn't have the ability to distinguish "the first/second/third/fourth"
dump of a single day.

All my comments that follow are pure speculation.
Use at your own risk as I don't know the results.

Previously I suggested amrmtape if you only will ever want one
particular backup from that day.  Still a possibility.

Previously I mentioned manual backup using well described
procedures including amrestore/dd/gzip/tar/mt/...

One other possibility occured to me.  If you know you want
to recover files from a particular DLE, let's say "host:/usr",
check the index directory for that DLE.  I don't know what
happens to the indexes when you run multiple dumps on the same
day.  I think normally they are named simply for the date and
level like "20030818_0.gz".  But if there is some identifier
of your first through fourth dump of the day, you could 
to get the one you want by renaming the undesired index files.
It may also require renaming the undesired log files as well.

Basically what I'm suggesting is to "hide" all the info that
you don't want amrecover to consider.  But no guarentees that
it will work.  I'm certain the manual restoration should work.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

RE: amrecover problem

[Lei Zhong]

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 backups on the same day.  When I tried to restore using
amrecover, it always asked for the first backup tape.  How can I change
to a different backup tape?  When I ran history command in amrecover,
here is the result:

201- 2005-08-01 0 BiWeeklySet101 1
201- 2005-08-01 0 BiWeeklySet102 1
201- 2005-08-01 0 BiWeeklySet103 1
201- 2005-08-01 0 BiWeeklySet104 1

The following is my amanda.conf

dumpcycle 0 
runspercycle 0   
tapecycle 4 tapes

#runtapes 1
#tpchanger "chg-manual" 
tapedev "/dev/nst0" 
rawtapedev "/dev/null"  


define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't
have
# to type them everywhere.  All dumptype definitions in this sample
file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of
any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc.  Some examples:
# index yes
# record no
}

define dumptype always-full {
global
program "GNUTAR"
comment "Full dump of this filesystem always"
compress none
index yes
priority high
}

Please help.

Thank you,

Lei

Re: amrecover problem

[Jon LaBadie]

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 four different tapes on
> > the same day. When I ran amrecover, it always asked for the first
> > full backup tape. How can I change to the tape I want to restore
> > from?  Thank you very much.
> >
> I believe 'settape' is the subcommand to use in amrecover.  But see 
> the manpages to be sure.

I think that sets the server/device, not the specific tape.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: amrecover problem

[Gene Heskett]

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 always asked for the first
> full backup tape. How can I change to the tape I want to restore
> from?  Thank you very much.
>
I believe 'settape' is the subcommand to use in amrecover.  But see 
the manpages to be sure.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.

Re: amrecover problem

[Jon LaBadie]

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.
^^^

I don't recall your saying this in the first post.

> When I ran amrecover, it always asked for the first full backup tape.
> How can I change to the tape I want to restore from?  Thank you very
> much.

The design of Amanda did not anticipate multiple backups the same day.

You may have to manually extract the dump file from the particular
dump you want and then use tar or restore or whatever to get the
specific files.  The extraction can be done manually with mt and dd
or possibly with amrestore.

If you only want, ever will want, the 4th dump, perhaps you could
amrmtape the ones you don't want.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: amrecover problem (SOLVED)

[Frederic Medery]

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 McAuley wrote:
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 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.
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
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]? Y
EOF, check amidxtaped..debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Some hints ??
Thanks !!
--
Frederic Medery
System Administrator
LexUM, University of Montreal
   


 

Re: amrecover problem

[Paul Bijnens]

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: time 0.001: bsd security: remote host localhost.localdomain
I hope you understand that this only works when server == client.
Not very scalable, for a client-server tool.
user root local user amanda
amidxtaped: time 0.002: amandahosts security check passed
amidxtaped: time 0.002: > CONFIG=weekly
amidxtaped: time 0.002: > LABEL=weekly-05
amidxtaped: time 0.002: > FSF=23
amidxtaped: time 0.002: > HEADER
amidxtaped: time 0.002: > DEVICE=/dev/nst0
amidxtaped: time 0.002: > HOST=^urbino$
amidxtaped: time 0.002: > DISK=^/home/users$
amidxtaped: time 0.002: > DATESTAMP=20040529
amidxtaped: time 0.002: > END
amidxtaped: time 0.007: amrestore_nargs=0
amidxtaped: time 0.008: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "/dev/nst0"
argv[4] = "^urbino$"
argv[5] = "^/home/users$"
argv[6] = "20040529"
amrestore: WARNING: not at start of tape, file numbers will be offset
Here is your warning.  Amanda did not find the image from where it
started to end of tape.  You have to rewind the tape manually (with
a command 'mt rewind" I mean :-)  ), or add these two directives
to amanda.conf:
  amrecover_do_fsf yes  # this implies a rewind
  amrecover_check_label yes
Because of a little bug in your version you need both parameters set
to yes (that bug is solved in 2.4.4p3).

On Behalf Of Frederic Medery
When I tried to recover a folder called "my folder" (with space in it,
don't know if this could be the problem). I have for time to time,
Segment Fault.
This is probably a complete other problem.  Is it repeatable?
Can you send the debug file of such a restore attempt?
Can you find out what program is hit by the segmention fault? 
(amindexd, gzip, gnutar...)?  Any core file (if "ulimit -c" is
set sufficiently large) in /tmp/amanda on the server?

--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: amrecover problem

[Gene Heskett]

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.000: > SECURITY USER root
>amidxtaped: time 0.001: bsd security: remote host
> localhost.localdomain user root local user amanda

What is this^^?  [EMAIL PROTECTED] is not a valid, unique 
adress and will not work for recovery.  Please read the FAQ and 
TOP-TEN-QUESTIONS in the docs directory of the tarball.
 
>amidxtaped: time 0.002: amandahosts security check passed
>amidxtaped: time 0.002: > CONFIG=weekly
>amidxtaped: time 0.002: > LABEL=weekly-05
>amidxtaped: time 0.002: > FSF=23
>amidxtaped: time 0.002: > HEADER
>amidxtaped: time 0.002: > DEVICE=/dev/nst0
>amidxtaped: time 0.002: > HOST=^urbino$
>amidxtaped: time 0.002: > DISK=^/home/users$
>amidxtaped: time 0.002: > DATESTAMP=20040529
>amidxtaped: time 0.002: > END
>amidxtaped: time 0.007: amrestore_nargs=0
>amidxtaped: time 0.008: Ready to execv amrestore with:
>path = /usr/sbin/amrestore
>argv[0] = "amrestore"
>argv[1] = "-p"
>argv[2] = "-h"
>argv[3] = "/dev/nst0"
>argv[4] = "^urbino$"
>argv[5] = "^/home/users$"
>argv[6] = "20040529"
>amrestore: WARNING: not at start of tape, file numbers will be
> offset amrestore:   0: reached end of information
>amidxtaped: time 0.047: amrestore terminated normally with status: 1
>amidxtaped: time 0.047: rewinding tape ...
>amidxtaped: time 9.815: done
>amidxtaped: time 9.815: pid 1566 finish time Mon Jun 28 13:22:00
> 2004
>
>Frédéric Médery
>Administrateur Système
>LexUM, Université de Montréal
>
>[EMAIL PROTECTED]
>tel. : (514) 343-6111  #3288
>
>Bernard McAuley wrote:
>>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 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.
>>
>>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
>>>
>>>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]? Y
>>>EOF, check amidxtaped..debug file on localhost.
>>>amrecover: short block 0 bytes
>>>UNKNOWN file
>>>amrecover: Can't read file header
>>>extract_list - child returned non-zero status: 1
>>>
>>>
>>>Some hints ??
>>>Thanks !!
>>>
>>>--
>>>Frederic Medery
>>>System Administrator
>>>
>>>LexUM, University of Montreal

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

Re: amrecover problem

[Frederic Medery]

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 security: remote host localhost.localdomain
user root local user amanda
amidxtaped: time 0.002: amandahosts security check passed
amidxtaped: time 0.002: > CONFIG=weekly
amidxtaped: time 0.002: > LABEL=weekly-05
amidxtaped: time 0.002: > FSF=23
amidxtaped: time 0.002: > HEADER
amidxtaped: time 0.002: > DEVICE=/dev/nst0
amidxtaped: time 0.002: > HOST=^urbino$
amidxtaped: time 0.002: > DISK=^/home/users$
amidxtaped: time 0.002: > DATESTAMP=20040529
amidxtaped: time 0.002: > END
amidxtaped: time 0.007: amrestore_nargs=0
amidxtaped: time 0.008: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-p"
argv[2] = "-h"
argv[3] = "/dev/nst0"
argv[4] = "^urbino$"
argv[5] = "^/home/users$"
argv[6] = "20040529"
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore:   0: reached end of information
amidxtaped: time 0.047: amrestore terminated normally with status: 1
amidxtaped: time 0.047: rewinding tape ...
amidxtaped: time 9.815: done
amidxtaped: time 9.815: pid 1566 finish time Mon Jun 28 13:22:00 2004
Frédéric Médery
Administrateur Système
LexUM, Université de Montréal
[EMAIL PROTECTED]
tel. : (514) 343-6111  #3288

Bernard McAuley wrote:
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 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.
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
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]? Y
EOF, check amidxtaped..debug file on localhost.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Some hints ??
Thanks !!
--
Frederic Medery
System Administrator
LexUM, University of Montreal
   


 

RE: amrecover problem

[Bernard McAuley]

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 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.

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
> 
> 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]? Y
> EOF, check amidxtaped..debug file on localhost.
> amrecover: short block 0 bytes
> UNKNOWN file
> amrecover: Can't read file header
> extract_list - child returned non-zero status: 1
> 
> 
> Some hints ??
> Thanks !!
> 
> --
> Frederic Medery
> System Administrator
> 
> LexUM, University of Montreal

Re: Amrecover Problem

[Paul Bijnens]

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/local/libexec/amidxtaped
log_on_failure  += USERID
disable = no
}


--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amrecover Problem

[Jim Summers]

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 does 'ls -l /dev/nst0' say?  And what user and group runs amanda on 
> >>the server?
> > 
> > 
> > amrecover, in my hands, has a "root user" check at startup.
> > Thus, I assume that Jim was running amrecover as root.
> > 
> > Does amreocover su to another user before calling amrestore?
> > If not, would local permissions come into play?
> > 
> 
> but amrecover talks to amidxtape over the network (even when you restore 
> on the server) for reading the tape, and that should be started as
> user amanda on the server.  Verify the (x)inetd configuration.
My xinetd for the indexing is
==
# default: on
# description: The telnet server serves telnet sessions; it uses \
#   unencrypted username/password pairs for authentication.
service amidxtape
{
#   flags   = REUSE
socket_type = stream
wait= no
user= bin
server  = /usr/local/libexec/amidxtaped
log_on_failure  += USERID
disable = no
}

UPDATE:

Tape seems readable.  I ran the following:

amrestore -p /dev/nst0 no-such-host > /dev/null

and it was able to run through the tape showing each image.

Thanks again
-- 
Jim Summers <[EMAIL PROTECTED]>
University of Oklahoma - Computer Science

Re: Amrecover Problem

[Paul Bijnens]

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, in my hands, has a "root user" check at startup.
Thus, I assume that Jim was running amrecover as root.
Does amreocover su to another user before calling amrestore?
If not, would local permissions come into play?
but amrecover talks to amidxtape over the network (even when you restore 
on the server) for reading the tape, and that should be started as
user amanda on the server.  Verify the (x)inetd configuration.

--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: Amrecover Problem

[Gene Heskett]

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 runs
>> amanda on the server?
>
>Sorry I forgot to include that in the original:
>
>
>[EMAIL PROTECTED] amanda]# ls -l /dev/nst0
>crw-rw1 root disk   9, 128 Jan 30  2003 /dev/nst0
>[EMAIL PROTECTED] amanda]# ls -l /dev/sg1
>crw-rw1 root disk  21,   1 Jan 30  2003 /dev/sg1
>
>I built amanda with --with-user=bin and --with-group=disk
>
That looks as if it could be part of the problem.  I think bin has 
near root rights, and amandas --with-user should specify an 
unpriviledged user when configuring.

>TIA

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: Amrecover Problem

[Jean-Louis Martineau]

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 what user and group runs amanda on 
> > the server?
> Sorry I forgot to include that in the original:
> 
> 
> [EMAIL PROTECTED] amanda]# ls -l /dev/nst0
> crw-rw1 root disk   9, 128 Jan 30  2003 /dev/nst0
> [EMAIL PROTECTED] amanda]# ls -l /dev/sg1
> crw-rw1 root disk  21,   1 Jan 30  2003 /dev/sg1
> 
> I built amanda with --with-user=bin and --with-group=disk

Who run the amidxtaped process?
Look at your xinetd configuration.

Jean-Louis
-- 
Jean-Louis Martineau email: [EMAIL PROTECTED] 
Département IRO, Université de Montréal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montréal, Canada, H3C 3J7Fax: (514) 343-5834

Re: Amrecover Problem

[Gene Heskett]

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 system.  I have found references to EOF
> errors but not anything with th permission denied stuff.  My tape
> drive is actually a changer (/dev/sg1).
>
Linux normally uses two different devices to address a changer, one, 
the drive itself, is usually /dev/nst0, then the changer robot is 
treated as a generic scsi device, in your case /dev/sg1 because 
you've already got something on sg0.  But check your /var/log/dmesg 
file for the device assigned to the drive itself.

Norma;lly you won't need the changer to recover if you can manually 
position the right tapes into the drive.

>The host and disk are on a amanda client.
>
>I start amrecover, no problem.
>
>I issue a sethost   No errors or problems
>
>I issue a setdiskNo errors or problems
>
>Next I cd to the directory containing the file to recover and issue
> the add command.  No problem.
>
>Then I issue extract and it prompts for the tape needed and then a
>continue prompt and the following is displayed:
>===
>Extracting files using tape drive /dev/nst0 on host backus.
looks good
>Load tape daily06 now
do it manually
>Continue [?/Y/n/s/t]? Y
>EOF, check amidxtaped..debug file on backus.
>amrecover: short block 0 bytes
>UNKNOWN file
>amrecover: Can't read file header

Humm, can amverify read this tape?

>extract_list - child returned non-zero status: 1
>===
>
>The amidxtaped debug contains the following errors:
>===
>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

what user are you?

>amidxtaped: time 0.010: pid 31743 finish time Mon Nov  3 08:10:09
> 2003 ===

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

Re: Amrecover Problem

[Jon LaBadie]

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, in my hands, has a "root user" check at startup.
Thus, I assume that Jim was running amrecover as root.

Does amreocover su to another user before calling amrestore?
If not, would local permissions come into play?

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Amrecover Problem

[Jim Summers]

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 that in the original:


[EMAIL PROTECTED] amanda]# ls -l /dev/nst0
crw-rw1 root disk   9, 128 Jan 30  2003 /dev/nst0
[EMAIL PROTECTED] amanda]# ls -l /dev/sg1
crw-rw1 root disk  21,   1 Jan 30  2003 /dev/sg1

I built amanda with --with-user=bin and --with-group=disk

TIA


-- 
Jim Summers <[EMAIL PROTECTED]>
University of Oklahoma - Computer Science

Re: Amrecover Problem

[Marc Cuypers]

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 errors but
not anything with th permission denied stuff.  My tape drive is actually
a changer (/dev/sg1).  
 
The host and disk are on a amanda client.

I start amrecover, no problem.

I issue a sethost   No errors or problems

I issue a setdiskNo errors or problems

Next I cd to the directory containing the file to recover and issue the
add command.  No problem.
Then I issue extract and it prompts for the tape needed and then a
continue prompt and the following is displayed:
===
Extracting files using tape drive /dev/nst0 on host backus.
Load tape daily06 now
Continue [?/Y/n/s/t]? Y
EOF, check amidxtaped..debug file on backus.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
===
The amidxtaped debug contains the following errors:
===
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 time Mon Nov  3 08:10:09 2003
===
Are the filesystem permissions OK for /dev/nst0?
You should have read and write permissions on the device.
Are you logged in as root?
Marc

Re: Amrecover Problem

[Tom Brown]

> 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 time Mon Nov  3 08:10:09 2003

and what are the permissions on /dev/nst0

is it on the same machine?

Re: Amrecover Problem

[Joshua Baker-LePain]

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

Re: amrecover problem

[Markus Dohmann]

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 of directories.
> > 
> ...
> > 
> > All owner modes were ok, but the date of the directories get the actual 
> > system time. Files in this directories have the correct time.
> > Do you have any idea or hint?
> 
> I'm pretty certain that is the normal effect of recoveries.
> I do not believe there is a workaround.
>

When I use /bin/tar from Solaris 8 (instead of GNU tar) and tar a directory 
tree and then extract this tar archive, the directories have the corret date 
and time.

> You see the same thing with "pass through" transfer of one directory
> tree to another location with cpio or tar (i.e. cpio | cpio or tar | tar
> to copy a dir tree).  The directories always have the current date/time
> even when the "preserve mod times" options are used.
> 
> I think the reason is that the directories, which are actually files,
> are not copied into the backup image, just noted.  Then they are
> recreated as needed during recovery.
> 

It seems so, but in the example I sent there are directories recovered with the 
original dateand time, Ithink in this case all directories without a year number 
only month and time:

drwxr-xr-x   7 dohmann  b311 512 Mar 28 10:02 system/



Markus

Re: amrecover problem

[Jon LaBadie]

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.
> 
...
> 
> All owner modes were ok, but the date of the directories get the actual 
> system time. Files in this directories have the correct time.
> Do you have any idea or hint?

I'm pretty certain that is the normal effect of recoveries.
I do not believe there is a workaround.

You see the same thing with "pass through" transfer of one directory
tree to another location with cpio or tar (i.e. cpio | cpio or tar | tar
to copy a dir tree).  The directories always have the current date/time
even when the "preserve mod times" options are used.

I think the reason is that the directories, which are actually files,
are not copied into the backup image, just noted.  Then they are
recreated as needed during recovery.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: amrecover problem

[Paul Bijnens]

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.
> Are we missing some configuration parameter? See, if i want to
> recover my backup is obvious that the tape should rewind itself
> first, right?
That why in amanda 2.4.4 some new parameters in amanda.conf are
available:
  amrecover_do_fsf bool
 Default: off.  Amrecover will call amrestore with the ‐f flag 

 for faster positioning of the tape.
  amrecover_check_label bool
 Default: off.  Amrecover will call amrestore with the ‐l flag
 to check the label.
  amrecover_changer "string"
 Default: ''.  Amrecover will use the changer if you use
 'settape ' and that string is the same as the
 amrecover_changer setting.
(amrestore 2.4.4 has implemented those new flags -f and -l too)

--
Paul @ Home

Re: amrecover problem

[Bruno Negrão]

> 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 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 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 some configuration 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]>
> > Sent: Thursday, September 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 myserver -d /dev/st0
> > >
> > >   The server returned me:
> > >
> > > amrecover: Unexpected server end of file
> > >
> > >I'm using:  amrecover 2.4.2p2 on red hat client and server. Does
> > > anyone could help me please ?
> > >
> > > Thanks,
> > >
> > >
> > > Roberto Samarone Araujo
> > >
> > >
> > >
> >
>
>
>

Re: amrecover problem

[Roberto Samarone Araújo (RSA)]

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 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 some configuration 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]>
> Sent: Thursday, September 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 myserver -d /dev/st0
> >
> >   The server returned me:
> >
> > amrecover: Unexpected server end of file
> >
> >I'm using:  amrecover 2.4.2p2 on red hat client and server. Does
> > anyone could help me please ?
> >
> > Thanks,
> >
> >
> > Roberto Samarone Araujo
> >
> >
> >
>

Re: amrecover problem

[Paul Bijnens]

Roberto Samarone Araújo (RSA) wrote:

amrecover Day -s myserver -t myserver -d /dev/st0
You need the nonrewinding device /dev/nst0.

Re: amrecover problem

[Bruno Negrão]

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 
some configuration 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]>
Sent: Thursday, September 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 myserver -d /dev/st0
>
>   The server returned me:
>
> amrecover: Unexpected server end of file
>
>I'm using:  amrecover 2.4.2p2 on red hat client and server. Does
> anyone could help me please ?
>
> Thanks,
>
>
> Roberto Samarone Araujo
>
>
>

Re: amrecover problem

[Paul Bijnens]

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?"
Is the above really the complete errormessage?
What Amanda version are you running?
> define dumptype global {
> comment "Global definitions"
> # ...
> # You may want to use this for globally enabling or disabling
> # indexing, recording, etc.  Some examples:
> # index yes
> # record no
> }
>
> define dumptype always-full {
> global
> comment "Full dump of this filesystem always"
> compress server fast
> priority high
> dumpcycle 1
> }
You see above that "index yes" is commented out.
Remove the comments or add "index yes" to the always-full
dumptype.
You could have found this, by executing the command:
  amadmin normal disklist localhost | grep index

(I believe this command does not exist in versions older
than amanda 2.4.2 .)
In disklist you call your host "localhost" so you should call
it "localhost" everywhere.  (And that's just the reason to avoid
"localhost", because "localhost" on another host points to a different
computer - confusion garuanteed!)
--
Paul Bijnens, XplanationTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...*
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: amrecover problem

[briner]

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 directory
indexdir "/var/lib/amanda/normal/index" # index directory

so in borkerserver:/var/lib/amanda/normal/index you should find the
index information base...

is that the case?

if not!.. the server is usually where you run amanda.
then type amrecover -s 

hope it will help

briner
> 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 let me know if there is any 
> problem.
> I have addes both localhost and brokerserver in.amandahosts and I have enabled 
> amanda,amandaidx and amidxtape in /etc/xinetd.d. I dont know how to enable the index 
> of the records
> Regards
> Yogish
> --
> Yogish.G.K
> American Healthcare Solutions Inc
> 405, South Lincoln
> Steamboat Springs CO-80487
> Ph-970-870-6232 ( EXT 106) (office)
> Email: [EMAIL PROTECTED]
> 

Re: amrecover problem: need help/advice

[Freels, James D.]

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 ncr53c8xx and sym53c8xx ).  It won't utilize all the speed of the card/drives, but it will read my tapes !  The strange thing is that it writes the tapes fine, but has problems reading.  If I have time, I will investigate further and post to the debian-alpha mailing list to see if any similar problems have occurred in other machines.

On Sun, 2003-07-20 at 23:23, Gene Heskett wrote:

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 rewind
>mt -f=/dev/tape_norewind fsf 1
>dd if=/dev/tape_norewind of=./first_file bs=1k count=384
>
>the number of records read returned is
>
>64
>288
>384
>384
>64
>64
>384
>
>when it should be 384 every time !  Does this not smell of a
> hardware problem ?  Must be the scsi card ?

Yes it does on the face of it.

>If so, why don't I have other scsi errors on the hard drives ?
>
>Any ideas ?

The only additional one I keep stumbling over is that maybe this card 
is so optimized for disk useage that its not quite kosher for a tape 
drive.

If you are running the disks on this same card, a second ugly thought 
comes to mind, and this is something that historicly seems to be 
abused by tape drives more than disk drives, and that is the honoring 
of the 'scsi disconnect', which is the situation where a command is 
issued to a device on the scsi bus, and an immediate disconnect is 
done, opening up the bus for use by other programs and such, leaving 
it up to the device the command was issued to to notify the host that 
the command has been done, and any data read (or written for that 
matter) is now ready in the buffers to be read at the host and 
controllers convienience.

Many tape drives ignore the disconnect message and lock the bus from 
other uses by other devices until the command is completed.  I'm not 
saying that it couldn't happen to a disk, but if its a true scsi-2 or 
better, it should honor it.

You might investigate that aspect of it, and see if there are any 
workarounds starting with the cards own bios configuration available 
during the 'post' of a reboot.  If not, then that question might be 
answered by putting a different card in for the tape drive by itself 
so that it doesn't have to share a bus with disks that in all 
probability do honor a disconnect correctly.

Other than those 2 possibilities, I'm fresh out of ideas.

>On Sun, 2003-07-20 at 05:00, Gregor Ibic wrote:
>> 
>> 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

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.




-- 
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]

Re: amrecover Problem

[Frank Smith]

--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
> why this problem might be occuring. I am not sure if amanda uses the
> ethernet interface to do recover,if this is not the case, then it should
> not encpunter any problem with Firewall settings.
> wainting for replies
> Yogish
>  

Do you have entries in inetd.conf (or xinetd if you are using that) for
the amandaidx and amidxtape services?  And did you remember to restart
(x)inetd after adding them?  Also check to see there is anything in
your system logs about errors starting those processes.
   There's also the chance you have paranoid settings in your hosts.allow
and hosts.denied files.

Frank

--
Frank Smith [EMAIL PROTECTED]
Systems Administrator  Voice: 512-374-4673
Hoover's Online  Fax: 512-374-4501

Re: amrecover problem: need help/advice

[Gene Heskett]

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 rewind
>mt -f=/dev/tape_norewind fsf 1
>dd if=/dev/tape_norewind of=./first_file bs=1k count=384
>
>the number of records read returned is
>
>64
>288
>384
>384
>64
>64
>384
>
>when it should be 384 every time !  Does this not smell of a
> hardware problem ?  Must be the scsi card ?

Yes it does on the face of it.

>If so, why don't I have other scsi errors on the hard drives ?
>
>Any ideas ?

The only additional one I keep stumbling over is that maybe this card 
is so optimized for disk useage that its not quite kosher for a tape 
drive.

If you are running the disks on this same card, a second ugly thought 
comes to mind, and this is something that historicly seems to be 
abused by tape drives more than disk drives, and that is the honoring 
of the 'scsi disconnect', which is the situation where a command is 
issued to a device on the scsi bus, and an immediate disconnect is 
done, opening up the bus for use by other programs and such, leaving 
it up to the device the command was issued to to notify the host that 
the command has been done, and any data read (or written for that 
matter) is now ready in the buffers to be read at the host and 
controllers convienience.

Many tape drives ignore the disconnect message and lock the bus from 
other uses by other devices until the command is completed.  I'm not 
saying that it couldn't happen to a disk, but if its a true scsi-2 or 
better, it should honor it.

You might investigate that aspect of it, and see if there are any 
workarounds starting with the cards own bios configuration available 
during the 'post' of a reboot.  If not, then that question might be 
answered by putting a different card in for the tape drive by itself 
so that it doesn't have to share a bus with disks that in all 
probability do honor a disconnect correctly.

Other than those 2 possibilities, I'm fresh out of ideas.

>On Sun, 2003-07-20 at 05:00, Gregor Ibic wrote:
>> 
>> 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

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

RE: amrecover problem: need help/advice

[Freels, James D.]

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_norewind of=./first_file bs=1k count=384

the number of records read returned is

64
288
384
384
64
64
384

when it should be 384 every time !  Does this not smell of a hardware problem ?  Must be the scsi card ?
If so, why don't I have other scsi errors on the hard drives ?

Any ideas ?

On Sun, 2003-07-20 at 05:00, Gregor Ibic wrote:

 
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
 




-- 
James D. Freels, Ph.D.
[EMAIL PROTECTED]  or  [EMAIL PROTECTED]
mplayer -cache 100 http://wdvx.microcerv.net/wdvx

RE: amrecover problem: need help/advice

[Freels, James D.]

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/tape_norewind': Input/output error
64+0 records in
64+0 records out

Then if I issue a "more ./first_file", I get instructions on how to untar this block of data, with the following:

dd if=./first_file bs=32k skip=1 | /bin/tar -tf-

The output to the console looks like:

./
./APSE10/
./APSE10/comlib/
./APSE10/comlib/SAVE/
./APSE10/comslv/
./APSE10/fileshks/
./APSE10/matlib/
./APSE10/param/
./APSE10/prepro/
./APSE10/prepro/test/
./APSE10/preprof/
./APSE10/preprof/NMENU/
./APSE10/preprof/OMENU/
./APSE10/preprof/OMENU/test/
1+0 records in
1+0 records out
./APSE10/preprof/RMENU/
./APSE10/preprof/RMENU/models/
./APSE10/preprof/falloc/
./APSE10/preprof/findbc/
./APSE10/preprof/flip/
./APSE10/preprof/interp/
./APSE10/preprof/math/
./APSE10/preprof/matrices/
./APSE10/preprof/mkmac/
./APSE10/preprof/reader/
./APSE10/preprof/refine/
./APSE10/preprof/rotate/
/bin/tar: Unexpected EOF in archive
/bin/tar: Error is not recoverable: exiting now
fea6::/holding_disk/:

which is about what I get from the output of amrestore.  I think the key to the problem is the initial I/O error that I get from the dd statement from the tape as input device.  It is similar to what I get from amrestore.  It is as if the data is on the tape, but a scsi problem is not letting me read it from the tape.

One additional bit of info:  The server doing all the I/O is an Alpha using a symbios scsi card/driver. It has never had this problem before and restored many a file in the past...

On Sun, 2003-07-20 at 17:44, Freels, James D. wrote:

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 file ?  The amdump/amrestore is using gnutar.

Thanks...

On Sun, 2003-07-20 at 05:00, Gregor Ibic wrote: 

 
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




-- 
James D. Freels, Ph.D.
[EMAIL PROTECTED]  or  [EMAIL PROTECTED]
mplayer -cache 100 http://wdvx.microcerv.net/wdvx








-- 
James D. Freels, Ph.D.
[EMAIL PROTECTED]  or  [EMAIL PROTECTED]
mplayer -cache 100 http://wdvx.microcerv.net/wdvx

RE: amrecover problem: need help/advice

[Freels, James D.]

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 file ?  The amdump/amrestore is using gnutar.

Thanks...

On Sun, 2003-07-20 at 05:00, Gregor Ibic wrote:

 
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
 




-- 
James D. Freels, Ph.D.
[EMAIL PROTECTED]  or  [EMAIL PROTECTED]
mplayer -cache 100 http://wdvx.microcerv.net/wdvx

Re: amrecover problem: need help/advice

[Freels, James D.]

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 received a i/o error message.

Then I issued 

mt rewind

The I issue

amrestore /dev/tape_norewind  fea sdd9

where sdd9 is a bogus filesystem name to force the tape to go to the end.  I get a "0 skip header stuff", followed by 40 filesystem finds, then followed by 

amrestore:  41: reached end of tape: date 20030618

Then I issue a "mt rewind" again.

Finally, I issue

amrestore /dev/tape_norewind

which should restore every file on the tape to the local disk area.  Note the tape is written using gnutar.

But, when I do this, I get the following:

fea6::/holding_disk/: amrestore /dev/tape_norewind
amrestore:   0: skipping start of tape: date 20030618 label fea12
amrestore:   1: restoring fea.sda6.20030618.1
amrestore: read error: Input/output error
fea6::/holding_disk/:

which is my problem.    Only a small portion (beginning) of this file is restored.  If is issue

fea6::/holding_disk/: tar tvf fea.sda6.20030618.1
drwxr-xr-x root/root   137 2003-02-10 10:38:40 ./
drwxrwx--- fea/apse 59 2000-06-30 00:19:18 ./APSE10/
drwxrwxr-x fea/apse 90 2000-08-16 17:08:31 ./APSE10/comlib/
drwxrwxr-x fea/apse 20 2000-01-14 21:48:19 ./APSE10/comlib/SAVE/
drwxrwxr-x fea/apse    581 2000-08-16 17:12:38 ./APSE10/comslv/
drwxrwxr-x fea/apse 64 2000-08-15 16:36:15 ./APSE10/fileshks/
drwxrwx--- fea/apse   6280 2000-05-04 16:56:24 ./APSE10/matlib/
drwxrwxr-x fea/apse    171 2000-08-16 17:27:43 ./APSE10/param/
drwxrwx--- fea/apse    289 2000-08-11 14:46:34 ./APSE10/prepro/
drwxrwxr-x fea/apse 24 2000-06-01 14:22:15 ./APSE10/prepro/test/
drwxrwxr-x fea/apse    133 2000-06-07 14:51:30 ./APSE10/preprof/
drwxrwxr-x fea/apse 67 2000-06-07 14:52:38 ./APSE10/preprof/NMENU/
drwxrwxr-x fea/apse 66 2000-06-01 13:52:35 ./APSE10/preprof/OMENU/
drwxrwxr-x fea/apse 50 2000-06-01 12:46:41 ./APSE10/preprof/OMENU/test/
drwxrwxr-x fea/apse    166 2000-08-15 16:29:04 ./APSE10/preprof/RMENU/
drwxrwxr-x fea/apse 80 2000-02-22 16:45:48 ./APSE10/preprof/RMENU/models/
drwxrwxr-x fea/apse 31 1998-04-08 12:20:26 ./APSE10/preprof/falloc/
drwxrwxr-x fea/apse 65 2000-05-26 19:51:18 ./APSE10/preprof/findbc/
drwxrwxr-x fea/apse 29 1998-12-15 13:05:10 ./APSE10/preprof/flip/
drwxrwxr-x fea/apse    167 2000-08-14 13:14:25 ./APSE10/preprof/interp/
drwxrwxr-x fea/apse 17 2000-05-26 19:51:39 ./APSE10/preprof/math/
drwxrwxr-x fea/apse 38 1999-01-24 00:08:39 ./APSE10/preprof/matrices/
drwxrwxr-x fea/apse 35 1998-11-20 12:59:27 ./APSE10/preprof/mkmac/
drwxrwxr-x fea/apse 83 2000-08-11 14:49:37 ./APSE10/preprof/reader/
drwxrwxr-x fea/apse    175 1998-12-15 13:21:41 ./APSE10/preprof/refine/
drwxrwxr-x fea/apse 31 2000-05-26 19:52:46 ./APSE10/preprof/rotate/
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
fea6::/holding_disk/:

If seems there is a problem with the scsi I/O between the tape drive and the hard drive.

Any more good ideas ?

On Sat, 2003-07-19 at 13:02, Gene Heskett wrote:

That doesn't sound as if its the drive to me since 2 drives cannot 
read this tape, its more than likely a bad tape.  I don't think thats 
what you wanted to hear though...

Can you 'mt -f /device fsf nn' where nn is the number of the next file 
on the tape?

This is one of the reasons one should have a tapecycle that is at 
*least* 2*runspercycle*runtapes.  It would be somewhat dated, but 
better than nothing, to back up one dumpcycles worth of tapes in the 
sequence and recover that.




-- 
James D. Freels, Ph.D.
[EMAIL PROTECTED]  or  [EMAIL PROTECTED]
mplayer -cache 100 http://wdvx.microcerv.net/wdvx

RE: amrecover problem: need help/advice

[Gregor Ibic]




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
 

Re: amrecover problem: need help/advice

[Gene Heskett]

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 this happened do you--long
> story). Normally, if something like this happens I do not panic
> because I know that I can recover most, if not all, of the files
> deleted.
>
>The AMANDA log files all indicate backups have been written
> normally. Indeed, I can verify that myt home directory and each
> individual file thereof is listed in the index files on the backup
> server.  However, unlike in the past, when I issue the normal
>
>amrecover /dev/tape_norewind machine  disk-device
>
>I get a scsi-related error message after if finds the file on the
> tape. It searches through the tape, finds the file, and only dumps
> part of the file.  For example, if the file should be 4GB, it is
> only dumping about 500 Mb.  It is as if a buffer is overflowing or
> something like that.
>
>I get no similar messages when creating the tape, only when trying
> to read off the tape.
>
>Any help appreciated.  I am at a loss unless I have had a buggy tape
>drive for some time and not realized it.
>
>P.S.  I have also taken the tape to a second compatible drive on an
>entirely different machine.  This drive also could not read the
> tape. Not looking good...

That doesn't sound as if its the drive to me since 2 drives cannot 
read this tape, its more than likely a bad tape.  I don't think thats 
what you wanted to hear though...

Can you 'mt -f /device fsf nn' where nn is the number of the next file 
on the tape?

This is one of the reasons one should have a tapecycle that is at 
*least* 2*runspercycle*runtapes.  It would be somewhat dated, but 
better than nothing, to back up one dumpcycles worth of tapes in the 
sequence and recover that.

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.

RE: amrecover problem

[Frank Smith]

--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/./
07664670563/./.ICAClient/
07664670563/./.acrobat/
07664670563/./.b3tools/
07664670563/./.dt/
07664670563/./.dt/Desktop/
07664670563/./.dt/Trash/
07664670563/./.dt/appmanager/
07664670563/./.dt/help/
.
.
.
Entries in the index file without these numbers can be listed
in amrecover.
The first dump of this user disk was a level 0 dump with
GNUTAR and the capacity
of the tape was sufficient, so everthing is dumped to the
tape, but I cannot
restore it.
HINT: you are using a bad version of tar. If you believe you have a good
version...be sure that you configured amanda
with-gnutar=/your/path/to/non-sucky/tar. As an extra hint, you can tell
by looking at the config.cache file and see what your ac_cv_path_GNUTAR
entry is.
If you are desperate to amrecover something from this dump, let me
know...I may still have my notes on how to clean up this index mess and
still recover from it. I have done it before thanks to help from John
Jackson.
If you do still have the notes, please post them to the list so they can
be archived.  I'm sure others will run into the same problem someday (I
know I did when I started with Amanda, fortunately I never had to restore
from them before I got all the tars upgraded), and it would be helpful
to have some notes on how to recover with bad index files.
Frank

--
Frank Smith [EMAIL PROTECTED]
Systems Administrator  Voice: 512-374-4673
Hoover's Online  Fax: 512-374-4501

RE: amrecover problem

[Rebecca Pakish Crum]

> 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/./.b3tools/
> 07664670563/./.dt/
> 07664670563/./.dt/Desktop/
> 07664670563/./.dt/Trash/
> 07664670563/./.dt/appmanager/
> 07664670563/./.dt/help/
> .
> .
> .
> 
> Entries in the index file without these numbers can be listed 
> in amrecover.
> 
> The first dump of this user disk was a level 0 dump with 
> GNUTAR and the capacity 
> of the tape was sufficient, so everthing is dumped to the 
> tape, but I cannot 
> restore it.
> 
HINT: you are using a bad version of tar. If you believe you have a good
version...be sure that you configured amanda
with-gnutar=/your/path/to/non-sucky/tar. As an extra hint, you can tell
by looking at the config.cache file and see what your ac_cv_path_GNUTAR
entry is. 

If you are desperate to amrecover something from this dump, let me
know...I may still have my notes on how to clean up this index mess and
still recover from it. I have done it before thanks to help from John
Jackson.

Re: amrecover Problem

[Toralf Lund]

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 shown on client. There is a
backup on level 0 on specified date. In amanda.conf index yes is set on
dumptype. -> index is on the secified indexdir, so i can zcat it and see
all files an directorys.
Iam using tar (GNU tar 1.13.25), so it cant be the known bug on older
gtar versions, and amanda version 2.4.2p2.
Are there any solutions.
I got the same error message on a recovery attempt some time back, and it 
was caused by a permission problem that prevented the backup config from 
being read correctly. Note that the config files are read by amandad 
(amrecover is just a client application that interacts with amandad), 
which is usually executed as "amanda", so the files need to be readable by 
that user. Also, amandad apparently has (or had) a bug that prevents some 
file open problems from being reported in the logs.

In other words, you probably need to chmod or chown one or more of the 
config files (in my case it was the tapelist) to make them readable by 
amandad.


Greetings
Daniel

Re: amrecover problem with changer

[Eric . Doutreleau]

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 changes;  I can get at all of my
> > backups manually with dd and tar.  However, amrestore is not happy.
> > 
> > The details:   I'm using amanda 2.4.3 compiled locally (no RedHat RPM
> > for me).  'tapedev "0"' appears in amanda.conf since I'm using a
> > changer.
> 
> You are using a changer to change the tapes.
> You are still using a tape device to read and write the tapes.
> 
> > amidxtaped.*.debug reveals that amrecover, when used, exec's "amrestore
> > -h -p 0" followed by the usual remaining arguments.  Of course this
> > fails, since there is no file or device named "0" which amrestore can
> > get at.
> 
> Have you tried setting tapedev to your tape device?
> 
> 

amrecover doesn't use the device that is returned by the changer prior
the 28022003 shanpshot ( it s a snapshot after the 2.4.4 release ).

Moreover you have to configure this parameter in your amanda.conf

amrecover_changer "glopglop"# amrecover will use the changer if 
you restore

and to lauch amrecover -d glopglop to make amidxtaped use the changer.

Hope that helps


-- 
Eric Doutreleau
I.N.T   | Tel   : +33 (0) 160764687
9 rue Charles Fourier   | Fax   : +33 (0) 160764321
91011 Evry   France | email : [EMAIL PROTECTED]

Re: amrecover problem with changer

[Jon LaBadie]

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 manually with dd and tar.  However, amrestore is not happy.
> 
> The details:   I'm using amanda 2.4.3 compiled locally (no RedHat RPM
> for me).  'tapedev "0"' appears in amanda.conf since I'm using a
> changer.

You are using a changer to change the tapes.
You are still using a tape device to read and write the tapes.

> amidxtaped.*.debug reveals that amrecover, when used, exec's "amrestore
> -h -p 0" followed by the usual remaining arguments.  Of course this
> fails, since there is no file or device named "0" which amrestore can
> get at.

Have you tried setting tapedev to your tape device?

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: amrecover problem

[Jay Lessert]

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
> anyone any idea whats going on?
[clip]
> FAILED AND STRANGE DUMP DETAILS:
> 
> /-- hades  /mnt/data lev 0 STRANGE
> sendbackup: start [hades:/mnt/data level 0]
> sendbackup: info BACKUP=/bin/tar
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> ? gtar: ./home/dannyb/.Maildir/cur/1026897042.12092_1.hades,S=1602\:2,S:
> Warning: Cannot stat: No such file or directory
> | Total bytes written: 28790016000 (27GB, 1.5MB/s)

The STRANGE warning is solely due to some wacko thing your user dannyb
has down in his qmail delivery directory.  It should do no harm,
but you probably want to go clean it out.

> sendbackup: size 28115250

So *plenty* of files there, even if amrecover isn't letting you see 'em.  :-)

You can amrestore and confirm the data is actually there, that always
makes me sleep better.

amrecover doesn't run 'gtar -tv' on the tape, it just unzips what's in
the index file (under /var/adm/amanda/config_name/index for me).  The
most common cause of bad indexes is bad versions of GNU tar.  Do:

% /bin/tar --version

You want to see 1.13.19 or 1.13.25.  If you don't, build & install 1.13.25
from:

http://www.funet.fi/pub/gnu/alpha/gnu/tar/

MAKE SURE you install it where amanda expects to find it!  If your tar
version is already good, I'm out of ideas.

[clip]
> DUMP SUMMARY:
>  DUMPER STATSTAPER STATS
> HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
> -- - 
> hades/   0  988980 410048  41.5   7:08 957.6   7:08 957.1
> hades/boot   04900   2848  58.1   0:031097.0   0:031027.5
> hades/mnt/data   0 2811525022508256  80.1 297:321260.8 297:331260.8

Nothing to do w/your problem, but you might want to try a columnspec:

columnspec "HostName=0:10,Disk=1:10,OrigKB=1:9,OutKB=1:9,DumpRate=1:7,TapeRate=1:7"

or something similar, makes the summary output nice & pretty.

-- 
Jay Lessert   [EMAIL PROTECTED]
Accelerant Networks Inc.   (voice)1.503.439.3461
Beaverton OR, USA(fax)1.503.466.9472

RE: Amrecover problem with gtar

[Javier.Fernandez]

hi,
Well, i tell you my problem.
I have a cluster, 
[root@sc01us0103]> df -k
Filesystemkbytesused   avail capacity  Mounted on
/dev/vx/dsk/rootvol  13105131 1270880 1170320010%/
/proc  0   0   0 0%/proc
fd 0   0   0 0%/dev/fd
mnttab 0   0   0 0%/etc/mnttab
/dev/vx/dsk/var  3096423   77297 2957198 3%/var
swap 5678064 120 5677944 1%/var/run
swap 56806002656 5677944 1%/tmp
/dev/vx/dsk/software 14573538 4071313 1035649029%/software
/dev/vx/dsk/node@1 957022516   83616 3%/global/.devices/node@1
/dev/vx/dsk/cf_dg/datos
 99089760 4303325 93795538 5%/global/datos
/dev/vx/dsk/cf_dg/datos2
 21360505   93441 21053459 1%/global/datos2
/dev/vx/dsk/node@2 957022516   83616 3%/global/.devices/node@2

I want to dump /, could you tell me how to do it?

Thanks.

-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: jueves, 21 de febrero de 2002 13:56
Para: Javier 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
> sc01us0103.cf.jcyl.es   /   user-tar
> sc01us0103.cf.jcyl.es   /global/datos2/esri-web user-tar
> sc01us0104.cf.jcyl.es   /   user-tar
> 
> where sc01us0105 is the server.
> 
> When i connect to sc01us0105 from sc01us0103 with amrecover, and set the the disk 
>and the date make a ls, and amrecover list
> opt/
> usr/
> 
> but the other files and dirs where are they?, i don't know. Because of 
> this, i can not recover /etc/hosts by example.

Amanda runs tar with the --one-file-system flag.  So, if sc01us0103 has 
more than one filesystem ('df -k' should show all the filesystems), then 
you'll need to add a disklist entry for each of them if you want to back 
up the entire machine.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Amrecover problem with gtar

[Joshua Baker-LePain]

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.es   /global/datos2/esri-web user-tar
> sc01us0104.cf.jcyl.es   /   user-tar
> 
> where sc01us0105 is the server.
> 
> When i connect to sc01us0105 from sc01us0103 with amrecover, and set the the disk 
>and the date make a ls, and amrecover list
> opt/
> usr/
> 
> but the other files and dirs where are they?, i don't know. Because of 
> this, i can not recover /etc/hosts by example.

Amanda runs tar with the --one-file-system flag.  So, if sc01us0103 has 
more than one filesystem ('df -k' should show all the filesystems), then 
you'll need to add a disklist entry for each of them if you want to back 
up the entire machine.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Amrecover problem

[Clinton Dilks]

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 ago and I think the following patch will take care
of it for you.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]



__
The contents of this e-mail are privileged and/or confidential to the
named recipient and are not to be used by any other person and/or
organisation. If you have received this e-mail in error, please notify 
the sender and delete all material pertaining to this e-mail.
__

Re: Amrecover problem

[John R. Jackson]

>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.

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]



vrestore.diff
Description: vrestore.diff

Re: Amrecover problem.

[Joshua Baker-LePain]

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 at one time.  To 
get full backups every time of a particular disk, you can put 'dumpcycle 
0' in its dumptype in amanda.conf.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: amrecover problem with file permissions

[Chris Miller]

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 the holding disk record. By running amrestore a second time and
using the setmodes command only, all the permissions/modes were restored.

I ran amrecover locally on the tape host to a local disk with the same
results so this doesn't appear to be network related.

I am also missing files. I tried restoring manually with amrestore on the
tape host piped over ssh to restore on the remote host (something I've
done to recover a dead machine with success) but got the same overall
results, but with a new error. I had to do the tape and holding disk
records seperately, and again the permissions/modes were not set at the
end of the restore from tape. When running amrestore on the record on the
holding disk, I received the following error :

extract file ./home/user/filename.txt

gzip: stdin: decompression OK, trailing garbage ignored
extract file ./home/user/filename2.txt
extract file ./home/user/filename3.txt
Changing volumes on pipe input?
abort? [yn] n
Segmentation fault

What I don't understand is why amanda is asking to change volumes when
there was only a single dump record. And what's the gzip error about? I
couldn't find anything in the mail archives on this either.

The command I used was :

ssh  "amrecover -p   
" | /sbin/restore -ivb 2 -f -

I've come to the conclusion that the record written to tape/disk is not
complete. Does anyone have any suggestions for determining what went
wrong? Again I'm using FreeBSD 4.4 RELEASE with amanda 2.4.2 and a DLT
8000 in a Qualstar 20 tape changer. Compression is done via gzip on the
tape host, and hardware compression is shut off on the drive. Everything
has been rock solid for a year and I've recovered a few disks and
individual files/directories just fine in that time. Your help is much
appreciated.

Regards,
Chris

On Wed, 19 Dec 2001, Chris Miller wrote:

> 
> Hello,
>   I recently had to recover an entire disk from backup. Files were
> restored from one tape as well as a dump on the holding disk. Once
> complete, all directory ownership and permissions were set to root and
> 755. All files however were set appropriately. I'm using amanda2.4.2
> server on FreeBSD 4.4 RELEASE (recent O/S upgrade from 4.2 RELEASE, but
> did not upgrade amanda software) and amanda2.4.2 client on BSDi 4.1. I was
> unable to find any similar complaints in the email archives. Any ideas?
> 
> Regards,
> Chris
> 

Re: amrecover problem

[Marc SCHAEFER]

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 remote (network) tapes.

... ahem it has menus in French.

Re: amrecover problem

[Marc SCHAEFER]

John W. Price <[EMAIL PROTECTED]> wrote:
> amrecover: amandaidx/tcp unknown protocol

something is missing in your /etc/services.

Re: amrecover problem

[Juergen Knott]

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 for my changer?

When i take 
amrecover -d /dev/nst0 or
amrecover -d /dev/st0

and i become the same error, but 
sorry, i forgot to post a message called:

 WARNING: not on root of selected filesystem, check man-page!   

I think the $CWD mount point is not set correct.

The files will  be restored in 
/drives/drives2/projekte/Online-Marketing/customer/april

after checking from me.

My mountpoint for the scsi drive are

/dev/sdb1   /drives/drive2ext2defaults   1   2  
/dev/sdc1   /drives/drive3ext2defaults   1   2 
etc.

When i go to /drives/drive2 and start amrecover, the Warning Message don't 
come and restore works (i hope so)

When i go to /drives/drive2/Online-Marketing/customer/April the warning 
message is coming and the restore failed.

Where must i go to use the right $CWD mount point?

My idea is, a seperate directory for restore files, so that i can check the 
files after restoring before i move the files to the working directory.
But this directory called restore is not a mount point.

Thanks a lot and Bye Juergen 

-- 
Dies ist eine Microsoft freie Mail!

Re: amrecover problem

[Juergen Knott]

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 /dev/nst0 or
> >amrecover -d /dev/st0
> >and i become the same error ...
> Using /dev/nst0 should have worked.  I'm not sure I understood your
> last sentence.  Did "-d /dev/nst0" fail?  What messages did you get?
> In particular (if it failed), what was in /tmp/amanda/amidxtaped*debug?
> >sorry, i forgot to post a message called:
> > WARNING: not on root of selected filesystem, check man-page!
> >I think the $CWD mount point is not set correct.
> You didn't post the important message that comes out right before this:
>   $CWD '/some/path' is on disk '/some/disk' mounted at /some/mount/point'.
> Seeing that would help understand the problem.

That's fine.

> >When i go to /drives/drive2 and start amrecover, the Warning Message don't
> >come and restore works (i hope so)
> But the files replace the originals, right?

right, but before it comes a warning message that the files exists.

> >When i go to /drives/drive2/Online-Marketing/customer/April the warning
> >message is coming and the restore failed.
> What do you mean by "the restore failed"?

I don't no, amrestore is quiting with no comment.

> >Where must i go to use the right $CWD mount point?
> When I do restores, I create a directory at the top of the file system
> that was backed up, e.g. "/drives/drive2/.bkrest", then "cd" to there
> and start amrecover.
>
> If you cd to /drives/drive2/Online-Marketing/customer/April and run
> amrecover from there, files will be restored relative to that point.
> For instance, restoring Online-Marketing/customer/April/JJ would come
> back as:
> /drives/drive2/Online-Marketing/customer/April/Online-Marketing/customer/Ap
>ril/JJ
>
> which is probably not what you want (although you could rename it,
> of course).  That's why I create the temp area at the top of the mount
> point so there is only one extra directory layer involved.


well, i made a directory so you've written, i used the /dev/nst0 and the 
recovery is working fine.

Thank you very much for your Info. That helps!
Thanks a lot.

Bye Juergen
-- 
Dies ist eine Microsoft freie Mail!

Re: amrecover problem

[John R. Jackson]

>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 ...

Using /dev/nst0 should have worked.  I'm not sure I understood your
last sentence.  Did "-d /dev/nst0" fail?  What messages did you get?
In particular (if it failed), what was in /tmp/amanda/amidxtaped*debug?

>sorry, i forgot to post a message called:
>
> WARNING: not on root of selected filesystem, check man-page!   
>
>I think the $CWD mount point is not set correct.

You didn't post the important message that comes out right before this:

  $CWD '/some/path' is on disk '/some/disk' mounted at /some/mount/point'.

Seeing that would help understand the problem.

>When i go to /drives/drive2 and start amrecover, the Warning Message don't 
>come and restore works (i hope so)

But the files replace the originals, right?

>When i go to /drives/drive2/Online-Marketing/customer/April the warning 
>message is coming and the restore failed.

What do you mean by "the restore failed"?

>Where must i go to use the right $CWD mount point?

When I do restores, I create a directory at the top of the file system
that was backed up, e.g. "/drives/drive2/.bkrest", then "cd" to there
and start amrecover.

If you cd to /drives/drive2/Online-Marketing/customer/April and run
amrecover from there, files will be restored relative to that point.
For instance, restoring Online-Marketing/customer/April/JJ would come
back as:

  /drives/drive2/Online-Marketing/customer/April/Online-Marketing/customer/April/JJ

which is probably not what you want (although you could rename it,
of course).  That's why I create the temp area at the top of the mount
point so there is only one extra directory layer involved.

>Juergen 

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: amrecover problem on linux

[John R. Jackson]

>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 Specialist, [EMAIL PROTECTED]

Re: Amrecover Problem in 2.4.2pl1

[Patrick LIN]

"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: Connection reset by peer
> 
> Is there anything of interest in /tmp/amanda/amidxtaped*debug on the
> tape machine?  What about in wherever inetd.conf logs things?

Nothing bad

> 
> You might check out this thread, especially if your machines have
> multiple network interfaces:

Ok 
i have two network interfaces
but with previous version too


> 
>   http://groups.yahoo.com/group/amanda-users/message/27372

i am not able to get the patch in the forum
can you send it agoin please

> 
> >patrick
> 
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

thanks 
patrick

Re: Amrecover Problem in 2.4.2pl1

[John R. Jackson]

>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 interest in /tmp/amanda/amidxtaped*debug on the
tape machine?  What about in wherever inetd.conf logs things?

You might check out this thread, especially if your machines have
multiple network interfaces:

  http://groups.yahoo.com/group/amanda-users/message/27372

>patrick

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: Amrecover Problem, amandahostauth problem in amidxtaped.debug

[John R. Jackson]

>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 some problems in the parsing code with trailing
whitespace, so you might check for that in the file.

>Friedrich 

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: amrecover problem

[John R. Jackson]

>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 matches this error and also
send the exact set of commands you entered to amrecover.

>-- Mirko

John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]

Re: amrecover problem

[Urte Fuerst]

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 amrecover, but viewing the index-files manualy showed that the
> files are
> included in the backup... Whats the problem with this ?
>
> We use amanda on Solaris, but with gnu-tar...

I ran across the same problem yesterday when trying to restore a
directory which had been deleted by accident. I should have seen more
than 15 directories with "ls" in amrecover, but all I got was 3
entries. I tried the "setdate" command, but that did not help. In the
index-files all the directory entries where present, and I was able to
restore the directory "by hand". This happens in my case with amanda
2.4.1p1 on Solaris 2.6 system.

Has anybody an idea what is happening here?

Urte