Hello,
I just wondered if anyone else has seen this problem. I wanted to disconnect
the removable disk of a running job so that I could reconnect it to a faster
USB port. I thought I'd try the "stop" bconsole command to stop and restart
the job in question. However, my Bacula director always seems to cancel
running jobs instead, stating that the job hasn't started and so cannot be
stopped. Of course, the cancelled job cannot be resumed (and is not marked as
'Incomplete'). Here is an example from bconsole:
<quote>
*stop
Select Job(s):
1: JobId=6033 Job=Job1.2021-12-19_19.18.46_54
2: JobId=6036 Job=Job2.2021-12-19_20.08.42_03
Choose Job list to stop (1-2): 2
JobId=6036 Job=Job2.2021-12-19_20.08.42_03
Confirm stop of 1 Job (yes/no): yes
1000 Trying to cancel Job Job2.2021-12-19_20.08.42_03 since it was not started
yet hence no need for stopping it.
Events: code=FC0003 daemon=filedaemon-fd ref=0x7f2bf4080328 type=command
source=backupserver-dir text=Cancel jobid=6036 job=Job2.2021-12-19_20.08.42_03
2001 Job "Job2.2021-12-19_20.08.42_03" marked to be canceled.
3000 JobId=6036 Job="Job2.2021-12-19_20.08.42_03" marked to be canceled.
JobId 6036, Job Job2.2021-12-19_20.08.42_03 marked to be canceled.
*version
backupserver-dir Version: 11.0.5 (03 June 2021) x86_64-pc-linux-gnu redhat
</quote>
Is there something I should be doing to enable use of the 'stop' command for
marking jobs and incomplete and allowing for resuming them? The above was a
test, but my original backup had been running four hours and had saved 500GB of
data (and in my eyes was 'running'). I haven't found a section in the manual
stating what the 'stop' command requires in order to operate--it reads a though
this shouldn't happen.
Many thanks for any ideas.
--
Graham
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
