Welcome to the NetCologne GmbH open source mirroring service!

This machine mirrors various open-source projects and has 4 Gbit/s uplink.

If there are any issues or you want another project mirrored, please contact mirror-service -=AT=- netcologne DOT de !

Bareos Workshop MPG 2017 -
Bareos Logo
MPG Workshop

Bareos Overview

Bareos architecture

Bareos Architecture

Bareos architecture

Problems with conventional backup scheme

  1. Full data is copied over the network in regular intervals
  2. Identical Data is copied from client multiple times
  3. Job history loss caused by retention expiry
### always incremental backup scheme * Basic concept * Only changes are copied from the clients - always incremental * Existing data from the client is consolidated with the new incremental information (keep history) * The consolidation happens without client interaction * Minimized number of incrementals is kept to have a defined change history
### Two main tasks: 1. Incremental backup job is run every night during the backup window 2. Consolidation job consolidates during the day
### How to configure always incremental #### Backup Job Job { Name = BackupClient1 ... Accurate = yes Always Incremental = yes Always Incremental Job Retention = 7 days } #### Consolidation Job Job { Name = "Consolidate" Type = Consolidate }
### The Backup Job * runs an incremental backup during the backup window * *Always Incremental* directives configure behaviour * *accurate* Backup to notice file deletion
### The Consolidation Job * Loops over all Backup Jobs * Starts virtual backups according to Always Incremental settings
####Job availability with always incremental backup scheme ![conventional backup scheme job history loss](images/always-incremental.png)
#### Always Incremental Jobdata ![conventional backup scheme job history loss](images/always-incremental-jobdata.png)
### Always Incremental Jobdata - Problem * good: mininal data from the client * bad: Every day the consolidation runs the whole client data is moved during consolidation * impossible for a large number of clients
### Always Incremental Jobdata - Solution * only consolidate latest incremental during consolidation * leave the full backup as it is during daily consolidations * consolidate the full in longer intervals Job { Always Incremental Max Full Age = 21 days }
#### Always Incremental Max Full Age with multiple clients ![conventional backup scheme job history loss](images/jobdata_multiple_clients.png)
#### Always Incremental Max Full Age with multiple clients and Max Full Consolidations ![conventional backup scheme job history loss](images/jobdata_multiple_clients_maxfullconsilidate.png)
### Always Incremental configuration overview * Storage with minimum 2 devices * Backup Job with always incremental enabled * Better: define JobDefs as template * Consolidate Job * Optional: Virtual Full to keep longterm full backups separately
![Daily Jobs](images/ai_days.png)
### Always Incremental summary * Only incremental Backups are done from the client * Minimal network load * Minimal backup time * In backup window
### Always Incremental summary * Consolidation is done locally on storage * Outside of backup window * Very fast as local * Existing backups are consolidated into new backups * No holes in the backup history * Defined incremental backup history is always available * Adequate for File Backup, NOT for plugin Backups