My bad, I made a wrong statement in my earlier email.
Here is the corrected scenario.
I have a dynamic fileset creation with a script that runs on the client (Linux)
side with File resource, see the setting below:
File = "\\| su - username -c "/path/to/the/script"
The execution of this script takes a long time, resulting in timeout , thus
failing the backup job
bacula-server-dir JobId 1101693: Fatal error: Bad response to
Storage command: wanted 2000 OK storage
, got 2902 Bad storage |
FD termination status: Error
SD termination status: Waiting on FD
Thanks
Yateen
From: Yateen Shaligram Bhagat (Nokia)
Sent: Wednesday, June 18, 2025 4:53 PM
To: [email protected]
Subject: Timeout setting for ClientRunBeforeJob
Hi All,
We are using Bacula 13.x (dir & sd) with few legacy clients (fd) with 9.4.4
along with 13.x clients
We have client backup job configuration that uses the resource
ClientRunBeforeJob=<path/to/script/on/client>
For few clients this client side script execution takes about 20 to 30 minutes,
consequently the backup job for those clients fails with error
bacula-server-dir JobId 1101693: Fatal error: Bad response to
Storage command: wanted 2000 OK storage
, got 2902 Bad storage |
FD termination status: Error
SD termination status: Waiting on FD
Is there a way to increase the timeout period for the clientRunBefore script to
complete.
Thanks,
Yateen
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
