Backup Central

Hello,

I reported this problem for 2.5.1p2 and it was fixed by Jean-Louis. It came
back in 3.1.1, where I got a patch from Dustin which fixed it for restoring on
the server, but not when restoring on the client. But he said it was to late
to add the patch to 3.1.2. Today I upgraded to 3.2.0 and it's still broken.

amrecover shows files with umlauts:

2010-10-22-09-32-21 "M\\303\\266gliche Zusatzkosten f\\303\\274r QM-Projekt.odt"

The only way to recover is adding the file with wildcards (like 'add
M*gliche*'), but makes recovering an annoyning job.

I hope, there is a way to finally fix this soon again (like in 2.5.1p2 some
years ago). Thanks.

Regards,
Marc


--
Marc Muehlfeld (IT-Leiter)
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-78
http://www.medizinische-genetik.de

It's getting more and more strange:

Restore of a file with umlaut totally fails if you try to restore over network
(client and server are both 3.2.0). It's even impossible to use wildcards:


# amrecover TestSet -s nucleus -t nucleus
AMRECOVER Version 3.2.0. Contacting server on nucleus ...
...
amrecover> ls
...
2010-10-22-09-32-21 "M\\303\\266gliche Zusatzkosten f\\303\\274r QM-Projekt.odt"
amrecover> add M*
Added file "/M\\303\\266gliche Zusatzkosten f\\303\\274r QM-Projekt.odt"
amrecover> extract
...
Extracting files using tape drive HDD_Test_Changer on host nucleus.
Load tape TestSet002 now
Continue [?/Y/n/s/d]? y
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
/bin/tar: Read 7944 bytes from -
/bin/tar: ./M\303\266gliche Zusatzkosten f\303\274r QM-Projekt.odt: Not found
in archive
/bin/tar: Error exit delayed from previous errors



If I downgrade the client to 2.6.1p2, I can restore files when using wildcards
from an 3.2.0 server. But the usage of wildcards is still necessary.


Regards,
Marc


--
Marc Muehlfeld (IT-Leiter)
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-78
http://www.medizinische-genetik.de

Can you restore file that have no umlaut? try: add *

Can you post the debug files
amrecover.*.debug from the client

amandad.*.debug, amindexd.*.debug and amidxtaped.*.debug from the server

Send them for both run, with the 2.6.1p2 and 3.2 client.

Jean-Louis

Marc Muehlfeld wrote:
It's getting more and more strange:

Restore of a file with umlaut totally fails if you try to restore over
network (client and server are both 3.2.0). It's even impossible to
use wildcards:


# amrecover TestSet -s nucleus -t nucleus
AMRECOVER Version 3.2.0. Contacting server on nucleus ...
...
amrecover> ls
...
2010-10-22-09-32-21 "M\\303\\266gliche Zusatzkosten f\\303\\274r
QM-Projekt.odt"
amrecover> add M*
Added file "/M\\303\\266gliche Zusatzkosten f\\303\\274r QM-Projekt.odt"
amrecover> extract
...
Extracting files using tape drive HDD_Test_Changer on host nucleus.
Load tape TestSet002 now
Continue [?/Y/n/s/d]? y
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
/bin/tar: Read 7944 bytes from -
/bin/tar: ./M\303\266gliche Zusatzkosten f\303\274r QM-Projekt.odt:
Not found in archive
/bin/tar: Error exit delayed from previous errors



If I downgrade the client to 2.6.1p2, I can restore files when using
wildcards from an 3.2.0 server. But the usage of wildcards is still
necessary.


Regards,
Marc

Marc Muehlfeld wrote:
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
/bin/tar: Read 7944 bytes from -
It has nothing to do with umlauts.

I suspect a bug in the handling of the bsd auth in amrecover.
Can you try the bsdtcp auth?
You need to setup an inetd/xinetd entry on the server and run amrecover
with '-oauth=bsdtcp'

Jean-Louis

Marc,

It's a bug that can only be seen with the bsd auth.
Attached patch fix it, can you try it?

Jean-Louis

Jean-Louis Martineau wrote:
Marc Muehlfeld wrote:
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
/bin/tar: Read 7944 bytes from -
It has nothing to do with umlauts.

I suspect a bug in the handling of the bsd auth in amrecover.
Can you try the bsdtcp auth?
You need to setup an inetd/xinetd entry on the server and run
amrecover with '-oauth=bsdtcp'

Jean-Louis

Hi Jean-Louis,

It's a bug that can only be seen with the bsd auth.
Attached patch fix it, can you try it?

thanks for the patch. I applied it to the client and server (both 3.2.0) and
tried a restore a file without umlauts on the client:

...
Continue [?/Y/n]? y

amrecover: bad header
Extractor child exited with status 1

I attached all logfiles that were created for that try (2 from the server, 1
from the client)



Am 22.10.2010 18:06, schrieb Jean-Louis Martineau:
I suspect a bug in the handling of the bsd auth in amrecover.
Can you try the bsdtcp auth?
You need to setup an inetd/xinetd entry on the server and run
amrecover with '-oauth=bsdtcp'

bsdtcp allows recovering files with and without umlauts (without just when
using wildcards as workaround).

Regards,
Marc


Am 22.10.2010 21:47, schrieb Jean-Louis Martineau:
It's a bug that can only be seen with the bsd auth.
Attached patch fix it, can you try it?

Jean-Louis

Jean-Louis Martineau wrote:
Marc Muehlfeld wrote:
/bin/tar: This does not look like a tar archive
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
/bin/tar: Read 7944 bytes from -
It has nothing to do with umlauts.

I suspect a bug in the handling of the bsd auth in amrecover.
Can you try the bsdtcp auth?
You need to setup an inetd/xinetd entry on the server and run amrecover with
'-oauth=bsdtcp'

Jean-Louis



--
Marc Muehlfeld (IT-Leiter)
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-78
http://www.medizinische-genetik.de

Stupid me

Try this new patch, remove previous patch befora applying this one.

Jean-Louis

Marc Muehlfeld wrote:
Hi Jean-Louis,

It's a bug that can only be seen with the bsd auth.
Attached patch fix it, can you try it?

thanks for the patch. I applied it to the client and server (both
3.2.0) and tried a restore a file without umlauts on the client:

...
Continue [?/Y/n]? y

amrecover: bad header
Extractor child exited with status 1

I attached all logfiles that were created for that try (2 from the
server, 1 from the client)

Am 23.10.2010 13:02, schrieb Jean-Louis Martineau:
Try this new patch, remove previous patch befora applying this one.

I applied the patch to the client and server. Now recovery is possible if both
are 3.2.0 and using bsd auth. Thanks.



But the problem with the umlauts is still there: I can't recover files with
german umlauts, only if I use wildcards. Also they are not shown in amrecover:

amrecover> ls
2010-10-22-16-57-51 "M\\303\\266gliche Zusatzkosten f\\303\\274r QM-Projekt.odt"

You fixed this in 2.5.1p2
(http://groups.yahoo.com/group/amanda-hackers/message/5233), but it came back
in 3.1.1 and is still there in 3.2.0.


Regards,
Marc




--
Marc Muehlfeld (IT-Leiter)
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-78
http://www.medizinische-genetik.de