Hello,
My comments are below ...
On 09/14/2014 09:25 AM, Ivan Adzhubey wrote:
> Hi Kern,
>
> Thank you for taking your time and trying to help me. Please scroll down for
> my comments.
>
> On Sunday, September 14, 2014 08:26:23 AM Kern Sibbald wrote:
>> Hello,
>>
>> The rates that are shown in t
Mr. Ivan,
I really think picking data spooling for bottleneck verification is one of
the wildest shots you could do, since it could be affected by other factors
like network / client reading throuhput.
What is your client version?
Anyway: I dont think spooling has anything about overall data writi
Hi Kern,
Thank you for taking your time and trying to help me. Please scroll down for
my comments.
On Sunday, September 14, 2014 08:26:23 AM Kern Sibbald wrote:
> Hello,
>
> The rates that are shown in the status report are meant to be the
> incoming data rates, and as you say do not take into
Hello,
The rates that are shown in the status report are meant to be the
incoming data rates, and as you say do not take into account
spooling/despooling. I will be very surprised if there is any decrease
in throughput from version 2.4.x to 7.0.x. Concerning reporting
despooling rates: as far as
On Saturday, September 13, 2014 06:37:31 PM Ivan Adzhubey wrote:
> The "Running Jobs" Files, Bytes, AveBytes/sec, and LastBytes/sec track
> spooling process only. These counters stop as soon as the spooling to disk
> is completed. They do *not* track despooling at all. Despooling to tape is
> onl
On Saturday, September 13, 2014 03:38:52 PM Ivan Adzhubey wrote:
> CORRECTION: Reports for fobs doing despooling to tape also get their Files
> and Bytes reported values stuck (not incremented, unlike I wrote
> previously). Hence it makes sense that their speed rates get zero readings
> as well. T
Hi Kern,
On Saturday, September 13, 2014 08:34:47 AM Kern Sibbald wrote:
> Hello,
>
> The AveBytes/sec is the total number of bytes read from the FD for that
> job divided by the total number of seconds the job has been running.
>
> The LastBytes/sec is the number of bytes read from the FD for t
Hello,
The AveBytes/sec is the total number of bytes read from the FD for that
job divided by the total number of seconds the job has been running.
The LastBytes/sec is the number of bytes read from the FD for that job
since the last status command using a trivial smoothing algorithm that
include
Hi all,
I have recently upgraded to Bacula 7.0.5 on my old backup server, which seems
to have worked fine. However, I am now trying to figure out how to interpret
rather detailed status messages produced by various "status" command. One
particular puzzling thing is the following Storage status
