Hi James, On Thu, Jul 8, 2021 at 1:31 PM James Youngman <[email protected]> wrote:
> I like this idea. My configuration for example has a single machine > which is much larger than all the others put together. > Very nice. Always good to get feedback from somebody else. Your configuration is indeed similar to mine, and I guess is a quite common scenario. This analysis would be better if I could figure out the write throughput > while despooling, but I don't know how to extract that from the Bareos > catalog. > Not sure about the catalog, but I at least have these log lines on my jobs: 2021-07-08 09:14:50 bareos-sd JobId 405: Spooling data again ... 2021-07-08 09:16:53 bareos-sd JobId 405: Committing spooled data to Volume "P0033SL4". Despooling 9,181,225,019 bytes ... 2021-07-08 09:18:12 bareos-sd JobId 405: Despooling elapsed time = 00:01:19, Transfer rate = 116.2 M Bytes/second You might be able to parse those log lines and get what you are looking for. In my case, using Prometheus metrics and Grafana, this is how the runs look for me. https://storage.googleapis.com/bluecmd/spooling-interleaved.png You can quite clearly see that network and tape bandwidth alternates. Regards, -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/CADiuDARgA6ZS-hvcgTbmLVrK5hDJKA0Uv4upT7X8FJa8G%2BBdBQ%40mail.gmail.com.
