From: Eric Bollengier Date: Thu, 30 Jul 2009 17:14:36 +0000 (+0000) Subject: ebl update new features X-Git-Tag: Release-3.0.3~2^2~79 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=ac97127765553ed9522f6ca51985f573aecbdf5c;p=bacula%2Fdocs ebl update new features --- diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex index b210f215..86bde6fd 100644 --- a/docs/manuals/en/concepts/newfeatures.tex +++ b/docs/manuals/en/concepts/newfeatures.tex @@ -2,11 +2,62 @@ %% -\chapter{New Features in 3.0.2} +\chapter{New Features in 3.0.3} \label{NewFeaturesChapter} +This chapter presents the new features added to the development 3.0.3 +versions to be released as Bacula version 3.0.3 sometime in 2009. + +\section{Restore from multiple Storage Daemon} +\index[general]{Restore} + +\section{File deduplication using Base jobs} + +A base job is sort of like a Full save except that you will want the FileSet to +contain only files that are unlikely to change in the future (i.e. a snapshot +of most of your system after installing it). After the base job has been run, +when you are doing a Full save, you specify one or more Base jobs to be used. +All files that have been backed up in the Base job/jobs but not modified will +then be excluded from the backup. During a restore, the Base jobs will be +automatically pulled in where necessary. + +This is something none of the competition does, as far as we know (except +perhaps BackupPC, which is a Perl program that saves to disk only). It is big +win for the user, it makes Bacula stand out as offering a unique optimization +that immediately saves time and money. Basically, imagine that you have 100 +nearly identical Windows or Linux machine containing the OS and user files. +Now for the OS part, a Base job will be backed up once, and rather than making +100 copies of the OS, there will be only one. If one or more of the systems +have some files updated, no problem, they will be automatically restored. + +A new Job directive \texttt{Base=Jobx, Joby...} permits to specify the list of +files that will be used during Full backup as base. + +\begin{verbatim} +Job { + Name = BackupLinux + Level= Base + ... +} + +Job { + Name = BackupZog4 + Base = BackupZog4, BackupLinux + Accurate = yes + ... +} +\end{verbatim} + +In this example, the job \texttt{BackupZog4} will use the most recent version of all +files contained in \texttt{BackupZog4} and \texttt{BackupLinux} jobs. Base jobs should +have run with \texttt{level=Base} to be used. + +This project was funded by Bacula Systems. + +\chapter{New Features in 3.0.2} + This chapter presents the new features added to the development 3.0.2 -versions to be released as Bacula version 3.0.2 sometime in 2009. +versions to be released as Bacula version 3.0.2 in july 2009. \section{Full restore from a given JobId} \index[general]{Restore menu}