ZFS Bacula not backing up remote FreeBSD Client

Hello Everyone, I have two Installs of FreeBSD, the first one is a server and the other one is a client. When I use the server to backup itself it works fine. But when I want to backup the client to the server, the job status is just stuck at R (Running [I checked this using *list jobs]). I thought that maybe the server and the client couldn't communicate properly so I ran *estimate just to check, and it returned

Code:
Connecting to Client MyBaculaRemote at 192.168.1.144:9102

2000 OK estimate files=9 bytes=12,156,246
I added two more files and it showed
Code:
Connecting to Client MyBaculaRemote at 192.168.1.144:9102

2000 OK estimate files=11 bytes=12,281,611
So it can see the files but not back them up.

Any ideas on what is the problem?

This is my bacula-fd.conf FreeBSD Client (the one I want to backup)
Code:
#
# Default  Bacula File Daemon Configuration file
#
#  For Bacula release 7.4.2 (06 June 2016) -- freebsd 11.0-RC2
#
# There is not much to change here except perhaps the
# File daemon Name to
#
#
# Copyright (C) 2000-2015 Kern Sibbald
# License: BSD 2-Clause; see file LICENSE-FOSS
#

#
# List Directors who are permitted to contact this File daemon
#
Director {
  Name = MyBaculaDirector
  Password = "the bacula-fd password"
}

#
# Restricted Director, used by tray-monitor to get the
#   status of the file daemon
#
#Director {
#  Name = 110amd64-default-job-13-mon
#  Password = "G7SRq2vB8Qo8A4tT9zWUv/5ulg+AqbJywap8SwPiZzZD"
#  Monitor = yes
#}

#
# "Global" File daemon configuration specifications
#
FileDaemon {                          # this is me
  Name = MyBaculaRemote
  FDport = 9102                  # where we listen for the director
  WorkingDirectory = /var/db/bacula
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 100
# Plugin Directory = /usr/local/lib
}

# Send all messages except skipped files back to Director
Messages {
  Name = Standard
  director = MyBaculaDirector = all, !skipped, !restored
}

And my bacula-dir.conf FreeBSD Server (the one I want to backup to)

Code:
Client {
  Name           = MyBaculaRemote
  Address        = 192.168.1.144
  FDPort = 9102
  Catalog        = MyCatalog
  Password = "the bacula-fd password"
}

Job {
  Name     = "BACKUPRemoteInc"
  Client   = MyBaculaRemote
  Type     = "Backup"
  FileSet  = "BACKUPRemoteIncFS"
  Storage  = MyFirstStorage
  Messages = MyMessages

  Pool        = IncrFile # required parameter for all Jobs, despite what appears in the next few lines
  Full         Backup Pool = FullFile
  Differential Backup Pool = DiffFile
  Incremental  Backup Pool = IncrFile
}

FileSet {
  Name    = "BACKUPRemoteIncFS"
  Include {
    Options {
      signature=MD5
    }

    File = /root/vincentseefiles/garda
  }

  Exclude {
    File = *~
  }
}

Even after 20 minutes have passed the job status is still stuck at R.
I searched for guides on the internet about bacula remote backups but it still didn't work.
Can someone shed some light in this? :)
 
I waited for 30 minutes and finally there was an error.
Code:
10-Sep 13:34 MyBaculaRemote JobId 58: Warning: bsock.c:107 Could not connect to Storage daemon on localhost:9103. ERR=Connection refused

Retrying ...

10-Sep 13:39 MyBaculaRemote JobId 58: Warning: bsock.c:107 Could not connect to Storage daemon on localhost:9103. ERR=Connection refused

Retrying ...

10-Sep 13:44 MyBaculaRemote JobId 58: Warning: bsock.c:107 Could not connect to Storage daemon on localhost:9103. ERR=Connection refused

Retrying ...

10-Sep 13:49 MyBaculaRemote JobId 58: Warning: bsock.c:107 Could not connect to Storage daemon on localhost:9103. ERR=Connection refused

Retrying ...

10-Sep 13:55 MyBaculaRemote JobId 58: Warning: bsock.c:107 Could not connect to Storage daemon on localhost:9103. ERR=Connection refused

Retrying ...

10-Sep 14:00 MyBaculaRemote JobId 58: Warning: bsock.c:107 Could not connect to Storage daemon on localhost:9103. ERR=Connection refused

Retrying ...

10-Sep 14:04 MyBaculaRemote JobId 58: Fatal error: bsock.c:113 Unable to connect to Storage daemon on localhost:9103. ERR=Connection refused

10-Sep 14:04 MyBaculaRemote JobId 58: Fatal error: job.c:1886 Failed to connect to Storage daemon: localhost:9103

10-Sep 14:03 MyBaculaDirector JobId 58: Fatal error: Bad response to Storage command: wanted 2000 OK storage

, got 2902 Bad storage


10-Sep 14:03 MyBaculaDirector JobId 58: Error: Bacula MyBaculaDirector 7.4.2 (06Jun16):

  Build OS:               amd64-portbld-freebsd11.0 freebsd 11.0-RC2

  JobId:                  58

  Job:                    BACKUPRemoteInc.2016-09-10_13.33.33_03

  Backup Level:           Full (upgraded from Incremental)

  Client:                 "MyBaculaRemote" 7.4.2 (06Jun16) amd64-portbld-freebsd11.0,freebsd,11.0-RC2

  FileSet:                "BACKUPRemoteIncFS" 2016-09-09 17:27:16

  Pool:                   "FullFile" (From Job FullPool override)

  Catalog:                "MyCatalog" (From Client resource)

  Storage:                "MyFirstStorage" (From Pool resource)

  Scheduled time:         10-Sep-2016 13:33:32

  Start time:             10-Sep-2016 13:33:35

  End time:               10-Sep-2016 14:03:45

  Elapsed time:           30 mins 10 secs

  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

  Snapshot/VSS:           no

  Encryption:             no

  Accurate:               no

  Volume name(s):        

  Volume Session Id:      1

  Volume Session Time:    1473485578

  Last Volume Bytes:      35,224,746,543 (35.22 GB)

  Non-fatal FD errors:    2

  SD Errors:              0

  FD termination status:  Error

  SD termination status:  Waiting on FD

  Termination:            *** Backup Error ***

When I backup the server itself it says Backup OK. I can't figure out what to modify in the bacula-fd.conf client and bacula-dir.conf server configuration. The ipaddress of my client is 192.168.1.144 and the server is 192.168.1.145. When the server backup's itself that indicates it is working, shouldn't backing up the remote FreeBSD client work by just changing the bacula-fd.conf and bacula-dir.conf file?
 
Back
Top