Hello, czw., 5 mar 2020 o 17:38 William Muriithi <[email protected]> napisał(a):
> Hello, > > I have a single fairly job that failed due to network issue but it had > already put slightly above a TB into the tape. It was a full job > unfortunately, and have set it to do a full job twice a month and > differential/incremental in between. When I restarted the job, I see its > doing another full backup. > > So I got curious, is bacula able to continue from where the job was prior > to the previous job dying? Yes, absolutely. If you have an incomplete job, you can restart it from the point where issue occurred. > I am suspecting no, since data would then be owned by two jobs. No, when you are doing an incomplete job restart then it is the same job, not two. > So what does happen? There seem to be two options; > > - Leave the data in the tape but clean it on the catalog > - Leave it on both the catalog and the tape? > > Bacula always leaves backup data saved on tape until tape volume recycle. Regarding catalog it generally depends on the configuration. When you save backup metadata directly in catalog then failed job leaves it in catalog until prune process. When you save backup metadata to spool file during backup then failed job simply discard it without saving into catalog. > Would be glad if someone have this knowledge and would be willing to share > it > I hope it helps. -- Radosław Korzeniewski [email protected]
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
