Yes, this patch solved the problem. Thank you! Can we anticipate
it being integrated into future versions?
-Mitch
On Tue, 19 May 2009, Jean-Louis Martineau wrote:
amanda client 2.6.1p1 is compatible with server 2.4.3b4 and up. But it is not
with 2.4.3b3 and previous.
Try the attached
Mitch Collinsworth wrote:
Yes, this patch solved the problem. Thank you! Can we anticipate
it being integrated into future versions?
I committed the patch to SVN, it will be in the next release.
Jean-Louis
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from being backed up by a 2.4.3b3 server?
I've got it to the point where they are at least talking with each
other, using auth bsd.
amcheck -c is happy.
estimates worked ok.
But amstatus is showing this:
client-a:/a
I try to keep them compatible, but I don't test with release before 2.4.5.
index_server is used only by amrecover.
Can you post the amandad.*.debug file from the client?
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from
On Tue, 19 May 2009, Jean-Louis Martineau wrote:
I try to keep them compatible, but I don't test with release before 2.4.5.
index_server is used only by amrecover.
Can you post the amandad.*.debug file from the client?
Jean-Louis
Yup, here's a sample below.
-Mitch
1242745188.258722:
amanda client 2.6.1p1 is compatible with server 2.4.3b4 and up. But it
is not with 2.4.3b3 and previous.
Try the attached patch.
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from being backed up by a 2.4.3b3 server?
I've
