Hello,
Can you or anyone else on these lists confirm having this problem with Linux
2.0.3 (please ensure it is really 2.0.3) clients?If so, could you please
send me (if possible) one or more of the files (say as a compressed tar file)
that demonstrates the problem. It would simplify fixing
Was this problem resolved?
When restoring some file (tried 3 different files in 3 different
folders) I get same error, however the file gets restored without problems.
Bacula 2.0.3 Linux Dir and Win2k client.
I am also using 4096 bit keys (bacula doc had example as 2048)
Thanks.
24-Apr 16:48 back
Hello,
At this point, you should isolate the problem to a single file if possible
that is causing the problem. Do a backup of that file only, then a restore.
If you can isolate the error in that way, please open a bug report, giving
the appropriate output error messages, uploading your bacula-
> Hello,
>
> There was a bug in the restore code that was fixed in 2.0.3. Please
> update
> (at least the client FD), test again, and let us know if it resolves the
> problem.
>
> Best regards,
>
> Kern
Hi Kern. Thanks for getting back to me. I upgraded the client to version
2.0.3 but I'm experie
Hello,
There was a bug in the restore code that was fixed in 2.0.3. Please update
(at least the client FD), test again, and let us know if it resolves the
problem.
Best regards,
Kern
On Friday 30 March 2007 21:24, Michael Havas wrote:
> Hi everyone,
>
> I'm using bacula with encryption with
Hi everyone,
I'm using bacula with encryption with Windows Client version 2.02 and
Director/Storage daemons on CentOS 4.4. The client both the PKI Keypair
and Master certificate for encryption.
I've been testing out restores with bacula and encryption. I've found
some disturbing results. Certa