some cleanup and mention VirtualFull

manuals/en/main/autochangers.tex

@@ -50,8 +50,8 @@ \chapter{Autochanger Support}
 For more details, refer to the \ilink{Testing Autochanger}{AutochangerTesting} chapter.
 
 Bareos also supports autochangers with barcode
-readers. This support includes two Console commands: \bcommand{label barcodes}
-and \bcommand{update slots}. For more details on these commands, see the chapter about \ilink{Barcode Support}{Barcodes}.
+readers. This support includes two Console commands: \bcommand{label}{barcodes}
+and \bcommand{update}{slots}. For more details on these commands, see the chapter about \ilink{Barcode Support}{Barcodes}.
 
 Current Bareos autochanger support does not include cleaning, stackers, or
 silos. Stackers and silos are not supported because Bareos expects to

manuals/en/main/backward-compability.tex

@@ -17,7 +17,7 @@ \section{Tape Formats}
 must be able to recognize old formats.  All the problems except the
 last are ones that we cannot solve, but by careful planning you can.
 
-Since the very beginning of Bacula (January 2000) until today (2014),
+Since the very beginning of Bacula (January 2000) until today (2015),
 there have been three major Bacula/Bareos tape formats.  The second format
 was introduced in Bacula version 1.27 in November of 2002.
 Bareos has been required to adapt the tape format to avoid potential trademark issues,

manuals/en/main/bareos-sd-resource-device-definitions.tex

@@ -457,7 +457,7 @@
 without an explicit operator command.  It does so by using an internal
 algorithm as defined on the \linkResourceDirective{Dir}{Pool}{Label Format} record in each
 Pool resource.  If this is {\bf No} as by default, Bareos will label
-tapes only by specific operator command (\bcommand{label} in the Console) or
+tapes only by specific operator command (\bcommand{label}{} in the Console) or
 when the tape has been recycled.  The automatic labeling feature is most
 useful when writing to disk rather than tape volumes.
 }

manuals/en/main/bareos.sty

@@ -109,7 +109,8 @@
 %
 % specific types of text
 %
-\newcommand{\bcommand}[1]{\path|#1|}
+% bcommand{command}{parameter}
+\newcommand{\bcommand}[2]{\path|#1| \path|#2|}
 \newcommand{\bnfvar}[1]{\lt#1\gt}
 \newcommand{\commandPrompt}{root{\at}linux:\~{}\# }
 \newcommand{\command}[1]{\path|#1|}

manuals/en/main/bconsole.tex

@@ -992,7 +992,7 @@ \section{Console Commands}
     In the configuration files, Addresses can (and normally should) be specified as DNS names.
     As the different components of Bareos will establish network connections to other Bareos components,
     it is important that DNS name resolution works on involved components and delivers the same results.
-    The \bcommand{resolve} command can be used to test DNS resolution of a given hostname 
+    The \bcommand{resolve}{} command can be used to test DNS resolution of a given hostname 
     on director, storage daemonm or client.
 
 \begin{bconsole}{resolve example}
@@ -1390,10 +1390,10 @@ \section{Console Commands}
 
 
 
-The command \bcommand{status scheduler} (\sinceVersion{console}{status scheduler}{12.4.4}) can be used to check when a certain schedule will trigger.
-This gives more information than \bcommand{status director}.
+The command \bcommand{status scheduler}{} (\sinceVersion{console}{status scheduler}{12.4.4}) can be used to check when a certain schedule will trigger.
+This gives more information than \bcommand{status director}{}.
 
-Called without parameters, \bcommand{status scheduler} shows a preview for all schedules for the next 14 days.
+Called without parameters, \bcommand{status scheduler}{} shows a preview for all schedules for the next 14 days.
 It first shows a list of the known schedules and the jobs that will be triggered by these jobs:
 
 \begin{bconsole}{status scheduler}
@@ -1439,7 +1439,7 @@ \section{Console Commands}
 ====
 \end{bconsole}
 
-\bcommand{status scheduler} accepts the following parameters:
+\bcommand{status scheduler}{} accepts the following parameters:
 \begin{description}
     \item[client=clientname] shows only the schedules that affect the given client.
     \item[job=jobname] shows only the schedules that affect the given job.
@@ -1448,7 +1448,7 @@ \section{Console Commands}
 \end{description}
 
 In case you are running a maintained version of Bareos,
-the command \bcommand{status subscriptions} (\sinceVersion{console}{status subscriptions}{12.4.4}) can help you to keep the overview over the subscriptions
+the command \bcommand{status subscriptions}{} (\sinceVersion{console}{status subscriptions}{12.4.4}) can help you to keep the overview over the subscriptions
 that are used.
 
 To enable this functionality, just add the configuration directive subscriptions to the director configuration in the director ressource:
@@ -1462,7 +1462,7 @@ \section{Console Commands}
 }
 \end{bconfig}
 
-Using the console command \bcommand{status subscriptions}, the status of
+Using the console command \bcommand{status subscriptions}{}, the status of
 the subscriptions can be checked any time interactively:
 
 \begin{bconsole}{status subscriptions}
@@ -1499,7 +1499,7 @@ \section{Console Commands}
 
 \item [umount]
    \index[general]{Console!Command!umount}
-   Alias for \bcommand{unmount}.
+   Alias for \bcommand{unmount}{}.
 
 \item [unmount]
    \index[general]{Console!Command!unmount}

manuals/en/main/coverpage.tex

@@ -12,7 +12,7 @@
       \vspace{0.2in}
       Copyright {\copyright} 1999-2012, Free Software Foundation Europe e.V. \\
       Copyright {\copyright} 2010-2012, Planets Communications B.V. \\
-      Copyright {\copyright} 2013-2014, Bareos GmbH \& Co. KG \\
+      Copyright {\copyright} 2013-2015, Bareos GmbH \& Co. KG \\
       Bareos {\textregistered} is a registered trademark of Bareos GmbH \& Co KG.\\
       Bacula {\textregistered} is a registered trademark of Kern Sibbald.\\
       \vspace{0.2in}

manuals/en/main/dirdconf-fileset.tex

@@ -120,8 +120,7 @@ \subsection{FileSet Include Ressource}
    examples below show you how to do this.  However, please note two
    things: \\
    1.  if you want the local filesystems, you probably should be
-   using the new {\bf fstype} directive, which was added in version 1.36.3
-   and set {\bf onefs=no}.
+   using the {\bf fstype} directive and set {\bf onefs=no}.
    \\
 
    2.  the exact syntax of the command needed in the examples below is very
@@ -895,8 +894,7 @@ \subsubsection{FileSet Options Ressource}
 \item [checkfilechanges=yes{\textbar}no] \hfill \\
 \index[dir]{checkfilechanges}
 \index[dir]{Directive!checkfilechanges}
-   On versions 2.0.4 or greater,
-   if enabled, the Client will check size, age of each file after
+   If enabled, the Client will check size, age of each file after
    their backup to see if they have changed during backup. If time
    or size mismatch, an error will raise.
 
@@ -1500,8 +1498,7 @@ \subsection{FileSet Examples}
 different on different OSes. The above has been reported not to work
 on FreeBSD. This can be tested by using the {\bf estimate job=job-name
 listing} command in the console and adapting the RegexFile expression
-appropriately. In a future version of Bareos, we will supply our own
-Regex code to avoid such system dependencies.
+appropriately.
 
 Please be aware that allowing Bareos to traverse or change file systems can be
 {\bf very} dangerous. For example, with the following:

manuals/en/main/director-resource-director-definitions.tex

@@ -252,7 +252,7 @@
 
 \defDirective{Dir}{Director}{Subscriptions}{}{12.4.4}{%
 In case you want check that the number of active clients don't exceed a specific number,
-you can define this number here and check with the \bcommand{status subscriptions} command.
+you can define this number here and check with the \bcommand{status subscriptions}{} command.
 
 However, this is only indended to give a hint. No active limiting is implemented.
 }
@@ -271,7 +271,7 @@
 
 \defDirective{Dir}{Director}{Ver Id}{}{}{%
 where  \parameter{string} is an identifier which can be used for support purpose.
-This string is displayed using the \bcommand{version} command.
+This string is displayed using the \bcommand{version}{} command.
 }
 
 

manuals/en/main/director-resource-job-definitions.tex

@@ -339,7 +339,7 @@
 delete the original.
 
 However, to manage deleted files or directories changes in the
-catalog during an Incremental backup you can use \ilink{accurate mode}{accuratemode}.
+catalog during an Incremental backup you can use \nameref{accuratemode}.
 This is quite memory consuming process.
 
 \item [Differential] \hfill \\
@@ -376,12 +376,7 @@
 will then be backed up.  The start time used is displayed after the {\bf
 Since} on the Job report.  In rare cases, using the start time of the
 prior backup may cause some files to be backed up twice, but it ensures
-that no change is missed.  As with the Incremental option, you should
-ensure that the clocks on your server and client are synchronized or as
-close as possible to avoid the possibility of a file being skipped.
-Note, on versions 1.33 or greater Bareos automatically makes the
-necessary adjustments to the time between the server and the client so
-that the times Bareos uses are synchronized.
+that no change is missed.
 
 When Bareos does a Differential backup, all modified files that are
 still on the system are backed up.  However, any file that has been
@@ -421,6 +416,12 @@
 all the volumes on which the preceding Incremental and Differential
 backups since the last Full are done.
 
+\item [VirtualFull] \hfill \\
+\index[dir]{VirtualFull Backup}
+When the Level is set to VirtualFull, a new Full backup is generated from the last existing Full backup and the matching the Differential- and Incremental-Backups. This means, a Full backup will get available, without transfering all the data from the client to backup server again. The new Full backup will be stored in the pool defined in \linkResourceDirective{Dir}{Pool}{Next Pool}. The process of generating a VirtualFull backup is similar to the process described in  \nameref{MigrationChapter}.
+
+
+
 \end{description}
 
     \item [Restore] \hfill \\

manuals/en/main/recycling.tex

@@ -696,10 +696,9 @@ \subsection{Manually Recycling Volumes}
 steps:
 
 \begin{itemize}
-\item Use the {\bf purge jobs volume} command in the Console  to mark the
-   Volume as {\bf Purged}. Check by using  {\bf list volumes}.
-\item In Bareos version 1.30 or greater, use the Console  {\bf relabel}
-   command to relabel the Volume.
+\item Use the \bcommand{purge jobs volume}{} command in the Console  to mark the
+   Volume as {\bf Purged}. Check by using  \bcommand{list volumes}{}.
+\item Use the Console  \bcommand{relabel}{} command to relabel the Volume.
 \end{itemize}
 
 Please note that the relabel command applies only to tape Volumes.
@@ -723,7 +722,7 @@ \subsection{Manually Recycling Volumes}
 
 where you replace {\bf /dev/nst0} with the appropriate  device name on your
 system.
-\item Use the {\bf label} command to write a new label to  the tape and to
+\item Use the \bcommand{label}{} command to write a new label to  the tape and to
    enter it in the catalog.
 \end{itemize}
 

manuals/en/main/tutorial.tex

@@ -209,7 +209,7 @@ \section{Running a Job}
 Furthermore, we assume for the moment you are using the default configuration
 files.
 
-At this point, enter the \bcommand{show filesets} and you should get something similar this:
+At this point, enter the \bcommand{show filesets}{} and you should get something similar this:
 
 \begin{bconsole}{show filesets}
 * <input>show filesets</input>