From 012671a1801d9dcf2b6051671254999714844325 Mon Sep 17 00:00:00 2001 From: Joerg Steffens Date: Thu, 12 Sep 2013 09:52:21 +0200 Subject: [PATCH] remove trailing spaces from index Signed-off-by: Marco van Wieringen --- manuals/en/main/autochangers.tex | 46 +++++++++--------- manuals/en/main/bootstrap.tex | 4 +- manuals/en/main/catmaintenance.tex | 50 +++++++++---------- manuals/en/main/configure.tex | 24 +++++----- manuals/en/main/critical.tex | 12 ++--- manuals/en/main/dirdconf-fileset.tex | 16 +++---- manuals/en/main/disk.tex | 20 ++++---- manuals/en/main/general.tex | 60 +++++++++++------------ manuals/en/main/main.tex | 10 ++-- manuals/en/main/mysql.tex | 20 ++++---- manuals/en/main/postgresql.tex | 20 ++++---- manuals/en/main/quickstart.tex | 24 +++++----- manuals/en/main/requirements.tex | 4 +- manuals/en/main/restore.tex | 22 ++++----- manuals/en/main/security.tex | 2 +- manuals/en/main/spooling.tex | 12 ++--- manuals/en/main/sqlite.tex | 20 ++++---- manuals/en/main/storedconf.tex | 4 +- manuals/en/main/supporteddrives.tex | 16 +++---- manuals/en/main/tls.tex | 4 +- manuals/en/main/tutorial.tex | 72 ++++++++++++++-------------- manuals/en/main/verify.tex | 2 +- 22 files changed, 232 insertions(+), 232 deletions(-) diff --git a/manuals/en/main/autochangers.tex b/manuals/en/main/autochangers.tex index db6839d..a341345 100644 --- a/manuals/en/main/autochangers.tex +++ b/manuals/en/main/autochangers.tex @@ -3,8 +3,8 @@ \chapter{Autochanger Support} \label{AutochangersChapter} -\index[general]{Support!Autochanger } -\index[general]{Autochanger Support } +\index[general]{Support!Autochanger} +\index[general]{Autochanger Support} Bareos provides autochanger support for reading and writing tapes. In order to work with an autochanger, Bareos requires a number of things, each of @@ -170,8 +170,8 @@ \subsection{FreeBSD} % example directory does not exist: % \label{scripts} % \section{Example Scripts} -% \index[general]{Scripts!Example } -% \index[general]{Example Scripts } +% \index[general]{Scripts!Example} +% \index[general]{Example Scripts} % % Please read the sections below so that you understand how autochangers work % with Bareos. Although we supply a default {\bf mtx-changer} script, your @@ -249,8 +249,8 @@ \section{Multiple Devices} \label{ConfigRecords} \section{Device Configuration Records} -\index[general]{Records!Device Configuration } -\index[general]{Device Configuration Records } +\index[general]{Records!Device Configuration} +\index[general]{Device Configuration Records} Configuration of autochangers within Bareos is done in the Device resource of the Storage daemon. Four records: {\bf Autochanger}, {\bf Changer Device}, @@ -265,12 +265,12 @@ \section{Device Configuration Records} \begin{description} \item [Autochanger = {\it Yes|No} ] - \index[sd]{Autochanger } + \index[sd]{Autochanger} The {\bf Autochanger} record specifies if the current device belongs to an autochanger ressource. The default is {\bf no}. \item [Changer Device = {\textless}device-name{\textgreater}] - \index[sd]{Changer Device } + \index[sd]{Changer Device} In addition to the Archive Device name, you must specify a {\bf Changer Device} name. This is because most autochangers are controlled through a different device than is used for reading and writing the cartridges. For @@ -291,7 +291,7 @@ \section{Device Configuration Records} device. \item [Changer Command = {\textless}command{\textgreater}] - \index[sd]{Changer Command } + \index[sd]{Changer Command} This record is used to specify the external program to call and what arguments to pass to it. The command is assumed to be a standard program or shell script that can be executed by the operating system. This command is @@ -328,7 +328,7 @@ \section{Device Configuration Records} output expected by Bareos are given in the \ilink{Bareos Autochanger Interface}{autochanger-interface} section. \item [Maximum Changer Wait = {\textless}time{\textgreater}] - \index[sd]{Maximum Changer Wait } + \index[sd]{Maximum Changer Wait} This record is used to define the maximum amount of time that Bareos will wait for an autoloader to respond to a command (e.g. load). The default is set to 120 seconds. If you have a slow autoloader you may @@ -338,7 +338,7 @@ \section{Device Configuration Records} and Bareos will request operator intervention. \item [Drive Index = {\textless}number{\textgreater}] - \index[sd]{Drive Index } + \index[sd]{Drive Index} This record allows you to tell Bareos to use the second or subsequent drive in an autochanger with multiple drives. Since the drives are numbered from zero, the second drive is defined by @@ -360,8 +360,8 @@ \section{Device Configuration Records} \label{example} \section{An Example Configuration File} -\index[general]{Example Configuration File } -\index[general]{File!Example Configuration } +\index[general]{Example Configuration File} +\index[general]{File!Example Configuration} The following two resources implement an autochanger: @@ -391,7 +391,7 @@ \section{An Example Configuration File} system. \section{A Multi-drive Example Configuration File} -\index[general]{Multi-drive Example Configuration File } +\index[general]{Multi-drive Example Configuration File} The following resources implement a multi-drive autochanger: @@ -434,8 +434,8 @@ \section{A Multi-drive Example Configuration File} \section{Specifying Slots When Labeling} -\index[general]{Specifying Slots When Labeling } -\index[general]{Labeling!Specifying Slots When } +\index[general]{Specifying Slots When Labeling} +\index[general]{Labeling!Specifying Slots When} \label{SpecifyingSlots} If you add an {\bf Autochanger = yes} record to the Storage resource in your @@ -486,7 +486,7 @@ \section{Specifying Slots When Labeling} \section{Changing Cartridges} -\index[general]{Changing Cartridges } +\index[general]{Changing Cartridges} If you wish to insert or remove cartridges in your autochanger or you manually run the {\bf mtx} program, you must first tell Bareos to release the autochanger by doing: @@ -565,8 +565,8 @@ \section{Dealing with Multiple Magazines} \hide{ % unwanted, commented out \section{Simulating Barcodes in your Autochanger} -\index[general]{Autochanger!Simulating Barcodes in your } -\index[general]{Simulating Barcodes in your Autochanger } +\index[general]{Autochanger!Simulating Barcodes in your} +\index[general]{Simulating Barcodes in your Autochanger} \label{simulating} You can simulate barcodes in your autochanger by making the {\bf mtx-changer} @@ -919,8 +919,8 @@ \section{Using the Autochanger} \section{Barcode Support} -\index[general]{Support!Barcode } -\index[general]{Barcode Support } +\index[general]{Support!Barcode} +\index[general]{Barcode Support} \label{Barcodes} Bareos provides barcode support with two Console commands, {\bf label @@ -966,8 +966,8 @@ \section{Use bconsole to display Autochanger content} \section{Bareos Autochanger Interface} -\index[general]{Interface!Bareos Autochanger } -\index[general]{Bareos Autochanger Interface } +\index[general]{Interface!Bareos Autochanger} +\index[general]{Bareos Autochanger Interface} \label{autochanger-interface} Bareos calls the autochanger script that you specify on the {\bf Changer diff --git a/manuals/en/main/bootstrap.tex b/manuals/en/main/bootstrap.tex index 7194d32..bd0bd8c 100644 --- a/manuals/en/main/bootstrap.tex +++ b/manuals/en/main/bootstrap.tex @@ -173,11 +173,11 @@ \section{Bootstrap File Format} This value is optional and not used by Bareos to restore files. % \item [*JobType] -% \index[general]{*JobType } +% \index[general]{*JobType} % Not yet implemented. % % \item [*JobLevel] -% \index[general]{*JobLevel } +% \index[general]{*JobLevel} % Not yet implemented. \end{description} diff --git a/manuals/en/main/catmaintenance.tex b/manuals/en/main/catmaintenance.tex index c39228f..0bfb257 100644 --- a/manuals/en/main/catmaintenance.tex +++ b/manuals/en/main/catmaintenance.tex @@ -3,8 +3,8 @@ \chapter{Catalog Maintenance} \label{CatMaintenanceChapter} -\index[general]{Maintenance!Catalog } -\index[general]{Catalog Maintenance } +\index[general]{Maintenance!Catalog} +\index[general]{Catalog Maintenance} Without proper setup and maintenance, your Catalog may continue to grow indefinitely as you run Jobs and backup Files, and/or it may become @@ -17,8 +17,8 @@ \chapter{Catalog Maintenance} \section{Setting Retention Periods} -\index[general]{Setting Retention Periods } -\index[general]{Periods!Setting Retention } +\index[general]{Setting Retention Periods} +\index[general]{Periods!Setting Retention} \label{Retention} Bareos uses three Retention periods: the {\bf File Retention} period, @@ -34,7 +34,7 @@ \section{Setting Retention Periods} \begin{description} \item [File Retention = {\textless}time-period-specification{\textgreater}] - \index[general]{File Retention } + \index[general]{File Retention} The File Retention record defines the length of time that Bareos will keep File records in the Catalog database. When this time period expires, and if {\bf AutoPrune} is set to {\bf yes}, Bareos will prune (remove) File records @@ -61,7 +61,7 @@ \section{Setting Retention Periods} The default File retention period is 60 days. \item [Job Retention = {\textless}time-period-specification{\textgreater}] - \index[general]{Job Retention } + \index[general]{Job Retention} The Job Retention record defines the length of time that {\bf Bareos} will keep Job records in the Catalog database. When this time period expires, and if {\bf AutoPrune} is set to {\bf yes} Bareos will prune @@ -87,7 +87,7 @@ \section{Setting Retention Periods} The default Job Retention period is 180 days. \item [AutoPrune = {\textless}yes/no{\textgreater}] - \index[general]{AutoPrune } + \index[general]{AutoPrune} If AutoPrune is set to {\bf yes} (default), Bareos will automatically apply the File retention period and the Job retention period for the Client at the end of the Job. @@ -98,8 +98,8 @@ \section{Setting Retention Periods} \section{MySQL} \label{CompactingMySQL} \subsection{Compacting Your MySQL Database} -\index[general]{Database!Compacting Your MySQL } -\index[general]{Compacting Your MySQL Database } +\index[general]{Database!Compacting Your MySQL} +\index[general]{Compacting Your MySQL Database} \TODO{check cleaner approaches (Sebastian?)} @@ -152,8 +152,8 @@ \subsection{Compacting Your MySQL Database} \label{DatabaseRepair} \label{RepairingMySQL} \subsection{Repairing Your MySQL Database} -\index[general]{Database!Repairing Your MySQL } -\index[general]{Repairing Your MySQL Database } +\index[general]{Database!Repairing Your MySQL} +\index[general]{Repairing Your MySQL Database} If you find that you are getting errors writing to your MySQL database, or Bareos hangs each time it tries to access the database, you should consider @@ -261,8 +261,8 @@ \section{PostgreSQL} \label{RepairingPSQL} \subsection{Repairing Your PostgreSQL Database} -\index[general]{Database!Repairing Your PostgreSQL } -\index[general]{Repairing Your PostgreSQL Database } +\index[general]{Database!Repairing Your PostgreSQL} +\index[general]{Repairing Your PostgreSQL Database} The same considerations apply that are indicated above for MySQL. That is, consult the PostgreSQL documents for how to repair the database, and also @@ -270,8 +270,8 @@ \subsection{Repairing Your PostgreSQL Database} using (see above). \subsection{Compacting Your PostgreSQL Database} -\index[general]{Database!Compacting Your PostgreSQL } -\index[general]{Compacting Your PostgreSQL Database } +\index[general]{Database!Compacting Your PostgreSQL} +\index[general]{Compacting Your PostgreSQL Database} \label{CompactingPostgres} Over time, as noted above, your database will tend to grow. I've noticed that @@ -489,8 +489,8 @@ \subsection{SQLite Indexes} % hidE: sqlite is not supported \hide{ \section{Compacting Your SQLite Database} -\index[general]{Compacting Your SQLite Database } -\index[general]{Database!Compacting Your SQLite } +\index[general]{Compacting Your SQLite Database} +\index[general]{Database!Compacting Your SQLite} First please read the previous section that explains why it is necessary to compress a database. SQLite version 2.8.4 and greater have the {\bf Vacuum} @@ -523,8 +523,8 @@ \section{Compacting Your SQLite Database} } \section{Backing Up Your Bareos Database} -\index[general]{Backing Up Your Bareos Database } -\index[general]{Database!Backing Up Your Bareos } +\index[general]{Backing Up Your Bareos Database} +\index[general]{Database!Backing Up Your Bareos} \label{BackingUpBareos} If ever the machine on which your Bareos database crashes, and you need to @@ -611,8 +611,8 @@ \section{Backing Up Your Bareos Database} \label{BackingUpBareosSecurityConsiderations} \section{Security considerations} -\index[general]{Backing Up Your Bareos Database - Security Considerations } -\index[general]{Database!Backing Up Your Bareos Database - Security Considerations } +\index[general]{Backing Up Your Bareos Database - Security Considerations} +\index[general]{Database!Backing Up Your Bareos Database - Security Considerations} We provide make\_catalog\_backup as an example of what can be used to backup your Bareos database. We expect you to take security precautions relevant @@ -637,8 +637,8 @@ \section{Security considerations} \label{BackingUPOtherDBs} \section{Backing Up Third Party Databases} -\index[general]{Backing Up Third Party Databases } -\index[general]{Databases!Backing Up Third Party } +\index[general]{Backing Up Third Party Databases} +\index[general]{Databases!Backing Up Third Party} If you are running a database in production mode on your machine, Bareos will happily backup the files, but if the database is in use while Bareos is @@ -658,8 +658,8 @@ \section{Backing Up Third Party Databases} \label{Size} \section{Database Size} -\index[general]{Size!Database } -\index[general]{Database Size } +\index[general]{Size!Database} +\index[general]{Database Size} As mentioned above, if you do not do automatic pruning, your Catalog will grow each time you run a Job. Normally, you should decide how long you want File diff --git a/manuals/en/main/configure.tex b/manuals/en/main/configure.tex index cef026d..3ddda64 100644 --- a/manuals/en/main/configure.tex +++ b/manuals/en/main/configure.tex @@ -49,8 +49,8 @@ \section{Character Sets} be automatically converted to UTF-8 format. \section{Resource Directive Format} -\index[general]{Resource Directive Format } -\index[general]{Format!Resource Directive } +\index[general]{Resource Directive Format} +\index[general]{Format!Resource Directive} Although, you won't need to know the details of all the directives a basic knowledge of Bareos resource directives is essential. Each directive contained @@ -194,7 +194,7 @@ \subsection{Recognized Primitive Data Types} A 32 bit integer value. It may be positive or negative. \item [positive integer] - \index[dir]{positive integer } + \index[dir]{positive integer} A 32 bit positive integer value. \item [long integer] @@ -203,7 +203,7 @@ \subsection{Recognized Primitive Data Types} exceed 4 billion and thus require a 64 bit value. \item [yes{\textbar}no] - \index[dir]{yes or no } + \index[dir]{yes or no} Either a {\bf yes} or a {\bf no}. \label{Size1} @@ -257,7 +257,7 @@ \subsection{Recognized Primitive Data Types} minutes (60 seconds) \item [hours] - \index[dir]{hours } + \index[dir]{hours} hours (3600 seconds) \item [days] @@ -269,15 +269,15 @@ \subsection{Recognized Primitive Data Types} weeks (3600*24*7 seconds) \item [months] - \index[dir]{months } + \index[dir]{months} months (3600*24*30 seconds) \item [quarters] - \index[dir]{quarters } + \index[dir]{quarters} quarters (3600*24*91 seconds) \item [years] - \index[dir]{years } + \index[dir]{years} years (3600*24*365 seconds) \end{description} @@ -423,8 +423,8 @@ \subsection{Variable Expansion} \section{Resource Types} -\index[general]{Types!Resource } -\index[general]{Resource Types } +\index[general]{Types!Resource} +\index[general]{Resource Types} \label{ResTypes} The following table lists all current Bareos resource types. It shows what @@ -472,8 +472,8 @@ \section{Resource Types} \section{Names, Passwords and Authorization} \label{Names} -\index[general]{Authorization!Names Passwords and } -\index[general]{Names, Passwords and Authorization } +\index[general]{Authorization!Names Passwords and} +\index[general]{Names, Passwords and Authorization} \index[general]{Passwords} In order for one daemon to contact another daemon, it must authorize itself diff --git a/manuals/en/main/critical.tex b/manuals/en/main/critical.tex index 7cb4c7b..34b8c94 100644 --- a/manuals/en/main/critical.tex +++ b/manuals/en/main/critical.tex @@ -3,8 +3,8 @@ \chapter{Critical Items to Implement Before Production} \label{CriticalChapter} -\index[general]{Production!Critical Items to Implement Before } -\index[general]{Critical Items to Implement Before Production } +\index[general]{Production!Critical Items to Implement Before} +\index[general]{Critical Items to Implement Before Production} We recommend you take your time before implementing a production a Bareos backup system since Bareos is a rather complex program, and if you make a @@ -19,8 +19,8 @@ \chapter{Critical Items to Implement Before Production} \label{Critical} \section{Critical Items} -\index[general]{Critical Items } -\index[general]{Items!Critical } +\index[general]{Critical Items} +\index[general]{Items!Critical} The following assumes that you have installed Bareos, you more or less understand it, you have at least worked through the tutorial or have @@ -85,8 +85,8 @@ \section{Critical Items} \end{itemize} \section{Recommended Items} -\index[general]{Items!Recommended } -\index[general]{Recommended Items } +\index[general]{Items!Recommended} +\index[general]{Recommended Items} Although these items may not be critical, they are recommended and will help you avoid problems. diff --git a/manuals/en/main/dirdconf-fileset.tex b/manuals/en/main/dirdconf-fileset.tex index 422d7df..f0b65b8 100644 --- a/manuals/en/main/dirdconf-fileset.tex +++ b/manuals/en/main/dirdconf-fileset.tex @@ -1668,8 +1668,8 @@ \subsection{FileSet Examples} \normalsize \subsection{Backing up Raw Partitions} -\index[general]{Backing up!Partitions } -\index[general]{Backing up Raw Partitions } +\index[general]{Backing up!Partitions} +\index[general]{Backing up Raw Partitions} The following FileSet definition will backup a raw partition: @@ -1693,8 +1693,8 @@ \subsection{Backing up Raw Partitions} \subsection{Excluding Files and Directories} -\index[general]{Directories!Excluding Files and } -\index[general]{Excluding Files and Directories } +\index[general]{Directories!Excluding Files and} +\index[general]{Excluding Files and Directories} You may also include full filenames or directory names in addition to using wild-cards and {\bf Exclude=yes} in the Options resource as specified above by @@ -1728,8 +1728,8 @@ \subsection{Excluding Files and Directories} \label{win32} \subsection{Windows FileSets} -\index[general]{Windows FileSets } -\index[general]{FileSets!Windows } +\index[general]{Windows FileSets} +\index[general]{FileSets!Windows} If you are entering Windows file names, the directory path may be preceded by the drive and a colon (as in c:). However, the path separators must be specified in Unix convention (i.e. forward slash (/)). If you wish to include @@ -1915,8 +1915,8 @@ \subsection{Windows FileSets} \subsection{Testing Your FileSet} -\index[general]{FileSet!Testing Your } -\index[general]{Testing Your FileSet } +\index[general]{FileSet!Testing Your} +\index[general]{Testing Your FileSet} If you wish to get an idea of what your FileSet will really backup or if your exclusion rules will work correctly, you can test it by using the diff --git a/manuals/en/main/disk.tex b/manuals/en/main/disk.tex index ed6b8c6..5f3f87c 100644 --- a/manuals/en/main/disk.tex +++ b/manuals/en/main/disk.tex @@ -21,8 +21,8 @@ \chapter{Basic Volume Management} \label{Concepts} \section{Key Concepts and Resource Records} -\index[general]{Key Concepts and Resource Records } -\index[general]{Records!Key Concepts and Resource } +\index[general]{Key Concepts and Resource Records} +\index[general]{Records!Key Concepts and Resource} Getting Bareos to write to disk rather than tape in the simplest case is rather easy. In the Storage daemon's configuration file, you simply define an @@ -80,8 +80,8 @@ \section{Key Concepts and Resource Records} Jobs}{ConcurrentDiskJobs}. \subsection{Pool Options to Limit the Volume Usage} -\index[general]{Usage!Pool Options to Limit the Volume } -\index[general]{Pool Options to Limit the Volume Usage } +\index[general]{Usage!Pool Options to Limit the Volume} +\index[general]{Pool Options to Limit the Volume Usage} Some of the options you have, all of which are specified in the Pool record, are: @@ -152,8 +152,8 @@ \subsection{Pool Options to Limit the Volume Usage} \label{AutomaticLabeling} \subsection{Automatic Volume Labeling} -\index[general]{Automatic Volume Labeling } -\index[general]{Labeling!Automatic Volume } +\index[general]{Automatic Volume Labeling} +\index[general]{Labeling!Automatic Volume} Use of the above records brings up another problem -- that of labeling your Volumes. For automated disk backup, you can either manually label each of your @@ -329,7 +329,7 @@ \section{Concurrent Disk Jobs} \label{Example2} \section{An Example} -\index[general]{Example } +\index[general]{Example} The following example is not very practical, but can be used to demonstrate the proof of concept in a relatively short period of time. The example @@ -506,8 +506,8 @@ \section{An Example} \label{MultipleDisks} \section{Backing up to Multiple Disks} -\index[general]{Disks!Backing up to Multiple } -\index[general]{Backing up to Multiple Disks } +\index[general]{Disks!Backing up to Multiple} +\index[general]{Backing up to Multiple Disks} Bareos can, of course, use multiple disks, but in general, each disk must be a separate Device specification in the Storage daemon's conf file, and you must @@ -610,7 +610,7 @@ \section{Backing up to Multiple Disks} \label{MultipleClients} \section{Considerations for Multiple Clients} -\index[general]{Clients!Considerations for Multiple } +\index[general]{Clients!Considerations for Multiple} \index[general]{Multiple Clients} If we take the above example and add a second Client, here are a few diff --git a/manuals/en/main/general.tex b/manuals/en/main/general.tex index ce69cd3..0e47a1d 100644 --- a/manuals/en/main/general.tex +++ b/manuals/en/main/general.tex @@ -154,8 +154,8 @@ \subsection*{Bareos Tray Monitor} daemon, and the Catalog service (MySQL, PostgreSQL or SQLite). \section{Bareos Configuration} -\index[general]{Configuration!Bareos } -\index[general]{Bareos Configuration } +\index[general]{Configuration!Bareos} +\index[general]{Bareos Configuration} In order for Bareos to understand your system, what clients you want backed up and how, you must create a number of configuration files containing @@ -205,15 +205,15 @@ \section{Terminology} \begin{description} \item [Administrator] - \index[fd]{Administrator } + \index[fd]{Administrator} The person or persons responsible for administrating the Bareos system. \item [Backup] - \index[fd]{Backup } + \index[fd]{Backup} The term Backup refers to a Bareos Job that saves files. \item [Bootstrap File] - \index[fd]{Bootstrap File } + \index[fd]{Bootstrap File} The bootstrap file is an ASCII file containing a compact form of commands that allow Bareos or the stand-alone file extraction utility (bextract) to restore the contents of one or more Volumes, for @@ -222,7 +222,7 @@ \section{Terminology} a bootstrap file from a Catalog to extract any file or files you wish. \item [Catalog] - \index[fd]{Catalog } + \index[fd]{Catalog} The Catalog is used to store summary information about the Jobs, Clients, and Files that were backed up and on what Volume or Volumes. The information saved in the Catalog permits the administrator or user @@ -239,41 +239,41 @@ \section{Terminology} simple backup and archive programs such as dump and tar. \item [Client] - \index[fd]{Client } + \index[fd]{Client} In Bareos's terminology, the word Client refers to the machine being backed up, and it is synonymous with the File services or File daemon, and quite often, it is referred to it as the FD. A Client is defined in a configuration file resource. \item [Console] - \index[fd]{Console } + \index[fd]{Console} The program that interfaces to the Director allowing the user or system administrator to control Bareos. \item [Daemon] - \index[fd]{Daemon } + \index[fd]{Daemon} Unix terminology for a program that is always present in the background to carry out a designated task. On Windows systems, as well as some Unix systems, daemons are called Services. \item [Directive] - \index[fd]{Directive } + \index[fd]{Directive} The term directive is used to refer to a statement or a record within a Resource in a configuration file that defines one specific setting. For example, the {\bf Name} directive defines the name of the Resource. \item [Director] - \index[fd]{Director } + \index[fd]{Director} The main Bareos server daemon that schedules and directs all Bareos operations. Occasionally, the project refers to the Director as DIR. \item [Differential] - \index[fd]{Differential } + \index[fd]{Differential} A backup that includes all files changed since the last Full save started. Note, other backup programs may define this differently. \item [File Attributes] - \index[fd]{File Attributes } + \index[fd]{File Attributes} The File Attributes are all the information necessary about a file to identify it and all its properties such as size, creation date, modification date, permissions, etc. Normally, the attributes are handled entirely by @@ -281,14 +281,14 @@ \section{Terminology} attributes do not include the file's data. \item [File Daemon] - \index[fd]{File Daemon } + \index[fd]{File Daemon} The daemon running on the client computer to be backed up. This is also referred to as the File services, and sometimes as the Client services or the FD. \label{FileSetDef} \item [FileSet] -\index[fd]{a name } +\index[fd]{a name} A FileSet is a Resource contained in a configuration file that defines the files to be backed up. It consists of a list of included files or directories, a list of excluded files, and how the file is to be stored @@ -297,14 +297,14 @@ \section{Terminology} chapter of this document. \item [Incremental] - \index[fd]{Incremental } + \index[fd]{Incremental} A backup that includes all files changed since the last Full, Differential, or Incremental backup started. It is normally specified on the {\bf Level} directive within the Job resource definition, or in a Schedule resource. \label{JobDef} \item [Job] -\index[fd]{a name } +\index[fd]{a name} A Bareos Job is a configuration resource that defines the work that Bareos must perform to backup or restore a particular Client. It consists of the {\bf Type} (backup, restore, verify, etc), the {\bf @@ -315,12 +315,12 @@ \section{Terminology} Director chapter of this document. \item [Monitor] - \index[fd]{Monitor } + \index[fd]{Monitor} The program that interfaces to all the daemons allowing the user or system administrator to monitor Bareos status. \item [Resource] - \index[fd]{Resource } + \index[fd]{Resource} A resource is a part of a configuration file that defines a specific unit of information that is available to Bareos. It consists of several directives (individual configuration statements). For example, the {\bf @@ -329,7 +329,7 @@ \section{Terminology} % TODO: clean up "..." for book \item [Restore] - \index[fd]{Restore } + \index[fd]{Restore} A restore is a configuration resource that describes the operation of recovering a file from backup media. It is the inverse of a save, except that in most cases, a restore will normally have a small set of @@ -341,7 +341,7 @@ \section{Terminology} % TODO: define "Full" \item [Schedule] - \index[fd]{Schedule } + \index[fd]{Schedule} A Schedule is a configuration resource that defines when the Bareos Job will be scheduled for execution. To use the Schedule, the Job resource will refer to the name of the Schedule. For more details, see the @@ -349,13 +349,13 @@ \section{Terminology} chapter of this document. \item [Service] - \index[fd]{Service } + \index[fd]{Service} 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 } + \index[fd]{Storage Coordinates} The information returned from the Storage Services that uniquely locates a file on a backup medium. It consists of two parts: one part pertains to each file saved, and the other part pertains to the whole Job. @@ -365,20 +365,20 @@ \section{Terminology} location of the information on the backup Volume. \item [Storage Daemon] - \index[fd]{Storage Daemon } + \index[fd]{Storage Daemon} The Storage daemon, sometimes referred to as the SD, is the code that writes the attributes and data to a storage Volume (usually a tape or disk). \item [Session] - \index[sd]{Session } + \index[sd]{Session} Normally refers to the internal conversation between the File daemon and the Storage daemon. The File daemon opens a {\bf session} with the Storage daemon to save a FileSet or to restore it. A session has a one-to-one correspondence to a Bareos Job (see above). \item [Verify] - \index[sd]{Verify } + \index[sd]{Verify} A verify is a job that compares the current file attributes to the attributes that have previously been stored in the Bareos Catalog. This feature can be used for detecting changes to critical system files @@ -396,14 +396,14 @@ \section{Terminology} original files on disk. %\item [*Archive] -% \index[fd]{*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 [Retention Period] - \index[fd]{Retention Period } + \index[fd]{Retention Period} There are various kinds of retention periods that Bareos recognizes. The most important are the {\bf File} Retention Period, {\bf Job} Retention Period, and the {\bf Volume} Retention Period. Each of these @@ -447,7 +447,7 @@ \section{Terminology} retention periods defined. \item [Scan] - \index[sd]{Scan } + \index[sd]{Scan} A Scan operation causes the contents of a Volume or a series of Volumes to be scanned. These Volumes with the information on which files they contain are restored to the Bareos Catalog. Once the information is @@ -460,7 +460,7 @@ \section{Terminology} details. \item [Volume] - \index[sd]{Volume } + \index[sd]{Volume} A Volume is an archive unit, normally a tape or a named disk file where Bareos stores the data from one or more backup jobs. All Bareos Volumes have a software label written to the Volume by Bareos so that it diff --git a/manuals/en/main/main.tex b/manuals/en/main/main.tex index c275d22..42fa685 100644 --- a/manuals/en/main/main.tex +++ b/manuals/en/main/main.tex @@ -91,7 +91,7 @@ \chapter{Installing Bareos} \chapter{Getting Started with Bareos} \label{QuickStartChapter} -\index[general]{Getting Started with Bareos } +\index[general]{Getting Started with Bareos} \input{quickstart} % install @@ -105,8 +105,8 @@ \part{Configuration Files} \chapter{Customizing the Configuration Files} \label{ConfigureChapter} -\index[general]{Files!Customizing the Configuration } -\index[general]{Customizing the Configuration Files } +\index[general]{Files!Customizing the Configuration} +\index[general]{Customizing the Configuration Files} \input{configure} % install \include{dirdconf} % install @@ -173,8 +173,8 @@ \part{Appendix} \chapter{Operating Systems} \label{SupportedOSes} -\index[general]{Systems!Supported Operating } -\index[general]{Supported Operating Systems } +\index[general]{Systems!Supported Operating} +\index[general]{Supported Operating Systems} \input{supportedoses} diff --git a/manuals/en/main/mysql.tex b/manuals/en/main/mysql.tex index 9fb3929..57dfef2 100644 --- a/manuals/en/main/mysql.tex +++ b/manuals/en/main/mysql.tex @@ -3,11 +3,11 @@ \chapter{Installing and Configuring MySQL} \label{MySqlChapter} -\index[general]{MySQL!Installing and Configuring } -\index[general]{Installing and Configuring MySQL } +\index[general]{MySQL!Installing and Configuring} +\index[general]{Installing and Configuring MySQL} \section{Installing and Configuring MySQL -- Phase I} -\index[general]{Installing and Configuring MySQL -- Phase I } +\index[general]{Installing and Configuring MySQL -- Phase I} \index[general]{Phase I!Installing and Configuring MySQL -- } If you use the ./configure \verb:--:with-mysql=mysql-directory statement for @@ -127,7 +127,7 @@ \section{Installing and Configuring MySQL -- Phase I} \label{mysql_phase2} \section{Installing and Configuring MySQL -- Phase II} -\index[general]{Installing and Configuring MySQL -- Phase II } +\index[general]{Installing and Configuring MySQL -- Phase II} \index[general]{Phase II!Installing and Configuring MySQL -- } At this point, you should have built and installed MySQL, or already have a @@ -196,8 +196,8 @@ \section{Installing and Configuring MySQL -- Phase II} \normalsize \section{Re-initializing the Catalog Database} -\index[general]{Database!Re-initializing the Catalog } -\index[general]{Re-initializing the Catalog Database } +\index[general]{Database!Re-initializing the Catalog} +\index[general]{Re-initializing the Catalog Database} After you have done some initial testing with {\bf Bareos}, you will probably want to re-initialize the catalog database and throw away all the test Jobs @@ -227,8 +227,8 @@ \section{Re-initializing the Catalog Database} device name for your machine. \section{Linking Bareos with MySQL} -\index[general]{Linking Bareos with MySQL } -\index[general]{MySQL!Linking Bareos with } +\index[general]{Linking Bareos with MySQL} +\index[general]{MySQL!Linking Bareos with} \index[general]{Upgrading} After configuring Bareos with @@ -289,8 +289,8 @@ \section{Installing MySQL from RPMs} This will be the same with most other package managers too. \section{Upgrading MySQL} -\index[general]{Upgrading MySQL } -\index[general]{Upgrading!MySQL } +\index[general]{Upgrading MySQL} +\index[general]{Upgrading!MySQL} \index[general]{Upgrading} If you upgrade MySQL, you must reconfigure, rebuild, and re-install Bareos otherwise you are likely to get bizarre failures. If you diff --git a/manuals/en/main/postgresql.tex b/manuals/en/main/postgresql.tex index ea3618b..1af7e53 100644 --- a/manuals/en/main/postgresql.tex +++ b/manuals/en/main/postgresql.tex @@ -3,8 +3,8 @@ \chapter{Installing and Configuring PostgreSQL} \label{PostgreSqlChapter} -\index[general]{PostgreSQL!Installing and Configuring } -\index[general]{Installing and Configuring PostgreSQL } +\index[general]{PostgreSQL!Installing and Configuring} +\index[general]{Installing and Configuring PostgreSQL} \index[general]{Upgrading} If you are considering using PostreSQL, you should be aware @@ -23,7 +23,7 @@ \chapter{Installing and Configuring PostgreSQL} for PostgreSQL. \section{Installing PostgreSQL} -\index[general]{PostgreSQL!Installing } +\index[general]{PostgreSQL!Installing} If you use the {\bf ./configure \verb:--:with-postgresql=PostgreSQL-Directory} statement for configuring {\bf Bareos}, you will need PostgreSQL version 7.4 @@ -279,8 +279,8 @@ \section{Configuring PostgreSQL} set to 600, limiting access to the owner of the file. \section{Re-initializing the Catalog Database} -\index[general]{Database!Re-initializing the Catalog } -\index[general]{Re-initializing the Catalog Database } +\index[general]{Database!Re-initializing the Catalog} +\index[general]{Re-initializing the Catalog Database} After you have done some initial testing with {\bf Bareos}, you will probably want to re-initialize the catalog database and throw away all the test Jobs @@ -348,8 +348,8 @@ \section{Installing PostgreSQL from RPMs} \section{Converting from MySQL to PostgreSQL} -\index[general]{PostgreSQL!Converting from MySQL to } -\index[general]{Converting from MySQL to PostgreSQL } +\index[general]{PostgreSQL!Converting from MySQL to} +\index[general]{Converting from MySQL to PostgreSQL} The conversion procedure presented here was worked out by Norm Dressler {\textless}ndressler at dinmar dot com{\textgreater} @@ -482,8 +482,8 @@ \section{Converting from MySQL to PostgreSQL} \end{enumerate} \section{Upgrading PostgreSQL} -\index[general]{Upgrading PostgreSQL } -\index[general]{Upgrading!PostgreSQL } +\index[general]{Upgrading PostgreSQL} +\index[general]{Upgrading!PostgreSQL} \index[general]{Upgrading} If you upgrade PostgreSQL, you must reconfigure, rebuild, and re-install Bareos otherwise you are likely to get bizarre failures. If you @@ -503,6 +503,6 @@ \section{Tuning PostgreSQL} \end{verbatim} \section{Credits} -\index[general]{Credits } +\index[general]{Credits} Many thanks to Dan Langille for writing the PostgreSQL driver. This will surely become the most popular database that Bareos supports. diff --git a/manuals/en/main/quickstart.tex b/manuals/en/main/quickstart.tex index bfc0e80..d2658a4 100644 --- a/manuals/en/main/quickstart.tex +++ b/manuals/en/main/quickstart.tex @@ -30,8 +30,8 @@ \section{Understanding Jobs and Schedules} \label{PoolsVolsLabels} \section{Understanding Pools, Volumes and Labels} -\index[general]{Labels!Understanding Pools Volumes and } -\index[general]{Understanding Pools, Volumes and Labels } +\index[general]{Labels!Understanding Pools Volumes and} +\index[general]{Understanding Pools, Volumes and Labels} If you have been using a program such as {\bf tar} to backup your system, Pools, Volumes, and labeling may be a bit confusing at first. A Volume is a @@ -76,8 +76,8 @@ \section{Understanding Pools, Volumes and Labels} \section{Setting Up Bareos Configuration Files} \label{config} -\index[general]{Setting Up Bareos Configuration Files } -\index[general]{Files!Setting Up Bareos Configuration } +\index[general]{Setting Up Bareos Configuration Files} +\index[general]{Files!Setting Up Bareos Configuration} On Unix, Bareos configuration files are usualy location in the \path|/etc/bareos/| directory and are named accordingly to the programs that use it: bareos-fd.conf, bareos-sd.conf, bareos-dir.conf, bconsole.conf, etc. @@ -110,8 +110,8 @@ \subsection{Configuring the Console Program} \ilink{Console configuration}{ConsoleConfChapter} chapter. % \subsection{Configuring the Monitor Program} -% \index[general]{Program!Configuring the Monitor } -% \index[general]{Configuring the Monitor Program } +% \index[general]{Program!Configuring the Monitor} +% \index[general]{Configuring the Monitor Program} % % The Monitor program is typically an icon in the system tray. However, once the % icon is expanded into a full window, the administrator or user can obtain @@ -224,8 +224,8 @@ \subsection{Configuring the Storage daemon} \ilink{Storage daemon configuration}{StoredConfChapter} chapter. \section{Testing your Configuration Files} -\index[general]{Testing your Configuration Files } -\index[general]{Files!Testing your Configuration } +\index[general]{Testing your Configuration Files} +\index[general]{Files!Testing your Configuration} You can test if your configuration file is syntactically correct by running the appropriate daemon with the {\bf -t} option. The daemon will process the @@ -275,8 +275,8 @@ \section{Testing Compatibility with Your Tape Drive} \label{Running1} \section{Running Bareos} -\index[general]{Bareos!Running } -\index[general]{Running Bareos } +\index[general]{Bareos!Running} +\index[general]{Running Bareos} Probably the most important part of running Bareos is being able to restore files. If you haven't tried recovering files at least once, when you actually @@ -289,8 +289,8 @@ \section{Running Bareos} you will get detailed instructions on how to run Bareos. % \section{Log Rotation} -% \index[general]{Rotation!Log } -% \index[general]{Log Rotation } +% \index[general]{Rotation!Log} +% \index[general]{Log Rotation} % If you use the default {\bf bareos-dir.conf} or some variation of it, you will % note that it logs all the Bareos output to a file. To avoid that this file % grows without limit, we recommend that you copy the file {\bf logrotate} from diff --git a/manuals/en/main/requirements.tex b/manuals/en/main/requirements.tex index 073f16b..8b1cb2b 100644 --- a/manuals/en/main/requirements.tex +++ b/manuals/en/main/requirements.tex @@ -3,8 +3,8 @@ \chapter{System Requirements} \label{SysReqs} -\index[general]{System Requirements } -\index[general]{Requirements!System } +\index[general]{System Requirements} +\index[general]{Requirements!System} \begin{itemize} \item The minimum versions for each of the databases supported by Bareos diff --git a/manuals/en/main/restore.tex b/manuals/en/main/restore.tex index 11ab61b..ad0007a 100644 --- a/manuals/en/main/restore.tex +++ b/manuals/en/main/restore.tex @@ -436,8 +436,8 @@ \subsection{Restore a pruned job using a pattern} See also \ilink{FileRegex bsr option}{FileRegex} for more information. \section{Selecting Files by Filename} -\index[general]{Selecting Files by Filename } -\index[general]{Filename!Selecting Files by } +\index[general]{Selecting Files by Filename} +\index[general]{Filename!Selecting Files by} If you have a small number of files to restore, and you know the filenames, you can either put the list of filenames in a file to be read by Bareos, or @@ -972,14 +972,14 @@ \section{File Selection Commands} C:} (note upper case) to get down to the first directory. \item [dir] - \index[dir]{dir } + \index[dir]{dir} The {\bf dir} command is similar to the {\bf ls} command, except that it prints it in long format (all details). This command can be a bit slower than the {\bf ls} command because it must access the catalog database for the detailed information for each file. \item [estimate] - \index[dir]{estimate } + \index[dir]{estimate} The {\bf estimate} command prints a summary of the total files in the tree, how many are marked to be restored, and an estimate of the number of bytes to be restored. This can be useful if you are short on disk space on the @@ -1044,7 +1044,7 @@ \section{File Selection Commands} if some files are marked. \item [unmark] - \index[dir]{unmark } + \index[dir]{unmark} The {\bf unmark} is identical to the {\bf mark} command, except that it unmarks the specified file or files so that they will not be restored. Note: the {\bf unmark} command works from the current directory, so it does not @@ -1052,31 +1052,31 @@ \section{File Selection Commands} unmark *} command if you want to unmark everything. \item [pwd] - \index[dir]{pwd } + \index[dir]{pwd} The {\bf pwd} command prints the current working directory. It accepts no arguments. \item [count] - \index[dir]{count } + \index[dir]{count} The {\bf count} command prints the total files in the directory tree and the number of files marked to be restored. \item [done] - \index[dir]{done } + \index[dir]{done} This command terminates file selection mode. \item [exit] - \index[fd]{exit } + \index[fd]{exit} This command terminates file selection mode (the same as done). \item [quit] - \index[fd]{quit } + \index[fd]{quit} This command terminates the file selection and does not run the restore job. \item [help] - \index[fd]{help } + \index[fd]{help} This command prints a summary of the commands available. \item [?] diff --git a/manuals/en/main/security.tex b/manuals/en/main/security.tex index ee6b3b4..b0e1896 100644 --- a/manuals/en/main/security.tex +++ b/manuals/en/main/security.tex @@ -202,7 +202,7 @@ \section{Configuring and Testing TCP Wrappers} \hide{ \section{Running as non-root} -\index[general]{Running as non-root } +\index[general]{Running as non-root} Security advice from Dan Langille: % TODO: don't use specific name diff --git a/manuals/en/main/spooling.tex b/manuals/en/main/spooling.tex index 8df6129..f9ca61e 100644 --- a/manuals/en/main/spooling.tex +++ b/manuals/en/main/spooling.tex @@ -3,8 +3,8 @@ \chapter{Data Spooling} \label{SpoolingChapter} -\index[general]{Data Spooling } -\index[general]{Spooling!Data } +\index[general]{Data Spooling} +\index[general]{Spooling!Data} Bareos allows you to specify that you want the Storage daemon to initially write your data to disk and then subsequently to tape. This serves several @@ -45,8 +45,8 @@ \chapter{Data Spooling} \label{directives} \section{Data Spooling Directives} -\index[general]{Directives!Data Spooling } -\index[general]{Data Spooling Directives } +\index[general]{Directives!Data Spooling} +\index[general]{Data Spooling Directives} The following directives can be used to control data spooling. @@ -111,8 +111,8 @@ \section{Data Spooling Directives} \label{points} \section{Other Points} -\index[general]{Points!Other } -\index[general]{Other Points } +\index[general]{Points!Other} +\index[general]{Other Points} \begin{itemize} \item When data spooling is enabled, Bareos automatically turns on attribute diff --git a/manuals/en/main/sqlite.tex b/manuals/en/main/sqlite.tex index 7005f34..f3eabdf 100644 --- a/manuals/en/main/sqlite.tex +++ b/manuals/en/main/sqlite.tex @@ -3,8 +3,8 @@ \chapter{Installing and Configuring SQLite} \label{SqlLiteChapter} -\index[general]{Installing and Configuring SQLite } -\index[general]{SQLite!Installing and Configuring } +\index[general]{Installing and Configuring SQLite} +\index[general]{SQLite!Installing and Configuring} Please note that SQLite both versions 2 and 3 are not network enabled, which means that they must be linked into the Director rather than accessed @@ -19,7 +19,7 @@ \chapter{Installing and Configuring SQLite} \section{Installing and Configuring SQLite -- Phase I} \index[general]{Phase I!Installing and Configuring SQLite -- } -\index[general]{Installing and Configuring SQLite -- Phase I } +\index[general]{Installing and Configuring SQLite -- Phase I} If you use the {\bf ./configure \verb:--:with-sqlite} statement for configuring {\bf Bareos}, you will need SQLite version 2.8.16 or later installed. Our standard @@ -77,7 +77,7 @@ \section{Installing and Configuring SQLite -- Phase I} \section{Installing and Configuring SQLite -- Phase II} \label{phase2} \index[general]{Phase II!Installing and Configuring SQLite -- } -\index[general]{Installing and Configuring SQLite -- Phase II } +\index[general]{Installing and Configuring SQLite -- Phase II} This phase is done {\bf after} you have run the {\bf ./configure} command to configure {\bf Bareos}. @@ -107,15 +107,15 @@ \section{Installing and Configuring SQLite -- Phase II} \end{enumerate} \section{Linking Bareos with SQLite} -\index[general]{SQLite!Linking Bareos with } -\index[general]{Linking Bareos with SQLite } +\index[general]{SQLite!Linking Bareos with} +\index[general]{Linking Bareos with SQLite} If you have followed the above steps, this will all happen automatically and the SQLite libraries will be linked into {\bf Bareos}. \section{Testing SQLite} -\index[general]{SQLite!Testing } -\index[general]{Testing SQLite } +\index[general]{SQLite!Testing} +\index[general]{Testing SQLite} We have much less "production" experience using SQLite than using MySQL. SQLite has performed flawlessly for us in all our testing. However, @@ -141,8 +141,8 @@ \section{Testing SQLite} \section{Re-initializing the Catalog Database} -\index[general]{Database!Re-initializing the Catalog } -\index[general]{Re-initializing the Catalog Database } +\index[general]{Database!Re-initializing the Catalog} +\index[general]{Re-initializing the Catalog Database} After you have done some initial testing with {\bf Bareos}, you will probably want to re-initialize the catalog database and throw away all the test Jobs diff --git a/manuals/en/main/storedconf.tex b/manuals/en/main/storedconf.tex index 2f39ced..2506911 100644 --- a/manuals/en/main/storedconf.tex +++ b/manuals/en/main/storedconf.tex @@ -739,7 +739,7 @@ \section{Device Resource} {\bf No} for non-random access devices such as tapes and named pipes. \item [Requires Mount = {\textless}yes{\textbar}no{\textgreater}] \hfill \\ -\index[sd]{Requires Mount } +\index[sd]{Requires Mount} When this directive is enabled, the Storage daemon will submit a {\bf Mount Command} before attempting to open the device. You must set this directive to {\bf yes} for removable @@ -1141,7 +1141,7 @@ \section{Device Resource} \subsection{Edit Codes for Mount and Unmount Directives} \index[general]{Directives!Edit Codes} -\index[general]{Edit Codes for Mount and Unmount Directives } +\index[general]{Edit Codes for Mount and Unmount Directives} \label{mountcodes} Before submitting the {\bf Mount Command}, or {\bf Unmount Command} diff --git a/manuals/en/main/supporteddrives.tex b/manuals/en/main/supporteddrives.tex index f32c804..e161ca8 100644 --- a/manuals/en/main/supporteddrives.tex +++ b/manuals/en/main/supporteddrives.tex @@ -3,8 +3,8 @@ \chapter{Supported Tape Drives} \label{SupportedDrives} -\index[general]{Drives!Supported Tape } -\index[general]{Supported Tape Drives } +\index[general]{Drives!Supported Tape} +\index[general]{Supported Tape Drives} Bareos uses standard operating system calls (read, write, ioctl) to interface to tape drives. As a consequence, it relies on having a @@ -81,8 +81,8 @@ \chapter{Supported Tape Drives} \section{Unsupported Tape Drives} \label{UnSupportedDrives} -\index[general]{Unsupported Tape Drives } -\index[general]{Drives!Unsupported Tape } +\index[general]{Unsupported Tape Drives} +\index[general]{Drives!Unsupported Tape} Previously OnStream IDE-SCSI tape drives did not work with Bareos. As of Bareos version 1.33 and the osst kernel driver version 0.9.14 or later, they @@ -94,8 +94,8 @@ \section{Unsupported Tape Drives} with Bareos. \section{FreeBSD Users Be Aware!!!} -\index[general]{FreeBSD Users Be Aware } -\index[general]{Aware!FreeBSD Users Be } +\index[general]{FreeBSD Users Be Aware} +\index[general]{Aware!FreeBSD Users Be} Unless you have patched the pthreads library on FreeBSD 4.11 systems, you will lose data when Bareos spans tapes. This is because the unpatched pthreads @@ -106,8 +106,8 @@ \section{FreeBSD Users Be Aware!!!} compatibility with Bareos. \section{Supported Autochangers} -\index[general]{Autochangers!Supported } -\index[general]{Supported Autochangers } +\index[general]{Autochangers!Supported} +\index[general]{Supported Autochangers} For information on supported autochangers, please see the \ilink{Autochangers Known to Work with Bareos}{Models} diff --git a/manuals/en/main/tls.tex b/manuals/en/main/tls.tex index 25ca843..134a936 100644 --- a/manuals/en/main/tls.tex +++ b/manuals/en/main/tls.tex @@ -115,8 +115,8 @@ \section{TLS Configuration Directives} \end{description} \section{Creating a Self-signed Certificate} -\index[general]{Creating a Self-signed Certificate } -\index[general]{Certificate!Creating a Self-signed } +\index[general]{Creating a Self-signed Certificate} +\index[general]{Certificate!Creating a Self-signed} You may create a self-signed certificate for use with the Bareos TLS that will permit you to make it function, but will not allow certificate diff --git a/manuals/en/main/tutorial.tex b/manuals/en/main/tutorial.tex index d0a34d2..d330fc1 100644 --- a/manuals/en/main/tutorial.tex +++ b/manuals/en/main/tutorial.tex @@ -69,7 +69,7 @@ \section{Starting the Database} \section{Starting the Daemons} \label{StartDaemon} -\index[general]{Starting the Daemons } +\index[general]{Starting the Daemons} \index[general]{Daemons!Starting the} Assuming you have installed the packages, @@ -213,8 +213,8 @@ \section{Using the Director to Query and Start Jobs} \section{Running a Job} \label{Running} -\index[general]{Job!Running a } -\index[general]{Running a Job } +\index[general]{Job!Running a} +\index[general]{Running a Job} At this point, we assume you have done the following: @@ -598,8 +598,8 @@ \section{Running a Job} \label{restoring} \section{Restoring Your Files} -\index[general]{Files!Restoring Your } -\index[general]{Restoring Your Files } +\index[general]{Files!Restoring Your} +\index[general]{Restoring Your Files} If you have run the default configuration and run the job as demonstrated above, you can restore the backed up files in the Console @@ -797,15 +797,15 @@ \section{Restoring Your Files} \normalsize \section{Quitting the Console Program} -\index[general]{Program!Quitting the Console } -\index[general]{Quitting the Console Program } +\index[general]{Program!Quitting the Console} +\index[general]{Quitting the Console Program} Simply enter the command {\bf quit}. \label{SecondClient} \section{Adding a Second Client} -\index[general]{Client!Adding a Second } -\index[general]{Adding a Second Client } +\index[general]{Client!Adding a Second} +\index[general]{Adding a Second Client} \subsection{Changes on the Client} @@ -924,8 +924,8 @@ \subsection{Changes on the Bareos Director (Server)} \section{When The Tape Fills} \label{FullTape} -\index[general]{Fills!When The Tape } -\index[general]{When The Tape Fills } +\index[general]{Fills!When The Tape} +\index[general]{When The Tape Fills} If you have scheduled your job, typically nightly, there will come a time when the tape fills up and {\bf Bareos} cannot continue. In this case, Bareos will @@ -1040,60 +1040,60 @@ \section{Other Useful Console Commands} \begin{description} \item [status dir] - \index[console]{status dir } + \index[console]{status dir} Print a status of all running jobs and jobs scheduled in the next 24 hours. \item [status] - \index[console]{status } + \index[console]{status} The console program will prompt you to select a daemon type, then will request the daemon's status. \item [status jobid=nn] - \index[console]{status jobid } + \index[console]{status jobid} Print a status of JobId nn if it is running. The Storage daemon is contacted and requested to print a current status of the job as well. \item [list pools] - \index[console]{list pools } + \index[console]{list pools} List the pools defined in the Catalog (normally only Default is used). \item [list media] - \index[console]{list media } + \index[console]{list media} Lists all the media defined in the Catalog. \item [list jobs] - \index[console]{list jobs } + \index[console]{list jobs} Lists all jobs in the Catalog that have run. \item [list jobid=nn] - \index[console]{list jobid } + \index[console]{list jobid} Lists JobId nn from the Catalog. \item [list jobtotals] - \index[console]{list jobtotals } + \index[console]{list jobtotals} Lists totals for all jobs in the Catalog. \item [list files jobid=nn] - \index[console]{list files jobid } + \index[console]{list files jobid} List the files that were saved for JobId nn. \item [list jobmedia] - \index[console]{list jobmedia } + \index[console]{list jobmedia} List the media information for each Job run. \item [messages] - \index[console]{messages } + \index[console]{messages} Prints any messages that have been directed to the console. \item [unmount storage=storage-name] - \index[console]{unmount storage } + \index[console]{unmount storage} Unmounts the drive associated with the storage device with the name {\bf storage-name} if the drive is not currently being used. This command is used if you wish Bareos to free the drive so that you can use it to label a tape. \item [mount storage=storage-name] - \index[sd]{mount storage } + \index[sd]{mount storage} Causes the drive associated with the storage device to be mounted again. When Bareos reaches the end of a volume and requests you to mount a new volume, you must issue this command after you have placed the new volume in the @@ -1101,7 +1101,7 @@ \section{Other Useful Console Commands} or writing the new volume. \item [quit] - \index[sd]{quit } + \index[sd]{quit} Exit or quit the console program. \end{description} @@ -1110,8 +1110,8 @@ \section{Other Useful Console Commands} \section{Debug Daemon Output} -\index[general]{Debug Daemon Output } -\index[general]{Output!Debug Daemon } +\index[general]{Debug Daemon Output} +\index[general]{Output!Debug Daemon} \TODO{needs to be adapted} @@ -1191,8 +1191,8 @@ \section{Difficulties Connecting from the FD to the SD} communications in Bareos). \section{Daemon Command Line Options} -\index[general]{Daemon Command Line Options } -\index[general]{Options!Daemon Command Line } +\index[general]{Daemon Command Line Options} +\index[general]{Options!Daemon Command Line} Each of the three daemons (Director, File, Storage) accepts a small set of options on the command line. In general, each of the daemons as well as the @@ -1208,7 +1208,7 @@ \section{Daemon Command Line Options} daemon. \item [-d nn] - \index[sd]{-d nn } + \index[sd]{-d nn} Set the debug level to {\bf nn}. Higher levels of debug cause more information to be displayed on STDOUT concerning what the daemon is doing. @@ -1242,8 +1242,8 @@ \section{Daemon Command Line Options} \section{Creating a Pool} \label{Pool} -\index[general]{Pool!Creating a } -\index[general]{Creating a Pool } +\index[general]{Pool!Creating a} +\index[general]{Creating a Pool} Creating the Pool is automatically done when {\bf Bareos} starts, so if you understand Pools, you can skip to the next section. @@ -1302,8 +1302,8 @@ \section{Creating a Pool} \label{Labeling} \section{Labeling Your Volumes} -\index[general]{Volumes!Labeling Your } -\index[general]{Labeling Your Volumes } +\index[general]{Volumes!Labeling Your} +\index[general]{Labeling Your Volumes} Bareos requires that each Volume contains a software label. There are several strategies for labeling volumes. The one I use is to label them as they are @@ -1328,8 +1328,8 @@ \section{Labeling Your Volumes} below for the details of using the {\bf label} command. \section{Labeling Volumes with the Console Program} -\index[general]{Labeling Volumes with the Console Program } -\index[general]{Program!Labeling Volumes with the Console } +\index[general]{Labeling Volumes with the Console Program} +\index[general]{Program!Labeling Volumes with the Console} Labeling volumes is normally done by using the console program. diff --git a/manuals/en/main/verify.tex b/manuals/en/main/verify.tex index fbbe7a5..6f60bcc 100644 --- a/manuals/en/main/verify.tex +++ b/manuals/en/main/verify.tex @@ -3,7 +3,7 @@ \chapter{Verify File Integrity with Bareos} \label{VerifyChapter} -\index[general]{Security!Using Bareos to Improve Computer } +\index[general]{Security!Using Bareos to Improve Computer} \index[general]{Verify!File Integrity} % TODO: only those two digest algorithms?