Re: [Bacula-users] Copy jobs marked as failed after original job went temporariliy out of space

[Eric B. <er...@ba...>]

Hello Andrea,

Maybe you can share the job output where the errors and warnings are printed, it 
will help to understand the situation.

Thanks,

Best Regards,
Eric

On 4/9/25 12:38, Andrea Venturoli wrote:
> Hello.
> 
> I'm seeing a behaviour I'm not sure is correct; at least I cannot find any 
> motivation for it.
> 
> Suppose:
> _ you are making a backup to disk;
> _ backup job starts (writing to volume Full0001);
> _ target storage goes out of disk space;
> _ you get the usual "Intervention needed" mail and make some space;
> _ the job resumes automatically (now writing to volume Full0002);
> _ in the end the job gets an "OK -- with warnings" status;
> _ I verified that such a job can be restore correctly, but the restore job also 
> is marked as Restore OK -- with warnings;
> _ now you want to "copy" this job somewhere else: the job selects Full0001 and 
> Full0002 volumes;
> _ as far as I can tell it copies both to a single volume on the new storage;
> _ however, in the end it's marked as "Error";
> _ restoring this jobs works too (and doesn't even give a warning).
> 
> Is there any hidden reason I cannot get, for the copy job to marked as "error"?
> If the original "restore" works, albeit with a warning (and I'm not even sure 
> that warning should be there), why should "copy" fail?
> 
> Or was it just luck that the restore job worked and I should expect it to fail 
> in some cases?
> 
>   bye & Thanks
>      av.
> 
> 
> _______________________________________________
> Bacula-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users