Timo Neuvonen schrieb:
> Below are a few clips from my recent backup logs (2.2.7 on CentOS 5.1). This 
> has never been a big issue to me, so I haven't bothered me with the rate 
> values. But could someone advice me what causes the huge difference between 
> the transfer rate reported by storage daemon (the 1st line in each clip) and 
> the rate value reported by the director thereafter?
> 
> The differences may be significant, eg. 696.5KB/s vs. 7.899MB/s.
> Storage daemon values can be calculated from "SD bytes written" and "write 
> elapsed time", but what is the latter, smaller value from the director? 
> Since it is smaller, it cannot even be any occasional top peak value.
> For example, in the first case elapsed time reported by the director (44:20) 
> and bytes written (17.8GB) would lead to value of  appr. 6.7 MB/s, not to 
> 696.5 kB/s.
> 
> 
> 18-Jan 17:36 dogbert-sd JobId 641: Job write elapsed time = 00:37:41, 
> Transfer rate = 7.899 M bytes/second
>   Elapsed time:           44 mins 20 secs
>   FD Bytes Written:       17,812,805,063 (17.81 GB)
>   SD Bytes Written:       17,861,799,431 (17.86 GB)
>   Rate:                   696.5 KB/s
[...]

It's a bug in 2.2.7 -> http://bugs.bacula.org/view.php?id=1036

Ralf

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to