Re: amrecover failure, corrupted gzip file?

2003-03-28 Thread Gene Heskett 
On Fri March 28 2003 12:46, Mike Simpson wrote:
>Hi --
>
>> Any tips or tricks or other thoughts?  Is this the Linux
>> dump/restore problem I've seen talked about on the mailing list?
>>  I don't understand how the gzip file could be corrupted by a
>> problem internal to the dump/restore cycle.
>
>Answering my own question after a week of testing ... I think I've
>discovered a bug in Amanda 2.4.4.  This is what I've deciphered:
>
>(1) Restores of backup sets that compressed to < 1 gb worked fine.
>Backup sets that, when compressed, were > 1 GB blew up every
> time with gzip corruption error messages.  This was consistent
> across OS's (Solaris 8, RedHat 7.x), filesystem types (ufs, vxfs,
> ext2/3), and backup modes (DUMP, GNUTAR).
>
>(2) The gzip corruption message always occured at the same spot,
> i.e.
>
>   gzip: stdin: invalid compressed data--format violated
>   Error 32 (Broken pipe) offset 1073741824+131072, wrote 0
>
>which is 1024^3 bytes + 128k.  I note that in my Amanda
>configuration, I had "chunksize" defined to "1 gbyte" and
>"blocksize" set to "128 kbytes" (the chunksize was just for
>convenience, the blocksize seems to maximize my write
>performance).
>
>(3) I used "dd" to retrieve one of the compressed images that was
>failing.  At the 1 gb mark in the file, the more-or-less
> random bytes of the compressed stream were interrupted by exactly
> 32k of zeroed bytes.  I note that 32k is Amanda's default
> blocksize.
>
>(4) For last night's backups, I set "chunksize" to an arbitrarily
>high number, to prevent chunking, which works fine in my setup
>because I use one very large ext3 partition for all of my
> Amanda holding disk, which nullifies concerns about filesystem
> size and max file size.  The restores I've done this morning have
> all worked fine, including the ones that had previously shown the
> corruption.

Well, after making a blithering idiot out of myself with the last 2 
replies, (I've been doing too much work in hex lately) this does 
sound as if you have nailed it.  I've no idea how big your tapes 
are, but if they handled a huge chunksize ok, then a retry at 2 
gigs might be in order to confirm this, or maybe even half a gig 
which should give a confirming result pretty quickly.

I don't recall running into that here as the huge majority of my 
stuff is broken into subdirs that rarely exceed 800 megs.  I also 
didn't use an even chunk size, but is set nominally to 1/4 of a 
DDS2 tape or 900something megs.

Interesting.  Sounds like Jean-Louis or JRJ might want to look into 
this one.  Like you, I know just enough C to be dangerous, I'd 
druther code in assembly, on a smaller machine...

Are you using the last snapshot from Jean-Louis's site at umontreal?
If not, maybe this has already been fixed.  The latest one is dated 
20030318.  (Or was an hour ago :)  I just checked the ChangeLog, 
but didn't spot any references to something like this from now back 
to about the middle of November last.

>I'm not enough of a C coder to come up with a real patch to fix
> this. I'm hoping the above gives enough clues to let someone who
> _is_ a real C coder do so.
>
>If this should be posted to the amanda-hackers list, please feel
> free to do so, or let me know and I'll do it.  Also, if any other
> information would be helpful, just ask.
>
>Thanks,
>
>-mgs

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

Re: Help for a first time user

2003-03-28 Thread Jim Summers 
On Fri, Mar 28, 2003 at 04:22:43PM -0600, Ryan Vennell wrote:
> Is amanda live as in you run it and it takes care of all your servers in
> an automated fashion every day?

Once configured, yes.

> 
> Can you use a Hard Disk instead of a tape drive?

Yes.

> 
> Are there amanda clients for use with database servers?

IMO, homegrown scripts work best.

> 
> Thanks, Ryan

Precompiled binaries for AIX 4.3

2003-03-28 Thread Orion Poplawski 
I'm looking for precompiled binaries for AIX 4.3 (having no luck 
compiling 2.4.4 myself on AIX).  I've found two by google:

www.cs.ucy.ac.cy/~ank/amanda/binaries/
http://aixpdslib.seas.ucla.edu/packages/amanda.html
but the 1st appears to have linking issues on my system (4.3 rather than 
4.3.3?), while the second does not appear to have been compiled with GNU 
tar support.

Any help would be greatly appreciated

- Orion

AÞK VE PARA

2003-03-28 Thread sibel 
DISIKUS NET SITESINDEN DUYURU / www.disikus.net

__-
Hala Sevgiliniz Yok ise

Hala Arkadasiniz yok ise...Evlenmek istiyor ama aradiginizi bulamiyorsaniz,

www.disikus.net  sitesinde 71 Bin kayitli uyenin varligindan haberiniz yok demektir..

www.disikus.net / YUVAYI DISIKUS YAPAR

___&

10 MB WEB ALANI
50 MB MAIL ALANI
5 Pop3 MAIL/SMTP
10 MB MySQL

25 MILYON + KDV

www.acilhost.com / INTERNETTEKI EVINIZ

_

Help for a first time user

2003-03-28 Thread Ryan Vennell 
Is amanda live as in you run it and it takes care of all your servers in
an automated fashion every day?

Can you use a Hard Disk instead of a tape drive?

Are there amanda clients for use with database servers?

Thanks, Ryan

Re: 'not an Amanda tape' after FreeBSD upgrade

2003-03-28 Thread Toomas Aas 
> From:  Scott Lambert <[EMAIL PROTECTED]>

> On Thu, Mar 27, 2003 at 11:15:52AM +0200, Toomas Aas wrote:
> > Hello!
> > 
> > My Amanda server is running 2.4.3b4. Three days ago I upgraded the 
> > operating system from FreeBSD 4.7-RELEASE-p6 to 4.7-RELEASE-p9. This is 
> > really just some security patches to sendmail, libc and openssl. Since 
> > the upgrade Amanda thinks that all the backup tapes that were written 
> > before the upgrade are "not Amanda tapes". 
> > 
> > After I re-label the tape, Amanda agrees to write the backup to it and 
> 
> Could the compression bit have been toggled in you tape drive?

This doesn't seem to be the case. I checked after loading the next tape 
today and the compression settings are what they've always been.

Also, (say hello to mr. Murphy) the problem doesn't seem to exist at 
all with todays tape. After loading it I checked the Amanda label with 
dd as recommended by Gerhard den Hollander in another message and it 
looked OK. Amcheck was also happy with the tape. Maybe it was just some 
weird random problem with a couple of tapes.
--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* War doesn't determine who's right. War determines who's left.

Re: amrecover failure, corrupted gzip file?

2003-03-28 Thread Mike Simpson 
Hi --

> Any tips or tricks or other thoughts?  Is this the Linux dump/restore 
> problem I've seen talked about on the mailing list?  I don't 
> understand how the gzip file could be corrupted by a problem internal 
> to the dump/restore cycle.

Answering my own question after a week of testing ... I think I've 
discovered a bug in Amanda 2.4.4.  This is what I've deciphered:

(1) Restores of backup sets that compressed to < 1 gb worked fine.
Backup sets that, when compressed, were > 1 GB blew up every time
with gzip corruption error messages.  This was consistent across
OS's (Solaris 8, RedHat 7.x), filesystem types (ufs, vxfs, 
ext2/3), and backup modes (DUMP, GNUTAR).

(2) The gzip corruption message always occured at the same spot, i.e.

gzip: stdin: invalid compressed data--format violated
Error 32 (Broken pipe) offset 1073741824+131072, wrote 0

which is 1024^3 bytes + 128k.  I note that in my Amanda 
configuration, I had "chunksize" defined to "1 gbyte" and 
"blocksize" set to "128 kbytes" (the chunksize was just for
convenience, the blocksize seems to maximize my write 
performance).

(3) I used "dd" to retrieve one of the compressed images that was 
failing.  At the 1 gb mark in the file, the more-or-less random
bytes of the compressed stream were interrupted by exactly 32k of
zeroed bytes.  I note that 32k is Amanda's default blocksize.

(4) For last night's backups, I set "chunksize" to an arbitrarily
high number, to prevent chunking, which works fine in my setup
because I use one very large ext3 partition for all of my Amanda
holding disk, which nullifies concerns about filesystem size and
max file size.  The restores I've done this morning have all 
worked fine, including the ones that had previously shown the
corruption.

I'm not enough of a C coder to come up with a real patch to fix this. 
I'm hoping the above gives enough clues to let someone who _is_ a 
real C coder do so.

If this should be posted to the amanda-hackers list, please feel free 
to do so, or let me know and I'll do it.  Also, if any other 
information would be helpful, just ask.

Thanks,

-mgs

Amanda TCP Reset Problem with CygWin

2003-03-28 Thread Brian White 
Well, after several weeks of on-again, off-again work on this, I've got
Amanda behaving pretty well under CygWin.  I've applied Enrico's patches
for v2.4.2 to v2.4.3 and it seems to run just fine.

However, when the run completes, the CygWin amanda client completes, it
resets the TCP connection instead of closing it properly and thus the
server fails with the error "data read: Connection reset by peer".

Here is the tcpdump of the session.  The XP machine is "watertown" and
the server is "tolkien".

20:07:04.675952 tolkien.ott.precidia.com.898 > watertown.ott.precidia.com.amanda:  udp 
296 (DF)
20:07:04.917385 watertown.ott.precidia.com.amanda > tolkien.ott.precidia.com.898:  udp 
50
20:07:05.876973 watertown.ott.precidia.com.amanda > tolkien.ott.precidia.com.898:  udp 
85
20:07:05.877362 tolkien.ott.precidia.com.898 > watertown.ott.precidia.com.amanda:  udp 
50 (DF)
20:25:23.573832 tolkien.ott.precidia.com.901 > watertown.ott.precidia.com.amanda:  udp 
323 (DF)
20:25:23.808420 watertown.ott.precidia.com.amanda > tolkien.ott.precidia.com.901:  udp 
50
20:25:24.104053 watertown.ott.precidia.com.amanda > tolkien.ott.precidia.com.901:  udp 
232
20:25:24.104409 tolkien.ott.precidia.com.901 > watertown.ott.precidia.com.amanda:  udp 
50 (DF)
20:25:24.106066 tolkien.ott.precidia.com.3291 > watertown.ott.precidia.com.782: S 
2770461836:2770461836(0) win 5840  
(DF)
20:25:24.106719 watertown.ott.precidia.com.782 > tolkien.ott.precidia.com.3291: S 
1488495206:1488495206(0) ack 2770461837 win 17520  (DF)
20:25:24.106821 tolkien.ott.precidia.com.3291 > watertown.ott.precidia.com.782: . ack 
1 win 5840  (DF)
20:25:24.108097 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: S 
2782800686:2782800686(0) win 5840  
(DF)
20:25:24.108744 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: S 
1488548459:1488548459(0) ack 2782800687 win 17520  (DF)
20:25:24.108835 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: . ack 
1 win 5840  (DF)
20:25:24.109919 tolkien.ott.precidia.com.3293 > watertown.ott.precidia.com.784: S 
2782309519:2782309519(0) win 5840  
(DF)
20:25:24.110570 watertown.ott.precidia.com.784 > tolkien.ott.precidia.com.3293: S 
1488716333:1488716333(0) ack 2782309520 win 17520  (DF)
20:25:24.110672 tolkien.ott.precidia.com.3293 > watertown.ott.precidia.com.784: . ack 
1 win 5840  (DF)
20:25:24.117646 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: P 
1:72(71) ack 1 win 17520  (DF)
20:25:24.117787 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: . ack 
72 win 5840  (DF)
20:25:24.200843 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: P 
72:109(37) ack 1 win 17520  (DF)
20:25:24.200988 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: . ack 
109 win 5840  (DF)
20:25:24.201879 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: P 
109:236(127) ack 1 win 17520  (DF)
20:25:24.201931 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: . ack 
236 win 5840  (DF)
20:25:24.779303 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: P 
236:278(42) ack 1 win 17520  (DF)
20:25:24.779460 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: . ack 
278 win 5840  (DF)
20:25:24.975184 watertown.ott.precidia.com.784 > tolkien.ott.precidia.com.3293: P 
1:356(355) ack 1 win 17520  (DF)
20:25:24.975286 tolkien.ott.precidia.com.3293 > watertown.ott.precidia.com.784: . ack 
356 win 6432  (DF)
20:25:25.118320 watertown.ott.precidia.com.782 > tolkien.ott.precidia.com.3291: . 
1:1449(1448) ack 1 win 17520  (DF)
20:25:25.119444 tolkien.ott.precidia.com.3291 > watertown.ott.precidia.com.782: . ack 
1449 win 8688  (DF)
20:25:25.119382 watertown.ott.precidia.com.782 > tolkien.ott.precidia.com.3291: . 
1449:2897(1448) ack 1 win 17520  (DF)
20:25:25.119759 tolkien.ott.precidia.com.3291 > watertown.ott.precidia.com.782: . ack 
2897 win 11584  (DF)
20:25:25.121090 watertown.ott.precidia.com.782 > tolkien.ott.precidia.com.3291: P 
2897:3278(381) ack 1 win 17520  (DF)
20:25:25.121190 tolkien.ott.precidia.com.3291 > watertown.ott.precidia.com.782: . ack 
3278 win 14480  (DF)
   vvv
20:25:25.230050 watertown.ott.precidia.com.784 > tolkien.ott.precidia.com.3293: R 
1488716689:1488716689(0) win 0 (DF)
   ^^^
20:25:25.230284 watertown.ott.precidia.com.782 > tolkien.ott.precidia.com.3291: R 
1488498484:1488498484(0) win 0 (DF)
20:25:25.233667 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: F 
1:1(0) ack 278 win 5840  (DF)
20:25:25.234326 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: . ack 
2 win 17520  (DF)
20:25:25.264133 watertown.ott.precidia.com.783 > tolkien.ott.precidia.com.3292: P 
278:298(20) ack 2 win 17520  (DF)
20:25:25.264297 tolkien.ott.precidia.com.3292 > watertown.ott.precidia.com.783: R 
2782800688:2782800688(0) win

amrecover - gpg

2003-03-28 Thread Nicki Messerschmidt 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
I just set up amanda with gpg the way it is mentioned on [1], but now I
have a very mean problem. If I want to use amrecover I just get '500
"/" is an invalid directory' in my debug files. When I do 'strace -o
amindx -p 204 -f -ff -s 255' I get the strace files which you can get
at [2].
Has anyone any idea why amindexd won't read the index file?


thanks a lot and cheers
Nicki

[1] http://security.uchicago.edu/tools/gpg-amanda/
[2] http://home.link-m.de/nmesserschmidt/strace/strace.zip

- -- 
Linksystem Muenchen GmbH  [EMAIL PROTECTED]
Schloerstrasse 10   http://www.link-m.de
80634 Muenchen  Tel. 089 / 890 518-0
We make the Net work.   Fax 089 / 890 518-77

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.3 for non-commercial use 
Comment: Keys at: https://www.link-m.de/pgp

iQA/AwUBPoRiS+s1nPm17iBDEQLq8gCcDFGtOuBY68aihCW2J0p2WHBg2AkAn0kg
AzhnUVQaxFFaK87Uemv0T41J
=ufwv
-END PGP SIGNATURE-

tape type

2003-03-28 Thread Xiongfei Wang 
I have redhat 7.3 server on dell poweredge 4600
the tape is fuji DG4-150M 20/40G 4mm datatape. what should i put in the
amanda.conf for this tape?

Thanks

Re: Problem with amrecover

2003-03-28 Thread Nicki Messerschmidt 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Bartho Saaiman wrote:
> I am trying to restore from a tape using amrecover. If I use
> amrecover DailyBackup it says:
>  > AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>  > amrecover: cannot connect to localhost: Connection refused
This sound like your inetd isn't started. Otherwise you would get a
message like "Access from [EMAIL PROTECTED] not allowed"... Or did you
play with your firewall/hosts.(allow|deny) files?


Cheers
Nicki

- -- 
Linksystem Muenchen GmbH  [EMAIL PROTECTED]
Schloerstrasse 10   http://www.link-m.de
80634 Muenchen  Tel. 089 / 890 518-0
We make the Net work.   Fax 089 / 890 518-77

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.3 for non-commercial use 
Comment: Keys at: https://www.link-m.de/pgp

iQA/AwUBPoRdres1nPm17iBDEQKWtwCfceUV74VlFWPnTY5Qdttas0se3V0AoIT7
QZ5aDKzsyqejy+zte4irYKwg
=qcaD
-END PGP SIGNATURE-

Re: Problem with amrecover

2003-03-28 Thread Stephen Carville 
Are backup and localhost different machines? 

On Thursday 27 March 2003 10:17 pm, Bartho Saaiman wrote:
> Hi All :)
> 
> I am trying to restore from a tape using amrecover. If I use
> amrecover DailyBackup it says:
>  > AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>  > amrecover: cannot connect to localhost: Connection refused
> 
> If I use the -s backup and/or -t backup I also get the same:
>  > AMRECOVER Version 2.4.2p2. Contacting server on backup ...
>  > amrecover: cannot connect to backup: Connection refused
> 
> I previously had a similar problem and rectified this by editing the
> /var/lib/amanda/.amandahosts and added localhost root to the file. 
Tried 
> this as I am running amrecover as root but still could not fix it.
> 
> Any suggestions on what I am missing??
> 
> -- 
> # Bartho Saaiman
> # Network Administrator
> # Stellenbosch Automotive Engineering
> # Tel :: 27 21 882 8820 x 215
> # Email :: bartho @ cae.co.za
> 
> 

-- 
Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt
===
The difference between robbery and taxes is simple:   The first is 
someone threatening to hurt you if you do not give them your money.   
The second is legal.

Re: Problem with amrecover

2003-03-28 Thread Laas Toom 



If i am not mistaken, then .amandahosts must contain all of the
users & machines that need access to that machine. So edit the
.amandahosts file on the BACKUP server and add lines to allow you to
access from the host recover-host with user root:

recover-host root
recover-host.domain root
192.168.0.xx root

(added all of the possible ways just to be sure that you get what you want
(it depends on amanda and machines conf, which of the lines gets to be
used, so i have all of them in my .amandahosts file)


Laas Toom

On Fri, 28 Mar 2003, Bartho Saaiman wrote:

> Hi All :)
>
> I am trying to restore from a tape using amrecover. If I use
> amrecover DailyBackup it says:
>  > AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>  > amrecover: cannot connect to localhost: Connection refused
>
> If I use the -s backup and/or -t backup I also get the same:
>  > AMRECOVER Version 2.4.2p2. Contacting server on backup ...
>  > amrecover: cannot connect to backup: Connection refused
>
> I previously had a similar problem and rectified this by editing the
> /var/lib/amanda/.amandahosts and added localhost root to the file. Tried
> this as I am running amrecover as root but still could not fix it.
>
> Any suggestions on what I am missing??
>
> --
> # Bartho Saaiman
> # Network Administrator
> # Stellenbosch Automotive Engineering
> # Tel :: 27 21 882 8820 x 215
> # Email :: bartho @ cae.co.za
>