Re: backing up the catalogue for Amrestore

[Charles Curley]

On Mon, 20 Sep 2021 15:59:31 +
David Simpson  wrote:

> Is there a definitive guide on backing up the catalogue/indexes?
> 
> (ideally appending to tape as an epilogue of sorts)

Oddly enough, we've just been having a discussion related to this.
Start with Gene Heskett's email in your inbox:

Subject: Re: DLE splitting
Date: Mon, 20 Sep 2021 01:27:43 -0400

(I went looking for the list archives; that link appears to be
broken. However, http://www.amanda.org/support/mailinglists.php)

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: backing up the catalogue for Amrestore

[Gene Heskett]

On Monday 20 September 2021 11:59:31 David Simpson wrote:

> Is there a definitive guide on backing up the catalogue/indexes?
>
> (ideally appending to tape as an epilogue of sorts)
>
That is basicly what GenesAmandaHelper does.

If comfy with shell scripts there is an older version that will need to 
be tweaked a bit for 3.5.1 on my web page in the sig. Its a bit out of 
date, written originally for a much older amanda that I started out with 
in 1999, but shouldn't be too hard to adapt. Zero consideration for the 
fixed capacity of real tapes, but I've been using vtapes on a big hd for 
well over a decade with relatively few problems that didn't resolve to 
hdwe in the final fix. They don't have a fixed tape length, only the 
disks capacity. 

This is NOT suitable for businesses requiring off site storage, but as a 
backup for a 6 machine home network, 4 of which are driving metal 
carving machines. Be my guest and I'll help if I can.

> -
> David Simpson - Senior Systems Engineer
> ARCCA, Redwood Building,
> King Edward VII Avenue,
> Cardiff, CF10 3NB
>
> David Simpson - peiriannydd uwch systemau
> ARCCA, Adeilad Redwood,
> King Edward VII Avenue,
> Caerdydd, CF10 3NB
>
> simpso...@cardiff.ac.uk
> +44 29208 74657



Copyright 2019 by Maurice E. Heskett
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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

backing up the catalogue for Amrestore

[David Simpson]

Is there a definitive guide on backing up the catalogue/indexes?

(ideally appending to tape as an epilogue of sorts)

-
David Simpson - Senior Systems Engineer
ARCCA, Redwood Building,
King Edward VII Avenue,
Cardiff, CF10 3NB

David Simpson - peiriannydd uwch systemau
ARCCA, Adeilad Redwood,
King Edward VII Avenue,
Caerdydd, CF10 3NB

simpso...@cardiff.ac.uk
+44 29208 74657

Re: amrecover/amrestore: block size too small

[Chris Hassell]

I do too.  I'm coming out of 'hibernation' to transfer some of our 
unit-test-and-multi-OS-build code back out.

Installcheck seems to be breathing and useful for me too.

On 7/16/19 5:01 AM, Stefan G. Weichinger wrote:
> Still believing in filing issues:
>
> https://github.com/zmanda/amanda/issues/109
>
>
>

Re: amrecover/amrestore: block size too small

[Stefan G. Weichinger]

Still believing in filing issues:

https://github.com/zmanda/amanda/issues/109

Re: amrecover/amrestore: block size too small

[Debra S Baddorf]

My backup has this as the instruction block,  for my first file on the tape
(after the label block):

AMANDA: SPLIT_FILE 2019062422/boot  part 1/-1  lev 1 comp 
.gz program /
sbin/dump
ORIGSIZE=52
DLE=<
  DUMP
  /boot
  1
  krb5
  SERVER-FAST
  YES
  YES
  AMANDA

ENDDLE
To restore, position tape at start of file and run:
dd if= bs=512k skip=1 | /bin/gzip -dc | /sbin/restore -xpGf - … 


I’m running amanda 3.3.8   so yes, it mentions the block size.
However, you have to already know it (or guess at something bigger?)
to get the block off tape.   

I used dd and “more"  to look at that info.I store an empty reminder file 
(in my recovery temp area)
titledUSE-BS-512k
to remind myself what to use.   I had to guess at several sizes & try them, 
before
I decided to create that reminder file.

Deb Baddorf
Fermilab




> On Jun 24, 2019, at 7:22 PM, Jon LaBadie  wrote:
> 
> I sent the following note to Steve.  I don't have facilities
> to check if my comments are correct.  Anyone care to comment
> or check?
> 
> On Wed, Jun 19, 2019 at 07:37:23PM +0200, Stefan G. Weichinger wrote:
> ...
>> 
>> $ amrestore  --config abt -b 2097152 /dev/nst0 jupi smb_revision
>> 
>> seems to work now ... at least it starts searching.
>> 
>> I don't know why I have to tell that ... but it seems I have a mismatch:
>> 
>> tapetype says 32 kbytes:
>> 
>> define tapetype LTO-4 {
>>comment "Created by amtapetype; compression disabled; 2017-10-31
>> sgw"
>>length 698510208 kbytes
>>filemark 0 kbytes
>>speed 36696 kps
>>blocksize 32 kbytes
>> }
>> 
>> changer def sets "2 mbytes":
>> 
>> define changer robot {
>>tpchanger "chg-robot:/dev/sg1"
>>property "tape-device" "0=tape:/dev/nst0"
>>device-property "BLOCK_SIZE" "2 mbytes"
>>device-property "READ_BLOCK_SIZE" "2 mbytes"
>>property "eject-before-unload" "no"
>>property "use-slots" "1-24"
>>changerfile "/etc/amanda/abt/chg-robot-dev-sg1"
>> }
>> 
>> storage def pulls in both:
>> 
>> define storage abt {
>>tapepool "abt"
>>tapetype "LTO-4"
>>tpchanger "robot"
>> [..]
>> }
>> 
>> Maybe then amrecover would also work (bailed out before as well)
>>>> End of included message <<<
> 
> I don't think LTO-4 will use a 32K blocksize.  Minimum is probably
> over 1M.  32K in tapetype is just what you said via command line
> or letting it default.  Amrestore is probably just reading this
> and knowing, or testing, that LT0-4 won't take 32K BS.
> 
> Pull off of a tape the first file.  It will be named "0.".
> I think it will be 1 tape block in size.  But contain < 32K of data.
> 
> Pull off the first data file of a DLE and look at the first 32K.
> One of mine ends with this:
> 
> To restore, position tape at start of file and run:
>dd if= bs=32k skip=1 | /usr/bin/gzip -d | /usr/libexec/
>amanda/application/amgtar restore [./file-to-restore]+
> 
> The "bs=32K" in my command line may be the BS actually used.
> 
> Jon
> -- 
> Jon H. LaBadie j...@jgcomp.com
> 11226 South Shore Rd.  (703) 787-0688 (H)
> Reston, VA  20190  (703) 935-6720 (C)

Re: amrecover/amrestore: block size too small

[Jon LaBadie]

I sent the following note to Steve.  I don't have facilities
to check if my comments are correct.  Anyone care to comment
or check?

On Wed, Jun 19, 2019 at 07:37:23PM +0200, Stefan G. Weichinger wrote:
...
> 
> $ amrestore  --config abt -b 2097152 /dev/nst0 jupi smb_revision
> 
> seems to work now ... at least it starts searching.
> 
> I don't know why I have to tell that ... but it seems I have a mismatch:
> 
> tapetype says 32 kbytes:
> 
> define tapetype LTO-4 {
> comment "Created by amtapetype; compression disabled; 2017-10-31
> sgw"
> length 698510208 kbytes
> filemark 0 kbytes
> speed 36696 kps
> blocksize 32 kbytes
> }
> 
> changer def sets "2 mbytes":
> 
> define changer robot {
> tpchanger "chg-robot:/dev/sg1"
> property "tape-device" "0=tape:/dev/nst0"
> device-property "BLOCK_SIZE" "2 mbytes"
> device-property "READ_BLOCK_SIZE" "2 mbytes"
> property "eject-before-unload" "no"
> property "use-slots" "1-24"
> changerfile "/etc/amanda/abt/chg-robot-dev-sg1"
> }
> 
> storage def pulls in both:
> 
> define storage abt {
> tapepool "abt"
> tapetype "LTO-4"
> tpchanger "robot"
> [..]
> }
> 
> Maybe then amrecover would also work (bailed out before as well)
>>> End of included message <<<

I don't think LTO-4 will use a 32K blocksize.  Minimum is probably
over 1M.  32K in tapetype is just what you said via command line
or letting it default.  Amrestore is probably just reading this
and knowing, or testing, that LT0-4 won't take 32K BS.

Pull off of a tape the first file.  It will be named "0.".
I think it will be 1 tape block in size.  But contain < 32K of data.

Pull off the first data file of a DLE and look at the first 32K.
One of mine ends with this:

To restore, position tape at start of file and run:
dd if= bs=32k skip=1 | /usr/bin/gzip -d | /usr/libexec/
amanda/application/amgtar restore [./file-to-restore]+

The "bs=32K" in my command line may be the BS actually used.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: amrecover/amrestore: block size too small

[Stefan G. Weichinger]

Am 24.06.19 um 22:06 schrieb Debra S Baddorf:

> You can also use  “dd”  to get the whole dump off tape.  You would have to 
> “glue” together
> any partial files;  I don’t know how to do that  (I’ve specified no partial 
> files).
> 
> “dd” still needs a reasonably correct block size.

thanks for the workaround howto

but I would prefer to have a fully working amanda setup ;-)

I fiddle with the parameters and managed to get amrecover working. Seems
one has to relabel and/or edit the tapelist as well.

I read the numerous how-to-relabel-postings ... couldn't we get a *tool*
doing that? I mean, other software projects improve over time ;-)

Another thought: if the blocksize of the tapetype and the blocksize of
the changer-definition mismatch: shouldn't there be a warning? Something
in amcheck or so ...

Right now we get errors in dmesg etc ... not very user-friendly IMO.

greets, Stefan

Re: amrecover/amrestore: block size too small

[Debra S Baddorf]

> On Jun 24, 2019, at 7:14 AM, Stefan G. Weichinger  wrote:
> 
> 
> I stil have issues here:
> 
>  amrestore  --config abt -b 2097152 /dev/nst0 jupi smb_revision
> Restoring from tape ABT-401 starting with file 1.
> amrestore: 1: skipping split dumpfile: date 20190607213002 host juno
> disk vm182 part 1/UNKNOWN lev 0 comp N program /bin/tar
> 
> 
> [..]
> 
> 
> amrestore: 12: restoring split dumpfile: date 20190607213002 host jupi
> disk smb_revision part 1/UNKNOWN lev 1 comp .gz program /bin/tar crypt
> enc client_encrypt /usr/sbin/amcrypt client_decrypt_option -d
> filter stderr:
> filter stderr: aespipe: write failed
> filter stderr: gzip: stdin: decompression OK, trailing garbage ignored
> 
> 
> What?
> 
> I will try it with "-r"/raw now and try to decrypt later.


You can also use  “dd”  to get the whole dump off tape.  You would have to 
“glue” together
any partial files;  I don’t know how to do that  (I’ve specified no partial 
files).

“dd” still needs a reasonably correct block size.

Deb Baddorf

Re: amrecover/amrestore: block size too small

[Stefan G. Weichinger]

I stil have issues here:

  amrestore  --config abt -b 2097152 /dev/nst0 jupi smb_revision
Restoring from tape ABT-401 starting with file 1.
amrestore: 1: skipping split dumpfile: date 20190607213002 host juno
disk vm182 part 1/UNKNOWN lev 0 comp N program /bin/tar


[..]


amrestore: 12: restoring split dumpfile: date 20190607213002 host jupi
disk smb_revision part 1/UNKNOWN lev 1 comp .gz program /bin/tar crypt
enc client_encrypt /usr/sbin/amcrypt client_decrypt_option -d
filter stderr:
filter stderr: aespipe: write failed
filter stderr: gzip: stdin: decompression OK, trailing garbage ignored


What?

I will try it with "-r"/raw now and try to decrypt later.

Re: amrecover/amrestore: block size too small

[Stefan G. Weichinger]

Am 19.06.19 um 19:30 schrieb Stefan G. Weichinger:
> 
> I get
> 
> $ amrestore  --config abt /dev/nst0 jupi smb_revision
> ERROR: Error reading Amanda header: block size too small
> 
> $ amrestore  --config abt -b 32768 /dev/nst0 jupi smb_revision
> ERROR: Error reading Amanda header: block size too small
> 
> I don't have to say that I need these restores ...
> 
> Never really understood these blocksize issues anyway.
> 
> The tapetype used for long says:
> 
> define tapetype LTO-4 {
> length 698510208 kbytes
> filemark 0 kbytes
> speed 36696 kps
>     blocksize 32 kbytes
> }
> 
> How to restore, please?



$ amrestore  --config abt -b 2097152 /dev/nst0 jupi smb_revision

seems to work now ... at least it starts searching.

I don't know why I have to tell that ... but it seems I have a mismatch:


tapetype says 32 kbytes:

define tapetype LTO-4 {
comment "Created by amtapetype; compression disabled; 2017-10-31
sgw"
length 698510208 kbytes
filemark 0 kbytes
speed 36696 kps
blocksize 32 kbytes
}


changer def sets "2 mbytes":

define changer robot {
tpchanger "chg-robot:/dev/sg1"
property "tape-device" "0=tape:/dev/nst0"
device-property "BLOCK_SIZE" "2 mbytes"
device-property "READ_BLOCK_SIZE" "2 mbytes"
property "eject-before-unload" "no"
property "use-slots" "1-24"
changerfile "/etc/amanda/abt/chg-robot-dev-sg1"
}


storage def pulls in both:


define storage abt {
tapepool "abt"
tapetype "LTO-4"
tpchanger "robot"

[..]

}


Maybe then amrecover would also work (bailed out before as well)

amrecover/amrestore: block size too small

[Stefan G. Weichinger]

I get

$ amrestore  --config abt /dev/nst0 jupi smb_revision
ERROR: Error reading Amanda header: block size too small

$ amrestore  --config abt -b 32768 /dev/nst0 jupi smb_revision
ERROR: Error reading Amanda header: block size too small

I don't have to say that I need these restores ...

Never really understood these blocksize issues anyway.

The tapetype used for long says:

define tapetype LTO-4 {
length 698510208 kbytes
filemark 0 kbytes
speed 36696 kps
blocksize 32 kbytes
}

How to restore, please?

Re: amrestore and split dumps

[Jean-Francois Malouin]

* Jean-Louis Martineau <jmartin...@carbonite.com> [20160426 14:11]:
> You can't do that with amrestore.
> 
> Use amfetchdump to do that.

OK! 
I'm aware of amfetchdump. I was asking because I'm preparing an archive
to be shipped offsite for some people that don't have the archive's logs
and Amanda installed, for that matter. I thought they could make a fast
Amanda build without a config and use some amrestore incantation to
access and extract the archive.  I guess they will have to use mt, dd
and cat if they ever want to extract anything from it :)

Thanks,
jf

> 
> Jean-Louis
> 
> On 26/04/16 01:59 PM, Jean-Francois Malouin wrote:
> >Hi,
> >
> >It's been a while since I played with low-level restore tool like
> >amrestore: is there a way to force amrestore to restore all the split
> >dumps matching a client name and DLE on a volume without first
> >extracting them one by one on disk and then concatenate them to recreate
> >a tar ball, ie doing the restore on the fly so to speak, in one pass?
> >
> >thanks,
> >jf

-- 
Jean-Francois Malouin | IT Operations and Infrastructure
McConnell Brain Imaging Centre | MNI | McGill University

amrestore and split dumps

[Jean-Francois Malouin]

Hi,

It's been a while since I played with low-level restore tool like
amrestore: is there a way to force amrestore to restore all the split
dumps matching a client name and DLE on a volume without first
extracting them one by one on disk and then concatenate them to recreate
a tar ball, ie doing the restore on the fly so to speak, in one pass?

thanks,
jf

Re: restoring encrypted backups: amrecover vs amrestore

[Debra S Baddorf]

I’m pretty sure I tested an  amrecover  (not a whole amrestore)   with my 
setup,   where the server does the encryption.
And it worked,  I mean.   Or I wouldn’t have continued.

I might only have tested an amrecover  ON the server though,  and not on the 
client.  Mine are all connected,  so I guess
I figured I could recover onto the server  transport later   (more likely,  it 
just didn’t occur to me to test from a client).
Or maybe I did ….

Let us know how your test works.

Deb Baddorf




On Mar 13, 2015, at 3:46 PM, Oscar Ricardo Silva osi...@utexas.edu wrote:

 The idea behind client encryption is to treat each server/sysadmin as an 
 independent operator and with encryption done by the client the contents of 
 the tapes (or in our case, vtapes) wouldn't necessarily be accessible to the 
 amanda server operator.
 
 Ultimately, server encryption gets us a little closer. We're already 
 transmitting the backups over ssh so that gets us some privacy over the wire. 
 I'll switch over one of my test systems to server encryption and see how 
 that works.
 
 Thank you for the reply and the bump
 
 
 
 Oscar
 
 
 On 03/13/2015 03:33 PM, Debra S Baddorf wrote:
 Since you’ve gotten no answers yet  (I know very little):might this be 
 related to whether the client   or the  server
 is the one doing  the unpacking of the dump,   and in turn,   which one of 
 those also did the encrypting?
 
 I do some encrypting on one small set of nodes,  but the server does the 
 encrypting.   I’m merely making sure the tapes
 are encrypted so they can be stored remotely. Any reason why you have 
 the client itself doing the encryption?
 I suppose it is more private that way …..  specially if the data is going 
 over the network and might be seen there.
 
 This is by way of starting a discussion,  and also  “bump”.
 
 Deb Baddorf
 Fermilab
 
 
 On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva osi...@utexas.edu wrote:
 
 I've been testing encrypted storage of backups but am confused as to how to 
 restore files. In my setup, I run the backup server with other sysadmins 
 running the individual servers being backed up and ideally I'd like for 
 these sysadmins to restore files from the client systems without bothering 
 me ... I mean without involving me ...
 
 
 I've had no luck restoring files using amrecover (one server encrypted with 
 amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the 
 man page and saw:
 
 
 ***
 Note
 The Default values are those set at compile-time. Use amrestore to recover 
 client-encrypted or client-custom-compressed tapes.
 ***
 
 
 
 Does this mean that for the sysadmin of a client to restore files from an 
 encrypted backup, they can only use amrestore and not amrecover? amrestore 
 suggests (and I might be wrong) that the individual running it know a lot 
 about how the backups are stored.
 
 
 The backups *SEEM* to run OK and using amrecover I can even browse the 
 files that were backed up.
 
 
 I've reviewed the amanda HOWTOs and FAQ but while they describe the setup 
 for encrypted storage of backups, I don't believe there are examples on 
 restoring files.
 
 
 
 
 Oscar
 

Re: restoring encrypted backups: amrecover vs amrestore

[Debra S Baddorf]

Since you’ve gotten no answers yet  (I know very little):might this be 
related to whether the client   or the  server
is the one doing  the unpacking of the dump,   and in turn,   which one of 
those also did the encrypting?

I do some encrypting on one small set of nodes,  but the server does the 
encrypting.   I’m merely making sure the tapes
are encrypted so they can be stored remotely. Any reason why you have the 
client itself doing the encryption?
I suppose it is more private that way …..  specially if the data is going over 
the network and might be seen there.

This is by way of starting a discussion,  and also  “bump”.

Deb Baddorf
Fermilab


On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva osi...@utexas.edu wrote:

 I've been testing encrypted storage of backups but am confused as to how to 
 restore files. In my setup, I run the backup server with other sysadmins 
 running the individual servers being backed up and ideally I'd like for these 
 sysadmins to restore files from the client systems without bothering me ... I 
 mean without involving me ...
 
 
 I've had no luck restoring files using amrecover (one server encrypted with 
 amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the 
 man page and saw:
 
 
 ***
 Note
 The Default values are those set at compile-time. Use amrestore to recover 
 client-encrypted or client-custom-compressed tapes.
 ***
 
 
 
 Does this mean that for the sysadmin of a client to restore files from an 
 encrypted backup, they can only use amrestore and not amrecover? amrestore 
 suggests (and I might be wrong) that the individual running it know a lot 
 about how the backups are stored.
 
 
 The backups *SEEM* to run OK and using amrecover I can even browse the files 
 that were backed up.
 
 
 I've reviewed the amanda HOWTOs and FAQ but while they describe the setup for 
 encrypted storage of backups, I don't believe there are examples on restoring 
 files.
 
 
 
 
 Oscar

Re: restoring encrypted backups: amrecover vs amrestore

[Oscar Ricardo Silva]

The idea behind client encryption is to treat each server/sysadmin as an 
independent operator and with encryption done by the client the contents 
of the tapes (or in our case, vtapes) wouldn't necessarily be accessible 
to the amanda server operator.


Ultimately, server encryption gets us a little closer. We're already 
transmitting the backups over ssh so that gets us some privacy over the 
wire. I'll switch over one of my test systems to server encryption and 
see how that works.


Thank you for the reply and the bump



Oscar


On 03/13/2015 03:33 PM, Debra S Baddorf wrote:

Since you’ve gotten no answers yet  (I know very little):might this be 
related to whether the client   or the  server
is the one doing  the unpacking of the dump,   and in turn,   which one of 
those also did the encrypting?

I do some encrypting on one small set of nodes,  but the server does the 
encrypting.   I’m merely making sure the tapes
are encrypted so they can be stored remotely. Any reason why you have the 
client itself doing the encryption?
I suppose it is more private that way …..  specially if the data is going over 
the network and might be seen there.

This is by way of starting a discussion,  and also  “bump”.

Deb Baddorf
Fermilab


On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva osi...@utexas.edu wrote:


I've been testing encrypted storage of backups but am confused as to how to restore 
files. In my setup, I run the backup server with other sysadmins running the individual 
servers being backed up and ideally I'd like for these sysadmins to restore files from 
the client systems without bothering me ... I mean without involving me ...


I've had no luck restoring files using amrecover (one server encrypted with 
amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the man 
page and saw:


***
Note
The Default values are those set at compile-time. Use amrestore to recover 
client-encrypted or client-custom-compressed tapes.
***



Does this mean that for the sysadmin of a client to restore files from an 
encrypted backup, they can only use amrestore and not amrecover? amrestore 
suggests (and I might be wrong) that the individual running it know a lot about 
how the backups are stored.


The backups *SEEM* to run OK and using amrecover I can even browse the files 
that were backed up.


I've reviewed the amanda HOWTOs and FAQ but while they describe the setup for 
encrypted storage of backups, I don't believe there are examples on restoring 
files.




Oscar

restoring encrypted backups: amrecover vs amrestore

[Oscar Ricardo Silva]

I've been testing encrypted storage of backups but am confused as to how 
to restore files. In my setup, I run the backup server with other 
sysadmins running the individual servers being backed up and ideally I'd 
like for these sysadmins to restore files from the client systems 
without bothering me ... I mean without involving me ...



I've had no luck restoring files using amrecover (one server encrypted 
with amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to 
review the man page and saw:



***
Note
The Default values are those set at compile-time. Use amrestore to 
recover client-encrypted or client-custom-compressed tapes.

***



Does this mean that for the sysadmin of a client to restore files from 
an encrypted backup, they can only use amrestore and not amrecover? 
amrestore suggests (and I might be wrong) that the individual running it 
know a lot about how the backups are stored.



The backups *SEEM* to run OK and using amrecover I can even browse the 
files that were backed up.



I've reviewed the amanda HOWTOs and FAQ but while they describe the 
setup for encrypted storage of backups, I don't believe there are 
examples on restoring files.





Oscar

amrestore blocksize

[Stefan Gustafsson]

Hi,

We have an running amanda environment (Amanda-3.2.1) based on Ubuntu 
11.10 backing up

some XEN hosts.
Last week we did a full disaster recovery test and run into some 
problems using the

amrestore tool.

In our config we have:

define tapetype LTO-3 {
comment Created by amtapetype; compression enabled
length 413997056 kbytes
filemark 0 kbytes
speed 51186 kps
blocksize 1024 kbytes
}

I we run amrestore /dev/nst0 host / it exits with
ERROR: /bin/gzip exited with status 1

If we try amrestore --cconfig conf /dev/nst0 host /  it works
but it depends on the amanda.conf file being present and it's not
since it's a bare metal restore.

Our workaround is to do amrestore -r /dev/nst0 host / to read the RAW
files of the tape and then dd if=host._. bs=1024k skip=1 | gzip -dc 
| tar xv to

extract the files. It works for us but it's not ideal.

amrestore is documented to have a -b blocksize option but it does not 
work.


We tried amrestore -b 1024k /dev/nst0 host / but the perl code expects 
an integer and

aborts with a usage.

amrestore -b 1048576 /dev/nst0 host / dies with
ERROR: /bin/gzip exited with status 1 indicating the $opt_blocksize is 
not working.


Is it possible to get amrestore to automatically detect the block-size? 
Skipping all zero blocks

after the amanda header until start of data?

Best Regards,
Stefan Gustafsson
Expisoft AB, Sweden

Re: amrestore blocksize

[Jean-Louis Martineau]

Stefan,

The -b argument of amrestore is not working in 3.2.1
The attached patch was commited a long time ago to fix it.

Jean-Louis

On 12/03/2012 10:01 AM, Stefan Gustafsson wrote:

Hi,

We have an running amanda environment (Amanda-3.2.1) based on Ubuntu 
11.10 backing up

some XEN hosts.
Last week we did a full disaster recovery test and run into some 
problems using the

amrestore tool.

In our config we have:

define tapetype LTO-3 {
comment Created by amtapetype; compression enabled
length 413997056 kbytes
filemark 0 kbytes
speed 51186 kps
blocksize 1024 kbytes
}

I we run amrestore /dev/nst0 host / it exits with
ERROR: /bin/gzip exited with status 1

If we try amrestore --cconfig conf /dev/nst0 host /  it works
but it depends on the amanda.conf file being present and it's not
since it's a bare metal restore.

Our workaround is to do amrestore -r /dev/nst0 host / to read the RAW
files of the tape and then dd if=host._. bs=1024k skip=1 | gzip 
-dc | tar xv to

extract the files. It works for us but it's not ideal.

amrestore is documented to have a -b blocksize option but it does 
not work.


We tried amrestore -b 1024k /dev/nst0 host / but the perl code 
expects an integer and

aborts with a usage.

amrestore -b 1048576 /dev/nst0 host / dies with
ERROR: /bin/gzip exited with status 1 indicating the $opt_blocksize 
is not working.


Is it possible to get amrestore to automatically detect the 
block-size? Skipping all zero blocks

after the amanda header until start of data?

Best Regards,
Stefan Gustafsson
Expisoft AB, Sweden




diff --git a/server-src/amrestore.pl b/server-src/amrestore.pl
index 362ee65..41ea901 100644
--- a/server-src/amrestore.pl
+++ b/server-src/amrestore.pl
@@ -173,6 +173,16 @@ sub main {
 	return failure($err, $finished_cb) if $err;
 
 	$dev = $res-{'device'};
+
+	if ($opt_blocksize) {
+	if ( !$dev-property_set(BLOCK_SIZE, $opt_blocksize)) {
+		return failure($dev-error_or_status, $finished_cb);
+	}
+
+	# re-read the label with the correct blocksize
+	$dev-read_label();
+	}
+
 	if ($dev-status != $DEVICE_STATUS_SUCCESS) {
 	return failure($dev-error_or_status, $finished_cb);
 	}

Problems with amanda-3.3.0 and amrestore

[Michael Müskens]

Hello everybody,

since some time I've been testing amanda-3.3.0 but I'm still experiencing some 
troubles with using amrestore.

First of all: Backups to virtual tapes do run fine and extracting backups via

dd if=/backup/tapepools/DailySet/DailySet-15/00010.MYCLIENT._var_lib_amanda.0 
bs=32k skip=1 |gzip -dc |tar xvf - ./

as specified in the header of the tapefile brings the correct and expected 
result.
However, when I try to use amrestore the way I used to run in amanda-version  
3.0.0, the command ends with some error messages I do not understand.

For example: 

backup@MYSERVER:/backup/tapes/raid001/test$ amrestore -p 
/backup/tapepools/DailySet/DailySet-15/1.MYCLiENT._etc_amanda.0 | tar xvf - 
./
Reading from 
'/backup/tapepools/DailySet/DailySet-15/1.MYCLIENT._etc_amanda.0'
split dumpfile: date 20110801003001 host MYCLIENT disk /etc/amanda part 
1/UNKNOWN lev 0 comp .gz program /bin/tar
filter stderr: 
filter stderr: gzip: stdin: unexpected end of file
ERROR: /bin/gzip exited with status 1
tar: This does not look like a tar archive
tar: .: Not found in archive
tar: Exiting with failure status due to previous errors 

The tar-errors are follow-ups of the original gzip error, I guess, after 
googling some, I did not really find some threads or solutions to solve this 
problem, maybe I'm missing something? Do I have to use some other options? I 
tried -h and some other stuff, but it didn't work :/

Testing the tapefile on a system with the old c-based  amrestore, restoring 
works just fine, so I don't think the reason is the tapefile.

I know that I can still use dd but actually I was quite happy with amrestore, 
so I'd like to keep for my automated restores :)

If you need some more information please feel free to ask 

/Michael

-- 
Michael Müskens

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

amrestore, retriving ufsdump, bad filesystem block size

[Brian Cuttler]

Hi amanda users.

I am using amanda 3.1.2 on a Solaris 10/x86 system.
The client I'd been backing up is Solaris 9/sparc
with amanda 2.4.4.

While I recently changed the tape drive/jukebox on the
server from an SL24/LTO4 to a (I forget what)/lto5 I 
have made no other changes.

I have successfully retrieved data for the same client/DLE
from the LTO5 but am having a problem with the retireival
from the LTO4.

# amrestore /dev/rmt/3n mailserv /usr1

 ufsrestore -tf  mailserv._usr1.20110418183000.0.001
bad filesystem block size 1536

Same command, with only a change in the tape-device name,
worked correctly retreiving from the LTO5 drive.

Since I did not specify an amanda config to amrestore
I didn't think any changes to amanda.conf would come into play.

Am I overthinking this ?

How do I correctly retrieve the data from the LTO4 drive ?

thank you,

Brian
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amrestore, retriving ufsdump, bad filesystem block size

[Brian Cuttler]

Work-around
---

Looking in google I didn't see anything amanda specific but
did find articles talking about the zfs file system.

The client DLE is UFS, the work area I restored to is ZFS.

I copied one of the smaller dmp files over to /tmp which
is UFS and was able to read it fine.

I am now # cd'd to tmp but reading the dump file from the ZFS
file system. Seems to be working.

I don't have complete understanding though as the dumps that
had been written to the LTO5 where for the same UFS client DLE
and used the same ZFS work area...

I seem to be up and running but don't understand the underlying
mechanics.

The problem has been worked around, but I don't understand 
what is happening. Do any of you ?


On Tue, Jun 14, 2011 at 10:16:27AM -0400, Brian Cuttler wrote:
 
 Hi amanda users.
 
 I am using amanda 3.1.2 on a Solaris 10/x86 system.
 The client I'd been backing up is Solaris 9/sparc
 with amanda 2.4.4.
 
 While I recently changed the tape drive/jukebox on the
 server from an SL24/LTO4 to a (I forget what)/lto5 I 
 have made no other changes.
 
 I have successfully retrieved data for the same client/DLE
 from the LTO5 but am having a problem with the retireival
 from the LTO4.
 
 # amrestore /dev/rmt/3n mailserv /usr1
 
  ufsrestore -tf  mailserv._usr1.20110418183000.0.001
 bad filesystem block size 1536
 
 Same command, with only a change in the tape-device name,
 worked correctly retreiving from the LTO5 drive.
 
 Since I did not specify an amanda config to amrestore
 I didn't think any changes to amanda.conf would come into play.
 
 Am I overthinking this ?
 
 How do I correctly retrieve the data from the LTO4 drive ?
 
   thank you,
 
   Brian
 ---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amcrypt-ossl and amrestore

[lxnf98mm]

On Thu, 19 May 2011, Jean-Louis Martineau wrote:

Which amanda version are you using? There was a bug with 'amrestore -p' which 
is already fixed.


3.2.1



Jean-Louis

lxnf9...@comcast.net wrote:

 I use amcrypt-ossl for backups
 No problems using amrecover to restore
 In the past I have used amrestore -p /dev/nst1 no-such-host  /dev/null
 to read a tape and get a list when the index was lost
 That does not seem to work
 I get Restoring from tape week02 starting with file 1. and nothing else
 I probably have something misconfigured
 Any suggestions

 Richard Ray





--

amcrypt-ossl and amrestore

[lxnf98mm]

I use amcrypt-ossl for backups
No problems using amrecover to restore
In the past I have used amrestore -p /dev/nst1 no-such-host  /dev/null 
to read a tape and get a list when the index was lost

That does not seem to work
I get Restoring from tape week02 starting with file 1. and nothing else
I probably have something misconfigured
Any suggestions

Richard Ray

bug with amrestore and S3 vtapes

[Christopher McCrory]

Hello...

 amanda 3.2.0 on Ubuntu 10.04 32bit in an Amazon EC2 instance

 I seem to be running into a bug when restoring data from a S3 vtape
bucket.  amrestore -p  | restore -iovf -  always fails.  running
amrestore without -p works, but produces a ERROR: /bin/gzip exited with
status 2.  Then running restore on the resulting file works as
expected.  Has anyone else run into this?  

looking at the debug files I see something like:

Tue Jan 18 12:40:16 2011: amrestore: GET
https://s3.amazonaws.com/munge0004%2Dfilestart failed with
404/NoSuchKey

where there are 3 files for that dump.  It looks like amanda tries to
get a forth file that doesn't exist and passes the (non) result onto
gzip.

yes? no? maybe?



-- 
Christopher McCrory
To the optimist, the glass is half full.
To the pessimist, the glass is half empty.
To the engineer, the glass is twice as big as it needs to be.

Re: amrestore bug with split dumps (and workaround)

[Dustin J. Mitchell]

On Wed, Feb 24, 2010 at 5:08 PM, Christopher chris...@pricegrabber.com wrote:
 amfetchdump does not seem to have this problem, but you cannot run
 amfetchdump while amdump is running (which would be a cool feature ;)

We're working on that.  In fact, I think it should be doable in 3.1.
I'll make a note to test it before the release.

 I suspect something in amrestore does not like the 'part X/Y' text.  I
 looked at the source, but nothing jumped out at me as the cause.

Your first case, of amrestore trucking right on after finding the dump
it was looking for, is expected behavior - amrestore needs to scan
the whole tape, in case there are other dumps matching some.server /.

Amrestore is really not very good at re-assembling dumps.  I suspect
amrestore is outputting something to stdout despite the use of -p,
which is getting mixed into the datastream.  You could try the -p
command piped to a file instead of to /bin/restore.  Since it looks
like restore failed its checksum on the first bytes in the file, I
expect a hex editor would show the offending message in the first few
bytes of the piped output.

Dustin

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

Re: amrestore bug with split dumps (and workaround)

[Christopher]

Hello...

On Wed, 2010-02-24 at 17:33 -0600, Dustin J. Mitchell wrote:
 On Wed, Feb 24, 2010 at 5:08 PM, Christopher chris...@pricegrabber.com 
 wrote:
  amfetchdump does not seem to have this problem, but you cannot run
  amfetchdump while amdump is running (which would be a cool feature ;)
 
 We're working on that.  In fact, I think it should be doable in 3.1.
 I'll make a note to test it before the release.
 

yea!

  I suspect something in amrestore does not like the 'part X/Y' text.  I
  looked at the source, but nothing jumped out at me as the cause.
 
 Your first case, of amrestore trucking right on after finding the dump
 it was looking for, is expected behavior - amrestore needs to scan
 the whole tape, in case there are other dumps matching some.server /.
 

Was it always that way?  I haven't used amrestore since amfetchdump came
out.


 Amrestore is really not very good at re-assembling dumps.  I suspect
 amrestore is outputting something to stdout despite the use of -p,
 which is getting mixed into the datastream.  You could try the -p
 command piped to a file instead of to /bin/restore.  Since it looks
 like restore failed its checksum on the first bytes in the file, I
 expect a hex editor would show the offending message in the first few
 bytes of the piped output.


I'll spend some time tracking down exactly what is not being stripped
out.  Maybe stderr is being included?  My C programing skills are weak,
so I might not be able to provide a patch, but I can do the legwork to
find out exactly where the problem data is.  Currently my amdump runs
last 19 to 23 hours.  I got a third tape drive for the jukebox
specifically to be able to do restores without killing the running
amdump.  So being able to run amrestore without a workaround would be
good (amfetchdump --yes-I-know-what-I-am-doing --ignore-running-amdump
--use-drive /dev/nst2  would be better :).  In the example I gave the
data was only 25G, but the same workaround would be interesting with a
-gt 1Tb restore.


 Dustin
 


-- 
Christopher McCrory
 The guy that keeps the servers running
 
chris...@pricegrabber.com
 http://www.pricegrabber.com
 
Let's face it, there's no Hollow Earth, no robots, and
no 'mute rays.' And even if there were, waxed paper is
no defense.  I tried it.  Only tinfoil works.

Re: amrestore bug with split dumps (and workaround)

[Dustin J. Mitchell]

On Wed, Feb 24, 2010 at 6:40 PM, Christopher chris...@pricegrabber.com wrote:
 Was it always that way?  I haven't used amrestore since amfetchdump came
 out.

Yes.  Or, if not, it was a bug :)

 I'll spend some time tracking down exactly what is not being stripped
 out.  Maybe stderr is being included?  My C programing skills are weak,
 so I might not be able to provide a patch, but I can do the legwork to
 find out exactly where the problem data is.  Currently my amdump runs
 last 19 to 23 hours.  I got a third tape drive for the jukebox
 specifically to be able to do restores without killing the running
 amdump.  So being able to run amrestore without a workaround would be
 good (amfetchdump --yes-I-know-what-I-am-doing --ignore-running-amdump
 --use-drive /dev/nst2  would be better :).  In the example I gave the
 data was only 25G, but the same workaround would be interesting with a
 -gt 1Tb restore.

Stderr would not be included in the shell pipeline you pasted.  If you
can figure out what message is being included, you can probably
comment it out.  amrestore has been completely rewritten in 3.1, so
there's no sense producing a patch.

amidxtaped is careful to only try to lock the config if the tape drive
it's using is the same as the default for the config.  I thought
amfetchdump did the same thing, but perhaps not.  Anyway, amfetchdump
has also been rewritten (all of the recovery tools have been rewritte
- amidxtaped should be committed in a day or two once I sort out some
Amanda-2.4.5-compatibility issues), and now does not try to lock the
config at all.

By the way, the new code manages to not stomp on its own feet by
reserving particular volumes and/or drives in the changer, rather than
locking the entire config.

Dustin

P.S. You give yourself away as a shell programmer when you write -gt 1Tb ;)

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

amcheck vs amrestore

[Brian Cuttler]

Dustin, et al,

Periodically while I'm performing a restore with # amrestore
the cronjob # amcheck grabs and swaps out the tape on me.

Is there a way to interlock these two jobs so that doesn't happen ?

For my money, I guess, amcheck failing would be the prefered.

thanks,

Brian
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amcheck vs amrestore

[Dustin J. Mitchell]

On Mon, Nov 30, 2009 at 1:59 PM, Brian Cuttler br...@wadsworth.org wrote:
 Periodically while I'm performing a restore with # amrestore
 the cronjob # amcheck grabs and swaps out the tape on me.

 Is there a way to interlock these two jobs so that doesn't happen ?

 For my money, I guess, amcheck failing would be the prefered.

No, there's currently no way to interlock them because amrestore
doesn't take a config and therefore doesn't have any way to indicate
that any particular config is in use.

In the next version, amrestore will take a config, and will properly
reserve devices.

Dustin

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

Re: amcheck vs amrestore

[Brian Cuttler]

On Mon, Nov 30, 2009 at 02:08:01PM -0600, Dustin J. Mitchell wrote:
 On Mon, Nov 30, 2009 at 1:59 PM, Brian Cuttler br...@wadsworth.org wrote:
  Periodically while I'm performing a restore with # amrestore
  the cronjob # amcheck grabs and swaps out the tape on me.
 
  Is there a way to interlock these two jobs so that doesn't happen ?
 
  For my money, I guess, amcheck failing would be the prefered.
 
 No, there's currently no way to interlock them because amrestore
 doesn't take a config and therefore doesn't have any way to indicate
 that any particular config is in use.
 
 In the next version, amrestore will take a config, and will properly
 reserve devices.

Cool, can't wait.

thanks - Brian


 Dustin
 
 -- 
 Open Source Storage Engineer
 http://www.zmanda.com
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amcheck vs amrestore

[Jean-Louis Martineau]

Try amfetchdump instead of amrestore.

Jean-Louis

Brian Cuttler wrote:

Dustin, et al,

Periodically while I'm performing a restore with # amrestore
the cronjob # amcheck grabs and swaps out the tape on me.

Is there a way to interlock these two jobs so that doesn't happen ?

For my money, I guess, amcheck failing would be the prefered

Re: read only error on amrestore

[Dustin J. Mitchell]

On Fri, Oct 23, 2009 at 11:01 AM, Christopher chris...@pricegrabber.com wrote:
 I'm running amanda 2.6.1p1 on a rhel 5.4 server.  I am trying to restore
 some files from a ~2 year old archive backup.  Since it is an archive
 backup I have the write protect tab closed on the physical tape.  When I
 try to run amrestore I get:

 /usr/sbin/amrestore -p -h /dev/nst0 ...
 amrestore: Error reading volume label: Can't open tape device /dev/nst0:
 Read-only file system.

 Why does amrestore want to write to the tape?

From my answer to Ian 45 minutes ago:

This has been fixed in trunk.  Here's the patch:

http://github.com/djmitche/amanda/commit/c3548dc511152bfacf1b53abb7e452fc7161e2f8

Dustin

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

Re: amrestore and tape rewinding

[Darin Perusich]

Gene Heskett wrote:
 On Tuesday 26 May 2009, Darin Perusich wrote:
 Dustin J. Mitchell wrote:
 On Tue, May 26, 2009 at 2:56 PM, Darin Perusich

 darin.perus...@cognigencorp.com wrote:
 Why does 'amrestore' always rewind the tape when I go to restore
 something? This is something I just started seeing after upgrading to
 2.6.x, it wasn't happening with previous versions, 2.5.2. The man page
 says I can use '-f #' to fast forward the tape to a specific mark but
 when I've already done this or I want to say back it up a few marks to
 restore something else, or start another restore beginning at the
 current mark it's really a waste of time having to wait for the rewind
 and the ran back down the tape to retrieve the image.
 Amanda no longer relies on the no-rewind tape device, and always
 positions the tape itself.
 Being able to specify with an argument, -n or whatever, to not rewind
 the tape would be convenient, a time saver, and make for more efficient
 recovery I would think.

 You may want to consider using a single amrestore invocation to get
 the data you need, or using amrecover.
 The amount of data I'm attempting to restore is larger then the
 available holding disk space so using a single invocation or amrecover
 isn't an option.
 
 Since amrecover can, if you are sure of what you are doing, directly 
 overwrite 
 the stuff you are trying to restore, I am not seeing the connection between 
 amrecover and the holding disk's size.  Is my picture incomplete?

I'm restoring about 700gb of images for a bare metal restore and the
hold disk is around 500gb so after I restoring a portion of the images
I'm moving them to an nfs mount to free up space so I can continue
pulling the images from tape. When I initiate the amrestore it rewinds
the tape instead of just starting off at the current tape mark so I
can't just do 'amrestore ... server-name', I need to list out which
images to pull. Before 2.6.x I could just start the amrestore again and
it would pick up where I left off. Using the '-f #' option would be
nearly as convenient but it's not working, I posted another messages
about that already.

 Something else, how hard would it be to add another disk temporarily and spec 
 it as a holding disk, it could be mounted right on top of the /dumps 
 directory.  It wouldn't be the first time I've had temporary drives hanging 
 out of a 44 tower, propped up on a cardboard box if need be to make cables 
 fit. :)
 

I'm not able to do add any additional disk to this server unfortunately
and restoring to an nfs mount is just too slow.

-- 
Darin Perusich
Unix Systems Administrator
Cognigen Corporation
395 Youngs Rd.
Williamsville, NY 14221
Phone: 716-633-3463
Email: darin...@cognigencorp.com

Re: amrestore and tape rewinding

[Gene Heskett]

On Wednesday 27 May 2009, Darin Perusich wrote:
Gene Heskett wrote:
 On Tuesday 26 May 2009, Darin Perusich wrote:
 Dustin J. Mitchell wrote:
 On Tue, May 26, 2009 at 2:56 PM, Darin Perusich

 darin.perus...@cognigencorp.com wrote:
 Why does 'amrestore' always rewind the tape when I go to restore
 something? This is something I just started seeing after upgrading to
 2.6.x, it wasn't happening with previous versions, 2.5.2. The man page
 says I can use '-f #' to fast forward the tape to a specific mark but
 when I've already done this or I want to say back it up a few marks to
 restore something else, or start another restore beginning at the
 current mark it's really a waste of time having to wait for the rewind
 and the ran back down the tape to retrieve the image.

 Amanda no longer relies on the no-rewind tape device, and always
 positions the tape itself.

 Being able to specify with an argument, -n or whatever, to not rewind
 the tape would be convenient, a time saver, and make for more efficient
 recovery I would think.

 You may want to consider using a single amrestore invocation to get
 the data you need, or using amrecover.

 The amount of data I'm attempting to restore is larger then the
 available holding disk space so using a single invocation or amrecover
 isn't an option.

 Since amrecover can, if you are sure of what you are doing, directly
 overwrite the stuff you are trying to restore, I am not seeing the
 connection between amrecover and the holding disk's size.  Is my picture
 incomplete?

I'm restoring about 700gb of images for a bare metal restore and the
hold disk is around 500gb so after I restoring a portion of the images
I'm moving them to an nfs mount to free up space so I can continue
pulling the images from tape. When I initiate the amrestore it rewinds
the tape instead of just starting off at the current tape mark so I
can't just do 'amrestore ... server-name', I need to list out which
images to pull. Before 2.6.x I could just start the amrestore again and
it would pick up where I left off. Using the '-f #' option would be
nearly as convenient but it's not working, I posted another messages
about that already.

 Something else, how hard would it be to add another disk temporarily and
 spec it as a holding disk, it could be mounted right on top of the /dumps
 directory.  It wouldn't be the first time I've had temporary drives
 hanging out of a 44 tower, propped up on a cardboard box if need be to
 make cables fit. :)

I'm not able to do add any additional disk to this server unfortunately
and restoring to an nfs mount is just too slow.

No drive, or no spare channel?

But I still think you may be using the wrong tool.  Amrecover can write the 
recovered files anyplace you tell it to, and AFAIK there is no holding disk 
involved.  If you can cd to this NFS mount point, I believe that amrecover can 
write to it also.  If its slow, then I guess its slow.  AFAIK that should not 
kill the restoration.  Once you have added the list of files and typed 
extract, your only interaction would be inserting the tapes if it cannot find 
them in the rack, or in my case, the vtape list.  My tape insertion duties 
consist of hitting the return key when it asks for the next tape by name.  You 
would have to insert that tape by hand if it is not in the library already.

-- 
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)
The NRA is offering FREE Associate memberships to anyone who wants them.
https://www.nrahq.org/nrabonus/accept-membership.asp

AUTHOR
FvwmAuto just appeared one day, nobody knows how.
-- FvwmAuto(1x)

amrestore and tape rewinding

[Darin Perusich]

Why does 'amrestore' always rewind the tape when I go to restore
something? This is something I just started seeing after upgrading to
2.6.x, it wasn't happening with previous versions, 2.5.2. The man page
says I can use '-f #' to fast forward the tape to a specific mark but
when I've already done this or I want to say back it up a few marks to
restore something else, or start another restore beginning at the
current mark it's really a waste of time having to wait for the rewind
and the ran back down the tape to retrieve the image.

-- 
Darin Perusich
Unix Systems Administrator
Cognigen Corporation
395 Youngs Rd.
Williamsville, NY 14221
Phone: 716-633-3463
Email: darin...@cognigencorp.com

Re: amrestore and tape rewinding

[Darin Perusich]

Dustin J. Mitchell wrote:
 On Tue, May 26, 2009 at 2:56 PM, Darin Perusich
 darin.perus...@cognigencorp.com wrote:
 Why does 'amrestore' always rewind the tape when I go to restore
 something? This is something I just started seeing after upgrading to
 2.6.x, it wasn't happening with previous versions, 2.5.2. The man page
 says I can use '-f #' to fast forward the tape to a specific mark but
 when I've already done this or I want to say back it up a few marks to
 restore something else, or start another restore beginning at the
 current mark it's really a waste of time having to wait for the rewind
 and the ran back down the tape to retrieve the image.
 
 Amanda no longer relies on the no-rewind tape device, and always
 positions the tape itself.

Being able to specify with an argument, -n or whatever, to not rewind
the tape would be convenient, a time saver, and make for more efficient
recovery I would think.

 You may want to consider using a single amrestore invocation to get
 the data you need, or using amrecover.
 

The amount of data I'm attempting to restore is larger then the
available holding disk space so using a single invocation or amrecover
isn't an option.

-- 
Darin Perusich
Unix Systems Administrator
Cognigen Corporation
395 Youngs Rd.
Williamsville, NY 14221
Phone: 716-633-3463
Email: darin...@cognigencorp.com

Re: amrestore and tape rewinding

[Dustin J. Mitchell]

On Tue, May 26, 2009 at 4:32 PM, Darin Perusich
darin.perus...@cognigencorp.com wrote:
 Being able to specify with an argument, -n or whatever, to not rewind
 the tape would be convenient, a time saver, and make for more efficient
 recovery I would think.

One option may be to add a no-rewind property to the tape device.
I'm not sure how accurately varoius operating systems can determine
the current file, though, so this might be a dangerous property.  It's
also currently very difficult to supply properties via amrestore,
since it doesn't have a configuration file.

Dustin

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

Re: amrestore and tape rewinding

[Gene Heskett]

On Tuesday 26 May 2009, Darin Perusich wrote:
Dustin J. Mitchell wrote:
 On Tue, May 26, 2009 at 2:56 PM, Darin Perusich

 darin.perus...@cognigencorp.com wrote:
 Why does 'amrestore' always rewind the tape when I go to restore
 something? This is something I just started seeing after upgrading to
 2.6.x, it wasn't happening with previous versions, 2.5.2. The man page
 says I can use '-f #' to fast forward the tape to a specific mark but
 when I've already done this or I want to say back it up a few marks to
 restore something else, or start another restore beginning at the
 current mark it's really a waste of time having to wait for the rewind
 and the ran back down the tape to retrieve the image.

 Amanda no longer relies on the no-rewind tape device, and always
 positions the tape itself.

Being able to specify with an argument, -n or whatever, to not rewind
the tape would be convenient, a time saver, and make for more efficient
recovery I would think.

 You may want to consider using a single amrestore invocation to get
 the data you need, or using amrecover.

The amount of data I'm attempting to restore is larger then the
available holding disk space so using a single invocation or amrecover
isn't an option.

Since amrecover can, if you are sure of what you are doing, directly overwrite 
the stuff you are trying to restore, I am not seeing the connection between 
amrecover and the holding disk's size.  Is my picture incomplete?

Something else, how hard would it be to add another disk temporarily and spec 
it as a holding disk, it could be mounted right on top of the /dumps 
directory.  It wouldn't be the first time I've had temporary drives hanging 
out of a 44 tower, propped up on a cardboard box if need be to make cables 
fit. :)

-- 
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)
The NRA is offering FREE Associate memberships to anyone who wants them.
https://www.nrahq.org/nrabonus/accept-membership.asp

Z.O.I.D.: Zombie Optimized for Infiltration and Destruction

Re: amrestore and tape rewinding

[Dustin J. Mitchell]

On Tue, May 26, 2009 at 2:56 PM, Darin Perusich
darin.perus...@cognigencorp.com wrote:
 Why does 'amrestore' always rewind the tape when I go to restore
 something? This is something I just started seeing after upgrading to
 2.6.x, it wasn't happening with previous versions, 2.5.2. The man page
 says I can use '-f #' to fast forward the tape to a specific mark but
 when I've already done this or I want to say back it up a few marks to
 restore something else, or start another restore beginning at the
 current mark it's really a waste of time having to wait for the rewind
 and the ran back down the tape to retrieve the image.

Amanda no longer relies on the no-rewind tape device, and always
positions the tape itself.

You may want to consider using a single amrestore invocation to get
the data you need, or using amrecover.

Dustin

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

amrestore and multiple tapes

[Franck GANACHAUD]

Hello,

Server and client are 2.5.1p1 on debian etch

I've been trying to use amrestore but the backup is around 250Go 
splitted over 5 tapes and I'm not successful so far. amrestore is 
restoring the fileset using 10M size files.
Problem is amrestore doesn't close 10M files it already restored (can 
see it using lsof) and after some time, I hit the system limit for open 
files. I rose the system limit *4 but I'm not sure it will be enough as 
250Go/10Mo is a pretty high number.


Is this situation normal ?

Btw, is there a way to rebuild indexes from tapes?

Franck.

Re: amrestore and multiple tapes

[Jean-Louis Martineau]

It is easier to restore a splitted dump with amfetchdump. It will write 
a 250Go file.


There is no way to automatically rebuild index from tape.

Jean-Louis

Franck GANACHAUD wrote:

Hello,

Server and client are 2.5.1p1 on debian etch

I've been trying to use amrestore but the backup is around 250Go 
splitted over 5 tapes and I'm not successful so far. amrestore is 
restoring the fileset using 10M size files.
Problem is amrestore doesn't close 10M files it already restored (can 
see it using lsof) and after some time, I hit the system limit for 
open files. I rose the system limit *4 but I'm not sure it will be 
enough as 250Go/10Mo is a pretty high number.


Is this situation normal ?

Btw, is there a way to rebuild indexes from tapes?

Franck.

Re: amrestore and multiple tapes

[Dustin J. Mitchell]

On Wed, May 6, 2009 at 5:35 AM, Franck GANACHAUD
franck.ganach...@altran.com wrote:
 I've been trying to use amrestore but the backup is around 250Go splitted
 over 5 tapes and I'm not successful so far. amrestore is restoring the
 fileset using 10M size files.

First, you should be using a much larger split size than 10M -- you
are wasting a lot of time and tape space with files that small.
Assuming your tapes are ~60G, I would recommend somewhere around 1-3G.

 Problem is amrestore doesn't close 10M files it already restored (can see it
 using lsof) and after some time, I hit the system limit for open files. I
 rose the system limit *4 but I'm not sure it will be enough as 250Go/10Mo is
 a pretty high number.

 Is this situation normal ?

If the files are being restored in order, then amrestore should close
the files when it reassembles them.  If this is not happening, you
can use the -r flag, and then use dd to strip off the headers and
concatenate the results.

 Btw, is there a way to rebuild indexes from tapes?

Amfetchdump has a -i option to do this.  I'm not sure it was present in 2.5.1.

Dustin

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

Re: amrestore and multiple tapes

[Jean-Louis Martineau]

It neither works, then you must use dd!

For each file on tape
  position the tape on the file
  dd if=/dev/nst0 of=file.[number] bs=32k skip=1
concatenate all file.[number] files.

'amadmin [config] find hostname /fileset' list all files on tape you need.

You can also try to upgrade the server to 2.6.1p1.

The chunksize is for holding disk only, Dustin suggested to set the 
tape_splitsize and split_diskbuffer.


Jean-Louis

Franck GANACHAUD wrote:
Used amfetchdump and after 3hours of restore 10M files, it  just 
throwed a


amfetchdump: 3006: restoring split dumpfile: date 20090424 host 
hostname disk /fileset part 2992/UNKNOWN lev 0 comp .gz program /bin/tar

amfetchdump: missing file header block
could not fsf /dev/nst0: Input/output error
amfetchdump: could not fsf /dev/nst0: Input/output error

What does mean? I checked the library and it's still on first tape.
What can I do to manually get what's on various tapes?

Btw, I changed the chunksize to 1Gb in amanda.conf as Dustin suggested.

Jean-Louis Martineau a écrit :
It is easier to restore a splitted dump with amfetchdump. It will 
write a 250Go file.


There is no way to automatically rebuild index from tape.

Jean-Louis

Franck GANACHAUD wrote:

Hello,

Server and client are 2.5.1p1 on debian etch

I've been trying to use amrestore but the backup is around 250Go 
splitted over 5 tapes and I'm not successful so far. amrestore is 
restoring the fileset using 10M size files.
Problem is amrestore doesn't close 10M files it already restored 
(can see it using lsof) and after some time, I hit the system limit 
for open files. I rose the system limit *4 but I'm not sure it will 
be enough as 250Go/10Mo is a pretty high number.


Is this situation normal ?

Btw, is there a way to rebuild indexes from tapes?

Franck.

Re: amrestore and multiple tapes

[Franck GANACHAUD]

Used amfetchdump and after 3hours of restore 10M files, it  just throwed a

amfetchdump: 3006: restoring split dumpfile: date 20090424 host hostname 
disk /fileset part 2992/UNKNOWN lev 0 comp .gz program /bin/tar

amfetchdump: missing file header block
could not fsf /dev/nst0: Input/output error
amfetchdump: could not fsf /dev/nst0: Input/output error

What does mean? I checked the library and it's still on first tape.
What can I do to manually get what's on various tapes?

Btw, I changed the chunksize to 1Gb in amanda.conf as Dustin suggested.

Jean-Louis Martineau a écrit :
It is easier to restore a splitted dump with amfetchdump. It will 
write a 250Go file.


There is no way to automatically rebuild index from tape.

Jean-Louis

Franck GANACHAUD wrote:

Hello,

Server and client are 2.5.1p1 on debian etch

I've been trying to use amrestore but the backup is around 250Go 
splitted over 5 tapes and I'm not successful so far. amrestore is 
restoring the fileset using 10M size files.
Problem is amrestore doesn't close 10M files it already restored (can 
see it using lsof) and after some time, I hit the system limit for 
open files. I rose the system limit *4 but I'm not sure it will be 
enough as 250Go/10Mo is a pretty high number.


Is this situation normal ?

Btw, is there a way to rebuild indexes from tapes?

Franck.

amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[Charles Curley]

Running amanda-client-1:2.5.2p1-3--i386 on the client, Ubuntu 8.10,
and amanda-server-1:2.5.2p1-1--i386 on the server, Ubuntu
8.04. Everything is, as much as possible, stock.

I have never tried to restore from this client before. Backups appear
to be sucessful.

r...@dragon:/home/ccurley/projects/ror# echo $AMANDA_SERVER 
chaffee.localdomain
r...@dragon:/home/ccurley/projects/ror# echo $AMANDA_TAPE_SERVER 
chaffee.localdomain
r...@dragon:/home/ccurley/projects/ror# amrecover -C /etc/amanda/DailySet1
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
NAK: user root from localhost is not allowed to execute the service amindexd: 
Please add amindexd amidxtaped to the line in /var/backups/.amandahosts on 
the client
r...@dragon:/home/ccurley/projects/ror# 

However, I have already added the quoted text to the .amandahosts
file, on both client and server, like so:

chaffee.localdomain backup amindexd amidxtaped

(If I then run amcheck on the server, it complains ERROR: NAK
dragon.localdomain: user backup from chaffee.localdomain is not
allowed to execute the service noop: Please add amdump to the line
in /var/backups/.amandahosts on the client. So I added amdump, and
amcheck is once more satisfied.)

If I try to run amrecover as the backup user, it refuses to run:

bac...@dragon:~$ amrecover
amrecover: amrecover must be run by root
bac...@dragon:~$ 

On the server, chaffee, amanda is run by xinetd. All three of amanda,
amandaidx, and amidxtape have disable = no and server_args =
-auth=bsd amdump amindexd amidxtaped.

-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


signature.asc
Description: Digital signature

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[John Hein]

Charles Curley wrote at 08:29 -0700 on Mar  1, 2009:
  r...@dragon:/home/ccurley/projects/ror# amrecover -C /etc/amanda/DailySet1
  AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
  NAK: user root from localhost is not allowed to execute the service 
  amindexd: Please add amindexd amidxtaped to the line in 
  /var/backups/.amandahosts on the client

^^^ Note, user root


  However, I have already added the quoted text to the .amandahosts
  file, on both client and server, like so:
  
  chaffee.localdomain backup amindexd amidxtaped

You have the backup user here.

http://wiki.zmanda.com/index.php/How_To:Migrate_from_older_amanda_versions#Problems_with_amrecover_from_amanda_2.5

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[Charles Curley]

On Sun, Mar 01, 2009 at 10:11:38AM -0700, John Hein wrote:
 Charles Curley wrote at 08:29 -0700 on Mar  1, 2009:
   r...@dragon:/home/ccurley/projects/ror# amrecover -C /etc/amanda/DailySet1
   AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
   NAK: user root from localhost is not allowed to execute the service 
 amindexd: Please add amindexd amidxtaped to the line in 
 /var/backups/.amandahosts on the client
 
 ^^^ Note, user root
 
 
   However, I have already added the quoted text to the .amandahosts
   file, on both client and server, like so:
   
   chaffee.localdomain backup amindexd amidxtaped
 
 You have the backup user here.
 
 http://wiki.zmanda.com/index.php/How_To:Migrate_from_older_amanda_versions#Problems_with_amrecover_from_amanda_2.5

Right. I did:

--
chaffee.localdomain backup amdump
chaffee.localdomain root amindexd amidxtaped
--

and various permutations thereof on the client and the server. No go.

I also commented out server_args in the xinetd.d/amanda file. Also no
go.

-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


signature.asc
Description: Digital signature

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[John Hein]

Charles Curley wrote at 11:48 -0700 on Mar  1, 2009:
  On Sun, Mar 01, 2009 at 10:11:38AM -0700, John Hein wrote:
   Charles Curley wrote at 08:29 -0700 on Mar  1, 2009:
 r...@dragon:/home/ccurley/projects/ror# amrecover -C 
   /etc/amanda/DailySet1
 AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
 NAK: user root from localhost is not allowed to execute the service 
   amindexd: Please add amindexd amidxtaped to the line in 
   /var/backups/.amandahosts on the client
   
   ^^^ Note, user root
   
   
 However, I have already added the quoted text to the .amandahosts
 file, on both client and server, like so:
 
 chaffee.localdomain backup amindexd amidxtaped
   
   You have the backup user here.
   
   http://wiki.zmanda.com/index.php/How_To:Migrate_from_older_amanda_versions#Problems_with_amrecover_from_amanda_2.5
  
  Right. I did:
  
  --
  chaffee.localdomain backup amdump
  chaffee.localdomain root amindexd amidxtaped
  --
  
  and various permutations thereof on the client and the server. No go.
  
  I also commented out server_args in the xinetd.d/amanda file. Also no
  go.

Do you know how your stock ubuntu build of amanda was configured (the
args to configure)?

I just noticed that the request came from 'localhost' which does
not match your .amandahosts entry.

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[Charles Curley]

On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote:

 
 Do you know how your stock ubuntu build of amanda was configured (the
 args to configure)?
 
 I just noticed that the request came from 'localhost' which does
 not match your .amandahosts entry.

Short of pulling in the source package and looking at that, I have no
idea. I don't even know how to find out, other than ask on another
list.

I also don't see any way to override the host name. -o host and -o
hostname are rejected.

-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


signature.asc
Description: Digital signature

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[Charles Curley]

On Sun, Mar 01, 2009 at 02:18:27PM -0700, Charles Curley wrote:
 On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote:
 
  
  Do you know how your stock ubuntu build of amanda was configured (the
  args to configure)?
  
  I just noticed that the request came from 'localhost' which does
  not match your .amandahosts entry.
 
 Short of pulling in the source package and looking at that, I have no
 idea. I don't even know how to find out, other than ask on another
 list.
 
 I also don't see any way to override the host name. -o host and -o
 hostname are rejected.

For what it's worth, I came up with a work-around. On the server, I
added localhost.localdomain to .amandahosts, ran amrecover, and that
worked.

--
chaffee.localdomain backup amdump
chaffee.localdomain root amindexd amidxtaped
localhost.localdomain root amindexd amidxtaped
--

r...@chaffee:~/test# amrecover 
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
220 chaffee AMANDA index server (2.5.2p1) ready.
Setting restore date to today (2009-03-01)
200 Working date set to 2009-03-01.
200 Config set to DailySet1.
501 Host chaffee is not in your disklist.
Trying host chaffee.localdomain ...
200 Dump host set to chaffee.localdomain.
Use the setdisk command to choose dump disk to recover
amrecover help

From there, sethost, setdisk, setdate, and it looks like I'm on my
way.

But this is not The Way It's Supposed To Work, is it?

-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


signature.asc
Description: Digital signature

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[John Hein]

Charles Curley wrote at 16:53 -0700 on Mar  1, 2009:
  On Sun, Mar 01, 2009 at 02:18:27PM -0700, Charles Curley wrote:
   On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote:
Do you know how your stock ubuntu build of amanda was configured (the
args to configure)?

I just noticed that the request came from 'localhost' which does
not match your .amandahosts entry.
   
   Short of pulling in the source package and looking at that, I have no
   idea. I don't even know how to find out, other than ask on another
   list.

Yep, this is an example of one disadvantage of using prebuilt packages.


   I also don't see any way to override the host name. -o host and -o
   hostname are rejected.

man amrecover (see -s  -t).  I don't know if there is a run-time
configuration option for these (I didn't see one after a quick read
of the man pages) - if so, -o would be of no help.


  For what it's worth, I came up with a work-around. On the server, I
  added localhost.localdomain to .amandahosts, ran amrecover, and that
  worked.

Yes, that is what I was getting at.  Good to hear it worked for you.


  --
  chaffee.localdomain backup amdump
  chaffee.localdomain root amindexd amidxtaped
  localhost.localdomain root amindexd amidxtaped
  --
  
  r...@chaffee:~/test# amrecover 
  AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
  220 chaffee AMANDA index server (2.5.2p1) ready.
  Setting restore date to today (2009-03-01)
  200 Working date set to 2009-03-01.
  200 Config set to DailySet1.
  501 Host chaffee is not in your disklist.
  Trying host chaffee.localdomain ...
  200 Dump host set to chaffee.localdomain.
  Use the setdisk command to choose dump disk to recover
  amrecover help
  
  From there, sethost, setdisk, setdate, and it looks like I'm on my
  way.
  
  But this is not The Way It's Supposed To Work, is it?

Not sure what you mean.  If someone configured the build of amanda
(specifically the amrecover part of amanda in this case) with
--with-index-server=localhost, then, yes, what you experienced is the
expected behavior.

If you are asking if most people configure amanda that way, I'd say
probably not, but who knows - I can say that I don't.  If you want,
you can take it up with the debian/ubuntu packager.  FWIW, the default
in the configure script if you don't specify --with-index-server is
`uname -n`.

If you want better control, you can build amanda from source yourself.

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[John Hein]

John Hein wrote at 17:49 -0700 on Mar  1, 2009:
  man amrecover (see -s  -t).  I don't know if there is a run-time
  configuration option for these (I didn't see one after a quick read
  of the man pages) - if so, -o would be of no help.
  ^^^ s/so/not/

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[Charles Curley]

On Sun, Mar 01, 2009 at 05:49:20PM -0700, John Hein wrote:
 Charles Curley wrote at 16:53 -0700 on Mar  1, 2009:
   On Sun, Mar 01, 2009 at 02:18:27PM -0700, Charles Curley wrote:
On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote:
 Do you know how your stock ubuntu build of amanda was configured (the
 args to configure)?
 
 I just noticed that the request came from 'localhost' which does
 not match your .amandahosts entry.

Short of pulling in the source package and looking at that, I have no
idea. I don't even know how to find out, other than ask on another
list.
 
 Yep, this is an example of one disadvantage of using prebuilt packages.
 
 
I also don't see any way to override the host name. -o host and -o
hostname are rejected.
 
 man amrecover (see -s  -t).  I don't know if there is a run-time
 configuration option for these (I didn't see one after a quick read
 of the man pages) - if so, -o would be of no help.

Those set the index and tape servers, respectively. Supposedly, you
can also do that with environmental variables. I tried environmental
variables, and they didn't work.

 
 
   For what it's worth, I came up with a work-around. On the server, I
   added localhost.localdomain to .amandahosts, ran amrecover, and that
   worked.
 
 Yes, that is what I was getting at.  Good to hear it worked for you.
 
 
   --
   chaffee.localdomain backup amdump
   chaffee.localdomain root amindexd amidxtaped
   localhost.localdomain root amindexd amidxtaped
   --
   
   r...@chaffee:~/test# amrecover 
   AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
   220 chaffee AMANDA index server (2.5.2p1) ready.
   Setting restore date to today (2009-03-01)
   200 Working date set to 2009-03-01.
   200 Config set to DailySet1.
   501 Host chaffee is not in your disklist.
   Trying host chaffee.localdomain ...
   200 Dump host set to chaffee.localdomain.
   Use the setdisk command to choose dump disk to recover
   amrecover help
   
   From there, sethost, setdisk, setdate, and it looks like I'm on my
   way.
   
   But this is not The Way It's Supposed To Work, is it?
 
 Not sure what you mean.  If someone configured the build of amanda
 (specifically the amrecover part of amanda in this case) with
 --with-index-server=localhost, then, yes, what you experienced is the
 expected behavior.

I mean that amrecover should work on the client. It doesn't seem to be
a good idea for a large shop to allow folks root access on the Amanda
server so they can restore files. Of course, with virtual tapes, you
have to give the operator root access so he can play with
symlinks. (Or has that gotten better since I last played with them?)


 
 If you are asking if most people configure amanda that way, I'd say
 probably not, but who knows - I can say that I don't.  If you want,
 you can take it up with the debian/ubuntu packager.  FWIW, the default
 in the configure script if you don't specify --with-index-server is
 `uname -n`.

Which in a precompiled package would give you the host name of the
build machine, rather useless for the rest of the universe. How about
having it call the OS to enquire, and providing an option to override?
But that has its own security problems.

 
 If you want better control, you can build amanda from source
 yourself.

Thanks. I'll pass.

Anyway, thanks for helping me out.


-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


signature.asc
Description: Digital signature

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[John Hein]

Charles Curley wrote at 18:54 -0700 on Mar  1, 2009:
  On Sun, Mar 01, 2009 at 05:49:20PM -0700, John Hein wrote:
   man amrecover (see -s  -t).  I don't know if there is a run-time
   configuration option for these (I didn't see one after a quick read
   of the man pages) - if so, -o would be of no help.
  
  Those set the index and tape servers, respectively. Supposedly, you
  can also do that with environmental variables. I tried environmental
  variables, and they didn't work.

Indeed, and the code seems to agree with the man page...

recover-src/amrecover.c:server_name = getenv(AMANDA_SERVER);
recover-src/amrecover.c:tape_server_name = getenv(AMANDA_TAPE_SERVER);

I believe it has worked for me in the past.


  I mean that amrecover should work on the client.

Yes, it does work on the client.


   If you are asking if most people configure amanda that way, I'd say
   probably not, but who knows - I can say that I don't.  If you want,
   you can take it up with the debian/ubuntu packager.  FWIW, the default
   in the configure script if you don't specify --with-index-server is
   `uname -n`.
  
  Which in a precompiled package would give you the host name of the
  build machine, rather useless for the rest of the universe.

Which is perhaps why they might override that with 'localhost'.  If I
were the packager, I'd probably pick some host name that you could
define as a good CNAME (or additional A record) in DNS, like 'backup',
but there's a risk of picking something that will clash for someone
out there.
Having it overridable in amanda.conf would be good for this
issue.  If it really is not, then it might make a simple project
for someone.


  How about having it call the OS to enquire, and providing an option
  to override?  But that has its own security problems.

Inquire what?  DNS?  Some LDAP map?  I think -s  -t should work as
a way to override - not sure why they didn't for you.  I don't
see a security issue since the server can decide which client
hosts to allow (except perhaps for spoofing issues, but if
you have problems with that, amanda may be the least of
your worries).

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

[Charles Curley]

On Sun, Mar 01, 2009 at 07:28:32PM -0700, John Hein wrote:
 Charles Curley wrote at 18:54 -0700 on Mar  1, 2009:
   On Sun, Mar 01, 2009 at 05:49:20PM -0700, John Hein wrote:
man amrecover (see -s  -t).  I don't know if there is a run-time
configuration option for these (I didn't see one after a quick read
of the man pages) - if so, -o would be of no help.
   
   Those set the index and tape servers, respectively. Supposedly, you
   can also do that with environmental variables. I tried environmental
   variables, and they didn't work.
 
 Indeed, and the code seems to agree with the man page...
 
 recover-src/amrecover.c:server_name = getenv(AMANDA_SERVER);
 recover-src/amrecover.c:tape_server_name = 
 getenv(AMANDA_TAPE_SERVER);
 
 I believe it has worked for me in the past.

The problem is that amrecover is using the name localhost for the
host it is running on, not for the tape or index server. So those may
have worked correctly.

The problem was that there was no line for localhost in the server's
.amandahosts file. Once I added one, it worked, but only for amrecover
on the server. I conjecture that the server looks up the name that
amrecover uses, and it had better agree with the IP address where the
request comes from. Which in this case it would only do if the request
came from the same machine.


 
 
   I mean that amrecover should work on the client.
 
 Yes, it does work on the client.
 
 
If you are asking if most people configure amanda that way, I'd say
probably not, but who knows - I can say that I don't.  If you want,
you can take it up with the debian/ubuntu packager.  FWIW, the default
in the configure script if you don't specify --with-index-server is
`uname -n`.
   
   Which in a precompiled package would give you the host name of the
   build machine, rather useless for the rest of the universe.
 
 Which is perhaps why they might override that with 'localhost'.  If I
 were the packager, I'd probably pick some host name that you could
 define as a good CNAME (or additional A record) in DNS, like 'backup',
 but there's a risk of picking something that will clash for someone
 out there.

Now you'd have to muck with your DNS every time you wanted to change
which client could restore.

 Having it overridable in amanda.conf would be good for this
 issue.  If it really is not, then it might make a simple project
 for someone.

Or amanda-client.conf. Otherwise, (not having looked at the source) I
agree.

 
 
   How about having it call the OS to enquire, and providing an option
   to override?  But that has its own security problems.
 
 Inquire what?  DNS?  Some LDAP map?  I think -s  -t should work as
 a way to override - not sure why they didn't for you.

I think they worked just fine. What I need is a way, short of
compilation, to tell the client what its host is. In my case, on
dragon, the client, I would have liked to set something like:

my_host_name = dragon


 I don't see a security issue since the server can decide which
 client hosts to allow (except perhaps for spoofing issues, but if
 you have problems with that, amanda may be the least of your
 worries).

Spoofing is what I had in mind. Your comment about Amanda being the
least of one's worries in that case is well taken. I agree.

-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB


signature.asc
Description: Digital signature

[Amanda-users] how to use amrestore

[ay4you]

Hi
Can anyone tell me how to use amrestore i have done 
amrestore tapefile host
now i have a big file which i cant open
how do i extract the files there

+--
|This was sent by mahmoudh...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] how to use amrestore

[Marc Muehlfeld]

ay4you schrieb:
Can anyone tell me how to use amrestore i have done 
amrestore tapefile host

now i have a big file which i cant open
how do i extract the files there


Why you want to use amrestore and not amrecover?

# man amrecover



Regards
Marc


--
Marc Muehlfeld (Leitung IT)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780
http://www.medizinische-genetik.de

[Amanda-users] how to use amrestore

[ay4you]

i want to restore because the server was rebuilt and amrecover is not reading 
the old backups i took only the new ones i havnt had any luck with amrecover so 
i want to try amrestore

+--
|This was sent by mahmoudh...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] how to use amrestore

[Jean-Louis Martineau]

Why you can't open the file?

Jean-Louis

ay4you wrote:

Hi
Can anyone tell me how to use amrestore i have done 
amrestore tapefile host

now i have a big file which i cant open
how do i extract the files there

+--
|This was sent by mahmoudh...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


  

Re: amanda 2.6.1 amrestore issue

[Jon LaBadie]

On Fri, Feb 27, 2009 at 12:03:21PM -0500, Dustin J. Mitchell wrote:
 I'm sorry -- I somehow filed this away withot answering.
 
 On Mon, Feb 23, 2009 at 3:59 PM, Brian Cuttler br...@wadsworth.org wrote:
  read(4, 0x080887A0, 32768) ? ? ? ? ? ? ? ? ? ? ?Err#5 EIO
 
...
 Note that the actions Amanda is performing are:
  open
  rewind
  read 32k blocks until getting an EOF indication:
/2: read(4, 0x08170A40, 32768)  = 0
  attempt to read the next block (which should begin the next file)
 
 These steps aren't particularly easy to duplicate from the command
 line, since 'dd' closes its input once it reaches an EOF.

You can use a shell workaround/trick to deal with this:

# (
cmd1
cmd2
...
cmdn
)  /dev/tapedevice  /dev/tapedevice

The shell creates a subprocess that runs the commands
between the parentheses.  Stdin and stdout are open
to the tape device at the start of this subprocess and
stays open through all cmds between the parens.

Any dd commands between the parens should omit and if=
and of= arguments as you want the defaults of stdin/out.

jl
-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

amanda 2.6.1 amrestore issue

[Brian Cuttler]

I'm running amanda 2.6.1 on Solaris 10/x86 and having a problem with
my test of a file restore.

tapedev is /dev/rmt/0hn, its an LTO4, should probably just use /dev/rmt/0n.
Tape is imbedded in an SL24 jukebox, the the problem doesn't seem related
to the robot.

Interestingly, same version was able to run a restore on DLT drive
on solaris 10/Sparc, so I'm thinking me rather than architecture 
(that is solaris sparc v x86, not Amanda architecture), but I don't
know for sure.

Target file system is ZFS produced with snapshots, but again, parallel
config with the Sparc system.

# amrestore /dev/rmt/0hn 
Restoring from tape Curie01 starting with file 1.
amrestore: 1: restoring FILE: date 20090223143428 host curie disk /thump lev 1 
comp .gz program APPLICATION
Could not seek device /dev/rmt/0hn to file 2: Error reading Amanda header.


---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Re: amanda 2.6.1 amrestore issue

[Dustin J. Mitchell]

On Mon, Feb 23, 2009 at 3:18 PM, Brian Cuttler br...@wadsworth.org wrote:
 amdevchec liked the drive, and amlabel and amcheck report
 success when labeling or checking it.

Sorry, I didn't mean to reply privately in my last message.  Anyway,
can you try running the amrestore under 'truss' to see what is going
on at the syscall level?  Just snip the part between where it opens
the tape device and the final error message.

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com

Re: amanda 2.6.1 amrestore issue

[Paul Yeatman]

Are you able to manually seek to this tape file on this same host and
device?

   mt -f /dev/rmt/0hn asf 2

If so, can you read the header?

   dd if=/dev/rmt/0hn bs=32k count=1

Trying to narrow it down to the device/tape or Amanda.

Paul

On Mon, 2009-02-23 at 14:40 -0500, Brian Cuttler wrote:
 I'm running amanda 2.6.1 on Solaris 10/x86 and having a problem with
 my test of a file restore.
 
 tapedev is /dev/rmt/0hn, its an LTO4, should probably just use /dev/rmt/0n.
 Tape is imbedded in an SL24 jukebox, the the problem doesn't seem related
 to the robot.
 
 Interestingly, same version was able to run a restore on DLT drive
 on solaris 10/Sparc, so I'm thinking me rather than architecture 
 (that is solaris sparc v x86, not Amanda architecture), but I don't
 know for sure.
 
 Target file system is ZFS produced with snapshots, but again, parallel
 config with the Sparc system.
 
 # amrestore /dev/rmt/0hn 
 Restoring from tape Curie01 starting with file 1.
 amrestore: 1: restoring FILE: date 20090223143428 host curie disk /thump lev 
 1 comp .gz program APPLICATION
 Could not seek device /dev/rmt/0hn to file 2: Error reading Amanda header.
 
 
 ---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
 
 
 
 IMPORTANT NOTICE: This e-mail and any attachments may contain
 confidential or sensitive information which is, or may be, legally
 privileged or otherwise protected by law from further disclosure.  It
 is intended only for the addressee.  If you received this in error or
 from someone who was not authorized to send it to you, please do not
 distribute, copy or use it or any attachments.  Please notify the
 sender immediately by reply e-mail and delete this from your
 system. Thank you for your cooperation.
 
 
-- 
Design Engineer
Zmanda, Inc.
http://www.zmanda.com/

buglets with amrestore and amfetchdump

[Christopher McCrory]

Hello...

  amanda version: 2.5.2p1
  redhat linux 5.2 64bit
  intel hardware
  LTO-4 tapes in a dell jukebox with two drives

  Recently I had to restore some data from several months ago. I ran
into the folowing bugs/buglets.

1:
[EMAIL PROTECTED] tmp]$ amfetchdump -b 256k -d /dev/nst1   -ap  DailySet1
server /data 20080212171101 |  /sbin/restore -ivf - 
Verify tape and initialize maps
Input is from a local file/pipe

1 tape(s) needed for restoration
amfetchdump: /var/lib/amanda/DailySet1/log exists: amdump or amflush is
already running, or you must run amcleanup
/sbin/restore: Tape read error on first record


It would be nice to be able to tell amfetchdump that we are not using
the same tape drive as the running amdump process so it is OK to
continue. 


2: despite what the man page says, when compiled with
--with-maxtapeblocksize=512 and define tapetype LTO-4 { blocksize
256 ...  you still must use amfetchdump -b 256k when doing a recovery.

from man amfetchdump
-b blocksize
 Force a particular block size when reading from tapes. This value
 will usually be autodetected, and should not normally need to be
 set.

( same with amrestore  )

3: ( for me at least) amrestore cannot handle (with -p) tape_splitsize
( I have tape_splitsize 10 Gb) with amcrypt-ossl-asym. 

[EMAIL PROTECTED] tmp]$ amrestore -p  -b 256k /dev/nst1 server /data
| /sbin/restore -ivf -
Verify tape and initialize maps
Input is from a local file/pipe
amrestore: missing file header block
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 1: skipping otherserver._.20080212171801.0
amrestore: 2: restoring server._data.20080212171801.0.01
Checksum error 24522315214, inode 0 file (null)
/sbin/restore: Tape is not a dump tape
amrestore: restore: wrote 65536 of 262144 bytes: Broken pipe

( yes, using dump not gnutar )


not using -p will get them off the tape, but when you are trying to get
a couple files off a 1Tbyte+ filesystem it is tricky :) 

I suspect the crypto subsystem is causing the problem.  non-split
restores work fine.



-- 
Christopher McCrory
 The guy that keeps the servers running

To the optimist, the glass is half full.
To the pessimist, the glass is half empty.
To the engineer, the glass is twice as big as it needs to be.

Re: Discrepancy between amrestore and dd speeds

[Greg Troxel]

  [EMAIL PROTECTED] amrestore -r /dev/nst0 hostname /foo/bar

This will uncompress your dumps, which are probably gzipped, and that
takes CPU and more disk bandwidth to write.  If they are compressed,
give '-c' to amrestore to leave them alone.

(IMHO amrestore should default to not changing compression, and have
options to force compression and force uncompression.)

Re: Discrepancy between amrestore and dd speeds

[Dustin J. Mitchell]

On Dec 22, 2007 2:20 PM, Greg Troxel [EMAIL PROTECTED] wrote:
   [EMAIL PROTECTED] amrestore -r /dev/nst0 hostname /foo/bar

 This will uncompress your dumps, which are probably gzipped, and that
 takes CPU and more disk bandwidth to write.  If they are compressed,
 give '-c' to amrestore to leave them alone.

Even without decompression, there are a nontrivial number of  copies
performed in the amrestore process, vs. dd, which essentially runs
while (!eof()) { read(buf); write(buf); }, if not something faster
like memory mapping.  That said, the initial analysis of block sizes
uncovered the likely culprit, so I'll be interested to see how the
Device API (under which this was completely rewritten) performs.

Dustin

P.S. To Stefan's wondering where are all the hackers? -- we're all
working hard to get a new release ready.  That's also why I totally
failed to identify the source of the mystery 'r*' directories in
another thread.  Thanks to Jean-Louis for straightening me out there!

-- 
Storage Software Engineer
http://www.zmanda.com

Discrepancy between amrestore and dd speeds

[Ryan Steele]

Hello list,

I've been performance testing Amanda, trying to get the setup ready for 
prime-time, but I'm having an issue getting my read speeds from tape to 
get even to 6MB/s.  My writes are about 12.7MB/s, which is what the tape 
drive boasts (12-24MB/s normal and 2:1 compression, respectively).  But, 
my reads seem to hover around 5.5MB/s.  I ran some dd tests, which show 
the data being pulled off at 11.7MB/s, and I'm not quite sure how to 
tell what amrestore is doing that is causing the performance drop off.  
Here are the tests I ran; any help is appreciated.


[EMAIL PROTECTED] dd if=/dev/nst0 of=/home/restores/foobar bs=256K 
count=1G

  10308+0 records in
  10307+0 records out
  2701918208 bytes (2.7 GB) copied, 
230.539 seconds, 11.7 MB/s



[EMAIL PROTECTED] amrestore -r /dev/nst0 hostname /foo/bar

[EMAIL PROTECTED] stat /home/restores/hostname._foo_bar.20071216.0.1.RAW
  File: 
`home/restores/hostname._foo_bar.20071216.0.1.RAW'
  Size: 2836922368  Blocks: 
5546275IO Block: 131072 regular file
  Device: 908h/2312d  Inode: 
13  Links: 1
  Access: (0640/-rw-r-)  Uid: 
(   34/  backup)   Gid: (   34/  backup)
  Access: 2007-12-18 
12:50:15.0 -0500
  Modify: 2007-12-18 
12:58:40.0 -0500
  Change: 2007-12-18 
12:58:40.0 -0500


So,  ~8 minutes for a 2.7GB file = ~5.7MB/s.  I saw similar performance 
when retrieving a DLE that spanned 6 chunks (~5.3MB/s)  No errors or 
anything in my amrestore logs, just start and stop times.  I'm kind of 
at a loss as to what would be causing this, unless my calculations ( 
size / time ) aren't valid?  Thanks.


Best Regards,
Ryan

--
Ryan Steele 
Systems Administrator   
The Archer Group

Re: Discrepancy between amrestore and dd speeds

[Ryan Steele]

Jeremy,

If I can make the process more efficient, then that's what I want to 
do.  In the event of a catastrophe, time is money. 

I have tracked down what I believe to be a bug; that is, if no blocksize 
is defined for amrestore, it defaults to 32K, even though the man page 
says Amrestore should normally be able to determine the blocksize for 
tapes on its own and not need this parameter - I wrote to the tape in 
256K blocks.  I straced it both with and without the explicit blocksize 
parameter, and I can see the read/write blocksizes differ in between the 
runs.  This really ought to be fixed, both in amrestore's behavior, and 
in the man pages.  (Version 2.5.1p1-2.1, the latest in Debian Etch.  The 
source files do not differ from the original releases.)


However, setting that option seems (disappointingly) to not make any 
difference.  I ran strace with the -t option, and saw that in both 
cases, the data transfer rate was about the same - between 5 and 6 MB/s, 
even though the block sizes were different.  This kind of makes me think 
that's not my bottleneck, but any informed opinions on the subject are 
welcome.


I'm not sure if this is of any consequence or not, but 'mt -f /dev/nst0 
status' tells me my 'Tape block size' is 1024 bytes; the max is just shy 
of 256K.  I'll try setting that to both 0 and the max, and see if that 
generates any different results.  Again, informed opinions welcome.


TIA for any insight,

Ryan

--
Ryan Steele 
Systems Administrator   
The Archer Group




Jeremy Mordkoff wrote:

I know this is no answer, so apologies in advance.

Why are you worried about restore speeds? Hopefully you will never need
it and if you do, will anyone really complain that it took a little
longer than the tape drive is capable of? My users are usually just
grateful that they can get anything back. Plus, if I'm too quick,
they'll ask more and more often :)

JLM



  

-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-amanda-
[EMAIL PROTECTED] On Behalf Of Ryan Steele
Sent: Tuesday, December 18, 2007 1:16 PM
To: amanda-users@amanda.org
Subject: Discrepancy between amrestore and dd speeds

Hello list,

I've been performance testing Amanda, trying to get the setup ready


for
  

prime-time, but I'm having an issue getting my read speeds from tape


to
  

get even to 6MB/s.  My writes are about 12.7MB/s, which is what the
tape
drive boasts (12-24MB/s normal and 2:1 compression, respectively).
But,
my reads seem to hover around 5.5MB/s.  I ran some dd tests, which


show
  

the data being pulled off at 11.7MB/s, and I'm not quite sure how to
tell what amrestore is doing that is causing the performance drop off.
Here are the tests I ran; any help is appreciated.

[EMAIL PROTECTED] dd if=/dev/nst0 of=/home/restores/foobar bs=256K
count=1G
   10308+0 records in
   10307+0 records out
   2701918208 bytes (2.7 GB)
copied,
230.539 seconds, 11.7 MB/s


[EMAIL PROTECTED] amrestore -r /dev/nst0 hostname /foo/bar

[EMAIL PROTECTED] stat
/home/restores/hostname._foo_bar.20071216.0.1.RAW
   File:
`home/restores/hostname._foo_bar.20071216.0.1.RAW'
   Size: 2836922368  Blocks:
5546275IO Block: 131072 regular file
   Device: 908h/2312d  Inode:
13  Links: 1
   Access: (0640/-rw-r-)  Uid:
(   34/  backup)   Gid: (   34/  backup)
   Access: 2007-12-18
12:50:15.0 -0500
   Modify: 2007-12-18
12:58:40.0 -0500
   Change: 2007-12-18
12:58:40.0 -0500

So,  ~8 minutes for a 2.7GB file = ~5.7MB/s.  I saw similar


performance
  

when retrieving a DLE that spanned 6 chunks (~5.3MB/s)  No errors or
anything in my amrestore logs, just start and stop times.  I'm kind of
at a loss as to what would be causing this, unless my calculations (
size / time ) aren't valid?  Thanks.

Best Regards,
Ryan

--
Ryan Steele
Systems Administrator
The Archer Group



  

Re: Discrepancy between amrestore and dd speeds

[Ryan Steele]

It seems that changing the blocksize with mt -f /dev/nst0 setblk  
to anything other than what it defaulted to breaks things; I get errors 
much like the following:


18:06:39 read(3, 0x2b1a7dead010, 262144) = -1 EIO (Input/output error)
18:06:52 write(2, amrestore: error reading file he..., 57amrestore: 
error reading file header: Input/output error


So, I'm back at square one.  My read speeds are topping out in the 
5-6MB/s range, and manually setting the blocksize for amrestore doesn't 
seem to solve the issue.  Where else in Amanda should I be looking for 
bottlenecks?  As you may recall, simply using dd to dump from tape gets 
me in the 12MB/s range, so I would think it's something within Amanda, 
perhaps amrestore itself since my amdump hums along at 12MB/s.  I 
checked out amrestore.c, but nothing jumped out at me... then again, my 
C is a bit rusty.


If there's any details I left out, or that need reiteration, please let 
me know.  I've saved all my strace outputs if they'd be helpful to 
anyone.  I think I'm starting to run out of tricks trying to pinpoint 
the cause of the slowdown with amrestore. 


TIA,

Ryan

--
Ryan Steele
Systems Administrator
The Archer Group   



Ryan Steele wrote:

Jeremy,

If I can make the process more efficient, then that's what I want to 
do.  In the event of a catastrophe, time is money.


I have tracked down what I believe to be a bug; that is, if no 
blocksize is defined for amrestore, it defaults to 32K, even though 
the man page says Amrestore should normally be able to determine the 
blocksize for tapes on its own and not need this parameter - I wrote 
to the tape in 256K blocks.  I straced it both with and without the 
explicit blocksize parameter, and I can see the read/write blocksizes 
differ in between the runs.  This really ought to be fixed, both in 
amrestore's behavior, and in the man pages.  (Version 2.5.1p1-2.1, the 
latest in Debian Etch.  The source files do not differ from the 
original releases.)


However, setting that option seems (disappointingly) to not make any 
difference.  I ran strace with the -t option, and saw that in both 
cases, the data transfer rate was about the same - between 5 and 6 
MB/s, even though the block sizes were different.  This kind of makes 
me think that's not my bottleneck, but any informed opinions on the 
subject are welcome.


I'm not sure if this is of any consequence or not, but 'mt -f 
/dev/nst0 status' tells me my 'Tape block size' is 1024 bytes; the max 
is just shy of 256K.  I'll try setting that to both 0 and the max, and 
see if that generates any different results.  Again, informed opinions 
welcome.


TIA for any insight,

Ryan

--
Ryan Steele Systems 
Administrator   The Archer Group   



Jeremy Mordkoff wrote:

I know this is no answer, so apologies in advance.

Why are you worried about restore speeds? Hopefully you will never need
it and if you do, will anyone really complain that it took a little
longer than the tape drive is capable of? My users are usually just
grateful that they can get anything back. Plus, if I'm too quick,
they'll ask more and more often :)

JLM



 

-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-amanda-
[EMAIL PROTECTED] On Behalf Of Ryan Steele
Sent: Tuesday, December 18, 2007 1:16 PM
To: amanda-users@amanda.org
Subject: Discrepancy between amrestore and dd speeds

Hello list,

I've been performance testing Amanda, trying to get the setup ready


for
 

prime-time, but I'm having an issue getting my read speeds from tape


to
 

get even to 6MB/s.  My writes are about 12.7MB/s, which is what the
tape
drive boasts (12-24MB/s normal and 2:1 compression, respectively).
But,
my reads seem to hover around 5.5MB/s.  I ran some dd tests, which


show
 

the data being pulled off at 11.7MB/s, and I'm not quite sure how to
tell what amrestore is doing that is causing the performance drop off.
Here are the tests I ran; any help is appreciated.

[EMAIL PROTECTED] dd if=/dev/nst0 of=/home/restores/foobar bs=256K
count=1G
   10308+0 records in
   10307+0 records out
   2701918208 bytes (2.7 GB)
copied,
230.539 seconds, 11.7 MB/s


[EMAIL PROTECTED] amrestore -r /dev/nst0 hostname /foo/bar

[EMAIL PROTECTED] stat
/home/restores/hostname._foo_bar.20071216.0.1.RAW
   File:
`home/restores/hostname._foo_bar.20071216.0.1.RAW'
   Size: 2836922368  Blocks:
5546275IO Block: 131072 regular file
   Device: 908h/2312d  Inode:
13  Links: 1
   Access: (0640/-rw-r-)  Uid:
(   34/  backup)   Gid: (   34/  backup)
   Access: 2007-12-18
12:50:15.0 -0500

RE: amrestore

[Krahn, Anderson]

After creating a amada-client.conf in /etc/Amanda..

I get the following error 

/opt/amanda/server/sbin/amrecover Full

AMRECOVER Version 2.5.2p1. Contacting server on prdapp16-qa-master ...

NAK: amindexd: invalid service, add 'amindexd' as argument to amandad

 

#cat /etc/amanda/amanda-client.conf

conf Full

index_server prdapp16-qa-master

tape_server prdapp16-qa-master

 

client inetd.conf

amanda dgram udp wait amanda /opt/amanda/client/libexec/amandad amandad

 

Server:

cat /home/amanda/.amandahosts

prdapp16.transora.com amanda amdump

prdapp16.transora.com root amindexd amidxtaped

qaapp01-bkup.1sync.org root amindexd amidxtaped

qaapp01-bkup.1sync.org root amandaidx

 

inetd.conf

amanda dgram udp wait amanda /opt/amanda/client/libexec/amandad  amandad
# amanda

amandaidx stream tcp nowait amanda /opt/amanda/client/libexec/amindexd
amindexd # amanda

amidxtape stream tcp nowait amanda /opt/amanda/client/libexec/amidxtaped
amidxtaped # Amanda

Any thoughts?

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Krahn, Anderson
Sent: Wednesday, October 17, 2007 2:07 PM
To: amanda-users@amanda.org
Subject: amrestore

 

After running a amdump , I was trying to get amrecover to work on one of
the clients.

 

On the server prdapp16.

I modified the .amandahosts file

cat /home/amanda/.amandahosts

prdapp16.transora.com root amindexd amidxtaped

qaapp01-bkup.1sync.org root amindexd amidxtaped

 

On  the client I ran amrecover inside the /var directory.

 

[/var]#/opt/amanda/server/sbin/amrecover Full

AMRECOVER Version 2.5.2p1. Contacting server on egvmgmt5001 ...

[request failed: timeout waiting for ACK]

 

 

Strange this is that it is attempting to contact another client and not
the master backup server.

Is there a variable that needs to be set on the client side to change
the server that amrecover will connect to?

Thanks

Re: amrestore

[Jean-Louis Martineau]

Krahn, Anderson wrote:


After creating a amada-client.conf in /etc/Amanda..

I get the following error

/opt/amanda/server/sbin/amrecover Full

AMRECOVER Version 2.5.2p1. Contacting server on prdapp16-qa-master ...

NAK: amindexd: invalid service, add 'amindexd' as argument to amandad

 


#cat /etc/amanda/amanda-client.conf

conf Full

index_server prdapp16-qa-master

tape_server prdapp16-qa-master

 


client inetd.conf

amanda dgram udp wait amanda /opt/amanda/client/libexec/amandad amandad

 


Server:

cat /home/amanda/.amandahosts

prdapp16.transora.com amanda amdump

prdapp16.transora.com root amindexd amidxtaped

qaapp01-bkup.1sync.org root amindexd amidxtaped

qaapp01-bkup.1sync.org root amandaidx

 


inetd.conf

amanda dgram udp wait amanda /opt/amanda/client/libexec/amandad  
amandad # amanda


amandaidx stream tcp nowait amanda 
/opt/amanda/client/libexec/amindexd  amindexd # amanda


amidxtape stream tcp nowait amanda 
/opt/amanda/client/libexec/amidxtaped  amidxtaped # Amanda


Any thoughts?


Change server inetd.conf for (only one line):
amanda dgram udp wait amanda /opt/amanda/client/libexec/amandad  amandad 
amdump amindexd amidxtaped


The amandaidx and amidxtape lines are use by older amrecover only.

Jean-Louis


 




*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Krahn, Anderson

*Sent:* Wednesday, October 17, 2007 2:07 PM
*To:* amanda-users@amanda.org
*Subject:* amrestore

 

After running a amdump , I was trying to get amrecover to work on one 
of the clients.


 


On the server prdapp16.

I modified the .amandahosts file

cat /home/amanda/.amandahosts

prdapp16.transora.com root amindexd amidxtaped

qaapp01-bkup.1sync.org root amindexd amidxtaped

 


On  the client I ran amrecover inside the /var directory.

 


[/var]#/opt/amanda/server/sbin/amrecover Full

AMRECOVER Version 2.5.2p1. Contacting server on egvmgmt5001 ...

[request failed: timeout waiting for ACK]

 

 

Strange this is that it is attempting to contact another client and 
not the master backup server.


Is there a variable that needs to be set on the client side to change 
the server that amrecover will connect to?


Thanks

amrestore and tape changers: has it changed since 2.4.4p3?

[Francis Galiegue]

Hello,

Just a question: in the amrestore page from amanda 2.4.4p3 (well, packaged by 
Red Hat for RHEL 4.x), it says that amrestore does NOT use a tape changer.

Too bad, because in one of our configurations, we use a tape changer with 6 
tapes, four of which are dedicated to a configuration with a tape cycle of 3.

That means that the person restoring a DLE from such a configuration, should 
the changer not have the correct tape loaded, needs to have access to the 
backup server, and write access to the tape changer!

Is this fixed for 2.5.x? Or is this simply a problem between my keyboard and 
chair?

Thanks,
-- 
Francis Galiegue, One2team - [EMAIL PROTECTED]
[ATTENTION : CHANGEMENT DE COORDONNÉES !]
+33178945570, +33683877875, http://www.one2team.com
40 avenue Raymond Poincaré - 75116 PARIS

Re: amrestore and tape changers: has it changed since 2.4.4p3?

[Francis Galiegue]

Le jeudi 13 septembre 2007, vous avez écrit :
[...]
 
 That's still the case with amrestore, which is considered the
 bare-metal recovery tool of the three currently available.  In the
 copy of 2.4.4p1 I have available, amfetchdump does not exist, but that
 tool is able to use a changer to fetch whole dumpfiles in the same
 fashion as amrestore.  Similarly, in recent versions amrecover is
 capable of driving a changer, but IIRC did not have that capacity in
 2.4.4.
 

I guess I'll have to upgrade to 2.5.x then.

One question though: is it really the role of amrecover to drive the tape 
changer? Isn't that done on the server side? What if I decide to upgrade the 
server to the latest 2.5.x but leave clients with 2.4.x?

Thanks for the quick answer!
-- 
Francis Galiegue, One2team - [EMAIL PROTECTED]
[ATTENTION : CHANGEMENT DE COORDONNÉES !]
+33178945570, +33683877875, http://www.one2team.com
40 avenue Raymond Poincaré - 75116 PARIS

Re: amrestore and tape changers: has it changed since 2.4.4p3?

[Dustin J. Mitchell]

On 9/13/07, Francis Galiegue [EMAIL PROTECTED] wrote:
 One question though: is it really the role of amrecover to drive the tape
 changer? Isn't that done on the server side? What if I decide to upgrade the
 server to the latest 2.5.x but leave clients with 2.4.x?

Yes, that's correct -- I was trying to be brief :)

That arrangement is ok, with the proviso that you can't use tape
spanning on the server, or you won't be able to recover using older
clients.  There may be more limitations -- someone else please chime
in?

Dustin

-- 
Storage Software Engineer
http://www.zmanda.com

Re: amrestore does not work NAK: amindexd: invalid service

[Bjoern B]

Hi,

first i will use amoldrecover for recover ;-)
why didn´t i remember this before...

Thats not solving the problem, but it is a work arround.

This afternoon i will leave to vacation.
Will work on this at a later time.

Thanks for help.

bye

B²


Bjoern B schrieb:

Hi,

Jean-Louis Martineau schrieb:

Can you upgrade to 2.5.2p1?


would not to be my preferred way. I like my aptitude get update thing.
But i will look if there is a real reason for not upgrading.

When i upgrade i will use the configure options for the 2.5.1.p1 Debian 
package or what should i try ?


bye

B²


Jean-Louis

Bjoern B wrote:

Hi,

Jean-Louis Martineau schrieb:
The only way to get this error is if amandad doesn't get amindexd 
as argument.

But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have character 
you don't see.


I have retyped the server_args in /etc/xinetd.d/amanda, i had copied 
them before.


Did a server restart after this, to be really sure that xinitd was 
restarted.



Verify that you doesn't have an amandad process already running.


Made a ps ax | grep amandad

And then tried amrecover again.

marconi:~# ps ax | grep amandad
 2420 pts/0D+ 0:00 grep amandad
marconi:~# amrecover -s marconi.domain.tld
AMRECOVER Version 2.5.1p1. Contacting server on marconi.domain.tld ...
NAK: amindexd: invalid service
marconi:~# ps ax | grep amandad
 2422 ?Ss 0:00 amandad
 2424 pts/0S+ 0:00 grep amandad

The process 2422 is there for a few seconds after the Error message.

Same message. For me it is the same in the amandad.*.debug file like 
before.


More idears?

bye

B²

Jean-Louis

Bjoern B wrote:

Hi,

you are right i mean amrecover. sorry

Jean-Louis Martineau schrieb:


Your config looks good, are you sure you restarted xinetd?


I did a /etc/init.d/xinetd restart

To be sure, i have done a server restart and tested it again.
Same message.


amrecover in 2.4.* will use the amandaidx and amandaidx services
amrecover in 2.5.* will only use the amanda services.

Send the amandad.*.debug file


/var/log/amanda/amandad# more amandad.20070711180648.debug
amandad: debug 1 pid 2992 ruid 34 euid 34: start at Wed Jul 11 
18:06:48 2007

security_getdriver(name=BSD) returns 0xb7f470e0
amandad: version 2.5.1p1
amandad: build: VERSION=Amanda-2.5.1p1
amandad:BUILT_DATE=Wed Nov 29 02:15:07 CET 2006
amandad:BUILT_MACH=Linux intrepid 2.6.18-1-686 #1 SMP Fri 
Sep 29 16:25:40 UTC 2006 i686 GNU/Linux

amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' 
'--bindir=/usr/sbin' '--mandir=/usr/share/man
' '--libexecdir=/usr/lib/amanda' '--enable-shared' 
'--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnut
ar-listdir=/var/lib/amanda/gnutar-lists' 
'--with-index-server=localhost' '--with-user=backup' '--with-group=ba
ckup' '--with-bsd-security' '--with-amandahosts' 
'--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/
log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' 
'--with-tcpportrange=5,50100' '--with-udpportrange

=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security'
amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda
amandad:AMANDA_DBGDIR=/var/log/amanda 
CONFIG_DIR=/etc/amanda
amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ 
DUMP=/sbin/dump

amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore
amandad:VXDUMP=UNDEF VXRESTORE=UNDEF
amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY 
USE_AMANDAHOSTS

amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: dgram_recv(dgram=0xb7f48084, timeout=0, 
fromaddr=0xb7f58070)
amandad: time 0.000: (sockaddr_in *)0xb7f58070 = { 2, 849, 
192.168.129.133 }

security_handleinit(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 0.000: accept recv REQ pkt:

SERVICE amindexd
OPTIONS features=feff9ffeff7f;auth=bsd;

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service

amandad: dgram_send_addr(addr=0xbffbeef0, dgram=0xb7f48084)
amandad: time 0.000: (sockaddr_in *)0xbffbeef0 = { 2, 849, 
192.168.129.133 }

amandad: dgram_send_addr: 0xb7f48084-socket = 0

Re: amrestore does not work NAK: amindexd: invalid service

[Bjoern B]

Hi,

Jean-Louis Martineau schrieb:
The only way to get this error is if amandad doesn't get amindexd as 
argument.

But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have character you 
don't see.


I have retyped the server_args in /etc/xinetd.d/amanda, i had copied 
them before.


Did a server restart after this, to be really sure that xinitd was 
restarted.



Verify that you doesn't have an amandad process already running.


Made a ps ax | grep amandad

And then tried amrecover again.

marconi:~# ps ax | grep amandad
 2420 pts/0D+ 0:00 grep amandad
marconi:~# amrecover -s marconi.domain.tld
AMRECOVER Version 2.5.1p1. Contacting server on marconi.domain.tld ...
NAK: amindexd: invalid service
marconi:~# ps ax | grep amandad
 2422 ?Ss 0:00 amandad
 2424 pts/0S+ 0:00 grep amandad

The process 2422 is there for a few seconds after the Error message.

Same message. For me it is the same in the amandad.*.debug file like before.

More idears?

bye

B²

Jean-Louis

Bjoern B wrote:

Hi,

you are right i mean amrecover. sorry

Jean-Louis Martineau schrieb:


Your config looks good, are you sure you restarted xinetd?


I did a /etc/init.d/xinetd restart

To be sure, i have done a server restart and tested it again.
Same message.


amrecover in 2.4.* will use the amandaidx and amandaidx services
amrecover in 2.5.* will only use the amanda services.

Send the amandad.*.debug file


/var/log/amanda/amandad# more amandad.20070711180648.debug
amandad: debug 1 pid 2992 ruid 34 euid 34: start at Wed Jul 11 
18:06:48 2007

security_getdriver(name=BSD) returns 0xb7f470e0
amandad: version 2.5.1p1
amandad: build: VERSION=Amanda-2.5.1p1
amandad:BUILT_DATE=Wed Nov 29 02:15:07 CET 2006
amandad:BUILT_MACH=Linux intrepid 2.6.18-1-686 #1 SMP Fri Sep 
29 16:25:40 UTC 2006 i686 GNU/Linux

amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' 
'--bindir=/usr/sbin' '--mandir=/usr/share/man
' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' 
'--localstatedir=/var/lib' '--with-gnut
ar-listdir=/var/lib/amanda/gnutar-lists' 
'--with-index-server=localhost' '--with-user=backup' '--with-group=ba
ckup' '--with-bsd-security' '--with-amandahosts' 
'--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/
log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' 
'--with-tcpportrange=5,50100' '--with-udpportrange

=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security'
amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda
amandad:AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda
amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore
amandad:VXDUMP=UNDEF VXRESTORE=UNDEF
amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY 
USE_AMANDAHOSTS

amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: dgram_recv(dgram=0xb7f48084, timeout=0, 
fromaddr=0xb7f58070)
amandad: time 0.000: (sockaddr_in *)0xb7f58070 = { 2, 849, 
192.168.129.133 }

security_handleinit(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 0.000: accept recv REQ pkt:

SERVICE amindexd
OPTIONS features=feff9ffeff7f;auth=bsd;

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service

amandad: dgram_send_addr(addr=0xbffbeef0, dgram=0xb7f48084)
amandad: time 0.000: (sockaddr_in *)0xbffbeef0 = { 2, 849, 
192.168.129.133 }

amandad: dgram_send_addr: 0xb7f48084-socket = 0
security_close(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 29.996: pid 2992 finish time Wed Jul 11 18:07:18 2007

Re: amrestore does not work NAK: amindexd: invalid service

[Bjoern B]

Hi,

Jean-Louis Martineau schrieb:

Frank Smith wrote:

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service



My interpretation of this error is that it couldn't find the service
named amindexd.  Is this something new in 2.5, as in 2.4 it was named
amandaidx, which is what is in your xinetd config and probably in
your /etc/services as well.

If you don't get a more definitive answer, try changing the name in
/etc/services and see what happens (I think that is the name that
matters on lookups, not the name in your xinetd config, but I could
be wrong and you might want to change both and try again).
  
amindexd is not a system services, it is an amanda service, it should 
not be listed in /etc/services


There is a entry in /etc/services:

amanda  10080/tcp   # amanda backup services
amanda  10080/udp
kamanda 10081/tcp   # amanda backup services
(Kerberos)
kamanda 10081/udp
amandaidx   10082/tcp   # amanda backup services
amidxtape   10083/tcp   # amanda backup services

have tried:

amanda  10080/tcp   # amanda backup services
amanda  10080/udp
kamanda 10081/tcp   # amanda backup services
(Kerberos)
kamanda 10081/udp
amindexd10082/tcp   # amanda backup services
amidxtape   10083/tcp   # amanda backup services

But still the same error.

bye

B²

Jean-Louis

Re: amrestore does not work NAK: amindexd: invalid service

[Jean-Louis Martineau]

Can you upgrade to 2.5.2p1?

Jean-Louis

Bjoern B wrote:

Hi,

Jean-Louis Martineau schrieb:
The only way to get this error is if amandad doesn't get amindexd 
as argument.

But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have character 
you don't see.


I have retyped the server_args in /etc/xinetd.d/amanda, i had copied 
them before.


Did a server restart after this, to be really sure that xinitd was 
restarted.



Verify that you doesn't have an amandad process already running.


Made a ps ax | grep amandad

And then tried amrecover again.

marconi:~# ps ax | grep amandad
 2420 pts/0D+ 0:00 grep amandad
marconi:~# amrecover -s marconi.domain.tld
AMRECOVER Version 2.5.1p1. Contacting server on marconi.domain.tld ...
NAK: amindexd: invalid service
marconi:~# ps ax | grep amandad
 2422 ?Ss 0:00 amandad
 2424 pts/0S+ 0:00 grep amandad

The process 2422 is there for a few seconds after the Error message.

Same message. For me it is the same in the amandad.*.debug file like 
before.


More idears?

bye

B²

Jean-Louis

Bjoern B wrote:

Hi,

you are right i mean amrecover. sorry

Jean-Louis Martineau schrieb:


Your config looks good, are you sure you restarted xinetd?


I did a /etc/init.d/xinetd restart

To be sure, i have done a server restart and tested it again.
Same message.


amrecover in 2.4.* will use the amandaidx and amandaidx services
amrecover in 2.5.* will only use the amanda services.

Send the amandad.*.debug file


/var/log/amanda/amandad# more amandad.20070711180648.debug
amandad: debug 1 pid 2992 ruid 34 euid 34: start at Wed Jul 11 
18:06:48 2007

security_getdriver(name=BSD) returns 0xb7f470e0
amandad: version 2.5.1p1
amandad: build: VERSION=Amanda-2.5.1p1
amandad:BUILT_DATE=Wed Nov 29 02:15:07 CET 2006
amandad:BUILT_MACH=Linux intrepid 2.6.18-1-686 #1 SMP Fri 
Sep 29 16:25:40 UTC 2006 i686 GNU/Linux

amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' 
'--bindir=/usr/sbin' '--mandir=/usr/share/man
' '--libexecdir=/usr/lib/amanda' '--enable-shared' 
'--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnut
ar-listdir=/var/lib/amanda/gnutar-lists' 
'--with-index-server=localhost' '--with-user=backup' '--with-group=ba
ckup' '--with-bsd-security' '--with-amandahosts' 
'--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/
log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' 
'--with-tcpportrange=5,50100' '--with-udpportrange

=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security'
amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda
amandad:AMANDA_DBGDIR=/var/log/amanda 
CONFIG_DIR=/etc/amanda
amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ 
DUMP=/sbin/dump

amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore
amandad:VXDUMP=UNDEF VXRESTORE=UNDEF
amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY 
USE_AMANDAHOSTS

amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: dgram_recv(dgram=0xb7f48084, timeout=0, 
fromaddr=0xb7f58070)
amandad: time 0.000: (sockaddr_in *)0xb7f58070 = { 2, 849, 
192.168.129.133 }

security_handleinit(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 0.000: accept recv REQ pkt:

SERVICE amindexd
OPTIONS features=feff9ffeff7f;auth=bsd;

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service

amandad: dgram_send_addr(addr=0xbffbeef0, dgram=0xb7f48084)
amandad: time 0.000: (sockaddr_in *)0xbffbeef0 = { 2, 849, 
192.168.129.133 }

amandad: dgram_send_addr: 0xb7f48084-socket = 0
security_close(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 29.996: pid 2992 finish time Wed Jul 11 18:07:18 2007

amrestore does not work NAK: amindexd: invalid service

[Bjoern B]

Hi,

here i go again.

Backup works now, but i can´t recover.

Seems to be a problem, because of the bsd/bsdudp/bsdtcp authentication.

We have 3 Amandaserver running.
And a couple of clients.

Amandaserver1 = Version 2.4.2p2
Amandaserver2 = Version 2.4.4p3

Amandaserver3 = Version 2.5.1p1

There is no Problem with Backup to and restore from Amandaserver1 and 2 
and the long time ago configured clients.


With Amandaserver3 i could backup different clients, mostly Linux and 
one Windows.


Amcheck and amdump are successfull.

We could make a successfully amrestore from Amandaserver3 OS CENTOS with 
AMRECOVER Version 2.4.4p3.


But we can´t do an amrestore from Debian boxes with AMRECOVER Version 
2.5.1p1 to Amandaserver3.


I have read about changings in 2.5.1.

For example here 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication


I get the following message when trying:

amrecover -s Amandaserver3.fqdn

Error Message:

AMRECOVER Version 2.5.1p1. Contacting server on localhost ...
NAK: amindexd: invalid service

Yes i would like to recover from and to localhost.

Because of the successfully amrestore from the Centos with 2.4.4p3 i 
think that there is no

bsd/bsdudp/bsdtcp authentication configured.

Right?

So i´m looking for a solution of my Problem.

Have tried the indicated solution from 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication

but it does not work.

I will put The configfiles to the end.

I think there are 2 possible ways for solving this Problem:

1. Get bsd/bsdudp/bsdtcp authentication working
	- with the problem, that the Centos Client cant´t recover the data 
himself(old amrestore version)


2. Tell amrestore 2.5.1p1 not to use bsd/bsdudp/bsdtcp authentication

right?

The debian amanda package is configured with --with-bsd-seurity


Configfiles:

more /etc/xinetd.d/amanda
service amanda
{
   socket_type = dgram
   protocol= udp
   wait= yes
   user= backup
   group   = backup
   groups  = yes
   server  = /usr/lib/amanda/amandad
   server_args = -auth=bsd amdump amindexd amidxtaped
   disable = no
}


--

more /etc/xinetd.d/amandaidx
#default: on
# description: The amanda index service
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= backup
group   = backup
server  = /usr/lib/amanda/amindexd
}

--

more /etc/xinetd.d/amidxtape
#default: on
# description: The amanda tape service
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= backup
group   = backup
server  = /usr/lib/amanda/amidxtaped
}

--

:~# grep -v '#' /etc/inetd.conf








amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad 
-auth=bsd amdump amindexd amidxtaped


--

Configure Options

./configure --prefix=/usr --bindir=/usr/sbin --mandir=/usr/share/man \
--libexecdir=/usr/lib/amanda --enable-shared\
--sysconfdir=/etc --localstatedir=/var/lib \
--with-gnutar-listdir=/var/lib/amanda/gnutar-lists \
--with-index-server=localhost \
--with-user=backup --with-group=backup  \
--with-bsd-security --with-amandahosts \
--with-smbclient=/usr/bin/smbclient \
--with-debugging=/var/log/amanda \
--with-dumperdir=/usr/lib/amanda/dumper.d \
--with-tcpportrange=5,50100 
--with-udpportrange=840,860 \

--with-maxtapeblocksize=256 \
--with-ssh-security

--

snapits from netstat -tupln:

Proto Recv-Q Send-Q Local Address   Foreign Address 
State   PID/Program name
tcp0  0 0.0.0.0:10082   0.0.0.0:* 
LISTEN 2246/inetd
tcp0  0 0.0.0.0:10083   0.0.0.0:* 
LISTEN 2246/inetd
udp0  0 0.0.0.0:10080   0.0.0.0:* 
   2358/xinetd
udp0  0 0.0.0.0:10080   0.0.0.0:* 
   2358/xinetd
udp0  0 0.0.0.0:10080   0.0.0.0:* 
   2246/inetd


--




Hope that someone could help me.

bye

B²

Re: amrestore does not work NAK: amindexd: invalid service

[Jean-Louis Martineau]

amrestore doesn't use the network and can't fail with NAK: amindexd: 
invalid service.
amrestore and amrecover are two distinct commands, don't say amrestore 
when you talk about amrecover, it's really confusing.


Your config looks good, are you sure you restarted xinetd?

amrecover in 2.4.* will use the amandaidx and amandaidx services
amrecover in 2.5.* will only use the amanda services.

Send the amandad.*.debug file

Jean-Louis

Bjoern B wrote:

Hi,

here i go again.

Backup works now, but i can´t recover.

Seems to be a problem, because of the bsd/bsdudp/bsdtcp authentication.

We have 3 Amandaserver running.
And a couple of clients.

Amandaserver1 = Version 2.4.2p2
Amandaserver2 = Version 2.4.4p3

Amandaserver3 = Version 2.5.1p1

There is no Problem with Backup to and restore from Amandaserver1 and 
2 and the long time ago configured clients.


With Amandaserver3 i could backup different clients, mostly Linux and 
one Windows.


Amcheck and amdump are successfull.

We could make a successfully amrestore from Amandaserver3 OS CENTOS 
with AMRECOVER Version 2.4.4p3.


But we can´t do an amrestore from Debian boxes with AMRECOVER Version 
2.5.1p1 to Amandaserver3.


I have read about changings in 2.5.1.

For example here 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication 



I get the following message when trying:

amrecover -s Amandaserver3.fqdn

Error Message:

AMRECOVER Version 2.5.1p1. Contacting server on localhost ...
NAK: amindexd: invalid service

Yes i would like to recover from and to localhost.

Because of the successfully amrestore from the Centos with 2.4.4p3 i 
think that there is no

bsd/bsdudp/bsdtcp authentication configured.

Right?

So i´m looking for a solution of my Problem.

Have tried the indicated solution from 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication 


but it does not work.

I will put The configfiles to the end.

I think there are 2 possible ways for solving this Problem:

1. Get bsd/bsdudp/bsdtcp authentication working
- with the problem, that the Centos Client cant´t recover the data 
himself(old amrestore version)


2. Tell amrestore 2.5.1p1 not to use bsd/bsdudp/bsdtcp authentication

right?

The debian amanda package is configured with --with-bsd-seurity


Configfiles:

more /etc/xinetd.d/amanda
service amanda
{
   socket_type = dgram
   protocol= udp
   wait= yes
   user= backup
   group   = backup
   groups  = yes
   server  = /usr/lib/amanda/amandad
   server_args = -auth=bsd amdump amindexd amidxtaped
   disable = no
}


--

more /etc/xinetd.d/amandaidx
#default: on
# description: The amanda index service
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= backup
group   = backup
server  = /usr/lib/amanda/amindexd
}

--

more /etc/xinetd.d/amidxtape
#default: on
# description: The amanda tape service
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= backup
group   = backup
server  = /usr/lib/amanda/amidxtaped
}

--

:~# grep -v '#' /etc/inetd.conf








amandaidx stream tcp nowait backup /usr/sbin/tcpd 
/usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd 
/usr/lib/amanda/amidxtaped
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad 
-auth=bsd amdump amindexd amidxtaped


--

Configure Options

./configure --prefix=/usr --bindir=/usr/sbin --mandir=/usr/share/man \
--libexecdir=/usr/lib/amanda --enable-shared\
--sysconfdir=/etc --localstatedir=/var/lib \
--with-gnutar-listdir=/var/lib/amanda/gnutar-lists \
--with-index-server=localhost \
--with-user=backup --with-group=backup  \
--with-bsd-security --with-amandahosts \
--with-smbclient=/usr/bin/smbclient \
--with-debugging=/var/log/amanda \
--with-dumperdir=/usr/lib/amanda/dumper.d \
--with-tcpportrange=5,50100 
--with-udpportrange=840,860 \

--with-maxtapeblocksize=256 \
--with-ssh-security

--

snapits from netstat -tupln:

Proto Recv-Q Send-Q Local Address   Foreign Address 
State   PID/Program name
tcp0  0 0.0.0.0:10082   0.0.0.0:* LISTEN 
2246/inetd
tcp0  0 0.0.0.0:10083   0.0.0.0:* LISTEN 
2246/inetd

udp0  0 0.0.0.0:10080   0.0.0.0:*2358/xinetd
udp0  0 0.0.0.0:10080   0.0.0.0:*2358/xinetd
udp0  0 0.0.0.0:10080   0.0.0.0:*2246/inetd

--




Hope that someone could help me

Re: amrestore does not work NAK: amindexd: invalid service

[Bjoern B]

Hi,

you are right i mean amrecover. sorry

Jean-Louis Martineau schrieb:


Your config looks good, are you sure you restarted xinetd?


I did a /etc/init.d/xinetd restart

To be sure, i have done a server restart and tested it again.
Same message.


amrecover in 2.4.* will use the amandaidx and amandaidx services
amrecover in 2.5.* will only use the amanda services.

Send the amandad.*.debug file


/var/log/amanda/amandad# more amandad.20070711180648.debug
amandad: debug 1 pid 2992 ruid 34 euid 34: start at Wed Jul 11 18:06:48 2007
security_getdriver(name=BSD) returns 0xb7f470e0
amandad: version 2.5.1p1
amandad: build: VERSION=Amanda-2.5.1p1
amandad:BUILT_DATE=Wed Nov 29 02:15:07 CET 2006
amandad:BUILT_MACH=Linux intrepid 2.6.18-1-686 #1 SMP Fri Sep 
29 16:25:40 UTC 2006 i686 GNU/Linux

amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' 
'--bindir=/usr/sbin' '--mandir=/usr/share/man
' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' 
'--localstatedir=/var/lib' '--with-gnut
ar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' 
'--with-user=backup' '--with-group=ba
ckup' '--with-bsd-security' '--with-amandahosts' 
'--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/
log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' 
'--with-tcpportrange=5,50100' '--with-udpportrange

=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security'
amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda
amandad:AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda
amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore
amandad:VXDUMP=UNDEF VXRESTORE=UNDEF
amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY 
USE_AMANDAHOSTS

amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: dgram_recv(dgram=0xb7f48084, timeout=0, 
fromaddr=0xb7f58070)

amandad: time 0.000: (sockaddr_in *)0xb7f58070 = { 2, 849, 192.168.129.133 }
security_handleinit(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 0.000: accept recv REQ pkt:

SERVICE amindexd
OPTIONS features=feff9ffeff7f;auth=bsd;

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service

amandad: dgram_send_addr(addr=0xbffbeef0, dgram=0xb7f48084)
amandad: time 0.000: (sockaddr_in *)0xbffbeef0 = { 2, 849, 192.168.129.133 }
amandad: dgram_send_addr: 0xb7f48084-socket = 0
security_close(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 29.996: pid 2992 finish time Wed Jul 11 18:07:18 2007

What else could i do?

Thanks

B²

Jean-Louis

Bjoern B wrote:

Hi,

here i go again.

Backup works now, but i can´t recover.

Seems to be a problem, because of the bsd/bsdudp/bsdtcp authentication.

We have 3 Amandaserver running.
And a couple of clients.

Amandaserver1 = Version 2.4.2p2
Amandaserver2 = Version 2.4.4p3

Amandaserver3 = Version 2.5.1p1

There is no Problem with Backup to and restore from Amandaserver1 and 
2 and the long time ago configured clients.


With Amandaserver3 i could backup different clients, mostly Linux and 
one Windows.


Amcheck and amdump are successfull.

We could make a successfully amrestore from Amandaserver3 OS CENTOS 
with AMRECOVER Version 2.4.4p3.


But we can´t do an amrestore from Debian boxes with AMRECOVER Version 
2.5.1p1 to Amandaserver3.


I have read about changings in 2.5.1.

For example here 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication 



I get the following message when trying:

amrecover -s Amandaserver3.fqdn

Error Message:

AMRECOVER Version 2.5.1p1. Contacting server on localhost ...
NAK: amindexd: invalid service

Yes i would like to recover from and to localhost.

Because of the successfully amrestore from the Centos with 2.4.4p3 i 
think that there is no

bsd/bsdudp/bsdtcp authentication configured.

Right?

So i´m looking for a solution of my Problem.

Have tried the indicated solution from 
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication 


but it does not work.

I will put The configfiles to the end.

I think there are 2 possible ways for solving

Re: amrestore does not work NAK: amindexd: invalid service

[Frank Smith]

Bjoern B wrote:
 Hi,
 
 you are right i mean amrecover. sorry
 
 Jean-Louis Martineau schrieb:
 Your config looks good, are you sure you restarted xinetd?
 
 I did a /etc/init.d/xinetd restart
 
 To be sure, i have done a server restart and tested it again.
 Same message.
 
 amrecover in 2.4.* will use the amandaidx and amandaidx services
 amrecover in 2.5.* will only use the amanda services.

 Send the amandad.*.debug file
 
 /var/log/amanda/amandad# more amandad.20070711180648.debug
 amandad: debug 1 pid 2992 ruid 34 euid 34: start at Wed Jul 11 18:06:48 2007
 security_getdriver(name=BSD) returns 0xb7f470e0
 amandad: version 2.5.1p1
 amandad: build: VERSION=Amanda-2.5.1p1
 amandad:BUILT_DATE=Wed Nov 29 02:15:07 CET 2006
 amandad:BUILT_MACH=Linux intrepid 2.6.18-1-686 #1 SMP Fri Sep 
 29 16:25:40 UTC 2006 i686 GNU/Linux
 amandad:CC=gcc
 amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' 
 '--bindir=/usr/sbin' '--mandir=/usr/share/man
 ' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' 
 '--localstatedir=/var/lib' '--with-gnut
 ar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' 
 '--with-user=backup' '--with-group=ba
 ckup' '--with-bsd-security' '--with-amandahosts' 
 '--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/
 log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' 
 '--with-tcpportrange=5,50100' '--with-udpportrange
 =840,860' '--with-maxtapeblocksize=256' '--with-ssh-security'
 amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
 amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
 amandad:AMANDA_TMPDIR=/tmp/amanda
 amandad:AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda
 amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump
 amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
 amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore
 amandad:VXDUMP=UNDEF VXRESTORE=UNDEF
 amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
 amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
 amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
 amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
 amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
 amandad:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP HAVE_SYSVSHM
 amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
 amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY 
 USE_AMANDAHOSTS
 amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
 amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
 amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
 amandad: time 0.000: dgram_recv(dgram=0xb7f48084, timeout=0, 
 fromaddr=0xb7f58070)
 amandad: time 0.000: (sockaddr_in *)0xb7f58070 = { 2, 849, 192.168.129.133 }
 security_handleinit(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
 amandad: time 0.000: accept recv REQ pkt:
 
 SERVICE amindexd
 OPTIONS features=feff9ffeff7f;auth=bsd;
  
 amandad: time 0.000: amindexd: invalid service
 amandad: time 0.000: sending NAK pkt:
 
 ERROR amindexd: invalid service

My interpretation of this error is that it couldn't find the service
named amindexd.  Is this something new in 2.5, as in 2.4 it was named
amandaidx, which is what is in your xinetd config and probably in
your /etc/services as well.

If you don't get a more definitive answer, try changing the name in
/etc/services and see what happens (I think that is the name that
matters on lookups, not the name in your xinetd config, but I could
be wrong and you might want to change both and try again).

Frank

  
 amandad: dgram_send_addr(addr=0xbffbeef0, dgram=0xb7f48084)
 amandad: time 0.000: (sockaddr_in *)0xbffbeef0 = { 2, 849, 192.168.129.133 }
 amandad: dgram_send_addr: 0xb7f48084-socket = 0
 security_close(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
 amandad: time 29.996: pid 2992 finish time Wed Jul 11 18:07:18 2007
 
 What else could i do?
 
 Thanks
 
 B²
 Jean-Louis

 Bjoern B wrote:
 Hi,

 here i go again.

 Backup works now, but i can´t recover.

 Seems to be a problem, because of the bsd/bsdudp/bsdtcp authentication.

 We have 3 Amandaserver running.
 And a couple of clients.

 Amandaserver1 = Version 2.4.2p2
 Amandaserver2 = Version 2.4.4p3

 Amandaserver3 = Version 2.5.1p1

 There is no Problem with Backup to and restore from Amandaserver1 and 
 2 and the long time ago configured clients.

 With Amandaserver3 i could backup different clients, mostly Linux and 
 one Windows.

 Amcheck and amdump are successfull.

 We could make a successfully amrestore from Amandaserver3 OS CENTOS 
 with AMRECOVER Version 2.4.4p3.

 But we can´t do an amrestore from Debian boxes with AMRECOVER Version 
 2.5.1p1 to Amandaserver3.

 I have read about changings in 2.5.1.

 For example here 
 http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
  


 I get the following message when trying

Re: amrestore does not work NAK: amindexd: invalid service

[Jean-Louis Martineau]

The only way to get this error is if amandad doesn't get amindexd as 
argument.

But it is listed in the server_args of /etc/xinetd.d/amanda
You should recheck that file, verify that it doesn't have character you 
don't see.

Verify that you doesn't have an amandad process already running.

Jean-Louis

Bjoern B wrote:

Hi,

you are right i mean amrecover. sorry

Jean-Louis Martineau schrieb:


Your config looks good, are you sure you restarted xinetd?


I did a /etc/init.d/xinetd restart

To be sure, i have done a server restart and tested it again.
Same message.


amrecover in 2.4.* will use the amandaidx and amandaidx services
amrecover in 2.5.* will only use the amanda services.

Send the amandad.*.debug file


/var/log/amanda/amandad# more amandad.20070711180648.debug
amandad: debug 1 pid 2992 ruid 34 euid 34: start at Wed Jul 11 
18:06:48 2007

security_getdriver(name=BSD) returns 0xb7f470e0
amandad: version 2.5.1p1
amandad: build: VERSION=Amanda-2.5.1p1
amandad:BUILT_DATE=Wed Nov 29 02:15:07 CET 2006
amandad:BUILT_MACH=Linux intrepid 2.6.18-1-686 #1 SMP Fri Sep 
29 16:25:40 UTC 2006 i686 GNU/Linux

amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' 
'--bindir=/usr/sbin' '--mandir=/usr/share/man
' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' 
'--localstatedir=/var/lib' '--with-gnut
ar-listdir=/var/lib/amanda/gnutar-lists' 
'--with-index-server=localhost' '--with-user=backup' '--with-group=ba
ckup' '--with-bsd-security' '--with-amandahosts' 
'--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/
log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' 
'--with-tcpportrange=5,50100' '--with-udpportrange

=840,860' '--with-maxtapeblocksize=256' '--with-ssh-security'
amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda
amandad:AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda
amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore
amandad:VXDUMP=UNDEF VXRESTORE=UNDEF
amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY 
USE_AMANDAHOSTS

amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
amandad: time 0.000: dgram_recv(dgram=0xb7f48084, timeout=0, 
fromaddr=0xb7f58070)
amandad: time 0.000: (sockaddr_in *)0xb7f58070 = { 2, 849, 
192.168.129.133 }

security_handleinit(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 0.000: accept recv REQ pkt:

SERVICE amindexd
OPTIONS features=feff9ffeff7f;auth=bsd;

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service

amandad: dgram_send_addr(addr=0xbffbeef0, dgram=0xb7f48084)
amandad: time 0.000: (sockaddr_in *)0xbffbeef0 = { 2, 849, 
192.168.129.133 }

amandad: dgram_send_addr: 0xb7f48084-socket = 0
security_close(handle=0x804f5d8, driver=0xb7f470e0 (BSD))
amandad: time 29.996: pid 2992 finish time Wed Jul 11 18:07:18 2007

Re: amrestore does not work NAK: amindexd: invalid service

[Jean-Louis Martineau]

Frank Smith wrote:

amandad: time 0.000: amindexd: invalid service
amandad: time 0.000: sending NAK pkt:

ERROR amindexd: invalid service



My interpretation of this error is that it couldn't find the service
named amindexd.  Is this something new in 2.5, as in 2.4 it was named
amandaidx, which is what is in your xinetd config and probably in
your /etc/services as well.

If you don't get a more definitive answer, try changing the name in
/etc/services and see what happens (I think that is the name that
matters on lookups, not the name in your xinetd config, but I could
be wrong and you might want to change both and try again).
  
amindexd is not a system services, it is an amanda service, it should 
not be listed in /etc/services


Jean-Louis

Re: Amrestore

[Ian Turner]

On Saturday 05 May 2007 09:13, Donofrio, Lewis wrote:
 Do I still have to use another tty to change tapes with amanda 2.5.x?

Amrestore only supports one tape at a time, so you can change tapes with the 
same TTY.

Amrecover and amfetchdump know how to use the changer now, so you don't need 
another tty for those, either.

Cheers,

--Ian
-- 
Zmanda: Open Source Data Protection and Archiving.
http://www.zmanda.com

Amrestore

[Donofrio, Lewis]

Do I still have to use another tty to change tapes with amanda 2.5.x?
__
Lewis [EMAIL PROTECTED]
Cell: (734) 323-8776 
 

Re: amrestore help

[Steven Settlemyre]

I'd love to, but see my message below. I get an error when I try to run 
amrecover. Is there a way to get past this error?


Guy Dallaire wrote:

amrecover is easier to use

2007/4/27, Steven Settlemyre [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED]:


actually, i found how to put the desired tape into the active slot of
the changer. But when i do amrestore /dev/nst0 lollipop /files1
I get
this:

amrestore: missing file header block
amrestore:   2: skipping zoo._.20070419.1.1
amrestore: missing file header block
amrestore:   6: skipping marlin._var.20070419.1.1
amrestore:  10: reached end of information

What now?

Steven Settlemyre wrote:
 I am trying to restore a folder from a tape in a previous cycle
(last
 night had a level 0 of the disk, but the folder was deleted
prior). I
 have a tape changer and read that amrestore doesnt work with tape
 changers. My dumptypes are gnutar, so I probably can't use
amrecover.
 Is this correct? When I tried to run it, it said amrecover:
 Unexpected end of file, check amindexd*debug on server localhost.

 I've looked all over and can't seem to find what I need (possibly
 because I've never recovered before and don't know what to look
for).

 Steve

amrestore help

[Steven Settlemyre]

I am trying to restore a folder from a tape in a previous cycle (last 
night had a level 0 of the disk, but the folder was deleted prior). I 
have a tape changer and read that amrestore doesnt work with tape 
changers. My dumptypes are gnutar, so I probably can't use amrecover. Is 
this correct? When I tried to run it, it said amrecover: Unexpected end 
of file, check amindexd*debug on server localhost.


I've looked all over and can't seem to find what I need (possibly 
because I've never recovered before and don't know what to look for).


Steve

Re: amrestore help

[Steven Settlemyre]

actually, i found how to put the desired tape into the active slot of 
the changer. But when i do amrestore /dev/nst0 lollipop /files1 I get 
this:


amrestore: missing file header block
amrestore:   2: skipping zoo._.20070419.1.1
amrestore: missing file header block
amrestore:   6: skipping marlin._var.20070419.1.1
amrestore:  10: reached end of information

What now?

Steven Settlemyre wrote:
I am trying to restore a folder from a tape in a previous cycle (last 
night had a level 0 of the disk, but the folder was deleted prior). I 
have a tape changer and read that amrestore doesnt work with tape 
changers. My dumptypes are gnutar, so I probably can't use amrecover. 
Is this correct? When I tried to run it, it said amrecover: 
Unexpected end of file, check amindexd*debug on server localhost.


I've looked all over and can't seem to find what I need (possibly 
because I've never recovered before and don't know what to look for).


Steve

amrestore with disk with spaces in name

[Michael Keightley]

I am trying to use amrecover with with directory names in the disklist
file which
contain spaces.  Having no joy, e.g. with a test setup:

% cat disklist
myhost   /opt/test directorycomp-user-tar

% amrecover testset
AMRECOVER Version 2.5.1p3. Contacting server on myhost ...
220 myhost AMANDA index server (2.5.1p3) ready.
Setting restore date to today (2007-04-26)
200 Working date set to 2007-04-26.
200 Config set to testset.
200 Dump host set to myhost.
Use the setdisk command to choose dump disk to recover

amrecover listdisk
200- List of disk for host myhost
201- /opt/test directory

mrecover setdisk /opt/test directory
501 Disk myhost:\/opt/test directory\ is not in your disklist.

Any idea how to fix this?  Problem is lots of Windows folders that we want
to add to the disklist contain spaces.

Michael

Re: amrestore with disk with spaces in name

[Stefan G. Weichinger]

Michael Keightley schrieb:
 I am trying to use amrecover with with directory names in the disklist
 file which
 contain spaces.  Having no joy, e.g. with a test setup:
 
 % cat disklist
 myhost   /opt/test directorycomp-user-tar
 
 % amrecover testset
 AMRECOVER Version 2.5.1p3. Contacting server on myhost ...
 220 myhost AMANDA index server (2.5.1p3) ready.
 Setting restore date to today (2007-04-26)
 200 Working date set to 2007-04-26.
 200 Config set to testset.
 200 Dump host set to myhost.
 Use the setdisk command to choose dump disk to recover
 
 amrecover listdisk
 200- List of disk for host myhost
 201- /opt/test directory
 
 mrecover setdisk /opt/test directory
 501 Disk myhost:\/opt/test directory\ is not in your disklist.
 
 Any idea how to fix this?  Problem is lots of Windows folders that we want
 to add to the disklist contain spaces.

Strange name for a DLE ...

What about:

amrecover setdisk /opt/test\ directory

?

sgw

Re: amrestore with disk with spaces in name

[Stefan G. Weichinger]

Michael Keightley schrieb:

 Any idea how to fix this?  Problem is lots of Windows folders that we want
 to add to the disklist contain spaces.

Additional thought:

Read man amanda, section DISKLIST FILE.

You could use disknames without spaces, like in

amclient mydiskname /opt/test directory root-tar

Then use setdisk mydiskname instead.

sgw

Re: amrestore with disk with spaces in name

[Michael Keightley]

Tried this already:

amrecover setdisk /opt/test\ directory
501 Disk myhost:\/opt/test\\ directory\ is not in your disklist.

Michael

On 26/04/07, Stefan G. Weichinger [EMAIL PROTECTED] wrote:

Michael Keightley schrieb:
 I am trying to use amrecover with with directory names in the disklist
 file which
 contain spaces.  Having no joy, e.g. with a test setup:

 % cat disklist
 myhost   /opt/test directorycomp-user-tar

 % amrecover testset
 AMRECOVER Version 2.5.1p3. Contacting server on myhost ...
 220 myhost AMANDA index server (2.5.1p3) ready.
 Setting restore date to today (2007-04-26)
 200 Working date set to 2007-04-26.
 200 Config set to testset.
 200 Dump host set to myhost.
 Use the setdisk command to choose dump disk to recover

 amrecover listdisk
 200- List of disk for host myhost
 201- /opt/test directory

 mrecover setdisk /opt/test directory
 501 Disk myhost:\/opt/test directory\ is not in your disklist.

 Any idea how to fix this?  Problem is lots of Windows folders that we want
 to add to the disklist contain spaces.

Strange name for a DLE ...

What about:

amrecover setdisk /opt/test\ directory

?

sgw

Re: amrestore with disk with spaces in name

[Jean-Louis Martineau]

Michael,

This bug is already fix in the latest 2.5.1p3 snapshot.
You can download it from http://www.zmanda.com/community-builds.php

The snapshot have many bugs fixed since the release of 2.5.1p3.

Jean-Louis

Michael Keightley wrote:

I am trying to use amrecover with with directory names in the disklist
file which
contain spaces.  Having no joy, e.g. with a test setup:

% cat disklist
myhost   /opt/test directorycomp-user-tar

% amrecover testset
AMRECOVER Version 2.5.1p3. Contacting server on myhost ...
220 myhost AMANDA index server (2.5.1p3) ready.
Setting restore date to today (2007-04-26)
200 Working date set to 2007-04-26.
200 Config set to testset.
200 Dump host set to myhost.
Use the setdisk command to choose dump disk to recover

amrecover listdisk
200- List of disk for host myhost
201- /opt/test directory

mrecover setdisk /opt/test directory
501 Disk myhost:\/opt/test directory\ is not in your disklist.

Any idea how to fix this?  Problem is lots of Windows folders that we 
want

to add to the disklist contain spaces.

Michael

Re: amrestore with disk with spaces in name

[Michael Keightley]

Downloaded an compiled amanda-2.5.1p3-20070420
Fixed the problem.

Thanks,
Michael

On 26/04/07, Jean-Louis Martineau [EMAIL PROTECTED] wrote:

Michael,

This bug is already fix in the latest 2.5.1p3 snapshot.
You can download it from http://www.zmanda.com/community-builds.php

The snapshot have many bugs fixed since the release of 2.5.1p3.

Jean-Louis

Michael Keightley wrote:
 I am trying to use amrecover with with directory names in the disklist
 file which
 contain spaces.  Having no joy, e.g. with a test setup:

 % cat disklist
 myhost   /opt/test directorycomp-user-tar

 % amrecover testset
 AMRECOVER Version 2.5.1p3. Contacting server on myhost ...
 220 myhost AMANDA index server (2.5.1p3) ready.
 Setting restore date to today (2007-04-26)
 200 Working date set to 2007-04-26.
 200 Config set to testset.
 200 Dump host set to myhost.
 Use the setdisk command to choose dump disk to recover

 amrecover listdisk
 200- List of disk for host myhost
 201- /opt/test directory

 mrecover setdisk /opt/test directory
 501 Disk myhost:\/opt/test directory\ is not in your disklist.

 Any idea how to fix this?  Problem is lots of Windows folders that we
 want
 to add to the disklist contain spaces.

 Michael

Re: amrestore with tar empty directories at mountpoints

[Nick Brockner]

Jon LaBadie wrote:

On Sun, Sep 24, 2006 at 02:23:56PM -0400, Nick Brockner wrote:
  

Hi All.

I am new to amanda, and maybe I just don't understand how it works, but 
here is my problem:


I have a remote machine that I back up over my network.  The backups and 
everything go fine.  I am doing a disaster recovery test today, and it 
went all wrong.  Very, very wrong.  I have a DLE in disklists for / of 
this remote host.  The problem is that on this host, I have several 
different partitions mounted at /usr, /var/ /home, . . . you get the 
idea, and when the backup of the / DLE happenes, empty directories are 
created for all the mountpoints! (I am using GNUTAR).  So, when I tried 
to do a bare-metal restore, it clobbered my base install by overwriting 
all the mountpoints with empty directories, and I couldn't restore the 
rest of the partitions because the base install was hosed.


Can anyone help me / tell me what to do in order to get tar not to 
create these empty directories at the other mountpoints?



When I think of bare-metal restoration, I think of going to an empty,
probably partitioned and formatted drive.  In that case, restoring
the root DLE followed by the /usr, /var, ... DLEs would achieve what
you seek.

When the backup of your root DLE was made, /usr, as a mountpoint, was
an empty directory in the root file system.  So that is what was
restored.


amrecover restores to the state as of a particular time/date.
If I ask to recover a single directory from a week ago,
and I do the recovery into the original directory, any files
created during the week are deleted because it is restoring
the state of the directory to that of a week ago.  Same with
ownership and permission changes I might have made during the
week.  For this reason it is oft said here, do not do amrecover
into the original location, but instead into an empty directory.
Then check the files and move/copy to the ultimate location.

I don't know if you had used exclude directives to eliminate
the mountpoints from the root DLE would have changed anything.
Perhaps if they were not even included in the backup, they might
be totally eliminated upon recovery rather than left as empty
directories.  I just don't know.

  

Jon,

Thanks. I now realize I was going about the restore all wrong.  In the 
end, working down from the top-level directory and then restoring all 
mountpoints below worked perfectly.  I guess I was expecting a 
dump/restore type of restoration, where the mountpoints wouldn't show up 
as empty dirs and therefore would not be overwritten during the actual 
restoration.  I had done a bare minimal install before doing the restore 
of the filesystems so that the MBR was happy.


Amanda rocks.

Thanks again,
Nick Brockner

amrestore with tar empty directories at mountpoints

[Nick Brockner]

Hi All.

I am new to amanda, and maybe I just don't understand how it works, but 
here is my problem:


I have a remote machine that I back up over my network.  The backups and 
everything go fine.  I am doing a disaster recovery test today, and it 
went all wrong.  Very, very wrong.  I have a DLE in disklists for / of 
this remote host.  The problem is that on this host, I have several 
different partitions mounted at /usr, /var/ /home, . . . you get the 
idea, and when the backup of the / DLE happenes, empty directories are 
created for all the mountpoints! (I am using GNUTAR).  So, when I tried 
to do a bare-metal restore, it clobbered my base install by overwriting 
all the mountpoints with empty directories, and I couldn't restore the 
rest of the partitions because the base install was hosed.


Can anyone help me / tell me what to do in order to get tar not to 
create these empty directories at the other mountpoints?


Thanks,
Nick Brockner

Re: amrestore with tar empty directories at mountpoints

[Jon LaBadie]

On Sun, Sep 24, 2006 at 02:23:56PM -0400, Nick Brockner wrote:
 Hi All.
 
 I am new to amanda, and maybe I just don't understand how it works, but 
 here is my problem:
 
 I have a remote machine that I back up over my network.  The backups and 
 everything go fine.  I am doing a disaster recovery test today, and it 
 went all wrong.  Very, very wrong.  I have a DLE in disklists for / of 
 this remote host.  The problem is that on this host, I have several 
 different partitions mounted at /usr, /var/ /home, . . . you get the 
 idea, and when the backup of the / DLE happenes, empty directories are 
 created for all the mountpoints! (I am using GNUTAR).  So, when I tried 
 to do a bare-metal restore, it clobbered my base install by overwriting 
 all the mountpoints with empty directories, and I couldn't restore the 
 rest of the partitions because the base install was hosed.
 
 Can anyone help me / tell me what to do in order to get tar not to 
 create these empty directories at the other mountpoints?

When I think of bare-metal restoration, I think of going to an empty,
probably partitioned and formatted drive.  In that case, restoring
the root DLE followed by the /usr, /var, ... DLEs would achieve what
you seek.

When the backup of your root DLE was made, /usr, as a mountpoint, was
an empty directory in the root file system.  So that is what was
restored.


amrecover restores to the state as of a particular time/date.
If I ask to recover a single directory from a week ago,
and I do the recovery into the original directory, any files
created during the week are deleted because it is restoring
the state of the directory to that of a week ago.  Same with
ownership and permission changes I might have made during the
week.  For this reason it is oft said here, do not do amrecover
into the original location, but instead into an empty directory.
Then check the files and move/copy to the ultimate location.

I don't know if you had used exclude directives to eliminate
the mountpoints from the root DLE would have changed anything.
Perhaps if they were not even included in the backup, they might
be totally eliminated upon recovery rather than left as empty
directories.  I just don't know.

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