Hello everyone
Investigating a little more about what might be happening, I compared
the records (from the Bacula catalog in the database) of a file that was
backed up by 9.6.7 and 11.0.5, without having changed during these two
jobs .
I noticed that the "lstat" field of the "filename" table is calculated
differently between the two versions, although the file hashes, stored
in the "md5" field are the same, see:
jobid | pathid | filename | lstat
| md5
-------+--------+------------+------------------------------------------------------------+-----------------------------
14469 | 83108 | BPAGAR.DBF | A BAAAAAQCz IH/ B A A A Iu A A BOk0Kn
xxyqA BQdcaU A A M g | TYUkCmxYjmRvmCoTaOBDO+CRJx8
14749 | 83108 | BPAGAR.DBF | A A IH/ B A A A Iu A A BOk0Kn xxyqA
xxyqA A A M g | TYUkCmxYjmRvmCoTaOBDO+CRJx8
Now, why is this field calculated differently?
Thanks!
Em 06/12/2021 08:57, Márcio (Departamento de Informática - PMI) escreveu:
Greetings everyone
The issue of disabling TLS didn't resolve the issue, but after the
FULL backup ran last weekend, the Differential backup's performance
returned to the time it used to take.
Initially I thought that this happened because, at the time of
removing the file daemon from the previous version, I had not saved
the contents of the "working" folder.
Now I updated the file daemon on another server, but before removing
the old version, I saved the contents of the "working" folder and
restored it after the new version was installed.
If I run the "estimate" command on this server, selecting
"level=Differential", the command returns as if there wasn't a Full
backup done previously, reporting that all files would be backed up.
Here is a question: is there a way to enable a DEBUG level, on the
client or on the director, to try to understand what is happening?
Grateful for the attention
Em 02/12/2021 13:47, Bill Arlofski via Bacula-users escreveu:
On 12/2/21 05:12, Márcio wrote:
Greetings everyone
I recently updated the file daemon version on two Windows Server 2019
clients from version 9.6.7 to version 11.0.5.
In both I noticed that the backup performance dropped, making the job
take longer to finish.
I noticed that the rate (in KB/sec) reported in the job report was
pretty much the same using both versions of the file daemon.
Has anyone else noticed this loss of performance?
Márcio
How big is the difference in performance?
11.0.x encrypts all communication between all daemons by default.
I can't really believe this would be the cause, but to test you can
disable TLS encryption by setting:
----8<----
TLSPSKEnable = no
----8<----
In each of your daemon config files, restart the daemons and try again.
Hope this helps!
Bill
--
Bill Arlofski
w...@protonmail.com
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
