On 10/6/20 3:45 AM, Žiga Žvan wrote:
I believe that I have my spooling attributes set correctly on jobdefs
(see bellow). Spool attributes = yes; Spool data defaults to no. Any
other idea for performance problems?
Regard,
Ziga
The client version is very old. First try updating the client to 9.6.x.
For testing purposes, create another storage device on local disk and
write a full backup to that. If it is much faster to local disk storage
than it is to the s3 driver, then there may be an issue with how the s3
driver is compiled, version of s3 driver, etc.
Otherwise, with attribute spooling enabled, the status of the job as
given by the status dir command in bconsole will change to "despooling
attributes" or something like that when the client has finished sending
data. That is the period at the end of the job when the spooled
attributes are being written to the catalog database. If despooling is
taking a long time, then database performance might be the bottleneck.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
