The joblog i was interested in was for job 41536, i.e. the job with the
'broken' volume. Sorry for the confusion!
As far as I am aware, yes, the previous incrementals should not get
consolidated into the old full. They should stay as they are.
Kind Regards
Sebastian Sura
Am 19.06.24 um 15:51 schrieb 'Philippe' via bareos-users:
Hi,
there's no joblog of 40548 anymore, or did I look at the wrong places
(no conmsg, no mails)?
'bls' shows no errors, it lists mostly nextcloud files and one file of
a different job.
I just restored some files from AI-Incremental-0525 and it looks fine
so far.
Now I'm creating a new full as you suggested using
run job=my-nextcloud-job level=Full
Does Bareos ignore the previous backups after that or will it try to
consolidate them regardless of the existence of a new full?
Kind regards,
Philippe
On 6/19/24 10:14, Sebastian Sura wrote:
Could you post the joblog of that job ? If you cannot find 40548 in
the database, then its probably because it got consolidated into a
different job (maybe even into 41536).
bscan currently needs access to both the storage configuration as
well as the database. Alternatively you can also use bls instead
which just needs access to the sd configuration.
In regards to updating the database: I would suggest that if you do
that, that you make sure that you do not consolidate that job at
first and instead do a normal restore with the updated entry and
check that that 1) the restore works and 2) the files that were
restored make sense to you, i.e. compare them with the entries of the
job table for that job.
Its hard to say why this happened so i cannot comment on how safe it
is to keep using that incremental for consolidations. If possible try
creating a new full instead.
Kind Regards
Sebastian Sura
Am 19.06.24 um 09:54 schrieb 'Philippe' via bareos-users:
Hi Sebastian,
that's a good approach :)
The only jobmedia entry for job 41536 is:
$ psql <<<'select * from jobmedia where jobid=41536'
jobmediaid | jobid | mediaid | firstindex | lastindex | startfile
| endfile | startblock | endblock | jobbytes | volindex
------------+-------+---------+------------+-----------+-----------+---------+------------+----------+----------+----------
123840 | 41536 | 525 | 1 | 50 | 0 |
0 | 256 | 16770527 | 0 | 2
Is it safe to "just" update the startblock value to 255?
Job 40548 is somehow gone as I can't find it in the database.
Probably it was no longer needed, i.e. from a decommissioned client
or the jobs on that client changed.
How do I get bscan to work, what's the right way and what's needed
to invoke it?
I presume it needs both the database connection and the sd configs,
right? Asking because the director (which also hosts the database)
has no sd configs and on the other hand the sd has no database access.
Thank you & kind regards,
Philippe
On 6/19/24 08:29, Sebastian Sura wrote:
[snipped]
--
Sebastian Sura [email protected]
Bareos GmbH & Co. KG Phone: +49 221 630693-0
https://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/4b1b03e4-958a-4d20-9f92-7c2b75dc14ca%40bareos.com.
