Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
Release 16.2 and Roadmap 2017
Bareos 16.2 and Roadmap 2017
Agenda1. What's new in Bareos 16.22. In depth: Always Incremental Backup Scheme3. What's on the roadmap for 2017?
What's new in Bareos 16.21. Always Incremental Backup Scheme2. Client initiated connection (see dedicated presentation)3. Enhanced ACLs: multitenancy4. Performance Enhancements5. News about the Web UI6. NDMP Enhancements7. New subdirectory configuration scheme8. Configuration API: First steps9. Plugins: Incremental backup und pointintime recovery forMySQL
In depth: AlwaysIncremental Backup
Scheme
Conventional backupscheme
1. daily incremental backups kept for one week2. weekly differential backups kept for three weeks3. monthly full backups kept for half year
Job availability for conventional backup scheme
Job history loss for conventional backup scheme
Data being moved in conventional backup scheme
Problems with conventionalbackup scheme
1. Full data is copied over the network in regular intervals2. Identical Data is copied from client multiple times3. Job history loss caused by retention expiry
always incremental backup schemeBasic conceptOnly changes are copied from the clients alwaysincrementalExisting data from the client is consolidated with the newincremental information (keep history)The consolidation happens without client interactionMinimized number of incrementals is kept to have adefined change history
Two main tasks:1. Incremental backup job is run every night during the backupwindow
2. Consolidation job consolidates during the day
How to configure always incrementalBackup Job
Job { Name = BackupClient1 ... Accurate = yes Always Incremental = yes Always Incremental Job Retention = 7 days }
Consolidation Job Job { Name = "Consolidate" Type = Consolidate }
The Backup Jobruns an incremental backup during the backup windowAlways Incremental directives configure behaviouraccurate Backup to notice file deletion
The Consolidation JobLoops over all Backup JobsStarts virtual backups according to Always Incrementalsettings
Job availability with always incremental backup scheme
Job availability compared
Always Incremental Jobdata
Always Incremental Jobdata Problem
good: mininal data from the clientbad: Every day the consolidation runs the whole client data ismoved during consolidationimpossible for a large number of clients
Always Incremental Jobdata Solution
only consolidate latest incremental during consolidationleave the full backup as it is during daily consolidationsconsolidate the full in longer intervals
Job { Always Incremental Max Full Age = 21 days }
Always Incremental Max Full Age = 21 days
Always Incremental Max Full Age = 21 days
Always Incremental Max Full Age with multiple clients
Always Incremental Max Full Age with multiple clients andMax Full Consolidations
Always Incremental configurationoverviewBackup Job
Job { Always Incremental = yes # enabled? Always Incremental Job Retention = 7 days # how long is the job history? Always Incremental Keep Number = 7 # guaranteed number of incs left? Always Incremental Max Full Age = 21 days # if full is older it will be # part of the consolidation }
Consolidation JobJob { Name = "Consolidate" Type = Consolidate Max Full Consolidations = 1 # how many consolidation jobs # with full included can be started }
Always Incremental summaryOnly incremental Backups are done from the clientMinimal network loadMinimal backup timeIn backup window
Always Incremental summaryConsolidation is done locally on storageOutside of backup windowVery fast as localExisting backups are consolidated into new backupsNo holes in the backup history
Defined incremental backup history is always availableAdequate for File Backup, NOT for plugin Backups
Subdirectory configuration schemeBeforeone configuration file per daemon:
Configuration file contains all configuration resourcesIncluding additional configuration files complicated
/etc/bareos/bareos-dir.conf /etc/bareos/bareos-sd.conf /etc/bareos/bareos-fd.conf
@/file/to/config/file @|"/etc/bareos/generate_configuration_to_stdout.sh"
Subdirectory configuration schemeNewone configuration directory per daemon:
one configuration file per resource in resource typedirectory:
Including additional configuration files is easy,
/etc/bareos/bareos-dir.d /etc/bareos/bareos-sd.d /etc/bareos/bareos-fd.d
/etc/bareos/bareos-dir.d/pool/Differential.conf /etc/bareos/bareos-dir.d/pool/Incremental.conf /etc/bareos/bareos-dir.d/pool/Full.conf /etc/bareos/bareos-dir.d/director/bareos-dir.conf /etc/bareos/bareos-dir.d/console/bareos-mon.conf /etc/bareos/bareos-dir.d/storage/File.conf /etc/bareos/bareos-dir.d/job/BackupClient1.conf
/etc/bareos/bareos-dir.d/*/*.conf is automatically loaded
Subdirectory configuration schemecompatibility:if /etc/bareos/bareosdir.conf exists, it is usedotherwise config subdirectories are used.
Configuration APIUses new configuration directory layoutCreate client via director API or bconsole
Enhanced ACL supportFixed inherited ACL limitations in the directorAffects bconsole, Web UI and director APIFull multitenancy supportDefinitions of rules and rolesUsers can only access and see data according to role accessPrerequisite for web UI as selfserviceportal for restore
News from the web UIMultilanguage supportGermanEnglishFrenchRussian
Client overview shows available FD updatesMedia HandlingAutochanger support
Autochanger View
Restore in Russian Language
NDMP EnhancementsDiskToDiskToTape SupportLMDB Backend for NDMP FileHierarchy Data (to be able tohandle very large number of files)
New MySQL / MariaDBPlugin
Uses xtrabackup from PerconaIncremental backups for INNODB tablesHotbackupPointInTime Recovery
RoadmapNDMP: Backup to storage attached tape drivesPerformance Enhancements for large environmentsRHEV / oVirt PluginDeduplicationEnhance configuration APIWebuiUse configuration APIJob availability GraphsPerformance Graphs included
Thank you
Philipp Storz + Maik Außendorf, Bareos GmbH & Co. KG Open Source Backup Conference 2016