getting sd error

saksham

server4-dir JobId 20: Error: Bacula dserver4-dir 9.6.7 (10Dec20):
Build OS: x86_64-pc-linux-gnu ubuntu 22.04
JobId: 20
Job: speed.2025-11-26_10.42.06_43
Backup Level: Full (upgraded from Incremental)
Client: "speed-fd" 15.0.3 (25Mar25) Windows Server 2019 Standard Evaluation ServerStandardEval (build 17763), 64-bit,Cross-compile,Win64;
FileSet: "Catalog" 2025-11-26 06:23:05
Pool: "Default" (From Command input)
Catalog: "MyCatalog" (From Client resource)
Storage: "Autochanger" (From Command input)
Scheduled time: 26-Nov-2025 10:42:06
Start time: 26-Nov-2025 10:42:08
End time: 26-Nov-2025 10:42:09
Elapsed time: 1 sec
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
Comm Line Compression: None
Snapshot/VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 1
Volume Session Time: 1764153497
Last Volume Bytes: 93,054 (93.05 KB)
Non-fatal FD errors: 1
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
dserver4-dir JobId 20: Fatal error: No Job status returned from FD.
dserver4-dir JobId 20: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2800 End Job TermCode=102 JobFiles=0 ReadBytes=0 JobBytes=0 Errors=1 VSS=1 Encrypt=0 CommBytes=66 CompressCommBytes=66
speed-fd JobId 20: Fatal error: filed/hello.c:191 Bad caps from SD: auth cram-md5 <980775219.1764153728@dserver4-sd> ssl=0
.
dserver4-dir JobId 20: Using Device "Autochanger-001" to write.
dserver4-dir JobId 20: Start Backup JobId 20, Job=speed.2025-11-26_10.42.06_43
dserver4-dir JobId 20: No prior or suitable Full backup found in catalog. Doing FULL backup.
dserver4-dir JobId 20: No prior Full backup Job record found.

gani

Hello @saksham,

This error can mean that you have incompatibility between Bacula DIR/SD and Bacula Client. The general rule in the Bacula component version compatibility is the following:

(Storage Daemon == Bacula Director) >= Bacula File Daemon (Client)

In other words, SD should be in the same version as DIR. The FD can be in the same version as DIR/SD or FD can be lower (older) than DIR/SD.

In you case DIR is 9.6.7 and FD is 15.0.3 and this is a problem. The solution for that is to upgrade DIR/SD to 15.0.x or downgrade FD to 9.6.x.

Good luck.

Best regards,
Marcin Haba (gani)

saksham

so how can i check the version ??
how can i install same

saksham

and can you plz provide me the link of 15 version of bacula for linux ubuntu 22 this is my main server

gani

Hello @saksham,

The component version you can check in the following way (for DIR, SD and FD):

bacula-dir -?
bacula-sd -?
bacula-fd -?

The upgrade process depends on the Bacula packages that you use. Usually with deb packages the process is automated and for rpm it requires manual updating Bacula SQL tables in the Bacula database.

For all cases, I encourage you to read the Bacula release notes. You can find it in the ReleaseNotes file attached to the Bacula sources. There is information about the upgrade and about the component compatibility.

Best regards,
Marcin Haba (gani)

gani

Hello @saksham,

The Bacula 15.0 packages for Ubuntu 22.04 you can find in the Bacula.org service after registering here:

https://www.bacula.org/bacula-binary-package-download/

NOTE: Packages from bacula.org are not compatible with packages from Ubuntu system repositories. So, if you use Bacula from system repositories, you need to uninstall them first, and then install these from Bacula.org. Before all, I suggest to do the Bacula database backup and Bacula configuration files backup as well. This process is not simple for new Bacula users, but if you prepare for it carefully, it can go well.

Best regards,
Marcin Haba (gani)