Maybe you have a run before/after directive that is causing it to run a
bconsole command?
__Martin
> On Mon, 5 Sep 2022 21:02:52 +0200, Justin Case said:
>
> It works for me, too, but I get this error.
>
> > On 5. Sep 2022, at 20:14, Martin Simmons wrote:
> >
> > A copy job works for me
I have that on 2 backup jobs that are copied, but not on the copy job itself.
doe copy jobs run the before/after of all the jobs being copied?
> On 6. Sep 2022, at 13:02, Martin Simmons wrote:
>
> Maybe you have a run before/after directive that is causing it to run a
> bconsole command?
>
>
Greetings,
so far I don’t yet have a nice solution for the problem described earlied (see
attached email).
Since verify jobs can only verify the latest job run with a specific name, and
since copy jobs have the same name as the original backup job, the only way to
verify both, the backup job
My experience with trying the steps planned in my previous email (as attached):
(2) verifies the backup job (1) as expected.
(4) does NOT verify the copy (3) on the pool and storage as provided for the
verify job, instead it verifies the backup job (1) by switching to the pool,
storage and
I’m S close. I can see there is a tape job waiting for an appendable
Volume. How do I tell which tape slot contains the media that needs to be
changed?
Jim
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
No, it doesn't run the before/after of all the jobs being copied for me (only
for the copy job itself).
It might help if you post the full copy job output rather than just the error
message to show the full sequence of events.
__Martin
> On Tue, 6 Sep 2022 15:02:50 +0200, Justin Case said:
