From ede99cb5b06787fe9b58ab6fcc16f04d0b5e7ddf Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Fri, 14 Aug 2015 14:38:27 +0200 Subject: [PATCH] Tweak new features --- docs/manuals/en/main/newfeatures.tex | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex index 2058eca9..12295375 100644 --- a/docs/manuals/en/main/newfeatures.tex +++ b/docs/manuals/en/main/newfeatures.tex @@ -494,29 +494,6 @@ drives for restores. An example is: Read Only = yes \end{verbatim} -\subsection{Catalog Performance Improvements} -There is a new Bacula database format (schema) in this version -of Bacula that eliminates the FileName table by placing the -Filename into the File record of the File table. -This substantiallly improves performance, -particularly for large (1GB or greater) databases. - -% waa - 20150317 - Is 1GB _really_ considered to be a large database? Do we mean to say 100GB?? - -The \texttt{update\_xxx\_catalog} script will automatically update the -Bacula database format, but you should realize that for -very large databases (greater than 1GB), it may take some -time, and there are several different options for doing the -update: 1. Shudown the database and update it. 2. Update the -database while production jobs are running. See the Bacula Systems -White Paper ``Migration-to-6.6'' on this subject. - -\smallskip -This database format change can provide very significant improvements in -the speed of metadata insertion into the database, and in some cases -(backup of large email servers) can significantly reduce the size of the -database. - \subsection{New Truncate Command} We have added a new truncate command to bconsole which will truncate a volume if the volume is purged, and if -- 2.39.5