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
