<? require_once("inc/header.php"); ?>
<table>
<tr>
- <td class="contentTopic">
- Professional Support for Bacula
- </td>
+ <td class="contentTopic">
+ Professional Support for Bacula
+ </td>
</tr>
<tr>
- <td class="content">
- The people listed are <b>independent contractors</b>.<br>
- We can't and won't take any responsibility for their actions when you hire them.<br>
- <br>
- Listing on the Bacula Professional page is offered as a <b>service</b>,
- <b>without</b> any guarantess.<br>
- <br>
- We reserve the right to decide with reason who is added/removed from the web page.<br>
- To be listed, you must have some tangible connection with and
- knowledge of Bacula (i.e. developer, contributed code/patches, Bacula
- user and subscribed to bacula-users, or bacula-devel, ...).<br>
- <br>
- People listed here agree to update their contact-information on a regular-basis.<br>
- Anyone listed with wrong informations will be removed immediatly.<br>
- <br>
- If you want to get listed on the page, please get in contact with Kern Sibbald.<br>
- </td>
+ <td class="content">
+ The people listed are <b>independent contractors</b>.<br>
+ We can't take responsibility for their actions when you hire them,
+ but we would appreciate feedback positive or negative.<br>
+ <br>
+ Listing on the Bacula Professional page is offered as a
+ <b>service</b>, <b>without</b> any guarantess.<br>
+ <br>
+ We reserve the right to decide with reason who is
+ added/removed from the web page.<br>
+ To be listed, you must have some tangible connection with and
+ knowledge of Bacula (i.e. developer, contributed
+ code/patches, Bacula user and subscribed to bacula-users, or
+ bacula-devel, and preferably a Web site ...).<br>
+ <br>
+ People listed here agree to update their contact information
+ on a regular basis.<br> Anyone listed with incorrect
+ information is subject to removal.<br> <br> If you want to be
+ listed on the page, please get in contact with Kern
+ Sibbald.<br>
+ </td>
</tr>
</table>
<? require_once("inc/footer.php"); ?>
<form name="_xclick" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<input type="hidden" name="cmd" value="_xclick">
-<input type="hidden" name="business" value="donations@bacula.org">
-<input type="hidden" name="currency_code" value="USD">
+<input type="hidden" name="business" value="projects@bacula.org">
+<input type="hidden" name="tax" value="0">
+<input type="hidden" name="bn" value="PP-DonationsBF">
<input type="image" src="http://www.paypal.com/en_US/i/btn/x-click-butcc-donate.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">
</form>
-
<table>
<tr>
<td class="contentTopic">
</tr>
<tr>
<td class="content">
- The following people are independent contractors.<br>
- We list their names here as a service only without any guarantees.<br>
+ The following people are independent contractors. Each has worked
+ with Bacula, and we are pleased to list their names here as a service, but
+ without any guarantees.<br>
<br>
Please read that short 'licence' for further details: <a href="?page=listlic">Listing licence</a><br>
All names have been reviewed and approved. <br>
<a href="http://www.instant-root.com">http://www.instant-root.com</a><br>
</td>
</tr>
+
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr> <td colspan="3"><hr></td>
+ <tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
+ <tr>
+ <td style="font-weight: bold">
+ IT-Service Lehmann
+ </td>
+ <td><img src="images/spacer.gif" width="50px" height="1px"></td>
+ <td>
+ <a href="mailto:infoNOSPAM@its-lehmann.de">Arno Lehmann</a><br>
+ Wittekamp 2<br>
+ 30177 Hannover<br>
+ Germany<br>
+ +49 (0) 511 69099508<br>
+ +49 (0) 160 92008971 (mobile)<br>
+ <br>
+ Storage, Communication, Backup and Monitoring using
+ Open-Source solutions. Services from
+ network design to system administration and
+ user education, with a focus on Small
+ Businesses looking for cost-effective solutions.
+ <br>
+ <a href="http://www.its-lehmann.de">http://www.its-lehmann.de</a>
+ </td>
+ </td>
+ </tr>
+
<tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
<tr> <td colspan="3"><hr></td>
<tr> <td colspan="3"><img src="images/spacer.gif" width="50px" height="25px"></td> </tr>
<pre>
Item n: One line summary ...
Origin: Name and email of originator.
+ Date: Date submitted (e.g. 28 October 2005)
Status:
What: More detailed explanation ...
<pre>
Item 1: Implement a Migration job type that will move the job
data from one device to another.
+ Date: 28 October 2005
Origin: Sponsored by Riege Sofware International GmbH. Contact:
Daniel Holtkamp <holtkamp at riege dot com>
Status: Partially coded in 1.37 -- much more to do. Assigned to
\multicolumn{1}{c| }{\bf Client } & \multicolumn{1}{c| }{\bf Storage } &
\multicolumn{1}{c| }{\bf Console } \\
\hline
+{Autochanger } & {No } & {No } & {Yes } & {No } \\
+\hline
{Catalog } & {Yes } & {No } & {No } & {No } \\
\hline
{Client } & {Yes } & {Yes } & {No } & {No } \\
\label{Names}
\index[general]{Authorization!Names Passwords and }
\index[general]{Names, Passwords and Authorization }
+\index[general]{Passwords}
\addcontentsline{toc}{subsection}{Names, Passwords and Authorization}
In order for one daemon to contact another daemon, it must authorize itself
\label{DirMaxConJobs}
\item [Maximum Concurrent Jobs = \lt{}number\gt{}]
- \index[dir]{Maximum Concurrent Jobs }
+\index[dir]{Maximum Concurrent Jobs }
+\index[general]{Simultaneous Jobs}
+\index[general]{Concurrent Jobs}
where \lt{}number\gt{} is the maximum number of total Director Jobs that
should run concurrently. The default is set to 1, but you may set it to a
larger number.
It is important to know that when the Volume Retention period expires,
Bacula does not automatically recycle a Volume. It attempts to keep the
- Volume data intact as long as possible before pruning it.
+ Volume data intact as long as possible before over writing the Volume.
- The default is 365 days. Note, this directive sets the default value
- for each Volume entry in the Catalog when the Volume is created. The
- value in the catalog may be later individually changed for each Volume
- using the Console program.
+ The default Volume retention period is 365 days. Note, this directive
+ sets the default value for each Volume entry in the Catalog when the
+ Volume is created. The value in the catalog may be later individually
+ changed for each Volume using the Console program.
By defining multiple Pools with different Volume Retention periods, you
may effectively have a set of tapes that is recycled weekly, another
\label{PoolRecycle}
\item [Recycle = \lt{}yes|no\gt{}]
\index[dir]{Recycle }
- This directive specifies the default for recycling Purged Volumes. If it is
-set to {\bf yes} and Bacula needs a volume but finds none that are
-appendable, it will search for Purged Volumes (i.e. volumes with all the Jobs
-and Files expired and thus deleted from the Catalog). If the Volume is
-recycled, all previous data written to that Volume will be overwritten.
+ This directive specifies whether or not Purged Volumes will be recycled.
+ If it is set to {\bf yes} (default) and Bacula needs a volume but finds
+ none that are appendable, it will search for and recycle (reuse) Purged
+ Volumes (i.e. volumes with all the Jobs and Files expired and thus
+ deleted from the Catalog). If the Volume is recycled, all previous data
+ written to that Volume will be overwritten. If Recycle is set to {\bf
+ no} you must manually set the recycle flag (update command) for
+ a Volume to be reused.
+
+ Please note that the value defined by this directive in the
+ bacula-dir.conf file is the default value used when a Volume is created.
+ Once the volume is created, changing the value in the bacula-dir.conf
+ file will not change what is stored for the Volume. To change the value
+ for an existing Volume you must use the {\bf update} command in the
+ Console.
-Please note that the value defined by this directive in the bacula-dir.conf
-file is the default value used when a Volume is created. Once the volume is
-created, changing the value in the bacula-dir.conf file will not change what
-is stored for the Volume. To change the value for an existing Volume you
-must use the {\bf update} command in the Console.
\label{RecycleOldest}
-
\item [Recycle Oldest Volume = \lt{}yes|no\gt{}]
\index[dir]{Recycle Oldest Volume }
- This directive instructs the Director to search for the oldest used Volume
-in the Pool when another Volume is requested by the Storage daemon and none
-are available. The catalog is then {\bf pruned} respecting the retention
-periods of all Files and Jobs written to this Volume. If all Jobs are
-pruned (i.e. the volume is Purged), then the Volume is recycled and will
-be used as the next Volume to be written. This directive respects any Job,
-File, or Volume retention periods that you may have specified, and as such
-it is {\bf much} better to use this directive than the Purge Oldest Volume.
-
-This directive can be useful if you have a fixed number of Volumes in the
-Pool and you want to cycle through them and you have specified the correct
-retention periods.
-However, if you use this directive and have only one
-Volume in the Pool, you will immediately recycle your Volume if you fill
-it and Bacula needs another one. Thus your backup will be totally invalid.
-Please use this directive with care.
+ This directive instructs the Director to search for the oldest used
+ Volume in the Pool when another Volume is requested by the Storage
+ daemon and none are available. The catalog is then {\bf pruned}
+ respecting the retention periods of all Files and Jobs written to this
+ Volume. If all Jobs are pruned (i.e. the volume is Purged), then the
+ Volume is recycled and will be used as the next Volume to be written.
+ This directive respects any Job, File, or Volume retention periods that
+ you may have specified, and as such it is {\bf much} better to use this
+ directive than the Purge Oldest Volume.
+
+ This directive can be useful if you have a fixed number of Volumes in the
+ Pool and you want to cycle through them and you have specified the correct
+ retention periods.
+
+ However, if you use this directive and have only one
+ Volume in the Pool, you will immediately recycle your Volume if you fill
+ it and Bacula needs another one. Thus your backup will be totally invalid.
+ Please use this directive with care. The default is {\no}.
\label{RecycleCurrent}
\item [Recycle Current Volume = \lt{}yes|no\gt{}]
\index[dir]{Recycle Current Volume }
- If Bacula needs a new Volume, this directive instructs Bacula to Prune the
-volume respecting the Job and File retention periods. If all Jobs are pruned
-(i.e. the volume is Purged), then the Volume is recycled and will be used as
-the next Volume to be written. This directive respects any Job, File, or
-Volume retention periods that you may have specified, and thus it is {\bf
-much} better to use it rather than the Purge Oldest Volume directive.
-
-This directive can be useful if you have: a fixed number of Volumes in the
-Pool, you want to cycle through them, and you have specified retention
-periods that prune Volumes before you have cycled through the Volume in the
-Pool.
-However, if you use this directive and have only one
-Volume in the Pool, you will immediately recycle your Volume if you fill
-it and Bacula needs another one. Thus your backup will be totally invalid.
-Please use this directive with care.
+ If Bacula needs a new Volume, this directive instructs Bacula to Prune
+ the volume respecting the Job and File retention periods. If all Jobs
+ are pruned (i.e. the volume is Purged), then the Volume is recycled and
+ will be used as the next Volume to be written. This directive respects
+ any Job, File, or Volume retention periods that you may have specified,
+ and thus it is {\bf much} better to use it rather than the Purge Oldest
+ Volume directive.
+
+ This directive can be useful if you have: a fixed number of Volumes in
+ the Pool, you want to cycle through them, and you have specified
+ retention periods that prune Volumes before you have cycled through the
+ Volume in the Pool.
+
+ However, if you use this directive and have only one Volume in the Pool,
+ you will immediately recycle your Volume if you fill it and Bacula needs
+ another one. Thus your backup will be totally invalid. Please use this
+ directive with care. The default is {\no}.
\label{PurgeOldest}
\item [Purge Oldest Volume = \lt{}yes|no\gt{}]
\index[dir]{Purge Oldest Volume }
- This directive instructs the Director to search for the oldest used Volume
-in the Pool when another Volume is requested by the Storage daemon and none
-are available. The catalog is then {\bf purged} irrespective of retention
-periods of all Files and Jobs written to this Volume. The Volume is then
-recycled and will be used as the next Volume to be written. This directive
-overrides any Job, File, or Volume retention periods that you may have
-specified.
-
-This directive can be useful if you have a fixed number of Volumes in the
-Pool and you want to cycle through them and reusing the oldest one when all
-Volumes are full, but you don't want to worry about setting proper retention
-periods. However, by using this option you risk losing valuable data.
-
-{\bf Please be aware that {\bf Purge Oldest Volume} disregards all retention
-periods.} If you have only a single Volume defined and you turn this variable
-on, that Volume will always be immediately overwritten when it fills! So at a
-minimum, ensure that you have a decent number of Volumes in your Pool before
-running any jobs. If you want retention periods to apply do not use this
-directive. To specify a retention period, use the {\bf Volume Retention}
-directive (see above).
-
-We {\bf highly} recommend against using this directive, because it is sure that
-some day, Bacula will recycle a Volume that contains current data.
+ This directive instructs the Director to search for the oldest used
+ Volume in the Pool when another Volume is requested by the Storage
+ daemon and none are available. The catalog is then {\bf purged}
+ irrespective of retention periods of all Files and Jobs written to this
+ Volume. The Volume is then recycled and will be used as the next Volume
+ to be written. This directive overrides any Job, File, or Volume
+ retention periods that you may have specified.
+
+ This directive can be useful if you have a fixed number of Volumes in
+ the Pool and you want to cycle through them and reusing the oldest one
+ when all Volumes are full, but you don't want to worry about setting
+ proper retention periods. However, by using this option you risk losing
+ valuable data.
+
+ Please be aware that {\bf Purge Oldest Volume} disregards all retention
+ periods. If you have only a single Volume defined and you turn this
+ variable on, that Volume will always be immediately overwritten when it
+ fills! So at a minimum, ensure that you have a decent number of Volumes
+ in your Pool before running any jobs. If you want retention periods to
+ apply do not use this directive. To specify a retention period, use the
+ {\bf Volume Retention} directive (see above).
+
+ We {\bf highly} recommend against using this directive, because it is
+ sure that some day, Bacula will recycle a Volume that contains current
+ data. The default is {\no}.
\item [Cleaning Prefix = \lt{}string\gt{}]
\index[dir]{Cleaning Prefix }
- This directive defines a prefix string, which if it matches the beginning
-of
-a Volume name during labeling of a Volume, the Volume will be defined with
-the VolStatus set to {\bf Cleaning} and thus Bacula will never attempt to use
-this tape. This is primarily for use with autochangers that accept barcodes
-where the convention is that barcodes beginning with {\bf CLN} are treated as
-cleaning tapes.
-\label{Label}
+ This directive defines a prefix string, which if it matches the
+ beginning of a Volume name during labeling of a Volume, the Volume will
+ be defined with the VolStatus set to {\bf Cleaning} and thus Bacula will
+ never attempt to use this tape. This is primarily for use with
+ autochangers that accept barcodes where the convention is that barcodes
+ beginning with {\bf CLN} are treated as cleaning tapes.
+\label{Label}
\item [Label Format = \lt{}format\gt{}]
\index[dir]{Label Format }
This directive specifies the format of the labels contained in this
pool. The format directive is used as a sort of template to create new
Volume names during automatic Volume labeling.
-The {\bf format} should be specified in double quotes, and consists of
-letters, numbers and the special characters hyphen ({\bf -}), underscore
-({\bf \_}), colon ({\bf :}), and period ({\bf .}), which are the legal
-characters for a Volume name. The {\bf format} should be enclosed in double
-quotes (").
-
-In addition, the format may contain a number of variable expansion characters
-which will be expanded by a complex algorithm allowing you to create Volume
-names of many different formats. In all cases, the expansion process must
-resolve to the set of characters noted above that are legal Volume names.
-Generally, these variable expansion characters begin with a dollar sign ({\bf
-\$}) or a left bracket ({\bf [}). If you specify variable expansion
-characters, you should always enclose the format with double quote characters
-({\bf "}). For more details on variable expansion, please see the
-\ilink{Variable Expansion}{_ChapterStart50} Chapter of this manual.
-
-If no variable expansion characters are found in the string, the Volume name
-will be formed from the {\bf format} string appended with the number of
-volumes in the pool plus one, which will be edited as four digits with
-leading zeros. For example, with a {\bf Label Format = "File-"}, the first
-volumes will be named {\bf File-0001}, {\bf File-0002}, ...
-
-With the exception of Job specific variables, you can test your {\bf
-LabelFormat} by using the
-\ilink{ var command}{var} the Console Chapter of this manual.
-
-In almost all cases, you should enclose the format specification (part after
-the equal sign) in double quotes. Please note that this directive is
-deprecated and is replaced in version 1.37 and greater with a Python script
-for creating volume names.
+ The {\bf format} should be specified in double quotes, and consists of
+ letters, numbers and the special characters hyphen ({\bf -}), underscore
+ ({\bf \_}), colon ({\bf :}), and period ({\bf .}), which are the legal
+ characters for a Volume name. The {\bf format} should be enclosed in
+ double quotes (").
+
+ In addition, the format may contain a number of variable expansion
+ characters which will be expanded by a complex algorithm allowing you to
+ create Volume names of many different formats. In all cases, the
+ expansion process must resolve to the set of characters noted above that
+ are legal Volume names. Generally, these variable expansion characters
+ begin with a dollar sign ({\bf \$}) or a left bracket ({\bf [}). If you
+ specify variable expansion characters, you should always enclose the
+ format with double quote characters ({\bf "}). For more details on
+ variable expansion, please see the \ilink{Variable
+ Expansion}{_ChapterStart50} Chapter of this manual.
+
+ If no variable expansion characters are found in the string, the Volume
+ name will be formed from the {\bf format} string appended with the
+ number of volumes in the pool plus one, which will be edited as four
+ digits with leading zeros. For example, with a {\bf Label Format =
+ "File-"}, the first volumes will be named {\bf File-0001}, {\bf
+ File-0002}, ...
+
+ With the exception of Job specific variables, you can test your {\bf
+ LabelFormat} by using the \ilink{ var command}{var} the Console Chapter
+ of this manual.
+
+ In almost all cases, you should enclose the format specification (part
+ after the equal sign) in double quotes. Please note that this directive
+ is deprecated and is replaced in version 1.37 and greater with a Python
+ script for creating volume names.
\end{description}
In order for a Pool to be used during a Backup Job, the Pool must have at
-least one Volume associated with it. Volumes are created for a Pool using the
-{\bf label} or the {\bf add} commands in the {\bf Bacula Console}, program. In
-addition to adding Volumes to the Pool (i.e. putting the Volume names in the
-Catalog database), the physical Volume must be labeled with a valid Bacula
-software volume label before {\bf Bacula} will accept the Volume. This will be
-automatically done if you use the {\bf label} command. Bacula can
-automatically label Volumes if instructed to do so, but this feature is not
-yet fully implemented.
+least one Volume associated with it. Volumes are created for a Pool using
+the {\bf label} or the {\bf add} commands in the {\bf Bacula Console},
+program. In addition to adding Volumes to the Pool (i.e. putting the
+Volume names in the Catalog database), the physical Volume must be labeled
+with a valid Bacula software volume label before {\bf Bacula} will accept
+the Volume. This will be automatically done if you use the {\bf label}
+command. Bacula can automatically label Volumes if instructed to do so,
+but this feature is not yet fully implemented.
The following is an example of a valid Pool resource definition:
\addcontentsline{toc}{subsection}{Catalog Resource}
The Catalog Resource defines what catalog to use for the current job.
-Currently, Bacula can only handle a single database server (SQLite, MySQL,
-PostgreSQL) that is defined when configuring {\bf Bacula}. However, there may be
-as many Catalogs (databases) defined as you wish. For example, you may want
-each Client to have its own Catalog database, or you may want backup jobs to
-use one database and verify or restore jobs to use another database.
+Currently, Bacula can only handle a single database server (SQLite, MySQL,
+PostgreSQL) that is defined when configuring {\bf Bacula}. However, there
+may be as many Catalogs (databases) defined as you wish. For example, you
+may want each Client to have its own Catalog database, or you may want
+backup jobs to use one database and verify or restore jobs to use another
+database.
\begin{description}
\begin{itemize}
\item The first console type is an {\bf anonymous} or {\bf default} console,
- which has full privileges. There is no console resource necessary for this
- type since the password is specified in the Director's resource and
-consequently such consoles do not have a name as defined on a {\bf Name =}
-directive. This is the kind of console that was initially implemented in
-versions prior to 1.33 and remains valid. Typically you would use it only for
- administrators.
+ which has full privileges. There is no console resource necessary for
+ this type since the password is specified in the Director's resource and
+ consequently such consoles do not have a name as defined on a {\bf Name
+ =} directive. This is the kind of console that was initially
+ implemented in versions prior to 1.33 and remains valid. Typically you
+ would use it only for administrators.
+
\item The second type of console, and new to version 1.33 and higher is a
- "named" console defined within a Console resource in both the Director's
- configuration file and in the Console's configuration file. Both the names
-and the passwords in these two entries must match much as is the case for
-Client programs.
-
-This second type of console begins with absolutely no privileges except those
-explicitly specified in the Director's Console resource. Thus you can have
-multiple Consoles with different names and passwords, sort of like multiple
-users, each with different privileges. As a default, these consoles can do
-absolutely nothing -- no commands whatsoever. You give them privileges or
-rather access to commands and resources by specifying access control lists
-in the Director's Console resource. The ACLs are specified by a directive
-followed by a list of access names. Examples of this are shown below.
+ "named" console defined within a Console resource in both the Director's
+ configuration file and in the Console's configuration file. Both the
+ names and the passwords in these two entries must match much as is the
+ case for Client programs.
+
+ This second type of console begins with absolutely no privileges except
+ those explicitly specified in the Director's Console resource. Thus you
+ can have multiple Consoles with different names and passwords, sort of
+ like multiple users, each with different privileges. As a default,
+ these consoles can do absolutely nothing -- no commands whatsoever. You
+ give them privileges or rather access to commands and resources by
+ specifying access control lists in the Director's Console resource. The
+ ACLs are specified by a directive followed by a list of access names.
+ Examples of this are shown below.
+
\item The third type of console is similar to the above mentioned one in that
- it requires a Console resource definition in both the Director and the
- Console. In addition, if the console name, provided on the {\bf Name =}
-directive, is the same as a Client name, that console is permitted to use the
-{\bf SetIP} command to change the Address directive in the Director's client
-resource to the IP address of the Console. This permits portables or other
-machines using DHCP (non-fixed IP addresses) to "notify" the Director of
-their current IP address.
+ it requires a Console resource definition in both the Director and the
+ Console. In addition, if the console name, provided on the {\bf Name =}
+ directive, is the same as a Client name, that console is permitted to
+ use the {\bf SetIP} command to change the Address directive in the
+ Director's client resource to the IP address of the Console. This
+ permits portables or other machines using DHCP (non-fixed IP addresses)
+ to "notify" the Director of their current IP address.
\end{itemize}
The Console resource is optional and need not be specified. The following
\item [Password = \lt{}password\gt{}]
\index[dir]{Password }
- Specifies the password that must be supplied for a named Bacula Console to
-be
-authorized. The same password must appear in the {\bf Console} resource of
-the Console configuration file. For added security, the password is never
-actually passed across the network but rather a challenge response hash code
-created with the password. This directive is required. If you have either
-{\bf /dev/random} {\bf bc} on your machine, Bacula will generate a random
-password during the configuration process, otherwise it will be left blank.
+ Specifies the password that must be supplied for a named Bacula Console
+ to be authorized. The same password must appear in the {\bf Console}
+ resource of the Console configuration file. For added security, the
+ password is never actually passed across the network but rather a
+ challenge response hash code created with the password. This directive
+ is required. If you have either {\bf /dev/random} {\bf bc} on your
+ machine, Bacula will generate a random password during the configuration
+ process, otherwise it will be left blank.
\item [JobACL = \lt{}name-list\gt{}]
\index[dir]{JobACL }
- This directive is used to specify a list of Job resource names that can be
-accessed by the console. Without this directive, the console cannot access
-any of the Director's Job resources. Multiple Job resource names may be
-specified by separating them with commas, and/or by specifying multiple
-JobACL directives. For example, the directive may be specified as:
+ This directive is used to specify a list of Job resource names that can
+ be accessed by the console. Without this directive, the console cannot
+ access any of the Director's Job resources. Multiple Job resource names
+ may be specified by separating them with commas, and/or by specifying
+ multiple JobACL directives. For example, the directive may be specified
+ as:
\footnotesize
\begin{verbatim}
\label{AuthorizationErrors}
\subsection*{I'm Getting Authorization Errors. What is Going On? }
\item [I'm Getting Authorization Errors. What is Going On? ]
- \index[general]{I'm Getting Authorization Errors. What is Going On? }
+\index[general]{Authorization Errors}
+\index[general]{Concurrent Jobs}
For security reasons, Bacula requires that both the File daemon and the
Storage daemon know the name of the Director as well as its password. As a
consequence, if you change the Director's name or password, you must make
Why? }
\item [Bacula Runs Fine but Cannot Access a Client on a Different Machine.
Why? ]
- \index[general]{Bacula Runs Fine but Cannot Access a Client on a Different
- Machine. Why? }
+\index[general]{Cannot Access a Client}
There are several reasons why Bacula could not contact a client on a
different machine. They are:
problems?}
\item [All my Jobs are scheduled for the same time. Will this cause
problems? ]
- \index[general]{All my Jobs are scheduled for the same time. Will this cause
- problems? }
+\index[general]{Schedule problems}
No, not at all. Bacula will schedule all the Jobs at the same time, but will
run them one after another unless you have increased the number of
simultaneous jobs in the configuration files for the Director, the File
\subsection*{Can Bacula Backup and Restore Files Greater than 2 Gigabytes?}
\item [Can Bacula Backup and Restore Files Greater than 2 Gigabytes in
Size? ]
-\index[general]{Can Bacula Backup and Restore Files Greater than 2 Gigabytes in
-Size? }
+\index[general]{Large file support}
If your operating system permits it, and you are running Bacula version 1.26
or later, the answer is yes. To the best of our knowledge all client system
supported by Bacula can handle files larger than 2 Gigabytes.
there a better way than {\bf ./bacula stop} to stop it?}
\item [I Started A Job then Decided I Really Did Not Want to Run It. Is
there a better way than {\bf ./bacula stop} to stop it?]
- \index[general]{I Started A Job then Decided I Really Did Not Want to
- Run It. Is there a better way than ./bacula stop to stop it? } Yes,
+\index[general]{Cancelling jobs}
+ Yes,
you normally should use the Console command {\bf cancel} to cancel a Job
that is either scheduled or running. If the Job is scheduled, it will
be marked for cancellation and will be canceled when it is scheduled to
Bacula\raisebox{.6ex}{{\footnotesize \textsuperscript{\textregistered}}}?}
\item [Why have You Trademarked the Name
Bacula\raisebox{.6ex}{{\footnotesize \textsuperscript{\textregistered}}}?]
-\index[general]{Why have You Trademarked the Name
-Bacula\textsuperscript{\textregistered}? }
+\index[general]{Bacula Trademark}
We have trademarked the name Bacula to ensure that all media written by any
program named Bacula will always be compatible. Anyone may use the name
Bacula, even in a derivative product as long as it remains totally compatible
\subsection*{Why is Your Online Document for Version 1.37 but the Released Version is 1.36?}
\item [Why is Your Online Document for Version 1.37 of Bacula when the
Currently Release Version is 1.36?]
-\index[general]{Why is Your Online Document for Version 1.37 but Released Version is 1.36? }
+\index[general]{Multiple manuals}
As Bacula is being developed, the document is also being enhanced, more often
than not it has clarifications of existing features that can be very useful
to our users, so we publish the very latest document. Fortunately it is rare
\subsection*{My retention periods don't work}
\item [I Change Recycling, Retention Periods, or File Sizes in my Pool
Resource and they Still Don't Work.]
- \index[general]{I Change Recycling, Retention Periods, or File Sizes in my
-Pool
- Resource and they Still Don't Work. }
+\index[general]{Recycling}
+\index[general]{Retention Periods}
+\index[general]{Pool changes}
The different variables associated with a Pool are defined in the Pool
Resource, but are actually read by Bacula from the Catalog database. On
Bacula versions prior to 1.30, after changing your Pool Resource, you must
\subsection*{Why aren't my files compressed?}
\item [I Have Configured Compression On, But None of My Files Are
Compressed. Why?]
- \index[general]{I Have Configured Compression On, But None of My Files Are
- Compressed. Why? }
+\index[general]{Compression}
There are two kinds of compression. One is tape compression. This is done by
the tape drive hardware, and you either enable or disable it with system
tools such as {\bf mt}. This compression works independently of Bacula.
\label{NewTape}
\item [Bacula is Asking for a New Tape After 2 GB of Data but My Tape
holds 33 GB. Why?]
-\index[general]{Bacula is Asking for a New Tape After 2 GB of Data but My Tape
-holds 33 GB. Why? }
+\index[general]{Tape capacity}
There are several reasons why Bacula will request a new tape.
\begin{itemize}
\subsection*{Incremental backups are not working}
\item [Bacula is Not Doing the Right Thing When I Request an Incremental
Backup. Why?]
- \index[general]{Bacula is Not Doing the Right Thing When I Request an
-Incremental
- Backup. Why? }
+ \index[general]{Incremental backups}
As explained in one of the previous questions, Bacula will automatically
upgrade an Incremental or Differential job to a Full backup if it cannot
find
(Dependency Packages). This can vastly simplify your life by providing you
with all the necessary packages rather than requiring you to find them on the
Web, load them, and install them.
-\label{upgrading1}
+\subsection*{Source Release Files}
+\index[general]{Source Files}
+\index[general]{Release Files}
+\addcontentsline{toc}{subsection}{Source Release File}
+Beginning with Bacula 1.38.0, the source code has been broken into
+four separate tar files each corresponding to a different module in
+the Bacula CVS. The released files are:
+
+\begin{description}
+\item [bacula-1.38.0.tar.gz]
+ This is the primary source code release for Bacula. On each
+ release the version number (1.38.0) will be updated.
+
+\item [bacula-docs-1.38.0.tar.gz]
+ This file contains a copy of the docs directory with the
+ documents prebuild. English html directory, single html
+ file, and pdf file. The French and German translations
+ are in progress, but are not built.
+
+\item [bacula-gui-1.38.0.tar.gz]
+ This file contains the non-core GUI programs. Currently,
+ it contains bacula-web, a PHP program for producing management
+ viewing of your Bacula job status in a browser; and bimagemgr
+ a browser program for burning CDROM images with Bacula Volumes.
+
+\item [bacula-rescue-1.8.1.tar.gz]
+ This is the Bacula Rescue CDROM code. Note, the version number
+ of this package is not tied to the Bacula release version, so
+ it will be different. Using this code, you can burn a CDROM
+ with your system configuration and containing a statically
+ linked version of the File daemon. This can permit you to easily
+ repartition and reformat your hard disks and reload your
+ system with Bacula in the case of a hard disk failure.
+
+\end{description}
+
+\label{upgrading1}
\subsection*{Upgrading Bacula}
\index[general]{Bacula!Upgrading }
\index[general]{Upgrading Bacula }
and the version to which you are upgrading. If the Bacula catalog database has
been upgraded, you will either need to reinitialize your database starting
from scratch, or save an ASCII copy of your database, then proceed to upgrade
-it. If there are several database upgrades between your version and the
+it. This is normally done after Bacula is build and installed by:
+
+\begin{verbatim}
+cd <installed-scripts-dir> (default /etc/bacula)
+./update_bacula_tables
+\end{verbatim}
+
+This update script can also be find in the Bacula source src/cats
+directory.
+
+If there are several database upgrades between your version and the
version to which you are upgrading, you will need to apply each database
upgrade script. For your convenience, you can find all the old upgrade scripts
in the {\bf upgradedb} directory of the source code. You will need to edit the
scripts to correspond to your system configuration. The final upgrade script,
-if any, will be in the {\bf src/cats} directory as described in the
-ReleaseNotes.
+if any, can be applied as noted above.
If you are upgrading from one major version to another, you will need to
replace all your components at the same time as generally the inter-daemon
Finally, please note that in general it is not necessary to do a
{\bf make uninstall} before doing an upgrade. In fact, if you do so, you will
most likely delete all your conf files, which could be disastrous.
+The normal procedure during an upgrade is simply {\bf make install}.
+In general none of your existing .conf or .sql files will be overwritten.
+
For additional information on upgrading, please see the \ilink{Upgrading Bacula
Versions}{upgrading} in the Tips chapter of this manual.
\item Detar the {\bf depkg} into the {\bf bacula} directory.
\item cd bacula/depkgs
\item make
- \end{enumerate}
+\end{enumerate}
Although the exact composition of the dependency packages may change from time
to time, the current makeup is the following:
min/max block sizes, ...).
The {\bf depkgs-win32} package contains the source code for the pthreads,
-zlib, and wxWidgets libraries used by the native Win32 client program.
-It will only be needed
-if you intend to build the Win32 client from source.
+zlib, and wxWidgets libraries used by the native Win32 client program. It
+will only be needed if you intend to build the Win32 client from source.
\subsection*{Supported Operating Systems}
\label{Systems}
in the {\bf libz-devel} package. On Debian systems, you will need to load the
{\bf zlib1g-dev} package. If you are not using rpms or debs, you will need to
find the appropriate package for your system.
+
Note, if you already have a running MySQL or PostgreSQL on your system, you
can skip this phase provided that you have built the thread safe libraries.
And you have already installed the additional rpms noted above.
+
\item As an alternative to MySQL and PostgreSQL, configure and install SQLite,
which is part of the {\bf depkgs}.
\ilink{Installing and Configuring SQLite}{_ChapterStart33}.
- \item Detar the Bacula source code preferably into the {\bf bacula} directory
+
+\item Detar the Bacula source code preferably into the {\bf bacula} directory
discussed above.
+
\item {\bf cd} to the directory containing the source code.
+
\item ./configure (with appropriate options as described below)
+
\item Check the output of ./configure very carefully, especially the Install
binaries and Install config directories. If they are not correct,
please rerun ./configure until they are. The output from ./configure is
stored in {\bf config.out} and can be re-displayed at any time without
rerunning the ./configure by doing {\bf cat config.out}.
+
\item If after running ./configure once, you decide to change options and
re-run it, that is perfectly fine, but before re-running it, you should run:
\footnotesize
\begin{verbatim}
make distclean
-
\end{verbatim}
\normalsize
make distclean} is also critical if you move the source directory from one
machine to another. If the {\bf make distclean} fails, just ignore it and
continue on.
+
\item make
+ If you get errors while linking in the Storage daemon directory
+ (src/stored), it is probably because you have not loaded the static
+ libraries on your system. I noticed this problem on a Solaris system.
+ To correct it, make sure that you have not added {\bf
+ {-}{-}enable-static-tools} to the {\bf ./configure} command.
- If you get errors while linking in the Storage daemon directory (src/stored),
-it is probably because you have not loaded the static libraries on your
-system. I noticed this problem on a Solaris system. To correct it, make sure
-that you have not added {\bf \verb:--:enable-static-tools} to the {\bf ./configure}
-command.
\item make install
-\item If you are new to Bacula, we {\bf strongly} recommend that you skip the
- next step and use the default configuration files, then run the example
- program in the next chapter, then come back and modify your configuration
-files to suit your particular needs.
+
+\item If you are new to Bacula, we {\bf strongly} recommend that you skip
+ the next step and use the default configuration files, then run the
+ example program in the next chapter, then come back and modify your
+ configuration files to suit your particular needs.
+
\item Customize the configuration files for each of the three daemons
- (Directory, File, Storage) and for the Console program. For the details of
- how to do this, please see
-\ilink{Setting Up Bacula Configuration Files}{_ChapterStart16} in
-the Configuration chapter of this manual. We recommend that you start by
-modifying the default configuration files supplied, making the minimum
-changes necessary. Complete customization can be done after you have Bacula
-up and running. Please take care when modifying passwords, which were
-randomly generated, and the {\bf Name}s as the passwords and names must agree
-between the configuration files for security reasons.
-\item Create the Bacula MySQL database and tables (if using MySQL)
- \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or
- create the Bacula PostgreSQL database and tables
-\ilink{Installing and Configuring PostgreSQL Phase
-II}{PostgreSQL_phase2} or alternatively if you are using
-SQLite
-\ilink{Installing and Configuring SQLite Phase II}{phase2}.
+ (Directory, File, Storage) and for the Console program. For the details
+ of how to do this, please see \ilink{Setting Up Bacula Configuration
+ Files}{_ChapterStart16} in the Configuration chapter of this manual. We
+ recommend that you start by modifying the default configuration files
+ supplied, making the minimum changes necessary. Complete customization
+ can be done after you have Bacula up and running. Please take care when
+ modifying passwords, which were randomly generated, and the {\bf Name}s
+ as the passwords and names must agree between the configuration files
+ for security reasons. \item Create the Bacula MySQL database and tables
+ (if using MySQL)
+ \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or
+ create the Bacula PostgreSQL database and tables
+ \ilink{Installing and Configuring PostgreSQL Phase
+ II}{PostgreSQL_phase2} or alternatively if you are using
+ SQLite
+ \ilink{Installing and Configuring SQLite Phase II}{phase2}.
+
\item Start Bacula ({\bf ./bacula start}) Note. the next chapter shows you
how to do this in detail.
+
\item Interface with Bacula using the Console program
+
\item For the previous two items, please follow the instructions in the
\ilink{Running Bacula}{_ChapterStart1} chapter of this manual,
where you will run a simple backup and do a restore. Do this before you make
-heavy modifications to the configuration files so that you are sure that
-Bacula works and are familiar with it. After that changing the conf files
-will be easier.
+ heavy modifications to the configuration files so that you are sure that
+ Bacula works and are familiar with it. After that changing the conf files
+ will be easier.
\item If after installing Bacula, you decide to "move it", that is to
install it in a different set of directories, proceed as follows:
customize your installation.
\begin{description}
-
\item [ {-}{-}sysbindir=\lt{}binary-path\gt{}]
\index[general]{{-}{-}sysbindir }
Defines where the Bacula binary (executable) files will be placed during a
from with in the {\bf src/filed} directory. Also, the {\bf
\verb:--:enable-client-only} option described below is useful for just
building a client so that all the other parts of the program are not
- compiled.
+ compiled.
+
+ When linking a static binary, the linker needs the static versions
+ of all the libraries that are used, so frequently users will
+ experience linking errors when this option is used. The first
+ thing to do is to make sure you have the static glibc library
+ installed on your system. The second thing to do is the make sure
+ you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./configure statement as these options require additional
+ libraries. You may be able to enable those options, but you will
+ need to load additional static libraries.
+
\item [ {-}{-}enable-static-sd]
\index[general]{{-}{-}enable-static-sd }
addition to the standard Storage daemon. This static version will
include statically linked libraries and could be useful during a Bare
Metal recovery.
+
+ When linking a static binary, the linker needs the static versions
+ of all the libraries that are used, so frequently users will
+ experience linking errors when this option is used. The first
+ thing to do is to make sure you have the static glibc library
+ installed on your system. The second thing to do is the make sure
+ you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./configure statement as these options require additional
+ libraries. You may be able to enable those options, but you will
+ need to load additional static libraries.
+
\item [ {-}{-}enable-static-dir]
\index[general]{{-}{-}enable-static-dir }
- This option causes the make process to build a {\bf static-bacula-dir} in
- addition to the standard Director. This static version will include
- statically linked libraries and could be useful during a Bare Metal recovery.
+ This option causes the make process to build a {\bf static-bacula-dir}
+ in addition to the standard Director. This static version will include
+ statically linked libraries and could be useful during a Bare Metal
+ recovery.
+
+ When linking a static binary, the linker needs the static versions
+ of all the libraries that are used, so frequently users will
+ experience linking errors when this option is used. The first
+ thing to do is to make sure you have the static glibc library
+ installed on your system. The second thing to do is the make sure
+ you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./configure statement as these options require additional
+ libraries. You may be able to enable those options, but you will
+ need to load additional static libraries.
\item [ {-}{-}enable-static-cons]
\index[general]{{-}{-}enable-static-cons }
- This option causes the make process to build a {\bf static-console} and a
- {\bf static-gnome-console} in addition to the standard console. This static
- version will include statically linked libraries and could be useful during a
- Bare Metal recovery.
+ This option causes the make process to build a {\bf static-console} and
+ a {\bf static-gnome-console} in addition to the standard console. This
+ static version will include statically linked libraries and could be
+ useful during a Bare Metal recovery.
+
+ When linking a static binary, the linker needs the static versions
+ of all the libraries that are used, so frequently users will
+ experience linking errors when this option is used. The first
+ thing to do is to make sure you have the static glibc library
+ installed on your system. The second thing to do is the make sure
+ you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./configure statement as these options require additional
+ libraries. You may be able to enable those options, but you will
+ need to load additional static libraries.
+
\item [ {-}{-}enable-client-only]
\index[general]{{-}{-}enable-client-only }
- This option causes the make process to build only the File daemon and the
- libraries that it needs. None of the other daemons, storage tools, nor the
- console will be built. Likewise a {\bf make install} will then only install
- the File daemon. To cause all daemons to be built, you will need to do a
- configuration without this option. This option greatly facilitates building a
- Client on a client only machine.
+ This option causes the make process to build only the File daemon and
+ the libraries that it needs. None of the other daemons, storage tools,
+ nor the console will be built. Likewise a {\bf make install} will then
+ only install the File daemon. To cause all daemons to be built, you
+ will need to do a configuration without this option. This option
+ greatly facilitates building a Client on a client only machine.
+
+ When linking a static binary, the linker needs the static versions
+ of all the libraries that are used, so frequently users will
+ experience linking errors when this option is used. The first
+ thing to do is to make sure you have the static glibc library
+ installed on your system. The second thing to do is the make sure
+ you do not specify {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./configure statement as these options require additional
+ libraries. You may be able to enable those options, but you will
+ need to load additional static libraries.
+
\item [ {-}{-}enable-largefile]
\index[general]{{-}{-}enable-largefile }
\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
this manual for more details.
+ See the note below under the {-}{-}with-postgresql item.
+
\item [ {-}{-}with-sqlite3=\lt{}sqlite3-path\gt{}]
\index[general]{{-}{-}with-sqlite3 }
- This enables use of the SQLite version 3.x database. The {\bf sqlite3-path} is not
- normally specified as Bacula looks for the necessary components in a
- standard location ({\bf depkgs/sqlite3}). Although Bacula will run
- with SQLite version 3.x, our testing shows that it is 4 to 10 times
- slower than version 2.8.x and consequently, we do not recommend using
- it. See
+ This enables use of the SQLite version 3.x database. The {\bf
+ sqlite3-path} is not normally specified as Bacula looks for the
+ necessary components in a standard location ({\bf depkgs/sqlite3}). See
\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
- this manual for more details.
+ this manual for more details.
\item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}]
\index[general]{{-}{-}with-mysql }
- This enables building of the Catalog services for Bacula. It assumes that
- MySQL is running on your system, and expects it to be installed in the {\bf
- mysql-path} that you specify. If this option is not present, the build will
- automatically include the internal Bacula database code. We recommend that
- you use this option if possible. If you do use this option, please proceed to
- installing MySQL in the
- \ilink{Installing and Configuring MySQL}{_ChapterStart} chapter
- before proceeding with the configuration.
+ This enables building of the Catalog services for Bacula. It assumes
+ that MySQL is running on your system, and expects it to be installed in
+ the {\bf mysql-path} that you specify. Normally, if MySQL is installed
+ in a standard system location, you can simply use {\bf {-}{-}with-mysql}
+ with no path specification. If you do use this option, please proceed
+ to installing MySQL in the \ilink{Installing and Configuring
+ MySQL}{_ChapterStart} chapter before proceeding with the configuration.
+
+ See the note below under the {-}{-}with-postgresql item.
+
+\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
+ \index[general]{{-}{-}with-postgresql }
+ This provides an explicit path to the PostgreSQL libraries if Bacula
+ cannot find it by default. Normally to build with PostgreSQL, you would
+ simply use {\bf {-}{-}with-postgresql}.
+
+ Note, for Bacula to be configured properly, you must specify one
+ of the four database options supported. That is:
+ {-}{-}with-sqlite, {-}{-}with-sqlite3, {-}{-}with-mysql, or
+ {-}{-}with-postgresql, otherwise the ./configure will fail.
\item [ {-}{-}with-openssl=\lt{}path\gt{}]
This configuration option is necessary if you want to enable TLS (ssl)
between the daemons. For more information on using TLS, please see the
\ilink{Bacula TLS}{_ChapterStart61} chapter of this manual.
-\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
- \index[general]{{-}{-}with-postgresql }
- This provides an explicit path to the PostgreSQL libraries if Bacula cannot
- find it by default.
\item [ {-}{-}with-python=\lt{}path\gt{}]
\index[general]{{-}{-}with-python }
\item [ {-}{-}enable-conio]
\index[general]{{-}{-}enable-conio }
- Tells Bacula to enable building the small, light weight readline replacement
- routine. It is generally much easier to configure than readline, although,
- like readline, it needs either the termcap or ncurses library.
+ Tells Bacula to enable building the small, light weight readline
+ replacement routine. It is generally much easier to configure than
+ readline, although, like readline, it needs either the termcap or
+ ncurses library.
\item [ {-}{-}with-readline=\lt{}readline-path\gt{}]
\index[general]{{-}{-}with-readline }
- Tells Bacula where {\bf readline} is installed. Normally, Bacula will find
- readline if it is in a standard library. If it is not found and no
- \verb:--:with-readline is specified, readline will be disabled. This option affects
- the Bacula build. Readline provides the Console program with a command line
- history and editing capability and is no longer supported, so you are on your
- own if you have problems.
+ Tells Bacula where {\bf readline} is installed. Normally, Bacula will
+ find readline if it is in a standard library. If it is not found and no
+ {-}{-}with-readline is specified, readline will be disabled. This
+ option affects the Bacula build. Readline provides the Console program
+ with a command line history and editing capability and is no longer
+ supported, so you are on your own if you have problems.
\item [ {-}{-}enable-readline]
\index[general]{{-}{-}enable-readline }
\end{description}
-Note, many other options are presented when you do a {\bf ./configure \verb:--:help},
-but they are not implemented.
+Note, many other options are presented when you do a {\bf ./configure
+\verb:--:help}, but they are not implemented.
\subsection*{Recommended Options for most Systems}
\index[general]{Systems!Recommended Options for most }
\addcontentsline{toc}{subsection}{Windows Systems with CYGWIN Installed}
As of version 1.34, Bacula no longer uses CYGWIN for the Win32 File daemon.
-However, it is still built under a CYGWIN build environment -- though you can
-probably do it with VC Studio only. If you wish to build the Win32 File daemon
-from the source, you will need Microsoft C++ version 6.0 or greater. In Bacula
-prior to version 1.33, CYGWIN was used. Details for building it are in the
-README.win32 file of the src/win32 directory.
+However, it is still built under a CYGWIN build environment -- though you
+can probably do it with VC Studio only. If you wish to build the Win32
+File daemon from the source, you will need Microsoft C++ version 7.1.
+Details for building the Win32 FD are in the README.win32 file of the
+src/win32 directory.
Note, although most parts of Bacula build on Windows systems, the only part
that we have tested and used is the File daemon.
fresh copy of the source tree, or using {\bf make\ distclean} before the {\bf
./configure}.
-Since the File daemon does not access the Catalog database, you can remove the
-{\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then add {\bf
-\verb:--:enable-client-only}. This will compile only the necessary libraries and the
-client programs and thus avoids the necessity of installing one or another of
-those database programs to build the File daemon. With the above option, you
-simply enter {\bf make} and just the client will be built.
+Since the File daemon does not access the Catalog database, you can remove
+the {\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then
+add {\bf \verb:--:enable-client-only}. This will compile only the
+necessary libraries and the client programs and thus avoids the necessity
+of installing one or another of those database programs to build the File
+daemon. With the above option, you simply enter {\bf make} and just the
+client will be built.
\label{autostart}
\subsection*{Auto Starting the Daemons}
\end{verbatim}
\normalsize
-Please note, that the auto-start feature is implemented only on systems that
-we officially support (currently, FreeBSD, RedHat/Fedora Linux, and Solaris), and has
-only been fully tested on Fedora Linux.
+Please note, that the auto-start feature is implemented only on systems
+that we officially support (currently, FreeBSD, RedHat/Fedora Linux, and
+Solaris), and has only been fully tested on Fedora Linux.
-The {\bf make install-autostart} will cause the appropriate startup scripts to
-be installed with the necessary symbolic links. On RedHat/Fedora Linux systems, these
-scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
-/etc/rc.d/init.d/bacula-fd}, and {\bf /etc/rc.d/init.d/bacula-sd}. However the
-exact location depends on what operating system you are using.
+The {\bf make install-autostart} will cause the appropriate startup scripts
+to be installed with the necessary symbolic links. On RedHat/Fedora Linux
+systems, these scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
+/etc/rc.d/init.d/bacula-fd}, and {\bf /etc/rc.d/init.d/bacula-sd}. However
+the exact location depends on what operating system you are using.
If you only wish to install the File daemon, you may do so with:
made to your configuration files as the installation process will not
overwrite them providing that you do not do a {\bf make uninstall}.
+If the new version of Bacula requires an upgrade to the database,
+you can upgrade it with the script {\bf update_bacula_tables}, which
+will be installed in your scripts directory (default {\bf /etc/bacula}),
+or alternatively, you can find it in the
+{\bf \lt{}bacula-source\gt{}/src/cats} directory.
+
\subsection*{Getting Notified of Job Completion}
\label{notification}
\index[general]{Getting Notified of Job Completion }
\label{ConcurrentJobs}
\index[general]{Jobs!Running Concurrent}
\index[general]{Running Concurrent Jobs}
+\index[general]{Concurrent Jobs}
\addcontentsline{toc}{subsection}{Running Concurrent Jobs}
Bacula can run multiple concurrent jobs, but the default configuration files
\index[dir]{Run directive}
\index[dir]{Clone a Job}
The Run directive (not to be confused with the Run option in a
- Schedule) allows you to clone jobs and thus, if you want backup
+ Schedule) allows you to start other jobs or to clone jobs. By using the
+ cloning keywords (see below), you can backup
the same data (or almost the same data) to two or more drives
at the same time. The {\bf job-name} is normally the same name
as the current Job resource (thus creating a clone). However, it
Options { This
wildfile = "*.Z" example
wildfile = "*.gz" doesn't
- Include = yes work
+ work
} !!!!!!!!!!!!
File = /myfile
}
Options {
wildfile = "*.Z"
wildfile = "*.gz"
- Include = yes
}
Options {
Exclude = yes
For 64 bit support add '--define "build_x86_64 1"'
\end{verbatim}
\normalsize
+
+\subsection*{Build Options}
+\index[general]{Build Options}
+\addcontentsline{toc}{subsection}{Build Options}
+The spec file currently supports building on the following platforms:
+\footnotesize
+\begin{verbatim}
+# RedHat builds
+--define "build_rh8 1"
+--define "build_rh9 1"
+
+# Fedora Core build
+--define "build_fc1 1"
+--define "build_fc3 1"
+
+# Whitebox Enterprise build
+--define "build_wb3 1"
+
+# RedHat Enterprise builds
+--define "build_rhel3 1"
+--define "build_rhel4 1"
+
+# CentOS build
+--define "build_centos4 1"
+
+# SuSE build
+--define "build_su9 1"
+
+# Mandrake build
+--define "build_mdk 1"
+
+MySQL support:
+
+--define "build_mysql 1"
+# if using mysql 4.x define this and mysql above
+# currently: Mandrake 10.x, SuSE 9.x, RHEL4
+--define "build_mysql4 1"
+
+PostgreSQL support:
+--define "build_postgresql 1"
+
+Sqlite support:
+--define "build_sqlite 1"
+
+\end{verbatim}
+\normalsize
+
+
-1.38.0 (28 October 2005)
+1.39.0 (05 November 2005)
projects / bacula / docs / commitdiff