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 prob
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 invisib
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 rec
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
signature.asc
Descrip
I have come across a problem with this script in that it has deleted some
volumes that have an associated job. To test this out I ran the query and list
media commands on a volume that the script reports as obsolete. From this I can
see that 'query 14' reports the volume has no associated job. H
On 4/13/23 02:51, Chris Wilkinson wrote:
This is the final mods to Bill's script. It scans the catalog for volumes without a job, deletes them from the catalog and
disk. There were a lot of orphaned volumes and this recovered ~1TB from my storage.
In my setup, all volumes are in one directory a
This is the final mods to Bill's script. It scans the catalog for volumes
without a job, deletes them from the catalog and disk. There were a lot of
orphaned volumes and this recovered ~1TB from my storage.
In my setup, all volumes are in one directory and therefore have unique
names e.g. poolname
On 4/12/23 11:01, Bill Arlofski via Bacula-users wrote:
Oops... I have a rogue `\` in those last two echo commands:
for vol in $(echo -e "list media pool=\n\quit\n" | "${bcbin}" -c "${bccfg}"
\
and
for vol in $(echo -e "list media\n\quit\n" | "${bcbin}" -c "${bccfg}" \
There should n
On 4/12/23 10:44, Chris Wilkinson wrote:
Thanks Bill.
I looked into using the query command but the standard queries prompts the user
to specify the volume name one by one. I
haven't yet been able to find a way to script this command by reading volume
names from storage so that the output can
Thanks Bill.
I looked into using the query command but the standard queries prompts the
user to specify the volume name one by one. I haven't yet been able to find
a way to script this command by reading volume names from storage so that
the output can be fed to the delete and rm commands.
My SQL
On 4/11/23 16:35, Chris Wilkinson wrote:
I have some disk volumes that are not associated with any job but have not yet
reached their expiry time so they are not
being pruned. These were created by a job run that was deleted. It seems
deleting a job run doesn't purge the associated volumes.
I
I have some disk volumes that are not associated with any job but have not
yet reached their expiry time so they are not being pruned. These were
created by a job run that was deleted. It seems deleting a job run doesn't
purge the associated volumes.
I would like to delete these now obsolete volum
12 matches
Mail list logo
