Yes that is true. I was concerned that a deleted volume of a job with no
files would cause subsequent backups to fail. That doesn't seem to be the
case. It is only incr/diffs that would get deleted since fulls are never
empty.
-Chris-
On Fri, 14 Apr 2023, 17:57 Martin Simmons, wrote:
> The problem is that the catalog doesn't record which jobs are on each
> volume.
> It uses the jobmedia table to record which files of a job are on each
> volume
> (in groups between firstindex and lastindex). As a result, if a job has no
> files then it has no rows in the jobmedia table and hence is invisible to
> 'query 14'.
>
> Why are you worried about deleting these empty volumes? There should be no
> problem because they will never be used in a restore.
>
> __Martin
>
>
> > On Thu, 13 Apr 2023 23:17:50 +0100, Chris Wilkinson said:
> >
> > Yes that is true. In the other cases I found, these were also zero file
> > incr/diff jobs.
> >
> > However it appears that the job wrote a Volume as it appears in the list
> > media result and there is such a Volume on disk but only 667 bytes so
> only
> > the label I presume.
> >
> > I had expected that 'query 14' would recognise that a Volume has an
> > associated job even if that job wrote zero files to the volume but it
> > doesn't.
> >
> > The script needs some additional condition for deletion to avoid deleting
> > these zero file volumes. No idea what that might be right now.
> >
> > Chris-
> >
> > On Thu, 13 Apr 2023, 22:55 Bill Arlofski, wrote:
> >
> > > Hello Chris,
> > >
> > > Your jobid 2,371 wrote 0 files, 0 bytes, and the job's Summary shows
> for
> > > `Volume name(s):` No volumes.
> > >
> > > So, unless there are other jobs on this volume, jobid 2,371 did not
> > > actually write to it.
> > >
> > >
> > > Hope this helps,
> > > Bill
> > >
> > > --
> > > Bill Arlofski
> > > w...@protonmail.com
> > >
> > > -Chris-
> >
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
