Stefan G. Weichinger wrote:
Am 2011-05-17 23:59, schrieb Stefan G. Weichinger:
Thanks, Jean-Louis, will do that tomorrow and report back!
ah, never mind, I tried it already ;-)
file bb
bb: data
Then it is clearly not a tar file nor a gzip file.
You said the backup is
Am 18.05.2011 12:56, schrieb Jean-Louis Martineau:
You said the backup is crypted with amcrypt? You should try to decrypt
it with amcrypt -d
bb was the decrypted file already.
I followed your suggestion:
$ amcrypt -d aa bb
I don't know what 'file' report for a file encrypted with
Check if amcrypt is working:
echo Stefan | amcrypt | amcrypt -d
Jean-Louis
Stefan G. Weichinger wrote:
Am 18.05.2011 12:56, schrieb Jean-Louis Martineau:
You said the backup is crypted with amcrypt? You should try to decrypt
it with amcrypt -d
bb was the decrypted file already.
I
Am 18.05.2011 15:33, schrieb Jean-Louis Martineau:
Check if amcrypt is working:
echo Stefan | amcrypt | amcrypt -d
Yes, it looks like:
$ echo Stefan | amcrypt | amcrypt -d
Stefan
I now removed 3.1.3, and installed 3.2.3 (latest stable).
I then redid the mentioned steps and now I get:
$ file bb
bb: gzip compressed data, from Unix, last modified: Wed May 18 02:50:06
2011, max speed
$
tar -tf bb | head
./
./.vmware/
./bin/
./boot/
./dev/
./etc/
./etc/NetworkManager/
Sorry folks, out of habbit I replied to a year old thread
not realizing I was writing to people who where largely out
of the project.
I hate to bring such an old thread back but...here is the issue.
I am running Solaris 10/x86 server and same on client.
Installed v 3.1.2 on the server and
Brian Cuttler wrote:
1305727744.474545: amgtar: /usr/sfw/bin/gtar terminated with signal 11: see /tmp
/amanda/client/curie/amgtar.20110518100904000.debug
It is not a timeout issue, it is gtar that segfault
You can try to install a newer gtar or find why this one crash.
Jean-Louis
On Wednesday, May 18, 2011 02:19:47 PM Stefan G. Weichinger did opine:
Am 18.05.2011 19:55, schrieb gene heskett:
Humm, at risk of hijacking this thread, I tried that here. And got a
huge list of output from which indicating it didn't find aespipe.
So I did a 'locate aespipe' and got
Am 18.05.2011 20:25, schrieb gene heskett:
A fairly complex setup it seems.
It depends ;-)
Rather complex but no rocket science.
aespipe != amaespipe
It has to be installed additionally to amanda.
Thanks Stefan. And it doesn't appear to be part of the pclos repo's
either, so would
Jean-Louis,
Thanks, thought from the compattibility chart I found that
1.23 was ok, but was going to attempt an update.
thank you - will let the you/list know if I succeed.
Brian
On Wed, May 18, 2011 at 01:42:01PM -0400, Jean-Louis Martineau wrote:
Brian Cuttler wrote:
1305727744.474545:
Yes, replacing gtar 1.23 with 1.26 seems to have done the trick.
Please note - dumptype user-tar will work with 1.23 but
zfs-snapshot will not. Its only when you move to zfs-snapshot
that you have to update gtar.
I will test the same thing on the other client.
thanks - Brian
On Wed, May 18,
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
12 matches
Mail list logo
