Use the amgtar application and set the TAR-BLOCKSIZE to a bigger value
(half the STREAM_BUFSIZE.
Why do you believe it is bottleneck?
Jean-Louis
Alan Griffiths wrote:
Thanks for the pointer.
I've re-compiled with
define STREAM_BUFSIZE (NETWORK_BLOCK_BYTES * 16)
And I can see that
We hit the problem of the TCP packet being too large
with amanda 2.6.1p1, though this threat indicates a
fix at 2.5.2.
http://forums.zmanda.com/showthread.php?t=1005
Is the problem corrected or does 2.6.1 require a patch
or something ?
thanks,
Dustin,
At least one problem (the buffer size error, I think) was fixed in
2.5.2 (and thus in 2.6.1 as well), but it may not be the same problem
you experienced. Have you upgraded? Does the problem still occur?
This system was a new deployment on a the Solaris 10/sparc
server that I've
On Wed, Oct 21, 2009 at 3:29 PM, Brian Cuttler br...@wadsworth.org wrote:
We hit the problem of the TCP packet being too large
with amanda 2.6.1p1, though this threat indicates a
fix at 2.5.2.
http://forums.zmanda.com/showthread.php?t=1005
Is the problem corrected or does 2.6.1 require a
Paul Mantz schrieb:
I'd be glad to explain. I'm working on a general update and rewrite
of amreport in Perl.
Big welcome to that ...
One of the components of this rewrite is xml
output for better monitoring by other programs.
I've been working on an abstraction of the logfile data
On Wed, Oct 21, 2009 at 5:07 PM, Stefan G. Weichinger s...@amanda.org wrote:
Maybe I am offtopic with my thoughts?
Nope, those are precisely the right thoughts. What Paul's looking for
is to make sure that you could build a tool to get the status you're
looking for from the XML his tool
Hi,
When I try to restore larger zip ( 4GB?) files from Windows backups,
they are corrupted.
The Amanda server is Solaris 10 running Amanda 2.6.1p1. The client is
Windows Server 2003, and I used the ZWCInstaller-Community-26.zip from
April 10.
I used amfetchdump with -l on the Amanda server to
