Fix old incorrect text about Maximum Volume Bytes

diff --git a/docs/manuals/bacula.sty b/docs/manuals/bacula.sty
index c1bfd68bb0eca59d01bb327f52a16c86a8662021..37a5703665397888d217752f18877e62e7b25512 100644 (file)
--- a/docs/manuals/bacula.sty
+++ b/docs/manuals/bacula.sty
@@ -79,7 +79,7 @@
 \pdfminorversion=4
 
 
-\def\version{7.2.0}
+\def\version{7.2.1}
 
 
 %%

diff --git a/docs/manuals/en/main/disk.tex b/docs/manuals/en/main/disk.tex
index e912eaf5b82923b084fa3ecb724dd7949df0c6f0..7bca3ad054553e617ec4bba58078494bbd8284c1 100644 (file)
--- a/docs/manuals/en/main/disk.tex
+++ b/docs/manuals/en/main/disk.tex
@@ -99,15 +99,23 @@ are:
 
    {\bf Maximum Volume Bytes = mmmm}.  
 
-   Note, if you use disk volumes, with all versions up to and including
-   1.39.28, you should probably limit the Volume size to some reasonable 
-   value such as say 5GB. This is because during a restore, Bacula is
-   currently unable to seek to the proper place in a disk volume to restore
-   a file, which means that it must read all records up to where the
-   restore begins. If your Volumes are 50GB, reading half or more of the
-   volume could take quite a bit of time.  Also, if you ever have a partial
-   hard disk failure, you are more likely to be able to recover more data
-   if they are in smaller Volumes.
+   Note, if you use disk volumes and do not specify a Maximum Volume Bytes,
+   Bacula will write to your first Volume until your whole disk fills.
+   This is probably not what you want.  We recommend keeping your total
+   number of Volumes created in the Catalog down to less than 5,000 for
+   performance reasons when pruning.  For a small site (10-20 clients), you
+   might choose a Maximum Volume Bytes of 5G, for a medium site (20-100
+   clients) you might choose as size of 50G, and for large sites (greater
+   than 100 clients) 200G.
+
+   The advantage of bigger Volumes is that it improves performance during
+   pruning (smaller number of Volumes to prune).  The advantage of smaller
+   Volumes is that you waste less disk space by being able to recycle them
+   more often than big Volumes.
+
+   As of Bacula version 2.0 and greater large Volumes present little
+   performance penality during restores, because Bacula is able to seek to
+   the start of each Job (and often within a Job).
 
 \item To limit the use time (i.e. write the Volume for a maximum of five days),
    use:
@@ -660,12 +668,12 @@ Schedule {
 FileSet {
   Name = "Example FileSet"
   Include {
-       Options {
-       compression=GZIP
-       signature=SHA1 
-               }
+        Options {
+        compression=GZIP
+        signature=SHA1 
+                }
     File = /home/kern/bacula/bin
-         }
+          }
 }
 Job {
   Name = "Backup-client1"

diff --git a/docs/manuals/version.tex b/docs/manuals/version.tex
index ae888ae56cf567f85f0b8d17ca4b3ffeb4359e7d..a8728f40bbc8d86c83fe76eef45359d31db82f63 100644 (file)
--- a/docs/manuals/version.tex
+++ b/docs/manuals/version.tex
@@ -1 +1 @@
-7.2.0 (12 August 2015)
+7.2.1 (23 December 2015)