ebl Add a note about new catalog format

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index d9550b781a53ef5f115b30cfe61235674c77a840..af036b088f4b59091aa566c45b2b7a201dcf4985 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -413,6 +413,15 @@ would be written to the {\bf Full} Pool which uses the Diskchanger Storage.
 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
 fail with an error.
 
 If the Virtual Full is run, and there are no prior Jobs, the Virtual Full will
 fail with an error.
 

+\section{Catalog format}
+Bacula 3.0 comes with some changes on the catalog format. The upgrade operation
+will convert an essential field of the File table that permits to handle more
+than 4 billions objects over the time, and this operation will take TIME and
+will DOUBLE THE SIZE of your catalog temporarily. Depending on your catalog
+backend, you won't be able to run jobs during this period. For example, a 3
+million files catalog will take 2mins to upgrade on a normal machine. Don't
+forget to have a valid backup of it before executing the script.
+

 \section{Duplicate Job Control}
 \index[general]{Duplicate Jobs}
 The new version of Bacula provides four new directives that
 \section{Duplicate Job Control}
 \index[general]{Duplicate Jobs}
 The new version of Bacula provides four new directives that