Bacula is an open software enterprise backup system! Check out the official site here
Complex but useful software, which could automate the whole backup process of all your servers.
Some errors are easy to track some are not, so here is one error with a misleading error message if you do not know or forget the details of how the daemons works.
Here is the error extracted from the logs:
01-Sep 00:45 backup01-de-dir JobId 8789: No prior Full backup Job record found. 01-Sep 00:45 backup01-de-dir JobId 8789: No prior or suitable Full backup found in catalog. Doing FULL backup. 01-Sep 00:45 backup01-de-dir JobId 8789: Job srv123us.2017-09-01_00.45.28_34 waiting 103 seconds for scheduled start time. 01-Sep 00:47 backup01-de-dir JobId 8789: Start Backup JobId 8789, Job=srv123us.2017-09-01_00.45.28_34 01-Sep 00:47 backup01-de-dir JobId 8789: Using Device "web" to write. 01-Sep 00:51 srv123us-fd JobId 8789: Warning: bsock.c:112 Could not connect to Storage daemon on 1.1.1.1:9103. ERR=Connection timed out 01-Sep 01:17 srv123us-fd JobId 8789: Fatal error: bsock.c:118 Unable to connect to Storage daemon on 1.1.1.1:9103. ERR=Interrupted system call 01-Sep 01:17 srv123us-fd JobId 8789: Fatal error: job.c:1893 Failed to connect to Storage daemon: 1.1.1.1:9103 01-Sep 01:17 backup01-de-dir JobId 8789: Fatal error: Bad response to Storage command: wanted 2000 OK storage 01-Sep 01:17 backup01-de-dir JobId 8789: Error: Bacula backup01-de-dir 7.0.5 (28Jul14): Build OS: x86_64-pc-linux-gnu ubuntu 16.04 JobId: 8789 Job: srv123us.2017-09-01_00.45.28_34 Backup Level: Full (upgraded from Incremental) Client: "srv123us" 7.0.5 (28Jul14) x86_64-pc-linux-gnu,ubuntu,16.04 FileSet: "web" 2017-11-07 17:19:45 Pool: "web-full" (From Job FullPool override) Catalog: "ucdn" (From Client resource) Storage: "web" (From Job resource) Scheduled time: 01-Sep-2018 00:47:11 Start time: 01-Sep-2018 00:47:11 End time: 01-Sep-2018 01:17:23 Elapsed time: 30 mins 12 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 VSS: no Encryption: no Accurate: no Volume name(s): Volume Session Id: 4719 Volume Session Time: 1510075534 Last Volume Bytes: 0 (0 B) Non-fatal FD errors: 2 SD Errors: 0 FD termination status: Error SD termination status: Waiting on FD Termination: *** Backup Error ***
But when we check the status of client from “bconsole” (Bacula’s management Console), everything seems OK, the backup server (Director daemon = bacula-dir) connects and get the report from the client daemon (Bacula File service = bacula-fd) in the server, even when you run a backup job, the status report is OK, the backup is running on the client, here is the output:
srv@local ~ # bconsole Connecting to Director localhost:9101 1000 OK: 1 backup01-de-dir Version: 7.0.5 (28 July 2014) Enter a period to cancel a command. *status Status available for: 1: Director 2: Storage 3: Client 4: Scheduled 5: All Select daemon type for status (1-5): 3 The defined Client resources are: 1: srv1us 2: srv2us 3: srv123us Select Client (File daemon) resource (1-3): 3 Connecting to Client srv123us at 108.61.250.36:9102 srv123us-fd Version: 7.0.5 (28 July 2014) x86_64-pc-linux-gnu ubuntu 16.04 Daemon started 23-Feb-17 00:43. Jobs: run=1 running=0. Heap: heap=98,304 smbytes=571,344 max_bytes=571,361 bufs=97 max_bufs=97 Sizes: boffset_t=8 size_t=8 debug=0 trace=0 mode=0,0 bwlimit=0kB/s Plugin: bpipe-fd.so Running Jobs: JobId 8789 Job srv123us.2017-09-01_00.45.28_34 is running. Incremental Backup Job started: 01-Sep-17 00:45 Files=0 Bytes=0 AveBytes/sec=0 LastBytes/sec=0 Errors=0 Bwlimit=0 Files: Examined=5 Backed up=0 SDReadSeqNo=6 fd=5 Director connected at: 01-Sep-17 01:10 ==== Terminated Jobs: ====
As you can see, everything seems OK of the status, there was a running job in the client server and it seemed the backup process had been running without errors for more then 20 minutes, but then suddenly got Fatal error (the first log):
01-Sep 00:51 srv123us-fd JobId 8789: Warning: bsock.c:112 Could not connect to Storage daemon on 1.1.1.1:9103. ERR=Connection timed out 01-Sep 01:17 srv123us-fd JobId 8789: Fatal error: bsock.c:118 Unable to connect to Storage daemon on 1.1.1.1:9103. ERR=Interrupted system call 01-Sep 01:17 srv123us-fd JobId 8789: Fatal error: job.c:1893 Failed to connect to Storage daemon: 1.1.1.1:9103 01-Sep 01:17 backup01-de-dir JobId 8789: Fatal error: Bad response to Storage command: wanted 2000 OK storage
And the problem is that, the Director (backup server) connects to the File Service of the client (the daemon on the client), but the opposite connection is not possible! When the backup is ready, the client daemon bacula file service connects to the bacula storage service (which could be on the same server with the director, but it could be on another server) to send the backup files and here is the problem! Client could not connect to the storage! So always check the two way connections: backup server -> client server-port:9102 and backup server-port:9103 (or storage server) <- client.
In the world of bacula:
bacula-dir -> bacula-fd:9102
bacula-sd:9103 -> bacula-fd
Misleading error on causal look it seems like bacula-sd is returning error to bacula-fd (which would mean that bacula-fd could connect to bacula-sd after all), but in reality bacula-dir received and logged that bacula-fd did not connect to bacula-sd resulting in Fatal error.
In our situation the firewall of the backup server was denying the connections from the client, but it could be a DNS resolve issue or another network problem. Most common problems are firewall or DNS resolve issues. The solution – just add accept rule for the IP of the client to connect to port 9103 of the backup (storage) server.
Posted by gaizkamaldieta 2016-09-06T08:39:03Z
Hi,
Once again i’m facing the issue with bacula backup.Sorry because i’m new in bacula.
I receive this notification yesterday while perform a backup full of backup.Info as per below:
Server name:backup
Client name:backup
Bacula KL: Backup Error of backup-fd Full
06-Sep 02:12 backup-dir JobId 5508: shell command: run BeforeJob «/etc/bacula/scripts/make_catalog_backup.pl MyCatalog»
06-Sep 02:12 backup-dir JobId 5508: BeforeJob: Can’t find your catalog (MyCatalog) in director configuration
06-Sep 02:12 backup-dir JobId 5508: Error: Runscript: BeforeJob returned non-zero status=1. ERR=Child exited with code 1
06-Sep 02:12 backup-dir JobId 5508: Error: Bacula backup-dir 5.2.6 (21Feb12):
Build OS: i486-pc-linux-gnu debian 7.0
JobId: 5508
Job: BackupCatalogg.2016-09-06_02.10.00_21
Backup Level: Full
Client: «backup-fd» 5.2.6 (21Feb12) i486-pc-linux-gnu,debian,7.0
FileSet: «Catalog» 2014-04-15 19:09:55
Pool: «Backup» (From Job resource)
Catalog: «MyCatalog» (From Client resource)
Storage: «BackupStorage» (From Job resource)
Scheduled time: 06-Sep-2016 02:10:00
Start time: 06-Sep-2016 02:12:17
End time: 06-Sep-2016 02:12:17
Elapsed time: 0 secs
Priority: 11
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
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 0
Volume Session Time: 0
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 1
SD Errors: 0
FD termination status:
SD termination status:
Termination: *** Backup Error ***
I did some research it says because of permission issue.And I change it
from
-rwxr-xr-x 1 root root 4182 Apr 27 2013 make_catalog_backup.pl
to
-rwxr—r— 1 bacula bacula 4182 Apr 27 2013 make_catalog_backup.pl
Did I need to others thing to fix it?
Please advice.Thanks
check
Best Answer
I usually found when that sort of thing happened, it was time to dive in and clean up Bacula-dir.conf. It’s easy to leave old and unused pools, clients, and jobs in there, and for those to create conflicts. Personally, I liked moving client and job definitions to separate files to keep the director configuration shorter.
Was this post helpful?
thumb_up
thumb_down
View Best Answer in replies below
12 Replies
-
Is the destination device full?
Was this post helpful?
thumb_up
thumb_down
-
I don’t have that script on my Bacula server. What is this job trying to backup, the Bacula server configuration itself?
If you’re backing up the Bacula server, I had mine do a MySQL dump on a schedule (in crontab). Then a Bacula job backed up /etc/bacula and the MySQL file. If there was a problem or I was moving to a new server, I just imported the database, reinstalled Bacula, and overwrote config files.
Otherwise, the standard set of questions — is this a new job, has it ever worked, what’s it doing, etc.
Was this post helpful?
thumb_up
thumb_down
-
Mike400 wrote:
Is the destination device full?
Hi Mike,
Thanks for asking,
There’s 1TB available for the backup.
/dev/md0 1.8T 838G 904G 49% /backup
Was this post helpful?
thumb_up
thumb_down
-
Bryan Doe wrote:
I don’t have that script on my Bacula server. What is this job trying to backup, the Bacula server configuration itself?
If you’re backing up the Bacula server, I had mine do a MySQL dump on a schedule (in crontab). Then a Bacula job backed up /etc/bacula and the MySQL file. If there was a problem or I was moving to a new server, I just imported the database, reinstalled Bacula, and overwrote config files.
Otherwise, the standard set of questions — is this a new job, has it ever worked, what’s it doing, etc.
Hi Bryan,
1)Yes,this script is for bacula server itself,to backup the bacula itself.I also use the MySQL dump for backup(without crontab).
2)It is a old job that I run using crontab every month(full backup) and it works.
Refer as per below:
02-Sep 02:00 backup-dir JobId 5464: Start Backup JobId 5464, Job=BackupMachineBackup.2016-09-02_02.00.00_16
02-Sep 02:00 backup-dir JobId 5464: Using Device «LocalDisk-Backup»
02-Sep 02:00 backup-sd JobId 5464: Volume «backup-0001» previously written, moving to end of data.
02-Sep 02:00 backup-sd JobId 5464: Ready to append to end of Volume «backup-0001» size=4361845070
02-Sep 02:00 backup-fd JobId 5464: /dev is a different filesystem. Will not descend from / into it.
02-Sep 02:00 backup-fd JobId 5464: /sys is a different filesystem. Will not descend from / into it.
02-Sep 02:07 backup-fd JobId 5464: /var/lib/nfs/rpc_pipefs is a different filesystem. Will not descend from / into it.
02-Sep 02:07 backup-fd JobId 5464: /run is a different filesystem. Will not descend from / into it.
02-Sep 02:17 backup-sd JobId 5464: Job write elapsed time = 00:17:35, Transfer rate = 1.539 M Bytes/second
02-Sep 02:17 backup-dir JobId 5464: Bacula backup-dir 5.2.6 (21Feb12):
Build OS: i486-pc-linux-gnu debian 7.0
JobId: 5464
Job: BackupMachineBackup.2016-09-02_02.00.00_16
Backup Level: Full
Client: «backup-fd» 5.2.6 (21Feb12) i486-pc-linux-gnu,debian,7.0
FileSet: «BackupFileSet» 2014-04-15 23:28:40
Pool: «Backup» (From Job resource)
Catalog: «MyCatalog» (From Client resource)
Storage: «BackupStorage» (From Job resource)
Scheduled time: 02-Sep-2016 02:00:00
Start time: 02-Sep-2016 02:00:02
End time: 02-Sep-2016 02:17:57
Elapsed time: 17 mins 55 secs
Priority: 10
FD Files Written: 44,528
SD Files Written: 44,528
FD Bytes Written: 1,618,492,110 (1.618 GB)
SD Bytes Written: 1,624,101,147 (1.624 GB)
Rate: 1505.6 KB/s
Software Compression: 60.0 %
VSS: no
Encryption: no
Accurate: no
Volume name(s): backup-0001
Volume Session Id: 254
Volume Session Time: 1469610418
Last Volume Bytes: 5,988,930,011 (5.988 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK02-Sep 02:17 backup-dir JobId 5464: Begin pruning Jobs older than 2 months .
02-Sep 02:17 backup-dir JobId 5464: Pruned 2 Jobs for client backup-fd from catalog.
02-Sep 02:17 backup-dir JobId 5464: Begin pruning Files.
02-Sep 02:17 backup-dir JobId 5464: Pruned Files from 1 Jobs for client backup-fd from catalog.
02-Sep 02:17 backup-dir JobId 5464: End auto prune.
Was this post helpful?
thumb_up
thumb_down
-
Well, if it’s an old job, I’d doubt it’s a permissions issue unless something has been modified recently. It does look like it’s backing up the entire system, however — if this server is only running Bacula, I’d change it to backup like I said and not have Bacula waste time and space on the entire OS.
Was this post helpful?
thumb_up
thumb_down
-
Bryan Doe wrote:
Well, if it’s an old job, I’d doubt it’s a permissions issue unless something has been modified recently. It does look like it’s backing up the entire system, however — if this server is only running Bacula, I’d change it to backup like I said and not have Bacula waste time and space on the entire OS.
Hi Bryan,
Thanks for the reply,for your information nothing was modified recently.I’m also not sure it is a permission issue or not because that one is base from what i have research at google.This is what we use in our bacula environment,what should i check then?Please advice.Thanks.
Was this post helpful?
thumb_up
thumb_down
-
Text
06-Sep 02:12 backup-dir JobId 5508: shell command: run BeforeJob "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog" 06-Sep 02:12 backup-dir JobId 5508: BeforeJob: Can't find your catalog (MyCatalog) in director configuration 06-Sep 02:12 backup-dir JobId 5508: Error: Runscript: BeforeJob returned non-zero status=1. ERR=Child exited with code 1
Those lines leads me to believe that if there is a permissions issue it’s in reading the MyCatalog that /etc/bacula/scripts/make_catalog.pl is supposed to create.
What is the result of the following command (make sure to replace the correct path for your dbcheck and bacula-dir.conf files respectively please):
Text
su -m bacula -c '/usr/local/sbin/dbcheck -B -c /usr/local/etc/bacula-dir.conf'
Also you stated that you changed the permissions on the perl script from:
Text
-rwxr-xr-x 1 root root 4182 Apr 27 2013 make_catalog_backup.pl
to:
Text
-rwxr--r-- 1 bacula bacula 4182 Apr 27 2013 make_catalog_backup.pl
First, if this has been running successfully and was previously owned by root:root I wouldn’t recommend changing the owner and group like that; most times you’d want the script to be executable by others and/or group normally (chmod 755).
I’m hesitant to speculate further as I have no experience with Bacula — can you run the perl script by itself successfully without any errors once you changed the permission back to what was at one time a known good state (root:root 755)? e.g.:
Text
su -m bacula -c '/etc/bacula/scripts/make_catalog_backup.pl MyCatalog'
Was this post helpful?
thumb_up
thumb_down
-
CarbonChauvinist wrote:
Text
06-Sep 02:12 backup-dir JobId 5508: shell command: run BeforeJob "/etc/bacula/scripts/make_catalog_backup.pl MyCatalog" 06-Sep 02:12 backup-dir JobId 5508: BeforeJob: Can't find your catalog (MyCatalog) in director configuration 06-Sep 02:12 backup-dir JobId 5508: Error: Runscript: BeforeJob returned non-zero status=1. ERR=Child exited with code 1
Those lines leads me to believe that if there is a permissions issue it’s in reading the MyCatalog that /etc/bacula/scripts/make_catalog.pl is supposed to create.
What is the result of the following command (make sure to replace the correct path for your dbcheck and bacula-dir.conf files respectively please):
Text
su -m bacula -c '/usr/local/sbin/dbcheck -B -c /usr/local/etc/bacula-dir.conf'
Also you stated that you changed the permissions on the perl script from:
Text
-rwxr-xr-x 1 root root 4182 Apr 27 2013 make_catalog_backup.pl
to:
Text
-rwxr--r-- 1 bacula bacula 4182 Apr 27 2013 make_catalog_backup.pl
First, if this has been running successfully and was previously owned by root:root I wouldn’t recommend changing the owner and group like that; most times you’d want the script to be executable by others and/or group normally (chmod 755).
I’m hesitant to speculate further as I have no experience with Bacula — can you run the perl script by itself successfully without any errors once you changed the permission back to what was at one time a known good state (root:root 755)? e.g.:
Text
su -m bacula -c '/etc/bacula/scripts/make_catalog_backup.pl MyCatalog'
Hi,
CarbonChauvinist,
Thanks for the respond,
1) This is the result when i run
su -m bacula -c ‘/usr/local/sbin/dbcheck -B -c /usr/local/etc/bacula-dir.conf’.I’m not sure where to find dbcheck file.Text
root@backup:/etc/bacula# su -m bacula -c '/usr/local/sbin/dbcheck -B -c /usr/local/etc/bacula-dir.conf' bash: /usr/local/sbin/dbcheck: No such file or directory
2)And for the permissions I already change it back as usual.
3)When I run this command —
su -m bacula -c ‘/etc/bacula/scripts/make_catalog_backup.pl MyCatalog’Text
root@backup:/etc/bacula# su -m bacula -c '/etc/bacula/scripts/make_catalog_backup.pl MyCatalog' Can't find your catalog (MyCatalog) in director configuration
Was this post helpful?
thumb_up
thumb_down
-
Hi,
I think the backup issue was resolve now,when i run it manually,the incremental backup for my bacula server running as usual.But one big question is why my full backup is running also?
My Backup Schedule is
Daily — Incremental backup
Monthly — Full backup.Now the incremental backup is running without any issue.(Include my bacula server itself).But it also run the full backup every day.(for bacula server backup).
I check at bconsole,there is no waiting/queue job.How to stop it?I’m still not understand why it run full backup on daily basis.
Please advice.Many thanks.
Was this post helpful?
thumb_up
thumb_down
-
Hi,
Somehow my server seemed there was a job running that didn’t need to run.I restart the server and back to normal.Thanks.
9-Sep 02:00 backup-dir JobId 5528: No prior Full backup Job record found.
09-Sep 02:00 backup-dir JobId 5528: No prior or suitable Full backup found in catalog. Doing FULL backup.
09-Sep 02:00 backup-dir JobId 5528: Start Backup JobId 5528, Job=BackupMachineBackup.2016-09-09_02.00.00_02
09-Sep 02:00 backup-dir JobId 5528: Using Device «LocalDisk-Backup»
09-Sep 02:00 backup-sd JobId 5528: Volume «backup-0033» previously written, moving to end of data.
09-Sep 02:00 backup-sd JobId 5528: Warning: For Volume «backup-0033»:
The sizes do not match! Volume=1325399133 Catalog=999936149
Correcting Catalog
09-Sep 02:00 backup-fd JobId 5528: /dev is a different filesystem. Will not descend from / into it.
09-Sep 02:00 backup-fd JobId 5528: /sys is a different filesystem. Will not descend from / into it.
09-Sep 02:07 backup-fd JobId 5528: /var/lib/nfs/rpc_pipefs is a different filesystem. Will not descend from / into it.
09-Sep 02:07 backup-fd JobId 5528: /run is a different filesystem. Will not descend from / into it.
09-Sep 02:16 backup-sd JobId 5528: Job write elapsed time = 00:16:52, Transfer rate = 1.604 M Bytes/second
09-Sep 02:17 backup-dir JobId 5528: Bacula backup-dir 5.2.6 (21Feb12):
Build OS: i486-pc-linux-gnu debian 7.0
JobId: 5528
Job: BackupMachineBackup.2016-09-09_02.00.00_02
Backup Level: Full (upgraded from Differential)
Client: «backup-fd» 5.2.6 (21Feb12) i486-pc-linux-gnu,debian,7.0
FileSet: «BackupFileSet» 2014-04-15 23:28:40
Pool: «Backup» (From Job resource)
Catalog: «MyCatalog» (From Client resource)
Storage: «BackupStorage» (From Job resource)
Scheduled time: 09-Sep-2016 02:00:00
Start time: 09-Sep-2016 02:00:02
End time: 09-Sep-2016 02:17:24
Elapsed time: 17 mins 22 secs
Priority: 10
FD Files Written: 44,607
SD Files Written: 44,607
FD Bytes Written: 1,618,555,839 (1.618 GB)
SD Bytes Written: 1,624,173,978 (1.624 GB)
Rate: 1553.3 KB/s
Software Compression: 60.1 %
VSS: no
Encryption: no
Accurate: no
Volume name(s): backup-0033
Volume Session Id: 2
Volume Session Time: 1473325117
Last Volume Bytes: 2,952,560,313 (2.952 GB)
Non-fatal FD errors: 0
SD Errors: 0
FD termination status: OK
SD termination status: OK
Termination: Backup OK09-Sep 02:17 backup-dir JobId 5528: Begin pruning Jobs older than 2 months .
09-Sep 02:17 backup-dir JobId 5528: No Jobs found to prune.
09-Sep 02:17 backup-dir JobId 5528: Begin pruning Files.
09-Sep 02:17 backup-dir JobId 5528: No Files found to prune.
09-Sep 02:17 backup-dir JobId 5528: End auto prune.
Was this post helpful?
thumb_up
thumb_down
-
I usually found when that sort of thing happened, it was time to dive in and clean up Bacula-dir.conf. It’s easy to leave old and unused pools, clients, and jobs in there, and for those to create conflicts. Personally, I liked moving client and job definitions to separate files to keep the director configuration shorter.
Was this post helpful?
thumb_up
thumb_down
-
Bryan Doe wrote:
I usually found when that sort of thing happened, it was time to dive in and clean up Bacula-dir.conf. It’s easy to leave old and unused pools, clients, and jobs in there, and for those to create conflicts. Personally, I liked moving client and job definitions to separate files to keep the director configuration shorter.
Agree…have a nice weekend guys….
Was this post helpful?
thumb_up
thumb_down
Read these next…
IT managers — what non-technical job responsibilities do you struggle to manage?
Best Practices & General IT
As an IT manager, most of the job involves a number technical problems to solve and plan for, but there are numerous non-technical hurdles to jump over as well. And if you’re a brand new IT manager without a mentor or guidance, it can be hard to know how …
Best way to approach a poorly-maintained network
Windows
So this veterinary clinic is asking me to fix their computer network but they don’t know their network passwords. Users can log in but I cannot get my remote software working because they don’t know the administrator passwords to install it on them. It …
Snap! — Learning Hibernation, Sound Printing, Accidental Bomb, Waves on Mars
Spiceworks Originals
Your daily dose of tech news, in brief.
Welcome to the Snap!
Flashback: February 10, 1996: Deep Blue Defeats Kasparov (Read more HERE.)
Bonus Flashback: February 10, 2009: Satellites Collide! (Read more HERE.)
You need to hear this.
…
Spark! Pro series – 10th February 2023
Spiceworks Originals
Happy Friday!
Just a reminder, if you are reading the Spark!, Spice it
up. We like it spicy here!Today in History:
February 10, 1996 —
A Computer Defeats a World Chess ChampionWorld chess champio…
Looking for a simple app to keep notes I can access on any device.
Software
Do you keep notes that you access across multiple devices? Online on a computer or app on a mobile device? I’d like to jot things down if an idea pops into my head, when I learn something new, get a new process, discover a switch port I may need to bounce…
Scenario: Server backs itself up just fine. Tried adding a file daemon on another computer, my workstation, and the job for that fails with the error «2902 Bad storage». The log also gives a link to bacula documentation regarding passwords but I think my configuration is already following the rules set there.
server daemons
director
#
# Default Bacula Director Configuration file
#
# The only thing that MUST be changed is to add one or more
# file or directory names in the Include directive of the
# FileSet resource.
#
# For Bacula release 5.2.12 (12 September 2012) -- gentoo
#
# You might also want to change the default email address
# from root to your address. See the "mail" and "operator"
# directives in the Messages resource.
#
Director { # define myself
Name = castellan-dir
DIRport = 9101 # where we listen for UA connections
QueryFile = "/usr/libexec/bacula/query.sql"
WorkingDirectory = "/var/lib/bacula"
PidDirectory = "/var/run"
Maximum Concurrent Jobs = 1
Password = "GRek4WPD2RlNGkdzhW00zyA6Xg2FU/fFMVP2eQyWEzi6" # Console password
Messages = Daemon
}
JobDefs {
Name = "DefaultJob"
Type = Backup
Level = Incremental
Client = castellan-fd
# FileSet = "Full Set"
Schedule = "WeeklyCycle"
Storage = MainBackupArray
Messages = Standard
Pool = File
Priority = 10
Write Bootstrap = "/var/lib/bacula/%c.bsr"
RunScript {
RunsWhen = Before
FailJobOnError = No
RunsOnClient = No
Command = "/bin/mount /dev/md4"
}
RunScript {
RunsWhen = After
RunsOnSuccess = Yes
RunsOnFailure = Yes
RunsOnClient = No
Command = "/bin/umount /dev/md4"
}
}
#
# Define the main nightly save backup job
# By default, this job will back up to disk in /tmp
Job {
Name = "BackupCastellan"
JobDefs = "DefaultJob"
FileSet = "Full Set"
}
Job {
Name = "BackupLiege"
JobDefs = "DefaultJob"
Client = liege-fd
FileSet = "LiegeFullset"
}
#Job {
# Name = "BackupClient2"
# Client = castellan2-fd
# JobDefs = "DefaultJob"
#}
# Backup the catalog database (after the nightly save)
Job {
Name = "BackupCatalog"
JobDefs = "DefaultJob"
Level = Full
FileSet = "Catalog"
Schedule = "WeeklyCycleAfterBackup"
# This creates an ASCII copy of the catalog
# Arguments to make_catalog_backup.pl are:
# make_catalog_backup.pl <catalog-name>
RunBeforeJob = "/usr/libexec/bacula/make_catalog_backup.pl MyCatalog"
# This deletes the copy of the catalog
RunAfterJob = "/usr/libexec/bacula/delete_catalog_backup"
Write Bootstrap = "/var/lib/bacula/%n.bsr"
Priority = 11 # run after main backup
}
#
# Standard Restore template, to be changed by Console program
# Only one such job is needed for all Jobs/Clients/Storage ...
#
Job {
Name = "RestoreFiles"
Type = Restore
Client = castellan-fd
FileSet = "Full Set"
Storage = MainBackupArray
Pool = Default
Messages = Standard
Where = /tmp/bacula-restores
RunScript {
RunsWhen = Before
FailJobOnError = No
RunsOnClient = No
Command = "/bin/mount /dev/md4"
}
RunScript {
RunsWhen = After
RunsOnSuccess = Yes
RunsOnFailure = Yes
RunsOnClient = No
Command = "/bin/umount /dev/md4"
}
}
# List of files to be backed up
FileSet {
Name = "Full Set"
Include {
Options {
signature = MD5
compression=gzip
}
File = /
File = /boot
File = /var
}
Exclude {
File = /dev
File = /var/lib/bacula
File = /proc
File = /mnt
File = /media
File = /.journal
File = /.fsck
File = /var/lib/minecraft/wholebackups
File = /var/lib/minecraft/backups
File = /var/nas/live_torrents
}
}
FileSet {
Name = "LiegeFullset"
Include {
Options {
signature = MD5
compression=gzip
}
File = "C:/"
}
Exclude {
File = "C:/Temp"
}
}
#
# When to do the backups, full backup on first sunday of the month,
# differential (i.e. incremental since full) every other sunday,
# and incremental backups other days
Schedule {
Name = "WeeklyCycle"
Run = Full 1st sun at 2:05
Run = Differential 2nd-5th sun at 2:05
Run = Incremental mon-sat at 2:05
}
# This schedule does the catalog. It starts after the WeeklyCycle
Schedule {
Name = "WeeklyCycleAfterBackup"
Run = Full sun-sat at 4:00
}
# This is the backup of the catalog
FileSet {
Name = "Catalog"
Include {
Options {
signature = MD5
}
File = "/var/lib/bacula/bacula.sql"
}
}
# Client (File Services) to backup
Client {
Name = castellan-fd
Address = castellan
FDPort = 9102
Catalog = MyCatalog
Password = "PeVkZSMSO/rvermyd0shMYfTGg70P3gB2YBdkXcEwDdE" # password for FileDaemon
File Retention = 2 months # 30 days
Job Retention = 12 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
# Client (File Services) to backup
Client {
Name = liege-fd
Address = liege
FDPort = 9102
Catalog = MyCatalog
Password = "vZwrnQRZanw4q8BE3BEraGsc9UQnehYHNyvirP1fhURU" # password for FileDaemon
File Retention = 2 months # 30 days
Job Retention = 12 months # six months
AutoPrune = yes # Prune expired Jobs/Files
}
#
# Second Client (File Services) to backup
# You should change Name, Address, and Password before using
#
#Client {
# Name = castellan2-fd
# Address = castellan2
# FDPort = 9102
# Catalog = MyCatalog
# Password = "PeVkZSMSO/rvermyd0shMYfTGg70P3gB2YBdkXcEwDdE2" # password for FileDaemon 2
# File Retention = 30 days # 30 days
# Job Retention = 6 months # six months
# AutoPrune = yes # Prune expired Jobs/Files
#}
# Definition of file storage device
Storage {
Name = MainBackupArray
# Do not use "localhost" here
Address = 192.168.10.192 # N.B. Use a fully qualified name here
SDPort = 9103
Password = "3Yzd6Ohb5GMWfMZx8GJbQNf06BSV3WpMQK3Tl3tTsil2"
Device = MainBackupArray
Media Type = File
}
# Definition of DDS tape storage device
#Storage {
# Name = DDS-4
# Do not use "localhost" here
# Address = castellan # N.B. Use a fully qualified name here
# SDPort = 9103
# Password = "3Yzd6Ohb5GMWfMZx8GJbQNf06BSV3WpMQK3Tl3tTsil2" # password for Storage daemon
# Device = DDS-4 # must be same as Device in Storage daemon
# Media Type = DDS-4 # must be same as MediaType in Storage daemon
# Autochanger = yes # enable for autochanger device
#}
# Definition of 8mm tape storage device
#Storage {
# Name = "8mmDrive"
# Do not use "localhost" here
# Address = castellan # N.B. Use a fully qualified name here
# SDPort = 9103
# Password = "3Yzd6Ohb5GMWfMZx8GJbQNf06BSV3WpMQK3Tl3tTsil2"
# Device = "Exabyte 8mm"
# MediaType = "8mm"
#}
# Definition of DVD storage device
#Storage {
# Name = "DVD"
# Do not use "localhost" here
# Address = castellan # N.B. Use a fully qualified name here
# SDPort = 9103
# Password = "3Yzd6Ohb5GMWfMZx8GJbQNf06BSV3WpMQK3Tl3tTsil2"
# Device = "DVD Writer"
# MediaType = "DVD"
#}
# Generic catalog service
Catalog {
Name = MyCatalog
# Uncomment the following line if you want the dbi driver
# dbdriver = "dbi:mysql"; dbaddress = 127.0.0.1; dbport =
dbname = "bacula"; dbuser = "bacula"; dbpassword = "GMWfMZx8GJbQNf06BSV3WpMQK3Tl3tTsil2"
}
# Reasonable message delivery -- send most everything to email address
# and to the console
Messages {
Name = Standard
#
# NOTE! If you send to two email or more email addresses, you will need
# to replace the %r in the from field (-f part) with a single valid
# email address in both the mailcommand and the operatorcommand.
# What this does is, it sets the email address that emails would display
# in the FROM field, which is by default the same email as they're being
# sent to. However, if you send email to more than one address, then
# you'll have to set the FROM address manually, to a single address.
# for example, a 'no-reply@mydomain.com', is better since that tends to
# tell (most) people that its coming from an automated source.
#
mailcommand = "/usr/sbin/bsmtp -h localhost -f "(Bacula) <bacula@aehdev.com>" -s "Bacula: %t %e of %c %l" %r"
operatorcommand = "/usr/sbin/bsmtp -h localhost -f "(Bacula) <bacula@aehdev.com>" -s "Bacula: Intervention needed for %j" %r"
mail = aeheathc@gmail.com = all, !skipped
operator = aeheathc@gmail.com = mount
console = all, !skipped, !saved
#
# WARNING! the following will create a file that you must cycle from
# time to time as it will grow indefinitely. However, it will
# also keep all your messages if they scroll off the console.
#
append = "/var/log/bacula/working/bacula.log" = all, !skipped
catalog = all
}
#
# Message delivery for daemon messages (no job).
Messages {
Name = Daemon
mailcommand = "/usr/sbin/bsmtp -h localhost -f "(Bacula) <%r>" -s "Bacula daemon message" %r"
mail = aeheathc@gmail.com = all, !skipped
console = all, !skipped, !saved
append = "/var/log/bacula/working/bacula.log" = all, !skipped
}
# Default pool definition
Pool {
Name = Default
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 2 days # one year
}
# File Pool definition
Pool {
Name = File
Pool Type = Backup
Recycle = yes # Bacula can automatically recycle Volumes
AutoPrune = yes # Prune expired volumes
Volume Retention = 2 days # one year
Maximum Volume Bytes = 100G # Limit Volume size to something reasonable
Maximum Volumes = 1000 # Limit number of Volumes in Pool
LabelFormat = "Vol"
}
# Scratch pool definition
Pool {
Name = Scratch
Pool Type = Backup
}
#
# Restricted console used by tray-monitor to get the status of the director
#
Console {
Name = castellan-mon
Password = "4BcHoJRAOkZJlMf8wm6s11ZoAfwYYpefAnMstlzfUj7h"
CommandACL = status, .status
}
file
#
# Default Bacula File Daemon Configuration file
#
# For Bacula release 5.2.13 (19 February 2013) -- gentoo
#
# There is not much to change here except perhaps the
# File daemon Name to
#
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = castellan-dir
Password = "PeVkZSMSO/rvermyd0shMYfTGg70P3gB2YBdkXcEwDdE"
}
#
# Restricted Director, used by tray-monitor to get the
# status of the file daemon
#
Director {
Name = castellan-mon
Password = "QEN/69pxCIYQ9GOvJK+XL1VGLl8ovRxfSMOe1Kt2Q/Fp"
Monitor = yes
}
#
# "Global" File daemon configuration specifications
#
FileDaemon { # this is me
Name = castellan-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = /var/lib/bacula
Pid Directory = /var/run
Maximum Concurrent Jobs = 20
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = castellan-dir = all, !skipped, !restored
}
storage
#
# Default Bacula Storage Daemon Configuration file
#
# For Bacula release 5.2.12 (12 September 2012) -- gentoo
#
# You may need to change the name of your tape drive
# on the "Archive Device" directive in the Device
# resource. If you change the Name and/or the
# "Media Type" in the Device resource, please ensure
# that dird.conf has corresponding changes.
#
Storage { # definition of myself
Name = castellan-sd
SDPort = 9103 # Director's port
WorkingDirectory = "/var/lib/bacula"
Pid Directory = "/var/run"
Maximum Concurrent Jobs = 20
}
#
# List Directors who are permitted to contact Storage daemon
#
Director {
Name = castellan-dir
Password = "3Yzd6Ohb5GMWfMZx8GJbQNf06BSV3WpMQK3Tl3tTsil2"
}
#
# Restricted Director, used by tray-monitor to get the
# status of the storage daemon
#
Director {
Name = castellan-mon
Password = "uA1iI8Vxirh+JZc7zPTengOQt978CG3F6V3MNI/I2Sbi"
Monitor = yes
}
#
# Note, for a list of additional Device templates please
# see the directory <bacula-source>/examples/devices
# Or follow the following link:
# http://bacula.svn.sourceforge.net/viewvc/bacula/trunk/bacula/examples/devices/
#
#
# Devices supported by this Storage daemon
# To connect, the Director's bacula-dir.conf must have the
# same Name and MediaType.
#
Device {
Name = MainBackupArray
Media Type = File
Archive Device = /mnt/backup/main
LabelMedia = yes; # lets Bacula label unlabeled media
Random Access = Yes;
AutomaticMount = yes; # when device opened, read it
Requires Mount = no;
RemovableMedia = no;
AlwaysOpen = no;
#Mount Command = "/bin/mount /dev/md4";
#Unmount Command = "/bin/umount /dev/md4";
Mount Point = "/mnt/backup"
Write Part Command = ""
}
#
# An autochanger device with two drives
#
#Autochanger {
# Name = Autochanger
# Device = Drive-1
# Device = Drive-2
# Changer Command = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
# Changer Device = /dev/sg0
#}
#Device {
# Name = Drive-1 #
# Drive Index = 0
# Media Type = DLT-8000
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# AutoChanger = yes
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI controller
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
# Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = "sh -c 'smartctl -H -l error %c'"
#}
#Device {
# Name = Drive-2 #
# Drive Index = 1
# Media Type = DLT-8000
# Archive Device = /dev/nst1
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
# Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = "sh -c 'smartctl -H -l error %c'"
#}
#
# A Linux or Solaris LTO-2 tape drive
#
#Device {
# Name = LTO-2
# Media Type = LTO-2
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# Maximum File Size = 3GB
## Changer Command = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
## Changer Device = /dev/sg0
## AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
## Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
## If you have smartctl, enable this, it has more info than tapeinfo
## Alert Command = "sh -c 'smartctl -H -l error %c'"
#}
#
# A Linux or Solaris LTO-3 tape drive
#
#Device {
# Name = LTO-3
# Media Type = LTO-3
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# Maximum File Size = 4GB
## Changer Command = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
## Changer Device = /dev/sg0
## AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
## Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
## If you have smartctl, enable this, it has more info than tapeinfo
## Alert Command = "sh -c 'smartctl -H -l error %c'"
#}
#
# A Linux or Solaris LTO-4 tape drive
#
#Device {
# Name = LTO-4
# Media Type = LTO-4
# Archive Device = /dev/nst0
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes;
# RemovableMedia = yes;
# RandomAccess = no;
# Maximum File Size = 5GB
## Changer Command = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
## Changer Device = /dev/sg0
## AutoChanger = yes
# # Enable the Alert command only if you have the mtx package loaded
## Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
## If you have smartctl, enable this, it has more info than tapeinfo
## Alert Command = "sh -c 'smartctl -H -l error %c'"
#}
#
# A FreeBSD tape drive
#
#Device {
# Name = DDS-4
# Description = "DDS-4 for FreeBSD"
# Media Type = DDS-4
# Archive Device = /dev/nsa1
# AutomaticMount = yes; # when device opened, read it
# AlwaysOpen = yes
# Offline On Unmount = no
# Hardware End of Medium = no
# BSF at EOM = yes
# Backward Space Record = no
# Fast Forward Space File = no
# TWO EOF = yes
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = "sh -c 'smartctl -H -l error %c'"
#}
#
# Send all messages to the Director,
# mount messages also are sent to the email address
#
Messages {
Name = Standard
director = castellan-dir = all
}
Workstation
file
#
# Default Bacula File Daemon Configuration file
#
# For Bacula release 7.0.5 (08/05/14) -- Windows MinGW64
#
# There is not much to change here except perhaps the
# File daemon Name
#
#
# "Global" File daemon configuration specifications
#
FileDaemon { # this is me
Name = liege-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = "C:\Program Files\Bacula\working"
Pid Directory = "C:\Program Files\Bacula\working"
Plugin Directory = "C:\Program Files\Bacula\plugins"
Maximum Concurrent Jobs = 10
}
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = castellan-dir
Password = "vZwrnQRZanw4q8BE3BEraGsc9UQnehYHNyvirP1fhURU" # Director must know this password
}
#
# Restricted Director, used by tray-monitor to get the
# status of the file daemon
#
Director {
Name = liege-mon
Password = ""
Monitor = yes
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = castellan-dir = all, !skipped, !restored
}
Job result
28-Mar 02:05 castellan-dir JobId 1518: No prior Full backup Job record found.
28-Mar 02:05 castellan-dir JobId 1518: No prior or suitable Full backup found in catalog. Doing FULL backup.
28-Mar 02:07 castellan-dir JobId 1518: shell command: run BeforeJob "/bin/mount /dev/md4"
28-Mar 02:07 castellan-dir JobId 1518: Start Backup JobId 1518, Job=BackupLiege.2015-03-28_02.05.00_19
28-Mar 02:07 castellan-dir JobId 1518: Using Device "MainBackupArray" to write.
28-Mar 01:48 liege-fd JobId 1518: Fatal error: Authorization key rejected by Storage daemon.
Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000 for help.
28-Mar 02:07 castellan-dir JobId 1518: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
28-Mar 02:07 castellan-dir JobId 1518: Error: Bacula castellan-dir 5.2.13 (19Jan13):
Build OS: x86_64-pc-linux-gnu gentoo
JobId: 1518
Job: BackupLiege.2015-03-28_02.05.00_19
Backup Level: Full (upgraded from Incremental)
Client: "liege-fd" 7.0.5 (04Aug14) Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit,Cross-compile,Win64
FileSet: "LiegeFullset" 2015-03-18 02:05:00
Pool: "File" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "MainBackupArray" (From Job resource)
Scheduled time: 28-Mar-2015 02:05:00
Start time: 28-Mar-2015 02:07:29
End time: 28-Mar-2015 02:07:41
Elapsed time: 12 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
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 127
Volume Session Time: 1422045928
Last Volume Bytes: 86,414,167,951 (86.41 GB)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
28-Mar 02:07 castellan-dir JobId 1518: shell command: run AfterJob "/bin/umount /dev/md4"
Hi all =20 Can anyone help me with the following error; I=92m trying to do a full = backup. On the client the job status is =93OK=94. It can=92t be at network error = because I have tried a bunch of times with the same error. =20 Cheers=20 =20 Ren=E9 =20 asterix-dir: Start Backup JobId 10891, Job=3Dhill-birch01-weekly.2004-12-06_22.56.47 asterix-dir: Volume used once. Marking Volume "hill-birch01_full0001" as Used. asterix-dir: Purging oldest volume "hill-birch01_full0001" asterix-dir: 1 File on Volume "hill-birch01_full0001" purged from = catalog. asterix-sd: Recycled volume "hill-birch01_full0001" on device /backup/bacula/hill-birch01, all previous data lost. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: = Network error with FD during Backup: ERR=3DConnection timed out asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: No Job status returned from FD. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Error: Bacula 1.32d (02Nov03): 07-Dec-2004 01:08 JobId: 10891 Job: hill-birch01-weekly.2004-12-06_22.56.47 Backup Level: Full Client: hill-birch01 FileSet: "hill-birch01_fileset" 2004-12-06 14:42:29 Start time: 06-Dec-2004 22:56 End time: 07-Dec-2004 01:08 FD Files Written: 0 SD Files Written: 10,627 FD Bytes Written: 0 SD Bytes Written: 338,183,094 Rate: 0.0 KB/s Software Compression: None Volume name(s): hill-birch01_full0001 Volume Session Id: 11 Volume Session Time: 1102338495 Last Volume Bytes: 338,926,620 Non-fatal FD errors: 0 SD Errors: 0 FD termination status: Error SD termination status: OK Termination: *** Backup Error *** =20 asterix-dir: Job hill-birch01-weekly.2004-12-06_22.56.47 waiting 60 = seconds for scheduled start time. asterix-dir: Start Backup JobId 10891, Job=3Dhill-birch01-weekly.2004-12-06_22.56.47 asterix-dir: Volume used once. Marking Volume "hill-birch01_full0001" as Used. asterix-dir: Purging oldest volume "hill-birch01_full0001" asterix-dir: 1 File on Volume "hill-birch01_full0001" purged from = catalog. asterix-sd: Recycled volume "hill-birch01_full0001" on device /backup/bacula/hill-birch01, all previous data lost. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: = Network error with FD during Backup: ERR=3DConnection timed out asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: No Job status returned from FD. asterix-dir: sql_update.c:148 UPDATE Job SET JobStatus=3D'f', EndTime=3D'2004-12-07 01:08:09', ClientId=3D2, JobBytes=3D0, = JobFiles=3D0, JobErrors=3D0, VolSessionId=3D18, VolSessionTime=3D1102338495, = PoolId=3D10, FileSetId=3D12, JobTDate=3D1102378089 WHERE JobId=3D10891 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Warning: Error = updating job record. sql_update.c:148 Update problem: affected_rows=3D0 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Warning: Error = getting job record for stats: sql_get.c:281 No Job found for JobId 10891 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Error: Bacula 1.32d (02Nov03): 07-Dec-2004 01:08 JobId: 10891 Job: hill-birch01-weekly.2004-12-06_22.56.47 Backup Level: Full Client: hill-birch01 FileSet: "hill-birch01_fileset" 2004-12-06 14:42:29 Start time: 07-Dec-2004 01:09 End time: 07-Dec-2004 01:08 FD Files Written: 0 SD Files Written: 10,627 FD Bytes Written: 0 SD Bytes Written: 338,183,094 Rate: 0.0 KB/s Software Compression: None Volume name(s): hill-birch01_full0001 Volume Session Id: 18 Volume Session Time: 1102338495 Last Volume Bytes: 338,926,620 Non-fatal FD errors: 1 SD Errors: 0 FD termination status: Error SD termination status: OK Termination: *** Backup Error *** =20 asterix-dir: Job hill-birch01-weekly.2004-12-06_22.56.47 waiting 60 = seconds for scheduled start time. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: Job canceled because max start delay time exceeded. asterix-dir: sql_update.c:148 UPDATE Job SET JobStatus=3D'f', EndTime=3D'2004-12-07 01:08:09', ClientId=3D2, JobBytes=3D0, = JobFiles=3D0, JobErrors=3D0, VolSessionId=3D18, VolSessionTime=3D1102338495, = PoolId=3D10, FileSetId=3D12, JobTDate=3D1102378089 WHERE JobId=3D10891 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Warning: Error = updating job record. sql_update.c:148 Update problem: affected_rows=3D0 asterix-dir: Job hill-birch01-weekly.2004-12-06_22.56.47 waiting 60 = seconds for scheduled start time. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: Job canceled because max start delay time exceeded. asterix-dir: sql_update.c:148 UPDATE Job SET JobStatus=3D'f', EndTime=3D'2004-12-07 01:08:09', ClientId=3D2, JobBytes=3D0, = JobFiles=3D0, JobErrors=3D0, VolSessionId=3D18, VolSessionTime=3D1102338495, = PoolId=3D10, FileSetId=3D12, JobTDate=3D1102378089 WHERE JobId=3D10891 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Warning: Error = updating job record. sql_update.c:148 Update problem: affected_rows=3D0 asterix-dir: Job hill-birch01-weekly.2004-12-06_22.56.47 waiting 60 = seconds for scheduled start time. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: Job canceled because max start delay time exceeded. asterix-dir: sql_update.c:148 UPDATE Job SET JobStatus=3D'f', EndTime=3D'2004-12-07 01:08:09', ClientId=3D2, JobBytes=3D0, = JobFiles=3D0, JobErrors=3D0, VolSessionId=3D18, VolSessionTime=3D1102338495, = PoolId=3D10, FileSetId=3D12, JobTDate=3D1102378089 WHERE JobId=3D10891 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Warning: Error = updating job record. sql_update.c:148 Update problem: affected_rows=3D0 asterix-dir: Job hill-birch01-weekly.2004-12-06_22.56.47 waiting 60 = seconds for scheduled start time. asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Fatal error: Job canceled because max start delay time exceeded. asterix-dir: sql_update.c:148 UPDATE Job SET JobStatus=3D'f', EndTime=3D'2004-12-07 01:08:09', ClientId=3D2, JobBytes=3D0, = JobFiles=3D0, JobErrors=3D0, VolSessionId=3D18, VolSessionTime=3D1102338495, = PoolId=3D10, FileSetId=3D12, JobTDate=3D1102378089 WHERE JobId=3D10891 asterix-dir: hill-birch01-weekly.2004-12-06_22.56.47 Warning: Error = updating job record. sql_update.c:148 Update problem: affected_rows=3D0 =20 =20 =20 ____________________________________=20 Ren=E9 Brask S=F8rensen=20 Outsourcit=20 Sandbjerggade 56=20 DK-2200 K=F8benhavn N=20 Phone: +45 7022 2106 Mobile: +45 3031 9126 (direct)=20 E-mail: rb...@ou...=20 http://www.outsourcit.dk <http://www.outsourcit.dk/> =20 =20 =20
-
#1
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?
-
Thread Starter
-
#2
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?