For one of the servers my main Bacula installation is backing up, a mail server running Cyrus IMAPD, I have this job definition:
Job {
Name = "posthamster"
Client = posthamster-fd
JobDefs = "DefaultJob"
Schedule = "WeeklyCycleLate"
RunScript {
RunsOnClient = yes
RunsWhen = Before
FailJobOnError = yes
Command = "/root/bin/prebackup"
}
RunScript {
RunsOnClient = yes
RunsWhen = After
RunsOnSuccess = yes
RunsOnFailure = yes
Command = "/root/bin/postbackup"
}
FileSet = "posthamster"
Priority = 15 # run separately
}
The prebackup script stops the IMAP service for consistent backup,
and the postbackup script starts it again, so I really, REALLY want
the postbackup scrupt to run even if something went wrong with the
backup. After all, there's no sense in blocking my users' mail
access just because the last backup didn't complete successfully.
More importantly, this is the very same mail server that handles
the mails produced by Bacula, so blocking it in case of a backup
problem is quite counterproductive.
However, last night's backup run completed thusly:
23-Feb 02:35 backup-dir JobId 6498: Start Backup JobId 6498,
Job=posthamster.2013-02-22_23.05.01_42
23-Feb 02:35 backup-dir JobId 6498: Using Device "LTO-3" to write.
23-Feb 02:36 posthamster-fd JobId 6498: shell command: run
ClientBeforeJob "/root/bin/prebackup"
23-Feb 02:36 posthamster-fd JobId 6498: ClientBeforeJob: cyrus-imapd
beenden: [ OK ]
23-Feb 02:37 posthamster-fd JobId 6498: ClientBeforeJob: Exporting
cyrus-imapd databases: [ OK ]
23-Feb 02:37 posthamster-fd JobId 6498: ClientBeforeJob: Backing up
Horde... Done. (0)
23-Feb 02:37 posthamster-fd JobId 6498: ClientBeforeJob: Backing up
mysql... Done. (0)
23-Feb 02:37 posthamster-fd JobId 6498: ClientBeforeJob: Backing up
webmail... Done. (0)
23-Feb 02:37 bacula-sd JobId 6498: Spooling data ...
23-Feb 03:45 bacula-sd JobId 6498: Fatal error: append.c:188
FI=-1431655766 from FD not positive or sequential=359701
23-Feb 03:45 backup-dir JobId 6498: Fatal error: Network error with FD
during Backup: ERR=Keine Daten verfügbar
23-Feb 03:45 backup-dir JobId 6498: Error: Director's comm line to SD
dropped.
23-Feb 03:45 backup-dir JobId 6498: Fatal error: No Job status returned
from FD.
23-Feb 03:45 backup-dir JobId 6498: Error: Bacula backup-dir 5.2.13
(19Jan13):
Build OS: x86_64-redhat-linux-gnu redhat Enterprise release
JobId: 6498
Job: posthamster.2013-02-22_23.05.01_42
Backup Level: Full
Client: "posthamster-fd" 5.2.13 (19Jan13)
x86_64-redhat-linux-gnu,redhat,Enterprise release
FileSet: "posthamster" 2012-01-20 22:05:00
Pool: "Weekly" (From Run pool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "LTO-3" (From Job resource)
Scheduled time: 22-Feb-2013 23:05:01
Start time: 23-Feb-2013 02:37:33
End time: 23-Feb-2013 03:45:01
Elapsed time: 1 hour 7 mins 28 secs
Priority: 15
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: 37
Volume Session Time: 1361435261
Last Volume Bytes: 503,044,190,208 (503.0 GB)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Error
Termination: *** Backup Error ***
And, sure enough, the IMAP service was subsequently down, preventing
me from receiving that report. Exactly what I wanted to avoid.
Did I do something wrong or is that a bug?
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
