Re: [Bacula-users] Timout problem with spooled jobs

One more suggestion, reducing the spool size has also helped. I have a mix of clients where initially everyone was using a 500GB spool size. My 10Gb connected clients were fine, but my 1 Gb clients would timeout when things were busy - I dropped the spool size to 50GB for the 1 Gb clients and

Re: [Bacula-users] Timout problem with spooled jobs

My heartbeat interval is set to 300 - you should probably increase yours. I originally had a smaller interval and had some clients that would time out - particularly if they were Windows clients. Patti Clark Linux System Administrator R Systems Support Oak Ridge National Laboratory On 9/3/15,

Re: [Bacula-users] Again: Device is BLOCKED waiting to create a volume for:

Hello Stefan, Sorry for my late reply. If you want to run jobs concurrently using the same pool and only one drive (your FileStorage device), your jobs should be configured to use this only pool. They will use only one volume in this pool since you have only one drive. >From your first post,

[Bacula-users] Read-only device resources

Is anyone using the relatively new read-only feature of Device resources? I had thought to use this feature to reserve an autochanger drive as the read drive for virtual full backups. But in a two-drive autochanger, making drive 1 read-only is problematic. A virtual full job will select the

Re: [Bacula-users] Again: Device is BLOCKED waiting to create a volume for:

On 9/4/2015 9:33 AM, Ana Emília M. Arruda wrote: Hello Stefan, Sorry for my late reply. If you want to run jobs concurrently using the same pool and only one drive (your FileStorage device), your jobs should be configured to use this only pool. They will use only one volume in this pool

Re: [Bacula-users] script to purge erred volumes

Hello Raymond, You can try the script bellow. But if your volume got into Error, I would recommend you to verify the volume before reusing it. This approach can led your backups into the same error if reusing a physically damaged volume. #!/bin/bash # DBHOST=localhost DATABASE=bacula

Re: [Bacula-users] Read-only device resources

Hello Josh, Are you using a physical or virtual autochanger? I haven´t tried the read-only feature yet. But I was wondering if in the case of a physical autochanger you could have the read-only drive also configured as a standalone drive. This way it would be possible to configure your Virtual

Re: [Bacula-users] Labeling when using native virtual autochanger

> On Sep 3, 2015, at 12:26 AM, Ana Emília M. Arruda > wrote: > > Hello Dan, > > On Wed, Sep 2, 2015 at 11:06 PM, Dan Langille > wrote: > >> On Aug 25, 2015, at 6:55 PM, Ana Emília M.

Re: [Bacula-users] Read-only device resources

On 9/4/2015 2:06 PM, Ana Emília M. Arruda wrote: Hello Josh, Are you using a physical or virtual autochanger? I haven´t tried the read-only feature yet. But I was wondering if in the case of a physical autochanger you could have the read-only drive also configured as a standalone drive.