Hello,
>> looks like the missing job has now been imported as 84814
(and the rest from another volume) also +1 in the jobid.
there's something fishy with those job ids... in your previous mail, updating
the job entries with the reported job Ids failed, and new ones were aparently
generated. This inconsitency is surely worth a bug report IMO.
I think because of the older recovery of the catalog all jobs where
lost.
I tried to add the job with the bsr file so a job was created as 84813.
Because I though update could be a problem i deleted the job with
*delete jobid=84813
Then I retried adding the job in the catalog by using bscan without the
bsr file, means by scanning the whole volume.
...
Unable to get Job Volume Parameters. ERR=sql_get.c:429 No volumes found for
JobId=84814
The above is also suspicious considering that job media records were reported
to be created. Probably referencing the wrong job id.
I though here because of deleting the 84813 job this id has to been
burned so it created simply the job by using the next id.
Unable to construct a valid BSR. Cannot continue.
...
What do you think, should I open a bug report/feature
request so jobs could also imported by bscan -b job.bsr
option?
By all means, yes. But you should first update to a recent version of Bacula.
Iirc, you run something rather old, and the developers are not going to spend a
lot of time with that, I suspect.
I'm also quite sure that some fixes in bscan were implemented in between, I
just don't recall the details.
I redirect copies of the messages in log files for the full volume scans.
But it looks like the problem can be reproduced.
My plan is to update to debian 13 first. This should update bacula to version
15, hopefully is new enough.
Have a nice weekend
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
