error occuring while takeing backup of window server

saksham

Bareos-test-dir JobId 7: Using Device "DemoAutochanger-002" to write.
Bareos-test-dir JobId 7: Start Backup JobId 7, Job=window-server.2025-11-18_06.13.00_36

saksham

*status dir
Bareos-test-dir Version: 9.6.7 (10 December 2020) x86_64-pc-linux-gnu ubuntu 22.04
Daemon started 18-Nov-25 06:04, conf reloaded 18-Nov-2025 06:10:24
Jobs: run=2, running=1 mode=0,0
Heap: heap=987,136 smbytes=143,266 max_bytes=218,544 bufs=465 max_bufs=868
Res: njobs=4 nclients=2 nstores=3 npools=3 ncats=1 nfsets=3 nscheds=2

Scheduled Jobs:

Level Type Pri Scheduled Job Name Volume

Incremental Backup 10 18-Nov-25 23:05 BackupClient1 unknown

Full Backup 11 18-Nov-25 23:10 BackupCatalog unknown

Running Jobs:
Console connected at 18-Nov-25 06:19

JobId Type Level Files Bytes Name Status

7 Back Full 0 0 window-server is waiting for Client window-fd to connect to Storage DemoAutochanger

Terminated Jobs:

JobId Level Files Bytes Status Finished Name

3 Cata 0 0 Error 18-Nov-25 06:04 window-server
5 Cata 0 0 Error 18-Nov-25 06:11 window-server
6 Full 1 52.96 K OK 18-Nov-25 06:11 BackupCatalog

====
*

saksham

![
](https://)

gani

Hello @saksham,

The most important in your logs is this message:

window-server is waiting for Client window-fd to connect to Storage DemoAutochanger

This means that the Bacula File Daemon is trying to connect to the Storage Daemon but from some reason it can't.

I would propose to check if the Bacula Storage Daemon does not listen on localhost but it listens on all interfaces or on the interface with address available for the Bacula Windows client.

If the Bacula Storage Daemon listens on the localhost, then you need to remove from the Bacula Storage Daemon Storage resource settings this directive

SdAddress = 127.0.0.1

and after restart the Bacula Storage Daemon. It should start listening on all network interfaces.

Best regards,
Marcin Haba (gani)

saksham

No sdAddress is displayed

gani

Hello @saksham,

OK. Thanks.

In this case I have two more questions:

1) Is the Bacula Storage Daemon available for Bacula Windows Client on port TCP 9103? I mean this connection:

Bacula File Daemon ==> [9103] Bacula Storage Daemon

2) Your Storage Daemon is named Bareos-test-sd. Does it mean that you use Bareos Storage Daemon or this is only the name?

Best regards,
Marcin Haba (gani)

gani

Hello @saksham

Also worth to check are the Storage connection parameters defined on the Director side. You can see them here:

[Main menu] => [Page: Director] => [Tab: Configure director] => [SubTab: Storage] => [Button: 'Edit' for given storage]

Are you sure that using these parameters the Windows File Daemon will be able to connect to the Storage Daemon? Specially there cannot be defined localhost for Storage Daemons available for connections outside the SD host.

Best regards,
Marcin Haba (gani)

saksham

Could you please advise which ports need to be open on Linux and Windows Server?

gani

Hello @saksham

On Windows with Bacula Client should be opened 9102.

On Linux with the Bacula Storage Daemon should be opened 9103

Best regards,
Marcin Haba (gani)

saksham

but sill i am getting not connecting error

gani

Hello @saksham,

Are you sure that:

the Director is able to connect to the Bacula Client on Windows host on port 9102?
the Bacula Client on Windows host is able to connect to Bacula Storage on 9103?
the Bacula Storage listens on interface with IP address available for Windows host?
the Director Storage resource configuration have valid Bacula Storage IP address defined?

Could you also show us result of the two following Bconsole commands:

status client=YOUR_CLIENT_NAME

status storage=YOUR_STORAGE_NAME

Thanks.

Best regards,
Marcin Haba (gani)