If you resume a job that is not Incomplete, it is quite possible that
Bacula then does a restart of an existing job and thus the parameters
could be different. In addition depending on the overrides you may use
and the manner in which you defined them (e.g. schedule, job resource,
command
ula-users@lists.sourceforge.net>
> Sent: Friday, February 26, 2016 7:56:39 PM
> Subject: Re: [Bacula-users] Bacula Resume Job Always Incremental
> Hello Wanderlei,
> I think you can't resume a canceled job, but you can resume a stopped one
> (stop
> command).
> I will test
bald.com>
> Cc: "Heitor Faria" <hei...@bacula.com.br>, "Bacula Users List"
> <bacula-users@lists.sourceforge.net>
> Sent: Friday, February 26, 2016 7:36:47 PM
> Subject: Re: [Bacula-users] Bacula Resume Job Always Incremental
> Hello Kern
>
For resume to work, the original Job must be marked Incomplete. If it
is not, it will be restarted from the beginning.
On 02/27/2016 08:05 AM, Heitor Faria wrote:
> Hello, Folks,
>
> Does anyone tested new resume command for canceled jobs?
> When used it only queue a new incremental job and
Hello Heitor
I noticed the same!
And Pool and Storage are wrong too!
Atenciosamente
*Nome **|* *Wanderlei Hüttel*
*Blog* | http://www.huttel.com.br
2016-02-26 19:05 GMT-03:00 Heitor Faria :
> Hello, Folks,
>
> Does anyone tested new resume command for canceled jobs?
Hello, Folks,
Does anyone tested new resume command for canceled jobs?
When used it only queue a new incremental job and seems to ignore the original
Job.
Command:
resume jobid=6 level=full
Original canceled Job:
| 6 | BkpArquivosBacula | 2016-02-26 16:57:04 | B | F | 3,091 |