update info on bvfs

[bacula/docs] / docs / manuals / en / main / newfeatures.tex

diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex
index 069679ae030101f73f24d66f28218216843745c9..d9d852f05acc79978c5f2218f935d89fe42f1d7e 100644 (file)
--- a/docs/manuals/en/main/newfeatures.tex
+++ b/docs/manuals/en/main/newfeatures.tex
@@ -143,8 +143,7 @@ directories.
   \caption{Bat Brestore Panel}
 \end{figure}
 
-\texttt{Important}, the Bvfs module does not yet work correctly with BaseJobs,
-Copy and Migration jobs.
+the Bvfs module works correctly with BaseJobs, Copy and Migration jobs.
 
 \medskip
 This project was funded by Bacula Systems.
@@ -328,6 +327,15 @@ To drop the table used by the restore command, you can use the
 .bvfs_cleanup path=b20001
 \end{verbatim}
 
+\subsection*{Clearing the BVFS Cache}
+
+To clear the BVFS cache, you can use the \texttt{.bvfs\_clear_cache} command.
+
+\begin{verbatim}
+.bvfs_clear_cache yes
+OK
+\end{verbatim}
+
 \section{Changes in the Pruning Algorithm}
 
 We rewrote the job pruning algorithm in this version. Previously, in some users
@@ -620,7 +628,7 @@ and is available with Bacula Enterprise Edition and Community Edition.
 \section{Class Based Database Backend Drivers}
 
 The main Bacula Director code is independent of the SQL backend
-in version 2.5.0 and greater.  This means that the Bacula Director can be
+in version 5.2.0 and greater.  This means that the Bacula Director can be
 packaged by itself, then each of the different SQL backends supported can
 be packaged separately.  It is possible to build all the DB backends at the
 same time by including multiple database options at the same time.
@@ -640,15 +648,15 @@ Order of testing for databases is:
 \end{itemize}
 
 Each configured backend generates a file named:
-\verb+libbaccats-<sql_backend_name>-<version>.so+ 
+\verb+libbaccats-<sql_backend_name>-<version>.so+
 A dummy catalog library is created named libbaccats-version.so
 
 At configure time the first detected backend is used as the so called
-default backend and at install time the dummy 
+default backend and at install time the dummy
 \verb+libbaccats-<version>.so+ is replaced with the default backend type.
 
 If you configure all three backends you get three backend libraries and the
-postgresql gets installed as the default.  
+postgresql gets installed as the default.
 
 When you want to switch to another database, first save any old catalog you
 may have then you can copy one of the three backend libraries over the
@@ -671,7 +679,7 @@ Then you must update the default backend in the following files:
   grant_bacula_privileges
   make_bacula_tables
   make_catalog_backup
-  update_bacula_tables 
+  update_bacula_tables
 \end{verbatim}
 
 And re-run all the above scripts.  Please note, this means