I am trying to understand more how Bareos works internally. One question is how does it handle if you get a hole in your backup history?
Say we have a very large backup 100TB, with only modest changes, but doing a new full out of cycle might be time/load/media capacity prohibitive. Now lets say we have a chain of 20 incrementals, 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. 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). So questions, 1. Verify that is correct understanding 2. Does adding accurate = yes capture those files getting them in the next backup? 3. Does DiskToCatalog Verify job detect that there are missing files in the catalog? Or is the only fix to run a new full backup? Brock Palen [email protected] www.mlds-networks.com Websites, Linux, Hosting, Joomla, Consulting -- 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/BF3B88FA-902E-46AC-A837-A6E15A0558A0%40mlds-networks.com.
