From a9e8d615811df201d9f43c1459bca555a37a277e Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Wed, 12 Dec 2007 20:40:53 +0000 Subject: [PATCH] Update changes --- docs/manual/console.tex | 4 ++-- docs/manual/general.tex | 34 ++++++++++++++++------------------ docs/manual/install.tex | 19 +++++++++++++++---- docs/manual/postgresql.tex | 3 ++- docs/manual/quickstart.tex | 20 +++++++------------- docs/manual/requirements.tex | 2 +- docs/manual/state.tex | 14 +++++++------- docs/manual/supportedoses.tex | 15 ++++++++------- docs/manual/tls.tex | 15 ++++++++++++++- docs/manual/version.tex | 2 +- 10 files changed, 73 insertions(+), 55 deletions(-) diff --git a/docs/manual/console.tex b/docs/manual/console.tex index 5454847a..4bb6869e 100644 --- a/docs/manual/console.tex +++ b/docs/manual/console.tex @@ -402,7 +402,7 @@ delete Job JobId=n,m,o-r,t ... jobids. \item [disable job\lt{}job-name\gt{}] - \index[console]{enable} + \index[console]{disable} This command permits you to disable a Job for automatic scheduling. The job may have been previously enabled with the Job resource {\bf Enabled} directive or using the console {\bf enable} command. @@ -576,7 +576,7 @@ and will not be mounted. Note, the full form of the command is: \footnotesize \begin{verbatim} -update storage=xxx pool=yyy slots=1-5,10 barcodes +label storage=xxx pool=yyy slots=1-5,10 barcodes \end{verbatim} \normalsize diff --git a/docs/manual/general.tex b/docs/manual/general.tex index a7350d57..b8dc2147 100644 --- a/docs/manual/general.tex +++ b/docs/manual/general.tex @@ -370,9 +370,9 @@ chapter on \item [Service] \index[fd]{Service } - This is Windows terminology for a {\bf daemon} -- see above. It is - frequently used in Unix environments as well. -% TODO: maybe do not say this is "Windows" terminology because it is common + This is a program that remains permanently in memory awaiting + instructions. In Unix environments, services are also known as + {\bf daemons}. \item [Storage Coordinates] \index[fd]{Storage Coordinates } @@ -414,20 +414,13 @@ chapter on to a Volume agrees with what is stored in the Catalog (i.e. it compares the file attributes), *or it can check the Volume contents against the original files on disk. -% TODO: fix book for asterisk above and below \item [*Archive] \index[fd]{*Archive } An Archive operation is done after a Save, and it consists of removing the -Volumes on which data is saved from active use. These Volumes are marked as -Archived, and may no longer be used to save files. All the files contained -on an Archived Volume are removed from the Catalog. NOT YET IMPLEMENTED. - -\item [*Update] - \index[fd]{*Update } - An Update operation causes the files on the remote system to be updated to be -the same as the host system. This is equivalent to an {\bf rdist} capability. -NOT YET IMPLEMENTED. + Volumes on which data is saved from active use. These Volumes are marked as + Archived, and may no longer be used to save files. All the files contained + on an Archived Volume are removed from the Catalog. NOT YET IMPLEMENTED. \item [Retention Period] \index[fd]{Retention Period } @@ -438,14 +431,19 @@ NOT YET IMPLEMENTED. in the Catalog database. This should not be confused with the time that the data saved to a Volume is valid. -% TODO: the following sentence is unclear to me The File Retention Period determines the time that File records are kept - in the catalog database. This period is important because the volume of - the database File records by far use the most storage space in the + in the catalog database. This period is important for two reasons: the + first is that as long as File records remain in the database, you + can "browse" the database with a console program and restore any + individual file. Once the File records are removed or pruned from the + database, the individual files of a backup job can no longer be + "browsed". The second reason for carefully choosing the File Retention + Period is because the volume of + the database File records use the most storage space in the database. As a consequence, you must ensure that regular "pruning" of - the database file records is done. (See the Console {\bf retention} + the database file records is done to keep your database from growing + too large. (See the Console {\bf prune} command for more details on this subject). -% TODO: Where? The Job Retention Period is the length of time that Job records will be kept in the database. Note, all the File records are tied to the Job diff --git a/docs/manual/install.tex b/docs/manual/install.tex index 8782a293..953fa440 100644 --- a/docs/manual/install.tex +++ b/docs/manual/install.tex @@ -9,7 +9,8 @@ In general, you will need the Bacula source release, and if you want to run a Windows client, you will need the Bacula Windows binary release. However, Bacula needs certain third party packages (such as {\bf MySQL}, -{\bf PostgreSQL}, or {\bf SQLite} to build properly depending on the +{\bf PostgreSQL}, or {\bf SQLite} to build and run +properly depending on the options you specify. Normally, {\bf MySQL} and {\bf PostgreSQL} are packages that can be installed on your distribution. However, if you do not have them, to simplify your task, we have combined a number of these @@ -21,9 +22,9 @@ them. \section{Source Release Files} \index[general]{Source Files} \index[general]{Release Files} -Beginning with Bacula 1.38.0, the source code has been broken into -four separate tar files each corresponding to a different module in -the Bacula SVN. The released files are: + Beginning with Bacula 1.38.0, the source code has been broken into + four separate tar files each corresponding to a different module in + the Bacula SVN. The released files are: \begin{description} \item [bacula-2.0.3.tar.gz] @@ -771,6 +772,16 @@ $ nm /usr/local/lib/libpq.a | grep mutex security, please modify src/version.h appropriately (it should be obvious when you look at the file). + Running with Batch Insert turned on is recommended because it can + significantly improve attribute insertion times. However, it does + put a significantly larger part of the work on your SQL engine, so + you may need to pay more attention to tuning it. In particular, + Batch Insert can require large temporary table space, and consequently, + the default location (often /tmp) may run out of space causing errors. + For MySQL, the location is set in my.conf with "tmpdir". You may also + want to increase the memory available to your SQL engine to further + improve performance during Batch Inserts. + \item [ {-}{-}enable-gnome ] \index[general]{{-}{-}enable-gnome} If you have GNOME installed on your computer including the diff --git a/docs/manual/postgresql.tex b/docs/manual/postgresql.tex index 835f7732..15be98e9 100644 --- a/docs/manual/postgresql.tex +++ b/docs/manual/postgresql.tex @@ -128,7 +128,8 @@ user). not set UTF8 as your default character set or because you have imported files from elsewhere (e.g. MacOS X). For this reason, Bacula uses SQL\_ASCII as the default encoding. If you want to change this, - please modify the script before running it. + please modify the script before running it, but be forewarned that + Bacula backups will fail if PostgreSQL finds any non-UTF8 sequences. If running the script fails, it is probably because the database is owned by a user other than yourself. On many systems, the database diff --git a/docs/manual/quickstart.tex b/docs/manual/quickstart.tex index 3be9f14c..468a1acf 100644 --- a/docs/manual/quickstart.tex +++ b/docs/manual/quickstart.tex @@ -328,19 +328,13 @@ compatibility of Bacula and your system. \label{notls} \section{Get Rid of the /lib/tls Directory} \index[general]{Directory!Get Rid of the /lib/tls } \index[general]{Get Rid of the /lib/tls Directory } - -% TODO: this seems dangerous -- how do you know if they don't use -% TODO: /lib/tls for something mission critical? Reword this or point to -% TODO: appropriate documentation. - -The new pthreads library {\bf /lib/tls} installed by default on recent Red Hat -systems running Linux kernel 2.4.x is defective. You must remove it or rename it, -then reboot your system before running Bacula otherwise after a week or so of -running, Bacula will either block for long periods or deadlock entirely. -You may want to use the loader environment variable override rather -than removing /lib/tls. Please see \ilink{ Supported Operating -Systems}{SupportedOSes} for more -information on this problem. +The new pthreads library {\bf /lib/tls} installed by default on recent Red +Hat systems running Linux kernel 2.4.x is defective. You must remove it or +rename it, then reboot your system before running Bacula otherwise after a +week or so of running, Bacula will either block for long periods or +deadlock entirely. You may want to use the loader environment variable +override rather than removing /lib/tls. Please see \ilink{ Supported +Operating Systems}{SupportedOSes} for more information on this problem. This problem does not occur on systems running Linux 2.6.x kernels. diff --git a/docs/manual/requirements.tex b/docs/manual/requirements.tex index 8f721412..9dbeed98 100644 --- a/docs/manual/requirements.tex +++ b/docs/manual/requirements.tex @@ -20,7 +20,7 @@ depkgs1} releases. However, most current Linux and FreeBSD systems provide these as system packages. \item The minimum versions for each of the databases supported by Bacula -are: + are: \begin{itemize} \item MySQL 4.1 diff --git a/docs/manual/state.tex b/docs/manual/state.tex index 51cee05b..066d8f2f 100644 --- a/docs/manual/state.tex +++ b/docs/manual/state.tex @@ -22,11 +22,10 @@ In other words, what is and what is not currently implemented and functional. (sometimes called multiplexing). \item Job sequencing using priorities. \item \ilink{Console}{UADef} interface to the Director allowing complete - control. A shell, GNOME GUI and wxWidgets GUI versions of the Console program - are available. Note, the GNOME GUI program currently offers very few - additional features over the shell program. - With version 2.2.0, a much more complete GUI interface has been - written, which is called the Bacula Admistration Tool, or bat. + control. A shell, Qt4 GUI, GNOME GUI and wxWidgets GUI versions of + the Console program are available. Note, the Qt4 GUI program called + the Bacula Administration tool or bat, offers many additional + features over the shell program. \end{itemize} \item Security @@ -178,7 +177,7 @@ In other words, what is and what is not currently implemented and functional. commercial application, probably because that application stores its catalog information in a large number of individual files rather than an SQL database as Bacula does. -\item Aside from a GUI administrative interface, Bacula has a +\item Aside from several GUI administrative interfaces, Bacula has a comprehensive shell administrative interface, which allows the administrator to use tools such as ssh to administrate any part of Bacula from anywhere (even from home). @@ -220,7 +219,8 @@ In other words, what is and what is not currently implemented and functional. You must explicitly update the date/time stamp on all moved files (we have a project to correct this). \item File System Modules (configurable routines for - saving/restoring special files) are not yet implemented. + saving/restoring special files) are not yet implemented. However, + this feature is easily implemented using RunScripts. \item Bacula supports doing backups and restores to multiple devices of different media type and multiple Storage daemons. However, if you have backed up a job to multiple storage diff --git a/docs/manual/supportedoses.tex b/docs/manual/supportedoses.tex index d5bf0d1d..797b9eb2 100644 --- a/docs/manual/supportedoses.tex +++ b/docs/manual/supportedoses.tex @@ -7,16 +7,15 @@ \index[general]{Supported Operating Systems } \begin{itemize} -\item Linux systems (built and tested on SuSE 10.2). -\item Most flavors of Linux (Gentoo, Red Hat, Fedora, Mandriva, Debian, Ubuntu, ...). +\item Linux systems (built and tested on CentOS 5). +\item Most flavors of Linux (Gentoo, Red Hat, Fedora, Mandriva, + Debian, OpenSuSE, Ubuntu, Kubuntu, ...). \item Solaris various versions. \item FreeBSD (tape driver supported in 1.30 -- for FreeBSD older than version 5.0, please see some {\bf important} considerations in the \ilink{ Tape Modes on FreeBSD}{FreeBSDTapes} section of the Tape Testing chapter of this manual.) -\item Windows (Win98/Me, WinNT/2K/XP) Client (File daemon) binaries. -\item Windows Vista VSS (Volume Shadow Copy) is reported not to work - with Bacula. +\item Windows (Win98/Me, WinNT/2K/XP, Vista) Client (File daemon) binaries. \item The Windows servers (Director and Storage daemon) are available in the binary Client installer. The are reported to work in many cases. However they are NOT supported. @@ -27,8 +26,10 @@ \item Tru64 \item Bacula is said to work on other systems (AIX, BSDI, HPUX, NetBSD, ...) but we do not have first hand knowledge of these systems. -\item RHat 7.2 AS2, AS3, AS4, Fedora Core 2,3,4,5, SuSE SLES 7,8,9,10,10.1 and Debian Woody and Sarge Linux on - S/390 and Linux on zSeries. +\item RHat 7.2 AS2, AS3, AS4, RHEL5, Fedora Core 2,3,4,5,6,7 SuSE SLES + 7,8,9,10,10.1,10.2,10.3 + and Debian Woody and Sarge Linux on + S/390 and Linux on zSeries. \item See the Porting chapter of the Bacula Developer's Guide for information on porting to other systems. diff --git a/docs/manual/tls.tex b/docs/manual/tls.tex index c5068d1a..6c90e110 100644 --- a/docs/manual/tls.tex +++ b/docs/manual/tls.tex @@ -249,12 +249,25 @@ for bconsole to the Director. TLS Verify Peer = yes # Allow only the Director to connect TLS Allowed CN = "bacula@backup1.example.com" - TLS CA Certificate File = /usr/local/etc/ssl/ca.pem\ + TLS CA Certificate File = /usr/local/etc/ssl/ca.pem # This is a server certificate. It is used by connecting # directors to verify the authenticity of this file daemon TLS Certificate = /usr/local/etc/ssl/server1/cert.pem TLS Key = /usr/local/etc/ssl/server1/key.pem } + + FileDaemon { + Name = backup1-fd + ... + # you need these TLS entries so the SD and FD can + # communicate + TLS Enable = yes + TLS Require = yes + + TLS CA Certificate File = /usr/local/etc/ssl/ca.pem + TLS Certificate = /usr/local/etc/ssl/server1/cert.pem + TLS Key = /usr/local/etc/ssl/server1/key.pem +} \end{verbatim} \normalsize diff --git a/docs/manual/version.tex b/docs/manual/version.tex index a73b3c8b..0b52667e 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -2.2.7 (04 December 2007) +2.3.6 (19 October 2007) -- 2.39.5