Hello
This morning, I wanted to clear some running jobs so that I can do a quick
restore. After cancelling all the jobs on one of my storage system, one of
the jobs hang and it I have tried every trick to clear it without success.
Running Jobs:
Writing: Incremental Backup job teamcity01-data-job-e JobId=39337 Volume=""
pool="windows_regular" device="ULTRIUM-HH6" (/dev/nst0)
spooling=0 despooling=1 despool_wait=0
Files=9,592,122 Bytes=4,851,978,768,263 AveBytes/sec=13,040,359
LastBytes/sec=73,734
FDReadSeqNo=153,264,736 in_msg=126339092 out_msg=6 fd=13
====
I noticed when I cancelled the tapes went into initialing mode and then
dismounted. I didn't trigger dismounting, so this is also odd and sharing in
case you notice there is no assigned tape in the above job.
>From the director's perspective, this job shouldn't exist.
39337 Incr 9,591,242 4.849 T Cancel 10-Jan-22 11:54
teamcity01-data-job-e
So why would the director and storage be so disconnected about a job status and
how can one do to avoid it in future.
Regards,
William
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
