Marek Simon wrote:
> Alan is right. The problem is not the inserting itself but the fact,
> that Storage is blocked while the job do not need it more. If I disable
> attribute spooling the attributes will be stored with data and the time
> the job spends will be the same (I think).
>
Maybe.
Alan is right. The problem is not the inserting itself but the fact,
that Storage is blocked while the job do not need it more. If I disable
attribute spooling the attributes will be stored with data and the time
the job spends will be the same (I think).
The database performance is another prob
On Wed, 7 Oct 2009, Cedric Tefft wrote:
> The second phase (what you describe as DIA) is a result of using "Spool
> Attributes = yes" in your job defs. Changing this to no MIGHT solve
> your problem. OTOH, it might actually make things worse. I suggest you
> look up the Spool Attributes direct
Marek Simon wrote:
> Hi,
> I have a complex bacula config (2.4.4) with about 100 clients, 300 Jobs
> and 48 Storages on two Storage Daemons (32 on one and 16 on the other).
> The multiplicity of Storages is for paralelism. The clients are spread
> among the storages with config generator, which
Hi,
I have a complex bacula config (2.4.4) with about 100 clients, 300 Jobs
and 48 Storages on two Storage Daemons (32 on one and 16 on the other).
The multiplicity of Storages is for paralelism. The clients are spread
among the storages with config generator, which selects the Storage for
them
