I was testing some recent builds and I nocited 26-Sep 08:15 myth-sd JobId 66683: Doing timed backup checkpoint. Next checkpoint in 60 seconds 26-Sep 08:15 myth-sd JobId 66683: Checkpoint: Syncing current backup status to catalog 26-Sep 08:15 myth-sd JobId 66683: Checkpoint completed
I looked at the changelog and PR this looks great! One of the biggest issues using Bareos over slow connections was doing larger backups. There are several questions, 1. will it let failed backups (max time limit window ) resume where it left off? If so is that only for Incremental what about Fulls? 2. Spooling, the log states checkpoints to catalog before any messages about spooling. How does it make sure that data in the catalog is committed to the volume and not lost in a spool eg. SD dies, or using large spools nothing is ever written to the volume before the backup fails? There doesn’t appear to be anything in the draft documentation about how checkpoints interact with spools, or not having a completed “Full” backup. Thanks! This is great work! 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 on the web visit https://groups.google.com/d/msgid/bareos-users/01643EFE-992E-45E5-82BC-1C0FF03BC99A%40mlds-networks.com.
