Am 13.05.26 um 19:22 schrieb 'Brock Palen' via bareos-users:
Now lets say disaster strikes. Drive eats the tape with incrementals 5, 7, and
10.
You purge that volume because the data is now not recoverable and you have
holes in your backup history.
I'd rather delete these volumes, because the physical tapes are gone.
Nevertheless, pruning the associated jobs (both "prune volume" and
"delete volume" imply that) is the right thing to do.
On the next backup it looks like by default Bareos will NOT detect there are
files on the client not in the catalog if they were last updated before the
most recent backup (Incremental 20).
If you have accurate disabled that is true. I very much hope you have
accurate mode enabled so these files will be picked up.
If you don't have accurate enabled yet, you can just enable it on an
existing set of jobs and it will just start to work.
So questions,
1. Verify that is correct understanding
Sounds right, yes.
2. Does adding accurate = yes capture those files getting them in the next
backup?
It will (besides other things) make the agent backup all files that are
not in the catalog yet, no matter how old these are.
3. Does DiskToCatalog Verify job detect that there are missing files in the
catalog?
I think this should be detected, but I never tried it myself.
Best Regards,
Andreas
--
Andreas Rogge [email protected]
Bareos GmbH & Co. KG Phone: +49 221-630693-86
http://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 visit
https://groups.google.com/d/msgid/bareos-users/dd6903f4-2b3d-4246-87e4-98d9e9e475b0%40bareos.com.
