compatible default value was changed

manuals/en/main/backward-compability.tex

@@ -53,12 +53,12 @@ \section{Compatibility between Bareos and Bacula}
 It is not possible to mix these components.
 This is because the protocol between Director and Storage Daemon itself is not versioned (also true for Bareos and Bacula).
 If you want to be able to switch back from Bareos to Bacula after using a Bareos director and storage daemon
-you have to enable the compatible mode in the Bareos storage daemon (which is currently the default)
-to have it write the data in the same format as the Bacula storage daemon.
+you have to enable the compatible mode in the Bareos storage daemon to have it write the data in the same
+format as the Bacula storage daemon.
 
-The Bareos File Daemon is compatible with all version of the Bacula director
-when you enable the compatible mode in the config of the file daemon.
-Currently the compatible option is on by default but that may change in the future.
+The Bareos File Daemon is compatible with all version of the Bacula director (of version 5.2.13 and lower)
+and not with Bacula 7.x. when you enable the compatible mode in the config of the file daemon.
+The compatible option was set by default in Bareos < 15, and is disabled by default since Version 15.
 To be sure this is enabled you can explicitly set the compatible option
 by putting the following in the bareos-fd.conf:
 

manuals/en/main/bareos-fd-resource-client-definitions.tex

@@ -76,7 +76,10 @@
 Bacula file daemon as possible. Enabling this option means that
 certain new options available in Bareos cannot be used as they would
 lead to data not being able to be restored by a Native Bareos file daemon.
-When you want to use bareos-only features, you have to set it to false.
+
+The default value for this directive was changed from yes to no since Bareos Version 15.
+
+When you want to use bareos-only features, the value of compatible must be no.
 }
 
 \defDirective{Fd}{Client}{Description}{}{}{%

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

@@ -39,6 +39,7 @@
 are Bareos specific. Which may be read when used by a Bareos storage
 daemon but might not be understood by any of the Bacula components
 (dir/sd/fd).
+The default setting of this directive was changed to no since Bareos version 15.
 }
 
 \defDirective{Sd}{Storage}{Description}{}{}{%

manuals/en/main/howto.tex

@@ -98,10 +98,8 @@ \subsubsection{MSSQL Plugin Installation}
   # remove comment in next line to load plugins from specified directory
   Plugin Directory = "C:/Program Files/Bareos/Plugins"
 
-  # if compatible is set to yes, we are compatible with bacula
-  # if you want to use new bareos features, please set compatible to no
   Plugin Names = "mssqlvdi"
-  compatible = no
+  compatible = no  # this is the default since bareos 15
 }
 \end{bconfig}
 
@@ -759,9 +757,7 @@ \subsubsection{Backup of a MySQL Databases by using the Python MySQL plugin}
   Name = mysql-fd
   ...
   Plugin Directory = /usr/lib64/bareos/plugins
-  # if compatible is set to yes, we are compatible with bacula
-  # if you want to use new bareos features, please set
-  compatible = no
+  compatible = no # default since bareos 15
 }
 \end{bconfig}
 

manuals/en/main/passiveclient.tex

@@ -32,7 +32,8 @@ \subsection{Usage}
 }
 \end{bconfig}
 
-Also, you need to set \configdirective{compatible=no} in the \file{bareos-fd.conf} configuration file:
+Also, prior to bareos version 15, you need to set \configdirective{compatible=no} in the \file{bareos-fd.conf} configuration file.
+Since Bareos Version 15, the compatible opion is set to no per default and does not need to be specified anymore.
 \begin{bconfig}{Disable compatible mode for the Bareos filedaemon in bareos-fd.conf} 
 Director {
   Name = bareos-dir
@@ -42,6 +43,6 @@ \subsection{Usage}
 FileDaemon {
    Name = client1-fd
    [...]
-   <input>Compatible = no</input>
+   <input>Compatible = no</input> # default since bareos version 15
 }
 \end{bconfig}

manuals/en/main/tapetesting.tex

@@ -812,4 +812,4 @@ \subsection{Syslog Errors}
 described earlier in this manual.  If you are running your Storage daemon
 as root, you should not be getting these system log messages, and if
 you are, something is probably wrong.
-}
+}