The reason why the level that ZWC is estimating is not seen is because the
logs are error level logs and nit debug level.
Robert, can you please change the log level to Debug. To do this go to
"Start Programs > Zmanda > Zmanda.. > ZWC Config Utility". Go to Debug
tab and change the level to 5.
On Fri, Jul 30, 2010 at 10:31 AM, McGraw, Robert P wrote:
> Below are two URL that has the log files from the server and the ZWC for the
> run.
Thanks! I see "Estimate" several times in the ZWC logfile, but I
don't see a description of the level it is estimating. Prashant?
Dustin
--
Open So
om] On Behalf Of
> Dustin J. Mitchell
> Sent: Friday, July 30, 2010 11:26 AM
> To: McGraw, Robert P
> Cc: Prashant Joshi; amanda-users@amanda.org
> Subject: Re: ZWC backup level.
>
>
> On Fri, Jul 30, 2010 at 9:50 AM, McGraw, Robert P
> wrote:
> > planner: time 113.
On Fri, Jul 30, 2010 at 9:50 AM, McGraw, Robert P wrote:
> planner: time 113.487: got result for host mailrelay disk "C:/Alligate": 0 ->
> 2604811K, 1 -> -3K, -1 -> -3K
> planner: time 113.487: getting estimates took 113.080 secs
It looks like ZWC only returned an estimate for a level 0 dump; -3
analysis took 0.000 secs
> -Original Message-
> From: djmit...@gmail.com [mailto:djmit...@gmail.com] On Behalf Of
> Dustin J. Mitchell
> Sent: Friday, July 30, 2010 9:47 AM
> To: Prashant Joshi
> Cc: McGraw, Robert P; amanda-users@amanda.org
> Subject: Re: ZWC backup le
On Fri, Jul 30, 2010 at 5:50 AM, Prashant Joshi wrote:
> Dustin, can you please confirm, why is the server sending a level 0 request
> every time?
That would happen if the planner's request for a level-1 estimate
failed for some reason, or if there's a strategy that causes the
planner to never do
RIG-MB OUT-MB COMP% MMM:SS
>> KB/s MMM:SS KB/s
>>
>> -------------
>> -- -
>>
>> hertz/galileo/scr1MISSING
>>
/gauss/export/pkgs MISSING
>
>
> hertz-ss/export/users-b MISSING
>
>
> hertz-ss/export/users-j MISSING
> -
Hi Robert,
We had seen a similar issue in which Level 0 & Level 1 backups were of the
same size. But that issue was seen in ZWC Community edition 2.6.1 which got
fixed in the 3.1 client released on 15th April 2010. Can you please confirm
what version of ZWC Community edition is installed on the Win