Well turned out I hadn't solved the issue with just extending the
Director max concurrent jobs. I had a file daemon that for various
reasons didn't run when it should have and so I didn't get the conflict
I was having before. However I have then created storage devices with
separate namings as in the manual in chapter 25 and this has now fixed
my problem. It has run for two nights, with all the File Daemons
operational and no issues have occurred.
Regards,
Adolf.
Sent from my Desktop Computer
On 19/08/17 07:50, Adolf Belka wrote:
Looks like extending just the Director max concurrent jobs has fixed
the problem.
Will still also look at following the storage daemon suggestions in
the manual.
Thanks for the help in sorting this out.
Regards,
Adolf.
Sent from my Samsung tablet
<br><br>-------- Original message --------<br>From: Adolf Belka <adolf.be...@gmail.com>
<br>Date: 15/08/2017 16:35 (GMT+01:00) <br>To: bacula-users@lists.sourceforge.net <br>Subject: Re:
[Bacula-users] Waiting to reserve a device messages after upgrade
to 9.0.3 <br><br>
Hi Phil,
Thanks for your help. My files have been like that since I started using
Bacula with a File Storage system. I just haven't realised as there
wasn't a warning message. Now there is so I will fix it.
The Director one is easy to fix.
For the Storage one there is a chapter in the Main manual that covers
running multiple Volumes with a File based system using different Media
Type names to differentiate them. I think this should work for what I
want. I will give it a try and if it works will let the list know.
Thanks very much,
Adolf
Sent from my Desktop Computer
On 14/08/17 22:51, Phil Stracchino wrote:
> On 08/14/17 15:56, Adolf Belka wrote:
>> Hi Phil,
>> Here is the director config file:-
> And here's your two problems:
>
>> Director { # define myself
>> Name = venus-dir
>> DIRport = 9101 # where we listen for UA connections
>> QueryFile = /opt/bacula/etc/query.sql
>> WorkingDirectory = /opt/bacula/working
>> PidDirectory = /opt/bacula/working
>> Maximum Concurrent Jobs = 1
> ...So your Director can run only one job at once.
>
>
>> Storage {
>> Name = FileStorage
>> Address = venus.harley.pimb.org # N.B. Use a fully
>> qualified name here
>> SDPort = 9103
>> Password = "+NL9puHa4nh4Fy0QVw6+tWKqBb8pWRoSLpbHL2bvlTa4"
>> Device = FileStorage
>> Media Type = File
>> }
>> Pool {
>> Name = Default
>> Pool Type = Backup
>> Recycle = yes # Bacula can automatically
>> recycle Volumes
>> AutoPrune = yes # Prune expired volumes
>> Volume Retention = 14 days # two weeks
>> Maximum Volume Jobs = 1;
> ...And so can your Storage, because you allow one Job per file and your
> Storage can only have one File open at a time.
>
>
> The Director's job concurrency is easily changed. The one-job-per-file
> setting is your decision. The one-file-at-a-time limit, you can't do
> anything about except by creating multiple Storage daemons assigned to
> the same Pool but running on different ports. If you try that, let us
> know how it works. It's not, as far as I know, an officially supported
> configuration.
>
>
Hi Phil,
Thanks for your help. My files have been like that since I started using
Bacula with a File Storage system. I just haven't realised as there
wasn't a warning message. Now there is so I will fix it.
The Director one is easy to fix.
For the Storage one there is a chapter in the Main manual that covers
running multiple Volumes with a File based system using different Media
Type names to differentiate them. I think this should work for what I
want. I will give it a try and if it works will let the list know.
Thanks very much,
Adolf
Sent from my Desktop Computer
On 14/08/17 22:51, Phil Stracchino wrote:
On 08/14/17 15:56, Adolf Belka wrote:
Hi Phil,
Here is the director config file:-
And here's your two problems:
Director { # define myself
Name = venus-dir
DIRport = 9101 # where we listen for UA connections
QueryFile = /opt/bacula/etc/query.sql
WorkingDirectory = /opt/bacula/working
PidDirectory = /opt/bacula/working
Maximum Concurrent Jobs = 1
...So your Director can run only one job at once.
Storage {
Name = FileStorage
Address = venus.harley.pimb.org # N.B. Use a fully
qualified name here
SDPort = 9103
Password = "+NL9puHa4nh4Fy0QVw6+tWKqBb8pWRoSLpbHL2bvlTa4"
Device = FileStorage
Media Type = File
}
Pool {
Name = Default
Pool Type = Backup
Recycle = yes # Bacula can automatically
recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 14 days # two weeks
Maximum Volume Jobs = 1;
...And so can your Storage, because you allow one Job per file and your
Storage can only have one File open at a time.
The Director's job concurrency is easily changed. The one-job-per-file
setting is your decision. The one-file-at-a-time limit, you can't do
anything about except by creating multiple Storage daemons assigned to
the same Pool but running on different ports. If you try that, let us
know how it works. It's not, as far as I know, an officially supported
configuration.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
