From: <gi...@ba...> - 2016-10-12 08:21:28
|
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Bacula Community manual". The branch, Branch-7.4 has been updated via 1bde0509e78bc357e9c6bfc3b48a12c6c2ad69e0 (commit) via 4f3faa23982b50afb0b3b38803ebebc37da7699d (commit) via acfcdb25d63913d7aaacc4163590638aeeab6d4c (commit) via 8b82f52a1e40ec2e5f020db15229d82b844489db (commit) via 29c25d48f4047848ca7c56c779b46b2f4becd7df (commit) via 3e1a8f549eb3c74a2a20ea4aed8959617daace5e (commit) via 9136ac998822a7f6a44fa4d531c04ad1b432064e (commit) via 363da9df7728aae0e2105b96671f6481ba12433c (commit) via 518ec351efeea9f8a39d930b258478080723bd1f (commit) from 1261b0961c7047515ecb0242fbeb4f7af6459627 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 1bde0509e78bc357e9c6bfc3b48a12c6c2ad69e0 Author: Kern Sibbald <ke...@si...> Date: Wed Sep 21 13:36:11 2016 +0200 Tweak: doc correct some license info commit 4f3faa23982b50afb0b3b38803ebebc37da7699d Author: Kern Sibbald <ke...@si...> Date: Wed Sep 21 11:52:56 2016 +0200 doc: spelling errors from Carsten Leonhardt + one from aspell commit acfcdb25d63913d7aaacc4163590638aeeab6d4c Author: Kern Sibbald <ke...@si...> Date: Wed Sep 21 11:13:28 2016 +0200 doc: Make changes suggested by Carsten Leonhardt commit 8b82f52a1e40ec2e5f020db15229d82b844489db Author: Kern Sibbald <ke...@si...> Date: Wed Sep 21 10:59:13 2016 +0200 doc: remove zero size images commit 29c25d48f4047848ca7c56c779b46b2f4becd7df Author: Kern Sibbald <ke...@si...> Date: Wed Sep 21 10:57:17 2016 +0200 Tweak update doc version commit 3e1a8f549eb3c74a2a20ea4aed8959617daace5e Author: Kern Sibbald <ke...@si...> Date: Mon Sep 19 17:22:54 2016 +0200 Add problems with Bacula unable to open tape device commit 9136ac998822a7f6a44fa4d531c04ad1b432064e Author: Kern Sibbald <ke...@si...> Date: Thu Aug 11 17:12:10 2016 +0200 Fix description of Volume Retention -- bug 1844 commit 363da9df7728aae0e2105b96671f6481ba12433c Author: Kern Sibbald <ke...@si...> Date: Mon Aug 1 12:21:37 2016 +0200 Tweak baculum doc again commit 518ec351efeea9f8a39d930b258478080723bd1f Author: Kern Sibbald <ke...@si...> Date: Mon Aug 1 12:10:07 2016 +0200 Update Baculum section of console manual ----------------------------------------------------------------------- Summary of changes: diff --git a/docs/README b/docs/README index cb0140a..f204e32 100644 --- a/docs/README +++ b/docs/README @@ -13,10 +13,30 @@ You normally should not edit that file, rather edit version.tex, see the end of this file for more on versions. +For latex2html to find latex/, you may need: + +export TEXINPUTS=`pwd`/latex + You must have at least the following packages loaded: latex2html te_latex tetex +libhtml-parser-perl +libhtml-treebuilder-libxml-perl + +instead of the full tex package, you can load: + +texlive-base +texlive-fonts-recommended +texlive-latex-recommended + +I tend to load pretty much everything with the following apt packages: + +dvipdfmx texlive latex2html + +and for rpms: + +tetex tetex-dvips tetx-fonds tetx-latex Web site: nothing to build, simply copy the files to the Web site, then load the documents in the appropriate @@ -35,6 +55,10 @@ English manual: named xxx which contains the web version of that particular manual. The pdf is in manuals/en/xxx/xxx.pdf + NOTE!!! Please note that running multiple simultaneous makes does + not work. I.e. "make -j3" will fail. If you have a solution, please + send it to me. Thanks. + German manual: cd <docs> make german diff --git a/docs/images/xp-control-panel.eps b/docs/images/xp-control-panel.eps deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-control-panel.png b/docs/images/xp-control-panel.png deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced-settings-after.eps b/docs/images/xp-windows-firewall-advanced-settings-after.eps deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced-settings-after.png b/docs/images/xp-windows-firewall-advanced-settings-after.png deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced-settings-before.eps b/docs/images/xp-windows-firewall-advanced-settings-before.eps deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced-settings-before.png b/docs/images/xp-windows-firewall-advanced-settings-before.png deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced-settings-service-details.eps b/docs/images/xp-windows-firewall-advanced-settings-service-details.eps deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced-settings-service-details.png b/docs/images/xp-windows-firewall-advanced-settings-service-details.png deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced.eps b/docs/images/xp-windows-firewall-advanced.eps deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall-advanced.png b/docs/images/xp-windows-firewall-advanced.png deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall.eps b/docs/images/xp-windows-firewall.eps deleted file mode 100644 index e69de29..0000000 diff --git a/docs/images/xp-windows-firewall.png b/docs/images/xp-windows-firewall.png deleted file mode 100644 index e69de29..0000000 diff --git a/docs/manuals/bacula.sty b/docs/manuals/bacula.sty index 7cbb12d..57f9521 100644 --- a/docs/manuals/bacula.sty +++ b/docs/manuals/bacula.sty @@ -79,7 +79,7 @@ \pdfminorversion=4 -\def\version{7.4.3} +\def\version{7.4.4} %% diff --git a/docs/manuals/en/console/baculum.tex b/docs/manuals/en/console/baculum.tex index d0cc33a..b185aa6 100644 --- a/docs/manuals/en/console/baculum.tex +++ b/docs/manuals/en/console/baculum.tex @@ -1,37 +1,38 @@ %% %% -\chapter{Baculum WebGUI Tool} +\chapter{Baculum Web GUI Tool} \label{BaculumChapter} -This chapter presents the new Bacula web based interface that has been added to -the Bacula projects in version 7.0 and later. +This chapter presents the Bacula Web based interface that has been added to +the Bacula project for version 7.0 and later. \section{Base Features} -Baculum provides following base features: +Baculum provides the following base features: \begin{itemize} \item Running Bacula jobs (backup, restore, verify...). -\item Monitoring Bacula services status. -\item Bacula console available via web interface. -\item Multi-users interface. +\item Monitoring Bacula service status. +\item Bacula console available via a Web window. +\item Multi-user interface. \item Support for customized and restricted consoles (Console ACL function). -\item Volumes management. +\item Volume management. \item User friendly graphs and metrics. -\item Basic storage daemon operations (mount, umount, release actions). -\item Easy in use configuration and restore wizards. -\item Multiple Directors support. +\item Basic storage daemon operations (mount, umount, release, ...). +\item Easy to use configuration and restore wizards. +\item Multiple Director support. \item Live AJAX based statuses. \end{itemize} \section{General Requirements} -Environment for Baculum installation should have following components installed: +Environment for Baculum installation should have following components +installed: \begin{itemize} -\item Web Server - with mod\_rewrite module loaded. Baculum has been tested with -Apache, Nginx and Lighttpd web servers. +\item A Web Server - with mod\_rewrite module loaded. Baculum has been +tested with Apache, Nginx and Lighttpd web servers. \item PHP 5.3 or higher with following modules installed: \begin{itemize} \item PDO PHP support - depending on your catalog database: PDO PostgreSQL @@ -42,20 +43,20 @@ native driver. It is php-mysqlnd for PHP, not php-mysql. \item MB String PHP module. \item JSON PHP module. \end{itemize} -\item Bconsole - configured Bacula text based console -\item Access to Bacula Catalog database (local or remote) +\item A working Bacula bconsole - configured Bacula text based console +\item Direct access to the Bacula Catalog database (local or remote) \end{itemize} -All above requirements are validated during Baculum start. If in installation -environment there occurs lack some from these components then you will be -informed about this fact. +All the above requirements are validated during Baculum start. If +an error is found you will be notified during the initial login. +See below for instructions on how to correct errors. -In case installation from binary packages (deb, rpm) all requirements are -installed automatically as packages dependencies. +With installation from binary packages (deb, rpm) all requirements +will be automatically installed as packages dependencies. \section{Installation from rpm binary packages} -For rpm binary packages format there exist following packages: +For rpm binary there are the following packages: \begin{itemize} \item baculum - main package with application files @@ -64,22 +65,25 @@ For rpm binary packages format there exist following packages: \item baculum-lighttpd - Lighttpd web server configuration files \end{itemize} -\subsection{Add rpm repository} +You must install at a minimum the {\bf baculum} package and either +baculum-http or {\bf baculum-lighttpd}. -To add Baculum repository, first is required importing public key: +\subsection{Add the Bacula rpm repository} + +To add the Baculum repository, first you must import the Baculum public key: \begin{verbatim} rpm --import http://bacula.org/downloads/baculum/baculum.pub \end{verbatim} -Once importing the key is done, next step is adding repository definition to -newly created file: +Once the key is imported, the next step is to add the repository +definition. First you must create the following file: \begin{verbatim} /etc/yum.repos.d/baculum.repo \end{verbatim} -For CentOS 7 the definition is: +The for CentOS 7, put the following in the file just created: \begin{verbatim} [baculumrepo] @@ -89,7 +93,7 @@ gpgcheck=1 enabled=1 \end{verbatim} -For Fedora 23 the definition is: +For Fedora 23 the {\bf bacula.repo} file should have the following contents: \begin{verbatim} [baculumrepo] @@ -99,73 +103,121 @@ gpgcheck=1 enabled=1 \end{verbatim} -\subsection{Installation for Apache} +\subsection{Installation for the Apache Web server} -Example installation for access via Apache web server can look like below: +Install Baculum for the Apache Web server as follows: \begin{verbatim} yum install baculum baculum-httpd \end{verbatim} -Start Baculum as application available through Apache web server: +Restart your Apache Web server: \begin{verbatim} service httpd restart \end{verbatim} -Access from web browser: \textbf{http://localhost:9095} +\subsection{Access to bconsole via sudo} + +Baculum requires access to Bconsole. To configure Bconsole sudo access there +can use following entries in newly created Baculum sudoers.d file (usually in +path /etc/sudoers.d/baculum): + +In case default user both for Apache and Lighttpd: + +\begin{verbatim} +Defaults:web-user !requiretty +web-user ALL=NOPASSWD: /usr/sbin/bconsole +\end{verbatim} + +Where {\bf web-user} must be replaced by the Linux +username under which your Web server is running. + +For example, on Fedora the default Apache server name is {\bf apache}; +on Debian/Ubuntu it is {\bf www-data}, and on CentOS/RedHat it +is {\bf apache} or {\bf apache2}. + +\subsection{Running Baculum for the First Time} +Access Baculum from a Web browser: \textbf{http://localhost:9095} First time login: \textbf{admin} First time password: \textbf{admin} +\subsection{Debugging your First Login} +At each step of the initial login to Baculum, the +screen will have a test button that will allow you +to check to see if your parameters were correctly +entered. If not, you can get additional detail by +examining the Apache error log, that is usually +found at: + +\begin{verbatim} +/var/log/apache2/error.log +\end{verbatim} + +In addition, special debug output is placed by Baculum in +the file: + +\begin{verbatim} +/etc/baculum/Data-apache/baculum.dbg +\end{verbatim} + +With the information in those two files, you can usually quickly +find and correct most problems. + + \subsection{Installation for Lighttpd} -Example installation on system with SELinux enabled access and access via -Lighttpd looks following: +Installation on system with SELinux enabled access and access via +Lighttpd is as follows \begin{verbatim} yum install baculum baculum-selinux baculum-lighttpd \end{verbatim} +You can skip installing baculum-selinux if you do not use SELinux. + Please note that in case CentOS distribution the Lighttpd web server is -available in distribution packages after enabling EPEL repository. +available in the distribution packages after enabling the EPEL repository. -Start Baculum as application available through Apache web server: +Start Baculum as application using the lighttpd Web server: \begin{verbatim} service baculum-lighttpd start \end{verbatim} -Access from web browser: \textbf{http://localhost:9095} - -First time login: \textbf{admin} - -First time password: \textbf{admin} \subsection{Access to bconsole via sudo} -Baculum requires access to Bconsole. To configure Bconsole sudo access there -can use following entries in newly created Baculum sudoers.d file (usually in -path /etc/sudoers.d/baculum): +Baculum requires access to Bconsole. To configure Bconsole sudo access +we strongly recommend that you create a Baculum sudoers.d file, which +should be in /etc/sudoers.d/baculum: -In case default Apache user: +In case default Apache user, the file contents must be: \begin{verbatim} Defaults:apache !requiretty -apache ALL= NOPASSWD: /usr/sbin/bconsole +apache ALL=NOPASSWD: /usr/sbin/bconsole \end{verbatim} -In case default Lighttpd user: +In case default Lighttpd user the file contents must be: \begin{verbatim} Defaults:lighttpd !requiretty -lighttpd ALL= NOPASSWD: /usr/sbin/bconsole +lighttpd ALL=NOPASSWD: /usr/sbin/bconsole \end{verbatim} +\subsection{Running Baculum for the First Time with Lighttpd} +Access Baculum from your Web browser: \textbf{http://localhost:9095} + +First time login: \textbf{admin} + +First time password: \textbf{admin} + \section{Installation from deb binary packages} -For deb binary packages format there exist following packages: +For deb binary packages format you will find the following packages: \begin{itemize} \item baculum - main package with application files @@ -175,73 +227,75 @@ For deb binary packages format there exist following packages: \subsection{Add deb repository} -To add Baculum repository, first is required importing public key: +To add the Baculum repository, first import the Baculum public key: \begin{verbatim} wget -qO - http://bacula.org/downloads/baculum/baculum.pub | apt-key add - \end{verbatim} -Once importing the key is done, next step is adding repository definition to -newly created file: +Once the key is imported, the next step is to create +a new baculum file: \begin{verbatim} /etc/apt/sources.list.d/baculum.list \end{verbatim} -For Debian 8 Jessie the definition is: +For Debian 8 Jessie the contents should be: \begin{verbatim} deb http://bacula.org/downloads/baculum/debian jessie main deb-src http://bacula.org/downloads/baculum/debian jessie main \end{verbatim} -For Ubuntu 15.04 Vivid the definition is: +For Ubuntu 15.04 Vivid the contents should be: \begin{verbatim} deb [ arch=amd64 ] http://bacula.org/downloads/baculum/ubuntu vivid main deb-src http://bacula.org/downloads/baculum/ubuntu vivid main \end{verbatim} -For Ubuntu 15.10 Wily the definition is: +For Ubuntu 15.10 Wily the contents should be: \begin{verbatim} deb [ arch=amd64 ] http://bacula.org/downloads/baculum/ubuntu wily main deb-src http://bacula.org/downloads/baculum/ubuntu wily main \end{verbatim} -After adding repository definition please refresh repository indexes: +After adding repository definition, please refresh repository indexes: \begin{verbatim} apt-get update \end{verbatim} \subsection{Installation for Apache} -Example installation for access via Apache web server by using apt packages -manager can look like below: +To install Baculum access via Apache Web server by using apt +packages manager use the command: \begin{verbatim} apt-get install baculum baculum-apache2 \end{verbatim} -Next is needed enable mod\_rewrite module for Apache: +Next you must enable mod\_rewrite module for Apache, with the +following command: \begin{verbatim} ln -s /etc/apache2/mods-available/rewrite.load \ /etc/apache2/mods-enabled/rewrite.load \end{verbatim} -and include Baculum VirtualHost definition into Apache configuration: +and include Baculum VirtualHost definition in the Apache configuration +with: \begin{verbatim} ln -s /etc/apache2/sites-available/baculum.conf \ /etc/apache2/sites-enabled/baculum.conf \end{verbatim} -Start Baculum as application available through Apache web server: +The restart your Apache server with: \begin{verbatim} service apache2 restart \end{verbatim} -Access from web browser: \textbf{http://localhost:9095} +and access Baculum from you Web browser with: \textbf{http://localhost:9095} First time login: \textbf{admin} @@ -267,24 +321,12 @@ First time login: \textbf{admin} First time password: \textbf{admin} -\subsection{Access to bconsole via sudo} -Baculum requires access to Bconsole. To configure Bconsole sudo access there -can use following entries in newly created Baculum sudoers.d file (usually in -path /etc/sudoers.d/baculum): - -In case default user both for Apache and Lighttpd: - -\begin{verbatim} -Defaults:www-data !requiretty -www-data ALL= NOPASSWD: /usr/sbin/bconsole -\end{verbatim} - -\section{Installation from source tar archive} +\section{Installation from the Source Tar File} -There is possible to install Baculum from source bacula-gui tar archive. +You may also install Baculum from the source bacula-gui tar archive. -To prepare Baculum runtime files there can be used Makefile file. +To prepare Baculum runtime files one uses the Makefile file. To do this, after unpacking bacula-gui archive please go to Baculum main directory: @@ -307,20 +349,20 @@ make build DESTDIR=/tmp/baculum-release SAMPLETYPE=deb-template \ HTTPDNAME=apache2 HTTPDSITECONF=sites-available \end{verbatim} -After execution above command, in path /tmp/baculum-runtime should already exist all -runtime files. +After execution above command, in path /tmp/baculum-runtime should +contain all required runtime files. -Base Baculum source files will be located in: +The Base Baculum source files will be located in: \begin{verbatim} /tmp/baculum-runtime/usr/share/baculum/htdocs/ \end{verbatim} -They are files that should be placed in web server's document root (or Virtual -Host document root) directory. +These are the files that should be placed in web server's document root (or +Virtual Host document root) directory. -Please note that for language files (including English) are created symbolic -links as below: +Please note that for language files (including English) +symbolic links must be created as shown below: \begin{verbatim} /usr/share/locale/en/LC_MESSAGES/baculum.mo @@ -333,19 +375,19 @@ links as below: => /tmp/baculum-runtime/usr/share/baculum/htdocs/protected/Lang/pt/baculum.mo \end{verbatim} -Please also update symbolic link to Baculum settings directory in following -path: +Please also update the symbolic link to the Baculum settings directory in +the following path: \begin{verbatim} /tmp/baculum-runtime/usr/share/baculum/htdocs/protected/Data \end{verbatim} -Rest of files are: web servers configuration files, systemd units, SELinux +Other files are: web servers configuration files, systemd units, SELinux policy module and others. Please select and copy appropriate files to your system environment and edit their content if needed. -At the end there is required to set read/write privileges for web server user -to listed below directories and files: +You must set read/write privileges for the Web server user +to the files and directories listed below: \begin{verbatim} ./baculum/assets/ @@ -359,24 +401,28 @@ to listed below directories and files: Baculum supports customized and restricted consoles for each logged in user. -General design allows to have one administrator and many users. For each -user there is possible to define own bconsole configuration file that will -allow the user to specific resources only. +General design permits one administrator and many users. For each +user it is possible to define a unique bconsole configuration file that will +allow the user access to specific resources only. -Resources limitation is realized by Bacula Restricted Consoles functionality. +Resources limitation is realized by using Bacula Restricted Consoles +functionality. Before using customized and restricted consoles with Baculum please check -location for bconsole configuration files for each user. To do it, there -is need to run configuration wizard and then to go to "Console" wizard step +the location for bconsole configuration files for each user. To do so, +please run the configuration wizard and then to go to "Console" wizard step (fourth step). -In "Console" wizard step there is field "Bconsole custom config file path". -In this field there is required to define location for restricted consoles. -In defined path exists keyword \textbf{\{user\}}. The keyword will be replaced -into currently logged in username. +In the "Console" wizard step there is a field "Bconsole custom config file +path". In this field you must define a location for restricted +consoles. In the defined path exists keyword \textbf{\{user\}}. +During login, Baculum will replace this keyword with the logged in +username. This permits using a single directory which contains +a different bconsole-xxx.conf for each user (where xxx is replaced by the +user login name. -For example, if there is logged user named "john", keyword \{user\} will be -replaced into "john". +For example, if there the user named "john", is logging in, Baculum +will replace the keyword \{user\} with {\bf john}. Example: @@ -386,23 +432,25 @@ Example: /usr/local/bacula/etc/bconsole-{user}.conf \end{verbatim} -After login user "john" to Baculum webGUI, for each bconsole request will be -used file: +Thus for user "john", Baculum will use the following file for +each access to bconsole: \begin{verbatim} /usr/local/bacula/etc/bconsole-john.conf \end{verbatim} -It makes available to define some specific Console access (or restricted +The permits defining user specific Console access (or restricted access) for each Baculum user. -Note that users are possible to create from Baculum web interface but bconsole -configuration files are not. From this reason please prepare bconsole -configuration files for each regular (not administrator) user self and check -access by logging in to Baculum as the new user. +Note that it is possible to create users and which bconsole file +will be accessed using Baculum, but it is not currently possible +to use Baculum to create the bconsole configuration files. +For this reason please prepare +bconsole configuration files for each regular (non-administrator) user +and check the access by logging in to Baculum as the new user. -For proper Baculum working some Bconsole commands are necessary. They are -commands: +For Baculum to work work correctly some Bconsole commands are necessary. +They are: \begin{itemize} \item show @@ -441,14 +489,24 @@ Console { \section{Screenshots} -\includegraphics{baculum01.png} +\includegraphics[width=\linewidth]{baculum01.png} + +\smallskip + +\includegraphics[width=\linewidth]{baculum02.png} + +\smallskip + +\includegraphics[width=\linewidth]{baculum03.png} + +\smallskip -\includegraphics{baculum02.png} +\includegraphics[width=\linewidth]{baculum04.png} -\includegraphics{baculum03.png} +\smallskip -\includegraphics{baculum04.png} +\includegraphics[width=\linewidth]{baculum05.png} -\includegraphics{baculum05.png} +\smallskip -\includegraphics{baculum06.png} +\includegraphics[width=\linewidth]{baculum06.png} diff --git a/docs/manuals/en/console/license.tex b/docs/manuals/en/console/license.tex index 86049a8..f1e0de1 100644 --- a/docs/manuals/en/console/license.tex +++ b/docs/manuals/en/console/license.tex @@ -32,7 +32,7 @@ at \elink{http://www.bacula.org}{http://www.bacula.org}. The vast bulk of the source code is released under the \ilink{Affero GNU General Public License version 3.}{GplChapter}. -Most of this code is copyrighted: Copyright \copyright 2000-2015 +Most of this code is copyrighted: Copyright \copyright 2000-2016, Kern Sibbald. Portions may be copyrighted by other people. These files are released @@ -74,8 +74,8 @@ and if you are submitting code, you should fill it out then sent to: \begin{quote} Kern Sibbald \\ - Cotes-de-Montmoiret 9 \\ - 1012 Lausanne \\ + Sentier du Lycee 1 \\ + 1009 Pully \\ Switzerland \\ \end{quote} diff --git a/docs/manuals/en/console/web.makefile b/docs/manuals/en/console/web.makefile index 12402a9..610675f 100644 --- a/docs/manuals/en/console/web.makefile +++ b/docs/manuals/en/console/web.makefile @@ -10,7 +10,7 @@ HTML_TITLE="Console and Operators Guide" HTML_DEPTH=3 HTML_TITLES=6 HTML_VERSION=4.0 -LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 +LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file ./latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 .SUFFIXES: .tex .html .PHONY: @@ -44,9 +44,9 @@ clean: web: pngimages @echo "Making web" - @rm -f next.png prev.png up.png + @rm -f next.png prev.png up.png @rm -f ${DOC}/xp-*.png - @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png + @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png @${LATEX_TO_HTML} @cp -f ${DOC}/${MAINDOC} ${DOC}/index.html @echo "Done making web" diff --git a/docs/manuals/en/developers/license.tex b/docs/manuals/en/developers/license.tex index daee9ba..34bd8fe 100644 --- a/docs/manuals/en/developers/license.tex +++ b/docs/manuals/en/developers/license.tex @@ -32,8 +32,8 @@ at \elink{http://www.bacula.org}{http://www.bacula.org}. The vast bulk of the source code is released under the \ilink{Affero GNU General Public License version 3.}{GplChapter}. -Most of this code is copyrighted: Copyright \copyright 2000-2014 -Free Software Foundation Europe e.V. +Most of this code is copyrighted: Copyright \copyright 2000-2016, +Kern Sibbald. Portions may be copyrighted by other people. These files are released under different licenses which are compatible with the Bacula AGPLv3 license. diff --git a/docs/manuals/en/developers/platformsupport.tex b/docs/manuals/en/developers/platformsupport.tex index 5832044..f2b67e5 100644 --- a/docs/manuals/en/developers/platformsupport.tex +++ b/docs/manuals/en/developers/platformsupport.tex @@ -65,7 +65,7 @@ Ideal requirements for a test machine: \begin{itemize} \item The principal developer will have non-root ssh access to the test machine at all times. -\item The pricipal developer will have a root password. +\item The principal developer will have a root password. \item The test machine will provide approximately 200 MB of disk space for continual use. \item The test machine will have approximately 500 MB of free @@ -83,7 +83,7 @@ Minimum requirements for a test machine: \begin{itemize} \item The principal developer will have non-root ssh access to the test machine when requested approximately once a month. -\item The pricipal developer not have root access. +\item The principal developer not have root access. \item The test machine will provide approximately 80 MB of disk space for continual use. \item The test machine will have approximately 300 MB of free @@ -101,7 +101,7 @@ Bare bones test machine requirements: \begin{itemize} \item The test machine is available only to a designated test person (your own machine). -\item The designated test person runs the regession +\item The designated test person runs the regression tests on demand. \item The test machine has a tape drive available. \end{itemize} diff --git a/docs/manuals/en/developers/web.makefile b/docs/manuals/en/developers/web.makefile index 813c6f8..6d3aecf 100644 --- a/docs/manuals/en/developers/web.makefile +++ b/docs/manuals/en/developers/web.makefile @@ -7,7 +7,7 @@ HTML_TITLE="Developer's Guide" HTML_DEPTH=3 HTML_TITLES=6 HTML_VERSION=4.0 -LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 +LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file ./latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 .SUFFIXES: .tex .html .PHONY: @@ -42,9 +42,9 @@ clean: web: pngimages @echo "Making web" - @rm -f next.png prev.png up.png + @rm -f next.png prev.png up.png @rm -f ${DOC}/xp-*.png - @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png + @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png @${LATEX_TO_HTML} @cp -f ${DOC}/${MAINDOC} ${DOC}/index.html @echo "Done making web" diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex index 3675b94..2293665 100644 --- a/docs/manuals/en/main/dirdconf.tex +++ b/docs/manuals/en/main/dirdconf.tex @@ -2246,18 +2246,18 @@ console run command. This directive is required. keep File records in the Catalog database after the End time of the Job corresponding to the File records. When this time period expires, and if - {\bf AutoPrune} is set to {\bf yes} Bacula will prune (remove) File records - that are older than the specified File Retention period. Note, this affects - only records in the catalog database. It does not affect your archive - backups. - - File records may actually be retained for a shorter period than you specify - on this directive if you specify either a shorter {\bf Job Retention} or a - shorter {\bf Volume Retention} period. The shortest retention period of the - three takes precedence. The time may be expressed in seconds, minutes, - hours, days, weeks, months, quarters, or years. See the - \ilink{Configuration chapter}{Time} of this manual for - additional details of time specification. + {\bf AutoPrune} is set to {\bf yes} Bacula will prune (remove) File + records that are older than the specified File Retention period. Note, + this affects only records in the catalog database. It does not affect + your archive backups. + + File records may actually be retained for a shorter period than you + specify on this directive if you specify either a shorter {\bf Job + Retention} or a shorter {\bf Volume Retention} period. The shortest + retention period of the three takes precedence. The time may be + expressed in seconds, minutes, hours, days, weeks, months, quarters, or + years. See the \ilink{Configuration chapter}{Time} of this manual for + additional details of time specification. The default is 60 days. @@ -2834,27 +2834,37 @@ The Pool Resource defined in the Director's configuration file \item [Volume Retention = \lt{}time-period-specification\gt{}] \index[dir]{Volume Retention} \index[dir]{Directive!Volume Retention} - The Volume Retention directive defines the length of time that {\bf - Bacula} will keep records associated with the Volume in - the Catalog database after the End time of each Job written to the - Volume. When this time period expires, and if {\bf AutoPrune} is set to - {\bf yes} Bacula may prune (remove) Job records that are older than the - specified Volume Retention period if it is necessary to free up a - Volume. Recycling will not occur until it is absolutely necessary to + The Volume Retention directive defines the longest amount of time that + {\bf Bacula} will keep records associated with the Volume in the Catalog + database after the End time of each Job written to the Volume. When + this time period expires, and if {\bf AutoPrune} is set to {\bf yes} + Bacula may prune (remove) Job records that are older than the specified + Volume Retention period if it is necessary to free up a Volume. Note, + it is also possible for all the Job and File records to be pruned before + the Volume Retention period is reached. In that case the Volume can + then be marked Pruned and subsequently recycled prior to expiration of + the Volume Retention period. + +\smallskip + Recycling will not occur until it is absolutely necessary to free up a volume (i.e. no other writable volume exists). All File records associated with pruned Jobs are also pruned. The time may be specified as seconds, minutes, hours, days, weeks, months, quarters, or years. The {\bf Volume Retention} is applied independently of the {\bf Job Retention} and the {\bf File Retention} periods defined in the Client resource. This means that all - the retentions periods are applied in turn and that the shorter period + the retention periods are applied in turn and that the shorter period is the one that effectively takes precedence. Note, that when the {\bf Volume Retention} period has been reached, and it is necessary to obtain - a new volume, Bacula will prune both the Job and the File records. This - pruning could also occur during a {\bf status dir} command because it - uses similar algorithms for finding the next available Volume. + a new volume, Bacula will prune both the Job and the File records. And + the inverse is also true that if all the Job and File records that + refer to a Volume are pruned, then the Volume may be pruned and recycled + regardless of its retention period. Pruning may also occur during a + {\bf status dir} command because it uses similar algorithms for finding + the next available Volume. It is important to know that when the Volume Retention period expires, + or all the Job and File records have been pruned that refer to a Volume, Bacula does not automatically recycle a Volume. It attempts to keep the Volume data intact as long as possible before over writing the Volume. diff --git a/docs/manuals/en/main/disk.tex b/docs/manuals/en/main/disk.tex index 7bca3ad..4a70120 100644 --- a/docs/manuals/en/main/disk.tex +++ b/docs/manuals/en/main/disk.tex @@ -234,14 +234,14 @@ records. \index[general]{Recycling!Restricting the Number of Volumes and Recycling} \index[general]{Restricting the Number of Volumes and Recycling} -Automatic labeling discussed above brings up the problem of Volume management. -With the above scheme, a new Volume will be created every day. If you have not -specified Retention periods, your Catalog will continue to fill keeping track -of all the files Bacula has backed up, and this procedure will create one new -archive file (Volume) every day. +Automatic labeling discussed above brings up the problem of Volume +management. With the above scheme, a new Volume will be created every day. +If you have not specified Retention periods, your Catalog will continue to +fill keeping track of all the files Bacula has backed up, and this +procedure will create one new archive file (Volume) every day. -The tools Bacula gives you to help automatically manage these problems are the -following: +The tools Bacula gives you to help automatically manage these problems are +the following: \begin{enumerate} \item Catalog file record retention periods, the @@ -287,10 +287,10 @@ Catalog, and they are discussed in detail in the \ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of this manual. -Volume Retention, AutoPrune, and Recycle determine how long Bacula will keep -your Volumes before reusing them, and they are also discussed in detail in the -\ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of -this manual. +Volume Retention, AutoPrune, and Recycle determine how long Bacula will +keep your Volumes before reusing them, and they are also discussed in +detail in the \ilink{Automatic Volume Recycling}{RecyclingChapter} chapter +of this manual. The Maximum Volumes record can also be used in conjunction with the Volume Retention period to limit the total number of archive Volumes (files) that diff --git a/docs/manuals/en/main/license.tex b/docs/manuals/en/main/license.tex index 944478c..d06ea2d 100644 --- a/docs/manuals/en/main/license.tex +++ b/docs/manuals/en/main/license.tex @@ -32,8 +32,8 @@ at \elink{http://www.bacula.org}{http://www.bacula.org}. The vast bulk of the source code is released under the \ilink{Affero GNU General Public License version 3.}{GplChapter}. -Most of this code is copyrighted: Copyright \copyright 2000-2014 -Free Software Foundation Europe e.V. +Most of this code is copyrighted: Copyright \copyright 2000-2016, +Kern Sibbald. Portions may be copyrighted by other people. These files are released under different licenses which are compatible with the Bacula AGPLv3 license. @@ -74,8 +74,8 @@ and if you are submitting code, you should fill it out then sent to: \begin{quote} Kern Sibbald \\ - Cotes-de-Montmoiret 9 \\ - 1012 Lausanne \\ + Sentier du Lycee 1 \\ + 1009 Pully \\ Switzerland \\ \end{quote} diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex index 1c0e332..7cb823c 100644 --- a/docs/manuals/en/main/newfeatures.tex +++ b/docs/manuals/en/main/newfeatures.tex @@ -1119,10 +1119,10 @@ by Bacula Systems. \subsection{Changes in the Pruning Algorithm} -We rewrote the job pruning algorithm in this version. Previously, in some users -reported that the pruning process at the end of jobs was very long. It should -not be longer the case. Now, Bacula won't prune automatically a Job if this -particular Job is needed to restore data. Example: +We rewrote the job pruning algorithm in this version. Previously, in some +users reported that the pruning process at the end of jobs was very long. +It should not be longer the case. Now, Bacula won't prune automatically a +Job if this particular Job is needed to restore data. Example: \begin{verbatim} JobId: 1 Level: Full @@ -1137,9 +1137,10 @@ resource causes that Jobs with Jobid in 1,2,3,4 can be pruned, Bacula will detect that JobId 1 and 4 are essential to restore data at the current state and will prune only JobId 2 and 3. -\texttt{Important}, this change affect only the automatic pruning step after a -Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the -\texttt{VolumeRetention} period, important jobs can be pruned. +\texttt{Important}, this change affect only the automatic pruning step +after a Job and the \texttt{prune jobs} Bconsole command. If a volume +expires after the \texttt{VolumeRetention} period, important jobs can be +pruned. \subsection{Ability to Verify any specified Job} You now have the ability to tell Bacula which Job should verify instead of diff --git a/docs/manuals/en/main/recycling.tex b/docs/manuals/en/main/recycling.tex index fec78c6..d842218 100644 --- a/docs/manuals/en/main/recycling.tex +++ b/docs/manuals/en/main/recycling.tex @@ -42,15 +42,20 @@ records are: The above three directives are all you need assuming that you fill each of your Volumes then wait the Volume Retention period before -reusing them. If you want Bacula to stop using a Volume and recycle +reusing them, providing there is some non-pruned Jobs or Files on the +Volume. + +If you want Bacula to stop using a Volume and recycle it before it is full, you will need to use one or more additional directives such as: + \begin{itemize} \item Use Volume Once = yes \item Volume Use Duration = ttt \item Maximum Volume Jobs = nnn \item Maximum Volume Bytes = mmm \end{itemize} + Please see below and the \ilink{Basic Volume Management}{DiskChapter} chapter of this manual for more complete examples. @@ -61,29 +66,35 @@ search the Pool for any Volumes with the {\bf Recycle} flag set and the Volume Status is {\bf Purged}. At that point, it will choose the oldest purged volume and recycle it. -If there are no volumes with Status {\bf Purged}, then -the recycling occurs in two steps: +If there are no volumes with Status {\bf Purged}, then the recycling occurs +in two steps: + +\smallskip The first is that the Catalog for a Volume must be pruned of all Jobs (i.e. -Purged). Files contained on that Volume, and the second step is the actual -recycling of the Volume. Only Volumes marked {\bf Full} or {\bf Used} will -be considerd for pruning. The Volume will be purged if the VolumeRetention -period has expired. When a Volume is marked as Purged, it means that no -Catalog records reference that Volume, and the Volume can be recycled. -Until recycling actually occurs, the Volume data remains intact. If no -Volumes can be found for recycling for any of the reasons stated above, -Bacula will request operator intervention (i.e. it will ask you to label a -new volume). - -A key point mentioned above, that can be a source of frustration, is that Bacula -will only recycle purged Volumes if there is no other appendable Volume -available, otherwise, it will always write to an appendable Volume before -recycling even if there are Volume marked as Purged. This preserves your data -as long as possible. So, if you wish to "force" Bacula to use a purged -Volume, you must first ensure that no other Volume in the Pool is marked {\bf -Append}. If necessary, you can manually set a volume to {\bf Full}. The reason -for this is that Bacula wants to preserve the data on your old tapes (even -though purged from the catalog) as long as absolutely possible before -overwriting it. There are also a number of directives such as +Purged) and Files contained on that Volume. + +\smallskip +The second step is the actual recycling of the Volume. Only Volumes marked +{\bf Full} or {\bf Used} will be considerd for pruning. The Volume will be +purged if the VolumeRetention period has expired. When a Volume is marked +as Purged, it means that no Catalog records reference that Volume, and the +Volume can be recycled and reused even though the Volume Retention period +has not expired. Until recycling actually occurs, the Volume data remains +intact. If no Volumes can be found for recycling for any of the reasons +stated above, Bacula will request operator intervention (i.e. it will ask +you to label a new volume). + +A key point mentioned above, that can be a source of frustration, is that +Bacula will only recycle purged Volumes if there is no other appendable +Volume available, otherwise, it will always write to an appendable Volume +before recycling even if there are Volume marked as Purged. This preserves +your data as long as possible. So, if you wish to "force" Bacula to use a +purged Volume, you must first ensure that no other Volume in the Pool is +marked {\bf Append}. If necessary, you can manually set a volume to {\bf +Full}. The reason for this is that Bacula wants to preserve the data on +your old tapes (even though purged from the catalog) as long as absolutely +possible before overwriting it. There are also a number of directives such +as {\bf Volume Use Duration} that will automatically mark a volume as {\bf Used} and thus no longer appendable. @@ -99,18 +110,20 @@ backup, and helps you locate files on past backups when you want to restore something. However, the catalog will grow larger and larger as time goes on, and eventually it can become unacceptably large. -Bacula's process for removing entries from the catalog is called Pruning. The -default is Automatic Pruning, which means that once an entry reaches a certain -age (e.g. 30 days old) it is removed from the catalog. Note that Job records -that are required for current restore won't be removed automatically, and File -records are needed for VirtualFull and Accurate backups. Once a job has been -pruned, you can still restore it from the backup tape, but one additional step -is required: scanning the volume with bscan. The alternative to Automatic -Pruning is Manual Pruning, in which you explicitly tell Bacula to erase the -catalog entries for a volume. You'd usually do this when you want to reuse a -Bacula volume, because there's no point in keeping a list of files that USED TO -BE on a tape. Or, if the catalog is starting to get too big, you could prune -the oldest jobs to save space. Manual pruning is done with the +Bacula's process for removing entries from the catalog is called Pruning. +The default is Automatic Pruning, which means that once a Job record +reaches a certain age (e.g. 30 days old) and a pruning occurs, it will be +removed from the catalog. Note that Job records that are required for +current restore won't be removed automatically, and File records are needed +for VirtualFull and Accurate backups. Once a job has been pruned, you can +still restore it from the backup Volume, provided that the Volume has not +been recycled, but one additional step is required: scanning the volume +with bscan. The alternative to Automatic Pruning is Manual Pruning, in +which you explicitly tell Bacula to erase the catalog entries for a volume. +You'd usually do this when you want to reuse a Bacula volume, because +there's no point in keeping a list of files that USED TO BE on a volume. +Or, if the catalog is starting to get too big, you could prune the oldest +jobs to save space. Manual pruning is done with the \borgxrlink{prune}{ManualPruning}{console}{command} in the \consoleman{} (thanks to Bryce Denney for the above explanation). @@ -118,13 +131,13 @@ the oldest jobs to save space. Manual pruning is done with the \index[general]{Pruning Directives } \index[general]{Directives!Pruning } -There are three pruning durations. All apply to catalog database records and -not to the actual data in a Volume. The pruning (or retention) durations are -for: Volumes (Media records), Jobs (Job records), and Files (File records). -The durations inter-depend a bit because if Bacula prunes a Volume, it -automatically removes all the Job records, and all the File records. Also when -a Job record is pruned, all the File records for that Job are also pruned -(deleted) from the catalog. +There are three pruning durations. All apply to catalog database records +and not to the actual data in a Volume. The pruning (or retention) +durations are for: Volumes (Media records), Jobs (Job records), and Files +(File records). The durations inter-depend a bit because if Bacula prunes +a Volume, it automatically removes all the Job records, and all the File +records. Also when a Job record is pruned, all the File records for that +Job are also pruned (deleted) from the catalog. Having the File records in the database means that you can examine all the files backed up for a particular Job. They take the most space in the catalog @@ -181,15 +194,21 @@ volume. The Pool records that control the pruning are described below. \index[console]{Volume Retention} The Volume Retention record defines the length of time that Bacula will guarantee that the Volume is not reused counting from the time the last - job stored on the Volume terminated. A key point is that this time + job stored on the Volume terminated, providing that all the File records + on the Volume have not been pruned. A key point is that this time period is not even considered as long at the Volume remains appendable. The Volume Retention period count down begins only when the Append status has been changed to some othe status (Full, Used, Purged, ...). + Note, when all the File records have been removed that are on the + Volume, the Volume will marked Purged (i.e. it has no more valid + Files stored on it), and the Volume may be recycled even if the Volume + Retention period has not expired. When this time period expires, and if {\bf AutoPrune} is set to {\bf yes}, and a new Volume is needed, but no appendable Volume is available, Bacula will prune (remove) Job records that are older than the specified - Volume Retention period. + Volume Retention period even if the Job or File retention has not been + reached. The Volume Retention period takes precedence over any Job Retention period you have specified in the Client resource. It should also be @@ -272,9 +291,9 @@ items. with the lowest MediaId is chosen). \item Try recycling any purged Volumes. \item Prune volumes applying Volume retention period (Volumes with VolStatus - Full, Used, or Append are pruned). Note, even if all the File and Job - records are pruned from a Volume, the Volume will not be marked Purged - until the Volume retention period expires. + Full, Used, or Append are pruned). Note, when all the File and Job + records are pruned from a Volume, the Volume may be marked Purged + prior to the expiration of the Volume retention period. \item Search the Pool for a Volume with VolStatus=Purged \item If a Pool named "Scratch" exists, search for a Volume and if found move it to the current Pool for the Job and use it. Note, when @@ -284,9 +303,8 @@ items. \item If we were looking for Volumes in the Autochanger, go back to step 2 above, but this time, look for any Volume whether or not it is in the Autochanger. -\item Attempt to create a new Volume if automatic labeling enabled - If Python is enabled, a Python NewVolume event is generated before - the Label Format directve is used. If the maximum number of Volumes +\item Attempt to create a new Volume if automatic labeling is enabled. + However, if the maximum number of Volumes specified for the pool is reached, a new Volume will not be created. \item Prune the oldest Volume if RecycleOldestVolume=yes (the Volume with the oldest LastWritten date and VolStatus equal to Full, Recycle, Purged, Used, @@ -365,15 +383,15 @@ Volume. For example in the following output from {\bf list volumes}: \end{verbatim} \normalsize -all the volumes are marked as recyclable, and the last Volume, {\bf File0007} -has been purged, so it may be immediately recycled. The other volumes are all -marked recyclable and when their Volume Retention period (14400 seconds or four -hours) expires, they will be eligible for pruning, and possibly recycling. -Even though Volume {\bf File0007} has been purged, all the data on the Volume -is still recoverable. A purged Volume simply means that there are no entries -in the Catalog. Even if the Volume Status is changed to {\bf Recycle}, the -data on the Volume will be recoverable. The data is lost only when the Volume -is re-labeled and re-written. +all the volumes are marked as recyclable, and the last Volume, {\bf +File0007} has been purged, so it may be immediately recycled. The other +volumes are all marked recyclable and when their Volume Retention period +(14400 seconds or four hours) expires, they will be eligible for pruning, +and possibly recycling. Even though Volume {\bf File0007} has been purged, +all the data on the Volume is still recoverable. A purged Volume simply +means that there are no entries in the Catalog. Even if the Volume Status +is changed to {\bf Recycle}, the data on the Volume will be recoverable. +The data is lost only when the Volume is re-labeled and re-written. To modify Volume {\bf File0001} so that it cannot be recycled, you use the {\bf update volume pool=File} command in the console program, or simply {\bf @@ -428,14 +446,15 @@ A typical volume life cycle is like this: \index[general]{Making Bacula Use a Single Tape} Most people will want Bacula to fill a tape and when it is full, a new tape -will be mounted, and so on. However, as an extreme example, it is possible for -Bacula to write on a single tape, and every night to rewrite it. To get this -to work, you must do two things: first, set the VolumeRetention to less than -your save period (one day), and the second item is to make Bacula mark the -tape as full after using it once. This is done using {\bf UseVolumeOnce = -yes}. If this latter record is not used and the tape is not full after the -first time it is written, Bacula will simply append to the tape and eventually -request another volume. Using the tape only once, forces the tape to be marked +will be mounted, and so on. However, as an extreme example, it is possible +for Bacula to write on a single tape, and every night to rewrite it. To +get this to work, you must do two things: first, set the VolumeRetention to +less than your save period (one day), and the second item is to make Bacula +mark the tape as full after using it once. This is done using {\bf +UseVolumeOnce = yes}. If this latter record is not used and the tape is +not full after the first time it is written, Bacula will simply append to +the tape and eventually request another volume. Using the tape only once, +forces the tape to be marked {\bf Full} after each use, and the next time {\bf Bacula} runs, it will recycle the tape. diff --git a/docs/manuals/en/main/web.makefile b/docs/manuals/en/main/web.makefile index 5a20d52..fff6ccf 100644 --- a/docs/manuals/en/main/web.makefile +++ b/docs/manuals/en/main/web.makefile @@ -7,7 +7,7 @@ HTML_TITLE="Main Reference" HTML_DEPTH=3 HTML_TITLES=6 HTML_VERSION=4.0 -LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 +LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file ./latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 .SUFFIXES: .tex .html .PHONY: @@ -41,9 +41,9 @@ clean: web: pngimages @echo "Making web" - @rm -f next.png prev.png up.png + @rm -f next.png prev.png up.png @rm -f ${DOC}/xp-*.png - @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png + @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png @${LATEX_TO_HTML} @cp -f ${DOC}/${MAINDOC} ${DOC}/index.html @echo "Done making web" diff --git a/docs/manuals/en/misc/license.tex b/docs/manuals/en/misc/license.tex index daee9ba..34bd8fe 100644 --- a/docs/manuals/en/misc/license.tex +++ b/docs/manuals/en/misc/license.tex @@ -32,8 +32,8 @@ at \elink{http://www.bacula.org}{http://www.bacula.org}. The vast bulk of the source code is released under the \ilink{Affero GNU General Public License version 3.}{GplChapter}. -Most of this code is copyrighted: Copyright \copyright 2000-2014 -Free Software Foundation Europe e.V. +Most of this code is copyrighted: Copyright \copyright 2000-2016, +Kern Sibbald. Portions may be copyrighted by other people. These files are released under different licenses which are compatible with the Bacula AGPLv3 license. diff --git a/docs/manuals/en/misc/web.makefile b/docs/manuals/en/misc/web.makefile index 3a5a573..28dd798 100644 --- a/docs/manuals/en/misc/web.makefile +++ b/docs/manuals/en/misc/web.makefile @@ -7,7 +7,7 @@ HTML_TITLE="Miscellaneous Guide" HTML_DEPTH=3 HTML_TITLES=6 HTML_VERSION=4.0 -LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 +LATEX_TO_HTML=latex2html -split ${HTML_DEPTH} -local_icons -t ${HTML_TITLE} -long_titles ${HTML_TITLES} -toc_stars -contents_in_nav -init_file ./latex2html-init.pl -no_antialias -no_antialias_text -white -notransparent ${DOC} -html_version ${HTML_VERSION} >tex.out 2>&1 .SUFFIXES: .tex .html @@ -43,9 +43,9 @@ clean: web: pngimages @echo "Making web" - @rm -f next.png prev.png up.png + @rm -f next.png prev.png up.png @rm -f ${DOC}/xp-*.png - @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png + @rm -f ${DOC}/next.png ${DOC}/prev.png ${DOC}/up.png @${LATEX_TO_HTML} @cp -f ${DOC}/${MAINDOC} ${DOC}/index.html @echo "Done making web" diff --git a/docs/manuals/en/problems/license.tex b/docs/manuals/en/problems/license.tex index daee9ba..34bd8fe 100644 --- a/docs/manuals/en/problems/license.tex +++ b/docs/manuals/en/problems/license.tex @@ -32,8 +32,8 @@ at \elink{http://www.bacula.org}{http://www.bacula.org}. The vast bulk of the source code is released under the \ilink{Affero GNU General Public License version 3.}{GplChapter}. -Most of this code is copyrighted: Copyright \copyright 2000-2014 -Free Software Foundation Europe e.V. +Most of this code is copyrighted: Copyright \copyright 2000-2016, +Kern Sibbald. Portions may be copyrighted by other people. These files are released under different licenses which are compatible with the Bacula AGPLv3 license. diff --git a/docs/manuals/en/problems/tapetesting.tex b/docs/manuals/en/problems/tapetesting.tex index 31ad503..994204d 100644 --- a/docs/manuals/en/problems/tapetesting.tex +++ b/docs/manuals/en/problems/tapetesting.tex @@ -650,8 +650,43 @@ module is being removed because the kernel deems it idle. This is done via remove this entry from {\bf crontab}, or you can manually {\bf modprob} your driver module (or add it to the local startup script). Thanks to Alan Brown for this tip. -\label{IncorrectFiles} +\smallskip +Sometimes the tape handler gets confused. This can happen if your tape +drive door is locked (Bacula locks it when writing a tape), and Bacula +crashes or some other problem occurs. After this kind of a problem, +the kernel driver will not recognize that a tape is loaded and you +may see messages such as: + +\footnotesize +\begin{verbatim} +19-Sep 16:39 groschat-sd JobId 16072: Warning: mount.c:219 Open of tape +device "LTO4-Drive" (/dev/tape/by-id/scsi-3500143801403cf22-nst) Volume +"AAJ372" failed: ERR=tape_dev.c:162 Unable to open device "LTO4-Drive" +(/dev/tape/by-id/scsi-3500143801403cf22-nst): ERR=No medium found + +19-Sep 16:39 groschat-sd JobId 16072: Please mount append Volume "AAJ372" +or label a new one for: + Job: Rufus.2016-09-19_16.34.22_03 + Storage: "LTO4-Drive" (/dev/tape/by-id/scsi-3500143801403cf22-nst) + Pool: Default + Media type: LTO-4 +\end{verbatim} +\normalsize + +in that case, the best thing to do is unload the tape by hand with: + +\begin{verbatim} +(stop Bacula) +mtx -f /dev/sgx unload +(restart Bacula) +\end{verbatim} + +where you replace /dev/sgx by your scsi control device name. + + + +\label{IncorrectFiles} \subsection{Incorrect File Number} \index[general]{Number!Incorrect File} \index[general]{Incorrect File Number} diff --git a/docs/manuals/en/problems/web.makefile b/docs/manuals/en/problems/web.makefile index f6ea2ad..64ececf 100644 --- a/docs/manuals/e... [truncated message content] |