To avoid this problem, existing incremental backups older than a configurable age are consolidated into a new backup. This would usually lead to an unlimited chain of incremental backups that depend on each other. The Always Incremental Backup Scheme works as follows:Ĭlient Backups are always run as incremental backups. Other data can not be combined on the server-side (e.g. Limitation - Always Incremental Backup: Only suitable for file-based backups.Īlways Incremental backups are only suitable for file-based backups. The Always Incremental Backup Scheme does only incremental backups of clients, which reduces the amount of data transferred over the network to a minimum. The problem with this way of removing jobs is the fact that jobs are removed from the system on which existing jobs depend. The next figure shows the amount of data being backed up over the network from that client over time:ĭepending on the retention periods, old jobs are removed to save space for newer backups: When you look for data at the horizontal axis, you see what backup jobs are available for a restore at this given time.
#DUNNO DICE INCREMENTAL MAX LEVEL FULL#
Red are full backups, green are differential backups and blue are incremental Backups. The following figure shows the jobs available for restore over time. To better understand the advantages of the Always Incremental Backup scheme, we first analyze the way that the conventional Incremental - Differential - Full Backup Scheme works. Always Incremental Backups are available since Bareos Version >= 16.2.4.
0 kommentar(er)
