Hi Martin,
Thanks a lot for your response.
> Is the log really "nothing"? It should at least show the last thing that
> happened.
Honestly nothing, the last 3 lines on bacula.log was on 12-Feb 15:58 and that
was before I started the pending backup job
> Also, try "status dir" to see what the Director is doing.
Hmm, this see to help. I believe this is the job number 7 that has a fatal
error as status. Wish it was more elaborate than that. Have you seen that
error before?
Daemon started 12-Feb-19 16:02. Jobs: run=0, running=5 mode=0,0
Heap: heap=270,336 smbytes=173,258 max_bytes=174,054 bufs=447 max_bufs=454
Scheduled Jobs:
Level Type Pri Scheduled Name Volume
===================================================================================
Incremental Backup 10 15-Feb-19 11:58 BackupClient1 000128L6
Full Backup 10 15-Feb-19 15:08 BackupClient2 000128L6
Full Backup 11 15-Feb-19 15:10 BackupCatalog 000128L6
====
Running Jobs:
Console connected at 12-Feb-19 16:02
Console connected at 14-Feb-19 16:09
JobId Level Name Status
======================================================================
7 Full BackupClient2.2019-02-12_16.08.21_03 has a fatal error
8 Full BackupClient1.2019-02-13_11.58.00_07 is waiting execution
9 Full BackupCatalog.2019-02-13_15.10.00_08 is waiting execution
10 Full BackupClient1.2019-02-14_11.58.00_14 is waiting execution
11 Full BackupCatalog.2019-02-14_15.10.00_15 is waiting execution
====
Regards,
William
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
