Thanks to everyone that responded. I’ve solved the problem.
We had 4 10Gbs network interfaces aggregated together using LACP. Running some
tests trying to send data to a Windows client we found the problem is not just
Bacula. Even ftp failed if the file size was bigger than about 1300 bytes.
[resent since the list server seems to work again now]
Am 14.02.2018 um 03:00 schrieb Kenneth Garges:
>
>> On 10Feb 2018, at 1:29 PM, Tilman Schmidt wrote:
>>
>> Any chance of checking on the firewall what's happening with the connection?
>
> Looking at the firewall rules show it will pass anyt
The answer to your question was already provided by Aldolf in citing
Phil's email, but just to confirm: yes building some of the Storage
Daemon tools requires information about the catalog database you are using.
Best regards,
Kern
On 02/12/2018 06:40 PM, Shawn Rappaport wrote:
Thank you fo
Normally when Bacula asks for a specific volume and the volume is not
"available" it will put up a message requesting the volume. If you then
put a different volume into the drive (assuming it is a tape), Bacula
will use that volume if it is appropriate (correct Media Type, Pool,
Volume Status,
