Hi, The issue is resolved after I increased the number of devices under a filechanger. Nevertheless, the suggestion to keep the file server and the bacula-sd on the same host is good one.
Thanks Yateen From: Josh Fisher <jfis...@pvct.com> Sent: Monday, April 6, 2020 6:22 PM To: Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) <yateen.shaligram_bha...@nokia.com>; bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Issue with concurrent jobs in disk based auto changer On 4/4/2020 1:50 PM, Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) wrote: Hello, ... All these jobs including the ones that are initially shown as "created not yet running" eventually complete successfully, but after a long time (~36 Hours), But the very purpose of concurrency is defeated. You may also be looking at a network bottleneck. Is the file server on the same network as the clients? If so, then client data is traversing the same network twice and it would be better to run bacula-sd on the file server. Also, if the db is being accessed across the network, then turning on attribute spooling may help.
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
