# autoconf/Make.common.in -*- Makefile -*-
# release date (man), LSM date, version number/name, current maintainer
-DATE="26 July 2005"
+DATE="03 August 2005"
LSMDATE=@LSMDATE@
-VERSION=1.37.32
+VERSION=1.37.34
VERNAME=bacula-$(VERSION)#
MAINT=Kern Sibbald#
MAINTEMAIL=<kern@sibbald.com>#
all:
(cd manual; make)
- (cd developers; make developers)
+ (cd developers; make)
configure: autoconf/configure.in autoconf/aclocal.m4 autoconf/acconfig.h autoconf/config.h.in
all:
(cd manual; make)
- (cd developers; make developers)
+ (cd developers; make)
configure: autoconf/configure.in autoconf/aclocal.m4 autoconf/acconfig.h autoconf/config.h.in
@echo "Making developers html"
@cp -fp ${IMAGES}/*.eps .
@rm -f next.eps next.png prev.eps prev.png up.eps up.png
- @(if [ -e imagename_translations ] ; then \
+ @(if [ -f imagename_translations ] ; then \
./translate_images.pl --from_meaningful_names developers.html; \
fi)
latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \
@rm -f next.eps next.png prev.eps prev.png up.eps up.png
@cp -fp ${IMAGES}/*.eps ${IMAGES}/*.png developers/
@rm -f developers/next.eps developers/next.png developers/prev.eps developers/prev.png developers/up.eps developers/up.png
- @(if [ -e developers/imagename_translations ] ; then \
+ @(if [ -f developers/imagename_translations ] ; then \
./translate_images.pl --to_meaningful_names developers/Bacula_Users_Guide.html; \
fi)
@rm -rf developers/*.html
-img4.png\ 1./flow.eps
-img6.png\ 1./Conf-Diagram.eps
-img7.png\ 1./bimagemgr1.eps
-img8.png\ 1./bimagemgr2.eps
-img10.png\ 1./win32-nsis.eps
-img12.png\ 1./win32-pkg.eps
-img13.png\ 1./win32-location.eps
-img14.png\ 1./win32-service.eps
-img15.png\ 1./win32-service-ok.eps
-img16.png\ 1./win32-start.eps
-img17.png\ 1./win32-finish.eps
-img18.png\ 1./idle.eps
-img20.png\ 1./menu.eps
-img21.png\ 1./running.eps
-img22.png\ 1./error.eps
-img23.png\ 1./access-is-denied.eps
-img25.png\ 1./properties-security.eps
-img26.png\ 1./properties-security-advanced-owner.eps
-img27.png\ 1./confirm.eps
+img1.png\ 1./bacula-logo.eps
+img2.png\ 1./smartall.eps
-1.37.32 (26 July 2005)
+1.37.34 (03 August 2005)
-1.37.32 (26 July 2005)
+1.37.34 (03 August 2005)
@echo "Making html"
@cp -fp ${IMAGES}/*.eps .
@rm -f next.eps next.png prev.eps prev.png up.eps up.png
- @(if [ -e imagename_translations ] ; then \
+ @(if [ -f imagename_translations ] ; then \
./translate_images.pl --from_meaningful_names bacula.html; \
fi)
latex2html -white -no_subdir -split 0 -toc_stars -white -notransparent \
In other words, if there is a possibility of Bacula encountering an
ANSI/IBM label, you must set this to yes.
\end{description}
-
The Autochanger resource supports single or multiple drive
autochangers by grouping one or more Device resources
into one unit called an autochanger in Bacula (often referred to
-as a ``tape library´´ by autochanger manufacturers).
+as a "tape library" by autochanger manufacturers).
\begin{description}
\item [Name = \lt{}Autochanger-Name\gt{}]
Bacula also supports autochangers with barcode
readers. This support includes two Console commands: {\bf label barcodes}
-and {\bf update slots}. For more details on these commands, see the ``Barcode
-Support'' section below.
+and {\bf update slots}. For more details on these commands, see the "Barcode
+Support" section below.
Current Bacula autochanger support does not include cleaning, stackers, or
silos. However, under certain conditions, you may be able to make Bacula
For each tape in the changer containing a barcode, Bacula will mount the tape
and then label it with the same name as the barcode. An appropriate Media
record will also be created in the catalog. Any barcode that begins with the
-same characters as specified on the ``CleaningPrefix=xxx'' command, will be
+same characters as specified on the "CleaningPrefix=xxx" command, will be
treated as a cleaning tape, and will not be labeled. For example with:
Please note that Volumes must be pre-labeled to be automatically used in
mtx-changer Script}
Before attempting to use the autochanger with Bacula, it is preferable to
-``hand-test'' that the changer works. To do so, we suggest you do the
+"hand-test" that the changer works. To do so, we suggest you do the
following commands (assuming that the {\bf mtx-changer} script is installed in
{\bf /etc/bacula/mtx-changer}):
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ loaded \ 0 \ /dev/nst0 \ 0]
\index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ loaded \ 0 \ /dev/nst0 \
0 }
-It should print ``3''
+It should print "3"
\item [/etc/bacula/mtx-changer \ /dev/sg0 \ unload]
\index[sd]{/etc/bacula/mtx-changer \ /dev/sg0 \ unload }
\lt{}bacula-source\gt{}/examples/devices} that implement the above features,
so they may be a help to you in getting your script to work.
-If Bacula complains ``Rewind error on /dev/nst0. ERR=Input/output error.'' you
+If Bacula complains "Rewind error on /dev/nst0. ERR=Input/output error." you
most likely need more sleep time in your {\bf mtx-changer} before returning to
Bacula after a load command has been completed.
Once all your Volumes are labeled, Bacula will automatically load them as they
are needed.
-To ``see'' how you have labeled your Volumes, simply enter the {\bf list
+To "see" how you have labeled your Volumes, simply enter the {\bf list
volumes} command from the Console program, which should print something like
the following:
Bacula calls the autochanger script that you specify on the {\bf Changer
Device} statement. Normally this script will be the {\bf mtx-changer} script
that we can provide, but it can in fact be any program. The only requirements
-are that the ``commands'' that Bacula uses are {\bf loaded}, {\bf load}, {\bf
+are that the "commands" that Bacula uses are {\bf loaded}, {\bf load}, {\bf
unload}, {\bf list}, and {\bf slots}. In addition,
each of those commands must return the information in the precise format as
specified below:
of Bacula. In addition, the file {\bf patches-version-number} in the
{\bf patches} directory contains a summary of each of the patches.
-A ``raw'' list of the current task list and known issues can be found in {\bf
+A "raw" list of the current task list and known issues can be found in {\bf
kernstodo} in the main Bacula source directory.
You may begin using Bacula with SQLite then later find that you want to switch
to MySQL for any of a number of reasons: SQLite tends to use more disk than
MySQL, SQLite apparently does not handle database sizes greater than 2GBytes,
-... Several users have done so by first producing an ASCII ``dump'' of the
+... Several users have done so by first producing an ASCII "dump" of the
SQLite database, then creating the MySQL tables with the {\bf
create\_mysql\_tables} script that comes with Bacula, and finally feeding the
SQLite dump into MySQL using the {\bf -f} command line option to continue past
\end{verbatim}
\normalsize
-Defines the Director resource with the name ``MyDir'' and a working directory
+Defines the Director resource with the name "MyDir" and a working directory
\$HOME/bacula/bin/working. In general, if you want spaces in a name to the
right of the first equal sign (=), you must enclose that name within double
quotes. Otherwise quotes are not generally necessary because once defined,
be accepted. Names may contain up to 127 characters. Currently, a name may
contain any ASCII character. Within a quoted string, any character following a
backslash (\textbackslash{}) is taken as itself (handy for inserting
-blackslashes and double quotes (``).
+blackslashes and double quotes (").
Please note, however, that Bacula resource names as well as certain other
names (e.g. Volume names) will in the future be severely limited to permit
64 bit integer value, but it is specified in two parts: a number part and a
modifier part. The number can be an integer or a floating point number. If it
is entered in floating point notation, it will be rounded to the nearest
-integer. The modifer is mandatory and follows the number part, either with
+integer. The modifier is mandatory and follows the number part, either with
or without intervening spaces. The following modifiers are permitted:
\begin{description}
each tape in the changer containing a barcode, Bacula will mount the tape and
then label it with the same name as the barcode. An appropriate Media record
will also be created in the catalog. Any barcode that begins with the same
-characters as specified on the ``CleaningPrefix=xxx'' directive in the
+characters as specified on the "CleaningPrefix=xxx" directive in the
Director's Pool resource, will be
treated as a cleaning tape, and will not be labeled. However,
an entry for the cleaning tape will be created in
job for that client. Doing a {\bf status} will not cause a database record to
be created. The client database record will be created whether or not the job
fails, but it must at least start. When the Client is actually contacted,
-additional info from the client will be added to the client record (a ``uname
--a'' output).
+additional info from the client will be added to the client record (a "uname
+-a" output).
If you want to see what Client resources you have available in your conf
file, you use the Console command {\bf show clients}.
\item [llist]
\index[console]{llist }
- The llist or ``long list'' command takes all the same arguments that the list
+ The llist or "long list" command takes all the same arguments that the list
command described above does. The difference is that the llist command list
the full contents of each database record selected. It does so by listing the
various fields of the record vertically, with one field per line. It is
\item[python]
\index[console]{python}
- The python command takes a slingle argument {\bf restart}:
+ The python command takes a single argument {\bf restart}:
python restart
immediately for all new jobs. However, if you change schedules,
be aware that the scheduler pre-schedules jobs up to two hours in
advance, so any changes that are to take place during the next two
- hours may be delayed. Jobs that have already been sheduled to run
- (i.e. depassed their requested start time) will continue with the
+ hours may be delayed. Jobs that have already been scheduled to run
+ (i.e. surpassed their requested start time) will continue with the
old values. New jobs will use the new values. Each time you issue
a reload command while jobs are running, the prior config values
will queued until all jobs that were running before issuing
the reload terminate, at which time the old config values will
- be released from memory. The Directory premits keeping up to
+ be released from memory. The Directory permits keeping up to
10 prior set of configurations before it will refuse a reload
command. Once at least one old set of config values has been
released it will again accept new reload commands.
Looking at the above listing from bottom to top, obviously JobId 5343 (Rufus)
is running. JobId 5348 (Minou) is waiting for JobId 5343 to finish because it
-is using the Storage resource, hence the ``waiting on max Storage jobs''.
+is using the Storage resource, hence the "waiting on max Storage jobs".
JobId 5349 has a lower priority than all the other jobs so it is waiting for
higher priority jobs to finish, and finally, JobId 2508 (MatouVerify) is
-waiting because only one job can run at a time, hence it is simply ``waiting
-execution\".</dd>
+waiting because only one job can run at a time, hence it is simply "waiting
+execution"
\item [unmount]
\index[console]{unmount }
it the same way variable expansion is done on the {\bf LabelFormat} string.
Thus, for the most part, you can test your LabelFormat strings. The
difference between the {\bf var} command and the actual LabelFormat process
- is that during the var command, no job is running so ''dummy`` values are
+ is that during the var command, no job is running so "dummy" values are
used in place of Job specific variables. Generally, however, you will get a
good idea of what is going to happen in the real case.
Before adding a volume, you must know the following information:
\begin{enumerate}
-\item The name of the Pool (normally ''Default``)
+\item The name of the Pool (normally "Default")
\item The Media Type as specified in the Storage Resource in the Director's
- configuration file (e.g. ''DLT8000``)
+ configuration file (e.g. "DLT8000")
\item The number and names of the Volumes you wish to create.
\end{enumerate}
Notice that the console program automatically appended a number to the base
Volume name that you specify (Save in this case). If you don't want it to
-append a number, you can simply answer 0 (zero) to the question ''Enter number
-of Media volumes to create. Max=1000:``, and in this case, it will create a
+append a number, you can simply answer 0 (zero) to the question "Enter number
+of Media volumes to create. Max=1000:", and in this case, it will create a
single Volume with the exact name you specify.
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
+ "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.
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.
+"notify" the Director of their current IP address.
\end{itemize}
The Console resource is optional and need not be specified. However, if it is
\company\ makes no warranty, either express or implied, including but not
limited to any implied warranties of merchantability and fitness for a
particular purpose, regarding these materials and makes such materials
-available solely on an ``as-is'' basis.
+available solely on an "as-is" basis.
In no event shall \company\ be liable to anyone for special, collateral,
incidental, or consequential damages in connection with or arising out of
is all files that have changed since the last successful backup of the
specified FileSet. If the Director cannot find a previous Full backup then
the job will be upgraded into a Full backup. When the Director looks for a
-``suitable'' backup record in the catalog database, it looks for a previous
+"suitable" backup record in the catalog database, it looks for a previous
Job with:
\begin{itemize}
The File daemon (Client) decides which files to backup for an Incremental
backup by comparing start time of the prior Job (Full, Differential, or
-Incremental) against the time each file was last ``modified'' (st\_mtime) and
-the time its attributes were last ``changed''(st\_ctime). If the file was
+Incremental) against the time each file was last "modified" (st\_mtime) and
+the time its attributes were last "changed"(st\_ctime). If the file was
modified or its attributes changed on or after this start time, it will then
be backed up.
Please note that some virus scanning software may change st\_ctime while
-doing the scan. For exaple, if the the virus scanning program attempts to
+doing the scan. For example, if the the virus scanning program attempts to
reset the access time (st\_atime), which Bacula does not use, it will cause
st\_ctime to change and hence Bacula will backup the file during an
Incremental or Differential backup. In the case of Sophos virus scanning, you
In addition, if you move a directory rather than copy it, the files in it do not
have their modification time (st\_mtime) or their attribute change time
(st\_ctime)
-changed. As a conseqence, those files will probably not be backed up by an
+changed. As a consequence, those files will probably not be backed up by an
Incremental
or Differential backup which depend solely on these time stamps. If you move a
directory,
is all files that have changed since the last successful Full backup of the
specified FileSet. If the Director cannot find a previous Full backup or a
suitable Full backup, then the Differential job will be upgraded into a Full
-backup. When the Director looks for a ``suitable'' Full backup record in the
+backup. When the Director looks for a "suitable" Full backup record in the
catalog database, it looks for a previous Job with:
\begin{itemize}
The File daemon (Client) decides which files to backup for a differential
backup by comparing the start time of the prior Full backup Job against the
-time each file was last ``modified'' (st\_mtime) and the time its attributes
-were last ``changed'' (st\_ctime). If the file was modified or its attributes
+time each file was last "modified" (st\_mtime) and the time its attributes
+were last "changed" (st\_ctime). If the file was modified or its attributes
were changed on or after this start time, it will then be backed up. The
start time used is displayed after the {\bf Since} on the Job report. In rare
cases, using the start time of the prior backup may cause some files to be
not
have their modification time (st\_mtime) or their attribute change time
(st\_ctime)
-changed. As a conseqence, those files will probably not be backed up by an
+changed. As a consequence, those files will probably not be backed up by an
Incremental
or Differential backup which depend solely on these time stamps. If you move a
directory,
{\bf Special Windows Considerations}
The command can be anything that cmd.exe or command.com will recognize as an
- executable file. Specifiying the executable's extension is optional, unless
+ executable file. Specifying the executable's extension is optional, unless
there is an ambiguity. (i.e. ls.bat, ls.exe)
The System \%Path\% will be searched for the command. (under the envrionment
System environment variables can be called out using the \%var\% syntax and
used as either part of the command name or arguments.
- When specifiying a full path to an executable if the path or executable name
+ When specifying a full path to an executable if the path or executable name
contains whitespace or special characters they will need to be quoted.
Arguments containing whitespace or special characters will also have to be
quoted.
The special characters \&()[]\{\}\^{}=;!'+,`\~{} will need to be quoted if
they are part of a filename or argument.
- If someone is logged in, a blank ``command'' window running the commands
+ If someone is logged in, a blank "command" window running the commands
will
be present during the execution of the command.
\item The batch file should explicitly 'exit 0' on successful completion.
\item The path to the batch file should be specified in Unix form:
- ClientRunBeforeJob = ``c:/bacula/bin/systemstate.bat''
+ ClientRunBeforeJob = "c:/bacula/bin/systemstate.bat"
rather than DOS/Windows form:
ClientRunBeforeJob =
-``c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}systemstate.bat''
+"c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}systemstate.bat"
INCORRECT
\end{enumerate}
\end{verbatim}
\normalsize
-The following line in the Job resoure in the bacula-dir.conf file:
+The following line in the Job resource in the bacula-dir.conf file:
\footnotesize
\begin{verbatim}
Client Run Before Job = "su - mercuryd -c \"/u01/mercuryd/backupdb.sh '%t'
second | third | forth | fifth
<wday-keyword> = sun | mon | tue | wed | thu | fri | sat |
sunday | monday | tuesday | wednesday |
- thursday | friday
+ thursday | friday | saturday
<week-of-year-keyword> = w00 | w01 | ... w52 | w53
<month-keyword> = jan | feb | mar | apr | may | jun | jul |
aug | sep | oct | nov | dec | january |
is
an arbitrary string of characters up to 127 maximum that you define. It can
be anything you want. However, it is best to make it descriptive of the
-storage media (e.g. File, DAT, ''HP DLT8000``, 8mm, ...). In addition, it is
+storage media (e.g. File, DAT, "HP DLT8000", 8mm, ...). In addition, it is
essential that you make the {\bf Media Type} specification unique for each
storage media type. If you have two DDS-4 drives that have incompatible
formats, or if you have a DDS-4 drive and a DDS-4 autochanger, you almost
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 ('').
+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
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
+({\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
+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
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
+ "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.
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
+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
-directives are permited within the Director's configuration resource:
+directives are permitted within the Director's configuration resource:
\begin{description}
\item The
\ilink{ Recycle Oldest Volume = yes}{RecycleOldest} record in the
Pool resource tells Bacula to Prune the oldest volume in the Pool, and if all
- files were pruned to recyle this volume and use it.
+ files were pruned to recycle this volume and use it.
\item The
\ilink{ Recycle Current Volume = yes}{RecycleCurrent} record in
the Pool resource tells Bacula to Prune the currently mounted volume in the
- Pool, and if all files were pruned to recyle this volume and use it.
+ Pool, and if all files were pruned to recycle this volume and use it.
\item The
\ilink{ Purge Oldest Volume = yes}{PurgeOldest} record in the
Pool resource permits a forced recycling of the oldest Volume when a new one
\addcontentsline{toc}{subsection}{Other Points}
\begin{itemize}
+\item DVD+RW supports only about 1000 overwrites. Every time you
+ mount the filesystem read/write will count as one write. This can
+ add up quickly, so it is best to mount your DVD+RW filesystem read-only.
+ Bacula does not need the DVD to be mounted read-write, since it uses
+ the raw device for writing.
+\item Reformatting DVD+RW 10-20 times can apparently make the medium
+ unusable. Normally you should not have to format or reformat
+ DVD+RW media. If it is necessary, current versions of growisofs will
+ do so automatically.
\item I had several problems writing to DVD-RWs (this does NOT concern DVD+RW),
-because these media have two writing-modes: {\bf Incremental Sequential} and
-{\bf Restricted Overwrite}. Depending on your device and the media you use,
-one of these modes may not work correctly (e.g. {\bf Incremental Sequential} does
-not work with my NEC DVD-writer and Verbatim DVD-RW).
+ because these media have two writing-modes: {\bf Incremental Sequential} and
+ {\bf Restricted Overwrite}. Depending on your device and the media you use,
+ one of these modes may not work correctly (e.g. {\bf Incremental Sequential} does
+ not work with my NEC DVD-writer and Verbatim DVD-RW).
-To retrieve the current mode of a DVD-RW, run:
+ To retrieve the current mode of a DVD-RW, run:
\begin{verbatim}
dvd+rw-mediainfo /dev/xxx
\end{verbatim}
-where you replace xxx with your DVD device name.
+ where you replace xxx with your DVD device name.
-{\bf Mounted Media} line should give you the information.
+ {\bf Mounted Media} line should give you the information.
-To set the device to {\bf Restricted Overwrite} mode, run:
+ To set the device to {\bf Restricted Overwrite} mode, run:
\begin{verbatim}
dvd+rw-format /dev/xxx
\end{verbatim}
-If you want to set it back to the default {\bf Incremental Sequential} mode, run:
+ If you want to set it back to the default {\bf Incremental Sequential} mode, run:
\begin{verbatim}
dvd+rw-format -blank /dev/xxx
\end{verbatim}
\item Bacula only accepts to write to blank DVDs. To quick blank a DVD+/-RW, run
-this command:
+ this command:
\begin{verbatim}
dd if=/dev/zero bs=1024 count=512 | growisofs -Z /dev/xxx=/dev/fd/0
\end{verbatim}
-Then, try to mount the device, if it cannot be mounted, it will be considered
-as blank by Bacula, if it can be mounted, try a full blank (see below).
+ Then, try to mount the device, if it cannot be mounted, it will be considered
+ as blank by Bacula, if it can be mounted, try a full blank (see below).
\item If you wish to blank completely a DVD+/-RW, use the following:
\begin{verbatim}
\item DVD+RW and DVD-RW support only about 1000 overwrites (i.e. don't use the
same medium for years if you don't want to have problems...).
-\item Reformating DVD+RW 10-20 time can apparently make the medium
- unusable. Normally you should not have to format or reformat
- DVD+RW media. If it is necessary, current versions of growisofs will
- do so automatically.
-
\item For more informations about DVD writing, please look at the
\elink{dvd+rw-tools homepage}{http://fy.chalmers.se/~appro/linux/DVD+RW/}.
\end{itemize}
\item [How Can I Be Sure that Bacula Really Saves and Restores All Files? ]
\index[general]{How Can I Be Sure that Bacula Really Saves and Restores
All Files? } It is really quite simple, but took me a while to figure
- out how to ``prove'' it. First make a Bacula Rescue disk, see the
+ out how to "prove" it. First make a Bacula Rescue disk, see the
\ilink{Disaster Recovery Using Bacula}{_ChapterStart38} of this manual.
Second, you run a full backup of all your files on all partitions.
Third, you run an Verify InitCatalog Job on the same FileSet, which
Bacula also has compression code, which is normally used only when backing
up
- to file Volumes. There are two conditions for this ''software`` to become
+ to file Volumes. There are two conditions for this "software" to become
enabled.
\begin{enumerate}
\label{ConnectionRefused}
\subsection*{I get a Connection refused when connecting to my Client}
-\item [In connecting to my Client, I get ''ERR:Connection Refused. Packet
- Size too big from File daemon:192.168.1.4:9102`` Why?]
- \index[general]{In connecting to my Client, I get ``ERR:Connection
+\item [In connecting to my Client, I get "ERR:Connection Refused. Packet
+ Size too big from File daemon:192.168.1.4:9102" Why?]
+ \index[general]{In connecting to my Client, I get "ERR:Connection
Refused.
- Packet Size too big from File daemon:192.168.1.4:9102'' Why? }
+ Packet Size too big from File daemon:192.168.1.4:9102" Why? }
This is typically a communications error resulting from one of the
following:
Bacula}, but may be shared by other Bacula daemons. This record is required.
On Win32 systems, in some circumstances you may need to specify a drive
- leter in the specified working directory path. Also, please be sure
+ letter in the specified working directory path. Also, please be sure
that this directory is writable by the SYSTEM user otherwise restores
- may fail (the bootstrap file that is tranferred to the File daemon from
+ may fail (the bootstrap file that is transferred to the File daemon from
the Director is temporarily put in this directory before being passed
to the Storage daemon).
However, one additional point is that
in the case that no match was found, Bacula will use the options found in
the last Options resource. As a consequence, if you want a particular set
-of ``default'' options, you should put them in an Options resource after
+of "default" options, you should put them in an Options resource after
any other Options.
This is perhaps a bit overwhelming, so there are a number of examples included
\item [hardlinks=yes|no]
\index[dir]{hardlinks}
- When enabled (default), this directive will cause hardl inks to be
+ When enabled (default), this directive will cause hard inks to be
backed up. However, the File daemon keeps track of hard linked files and
will backup the data only once. The process of keeping track of the
hard links can be quite expensive if you have lots of them (tens of
included. If {\bf Exclude=yes} is specified, the regex will select
which files are to be excluded. Multiple regex directives may be
specified within an Options resource, and they will be applied in turn
- until the first one that matches. Note, if you exculde a
+ until the first one that matches. Note, if you exclude a
directory, no files or directories below it will be matched.
\item [regexfile=\lt{}string\gt{}]
The default is {\bf no}. If this option is set to yes, and you have the
POSIX {\bf libacl} installed on your system, Bacula will backup the file
and directory UNIX Access Control Lists (ACL) as defined in IEEE Std
- 1003.1e draft 17 and ``POSIX.1e'' (abandoned). This feature is
+ 1003.1e draft 17 and "POSIX.1e" (abandoned). This feature is
available on UNIX only and depends on the ACL library. Bacula is
automatically compiled with ACL support if the {\bf libacl} library is
installed on your system (shown in config.out). While restoring the
\begin{itemize}
\item Any name preceded by an at-sign (@) is assumed to be the name of a
- file, which contains a list of files each preceded by a ``File =''. The
+ file, which contains a list of files each preceded by a "File =". The
named file is read once when the configuration file is parsed during the
Director startup. Note, that the file is read on the Director's machine
and not on the Client's. In fact, the @filename can appear anywhere
script as in the second example below. Also, you must take care to
escape (precede with a \textbackslash{}) wild-cards, shell character,
and to ensure that any spaces in your command are escaped as well. If
- you use a single quotes (') within a double quote (``), Bacula will
+ you use a single quotes (') within a double quote ("), Bacula will
treat everything between the single quotes as one field so it will not
be necessary to escape the spaces. In general, getting all the quotes
and escapes correct is a real pain as you can see by the next example.
will produce a list of all the local partitions on a RedHat Linux system.
Note, the above line was split, but should normally be written on one line.
Quoting is a real problem because you must quote for Bacula which consists of
- preceding every \textbackslash{} and every '' with a \textbackslash{}, and
+ preceding every \textbackslash{} and every " with a \textbackslash{}, and
you must also quote for the shell command. In the end, it is probably easier
just to execute a small file with:
and after one minute of waiting, Bacula will give up and go on to the next
file. The data read can be anything since Bacula treats it as a stream.
- This feature can be an excellent way to do a ``hot'' backup of a very large
+ This feature can be an excellent way to do a "hot" backup of a very large
database. You can use the {\bf RunBeforeJob} to create the fifo and to start
a program that dynamically reads your database and writes it to the fifo.
Bacula will then write it to the Volume.
\end{verbatim}
\normalsize
-The ``trick'' here was to add a RegexFile expression that matches
+The "trick" here was to add a RegexFile expression that matches
all files. It does not match directory names, so all directories in
/myfile will be backed up (the directory entry) and any *.Z and *.gz
files contained in them. If you know that certain directories do
specified in Unix convention (i.e. forward slash (/)). If you wish to include
a quote in a file name, precede the quote with a backslash
(\textbackslash{}). For example you might use the following
-for a Windows machine to backup the ``My Documents'' directory:
+for a Windows machine to backup the "My Documents" directory:
\footnotesize
\begin{verbatim}
\item To exclude a directory, you must not have a trailing slash on the
directory name.
\item If you have spaces in your filename, you must enclose the entire name
- in double-quote characters (``). Trying to use a backslash before the space
+ in double-quote characters ("). Trying to use a backslash before the space
will not work.
\item If you are using the old Exclude syntax (noted below), you may not
specify a drive letter in the exclude. The new syntax noted above should work
daemon or client, and SD the Storage daemon. The numbers that follow those
names are the standard ports used by Bacula, and the -\gt{} represents the
left side making a connection to the right side (i.e. the right side is the
-``server'' or is listening on the specified port), and the left side is the
-``client'' who initiates the conversation.
+"server" or is listening on the specified port), and the left side is the
+"client" who initiates the conversation.
Note, port 9103 serves both the Director and the File daemon, each having its
own independent connection.
programs and write over any tape that you put in the drive, then you will find
working with Bacula difficult. Bacula is designed to protect your data
following the rules you specify, and this means reusing a tape only
-as the last resort. It is possible to ``force'' Bacula to write
+as the last resort. It is possible to "force" Bacula to write
over any tape in the drive, but it is easier and more efficient to use a
simpler program for that kind of operation.
backup, restore, verify and archive operations. The system administrator uses
the Bacula Director to schedule backups and to recover files. For more
details see the Director Services Daemon Design Document in the Bacula
-Developer's Guild. The Director runs as a daemon or a service (i.e. in the
+Developer's Guide. The Director runs as a daemon or a service (i.e. in the
background).
\item
\label{UADef}
the Bacula Console is available in three versions. The first and simplest is
to run the Console program in a shell window (i.e. TTY interface). Most
system administrators will find this completely adequate. The second version
-is a GNOME GUI interface that for the moment (23 November 2003) is far from
+is a GNOME GUI interface that is far from
complete, but quite functional as it has most the capabilities of the shell
Console. The third version is a wxWidgets GUI with an interactive file
restore. It also has most of the capabilities of the shell console, allows
documentation, the File daemon is referred to as the Client (for example in
Bacula's configuration file). In addition to Unix/Linux File daemons, there
is a Windows File daemon (normally distributed in binary format). The Windows
-File daemon runs on all currently known Windows versions (95, 98, Me, NT,
-2000, XP).
+File daemon runs on current Windows versions (NT,
+2000, XP, 2003, and possibly Me and 98).
\item
\label{SDDef}
{\bf Bacula Storage} services consist of the software programs that perform
locate and restore any desired file. The Catalog services sets Bacula apart
from simple backup programs like tar and bru, because the catalog maintains a
record of all Volumes used, all Jobs run, and all Files saved, permitting
-efficicient restoration and Volume management. Bacula currently supports
+efficient restoration and Volume management. Bacula currently supports
three different databases, MySQL, PostgreSQL, and SQLite, one of which must
-be chosen when building {\bf Bacula}. There also exists an Internal database,
-but it is no longer supported.
+be chosen when building {\bf Bacula}.
The three SQL databases currently supported (MySQL, PostgreSQL or SQLite)
provide quite a number of features, including rapid indexing, arbitrary
Design Document in the developer's documented.
The RPMs for MySQL and PostgreSQL ship as part of the Linux RedHat
-and several other releases, or building the rpms from the source is
+and several other releases. Alternatively, building the rpms from the source is
quite easy, see the
\ilink{ Installing and Configuring MySQL}{_ChapterStart} chapter of
this document for the details. For more information on MySQL, please see:
\item [Monitor]
\index[fd]{Monitor }
- The program that interfaces to the all the daemons allowing the user or
+ The program that interfaces to all the daemons allowing the user or
system administrator to monitor Bacula status.
\item [Resource]
\index[fd]{Resource }
A resource is a part of a configuration file that defines a specific unit of
information that is available to Bacula. It consists of several directives
-(individual configuation statements). For example, the {\bf Job} resource
+(individual configuration statements). For example, the {\bf Job} resource
defines all the properties of a specific Job: name, schedule, Volume pool,
backup type, backup level, ...
\item [Restore]
\index[fd]{Restore }
A restore is a configuration resource that describes the operation of
-recovering a file (lost or damaged) from backup media. It is the inverse of a
+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
files to restore, while normally a Save backs up all the files on the system.
Of course, after a disk crash, Bacula can be called upon to do a full
The File Retention Period determines the time that File records are kept in
the catalog database. This period is important because the volume of the
database File records by far use the most storage space in the database. As a
-consequence, you must ensure that regular ``pruning'' of the database file
+consequence, you must ensure that regular "pruning" of the database file
records is done. (See the Console {\bf retention} command for more details on
this subject).
example, if you have created an emergency boot disk, a Bacula Rescue disk to
save the current partitioning information of your hard disk, and maintain a
complete Bacula backup, it is possible to completely recover your system from
-``bare metal'' that is starting from an empty disk.
+"bare metal" that is starting from an empty disk.
If you have used the {\bf WriteBootstrap} record in your job or some other
means to save a valid bootstrap file, you will be able to use it to extract
{\bf 0.} This License applies to any program or other work which contains a
notice placed by the copyright holder saying it may be distributed under the
-terms of this General Public License. The ``Program'', below, refers to any
-such program or work, and a ``work based on the Program'' means either the
+terms of this General Public License. The "Program", below, refers to any
+such program or work, and a "work based on the Program" means either the
Program or any derivative work under copyright law: that is to say, a work
containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter,
-translation is included without limitation in the term ``modification''.) Each
-licensee is addressed as ``you''.
+translation is included without limitation in the term "modification".) Each
+licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered
by this License; they are outside its scope. The act of running the Program is
new problems or concerns.
Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and ``any later
-version'', you have the option of following the terms and conditions either of
+specifies a version number of this License which applies to it and "any later
+version", you have the option of following the terms and conditions either of
that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License,
you may choose any version ever published by the Free Software Foundation.
{\bf 11.} BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE
-THE PROGRAM ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
+THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO
THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
To do so, attach the following notices to the program. It is safest to attach
them to the start of each source file to most effectively convey the exclusion
-of warranty; and each file should have at least the ``copyright'' line and a
+of warranty; and each file should have at least the "copyright" line and a
pointer to where the full notice is found.
\footnotesize
could even be mouse-clicks or menu items\verb:--:whatever suits your program.
You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a ``copyright disclaimer'' for the program, if
+school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
\footnotesize
Although the exact composition of the dependency packages may change from time
to time, the current makeup is the following:
-\addcontentsline{lot}{table}{Depedency Packages}
+\addcontentsline{lot}{table}{Dependency Packages}
\begin{longtable}{|l|l|l|l|}
\hline
\multicolumn{1}{|c| }{\bf 3rd Party Package } & \multicolumn{1}{c| }{\bf
so that you are sure to start from scratch and not have a mixture of the two
options. This is because ./configure caches much of the information. The {\bf
-make distclean} is also critical if you move the source dirctory from one
+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
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
+\item If after installing Bacula, you decide to "move it", that is to
install it in a different set of directories, proceed as follows:
\footnotesize
If you install Bacula on more than one system, and they are identical, you can
-simply transfer the source tree to that other system and do a ``make
-install''. However, if there are differences in the libraries or OS versions,
+simply transfer the source tree to that other system and do a "make
+install". However, if there are differences in the libraries or OS versions,
or you wish to install on a different OS, you should start from the original
compress tar file. If you do transfer the source tree, and you have previously
done a ./configure command, you MUST do:
prior to doing your new ./configure. This is because the GNU autoconf tools
cache the configuration, and if you re-use a configuration for a Linux machine
on a Solaris, you can be sure your build will fail. To avoid this, as
-mentioned above, either start from the tar file, or do a ``make distclean''.
+mentioned above, either start from the tar file, or do a "make distclean".
In general, you will probably want to supply a more complicated {\bf
configure} statement to ensure that the modules you want are built and that
\index[general]{{-}{-}with-dir-user }
This option allows you to specify the Userid used to run the Director. The
Director must be started as root, but doesn't need to run as root, and after
- doing preliminary initializations, it can ``drop'' to the UserId specified on
+ doing preliminary initializations, it can "drop" to the UserId specified on
this option.
\item [ {-}{-}with-dir-group=\lt{}Group\gt{} ]
\index[general]{{-}{-}with-dir-group }
This option allows you to specify the GroupId used to run the Director. The
Director must be started as root, but doesn't need to run as root, and after
- doing preliminary initializations, it can ``drop'' to the GroupId specified
+ doing preliminary initializations, it can "drop" to the GroupId specified
on this option.
\item [ {-}{-}with-sd-user=\lt{}User\gt{} ]
\index[general]{{-}{-}with-sd-user }
This option allows you to specify the Userid used to run the Storage daemon.
The Storage daemon must be started as root, but doesn't need to run as root,
- and after doing preliminary initializations, it can ``drop'' to the UserId
+ and after doing preliminary initializations, it can "drop" to the UserId
specified on this option. If you use this option, you will need to take care
that the Storage daemon has access to all the devices (tape drives, ...) that
it needs.
\index[general]{{-}{-}with-sd-group }
This option allows you to specify the GroupId used to run the Storage daemon.
The Storage daemon must be started as root, but doesn't need to run as root,
- and after doing preliminary initializations, it can ``drop'' to the GroupId
+ and after doing preliminary initializations, it can "drop" to the GroupId
specified on this option.
\item [ {-}{-}with-fd-user=\lt{}User\gt{} ]
This option allows you to specify the Userid used to run the File daemon. The
File daemon must be started as root, and in most cases, it needs to run as
root, so this option is used only in very special cases, after doing
- preliminary initializations, it can ``drop'' to the UserId specified on this
+ preliminary initializations, it can "drop" to the UserId specified on this
option.
\item [ {-}{-}with-fd-group=\lt{}Group\gt{} ]
\index[general]{{-}{-}with-fd-group }
This option allows you to specify the GroupId used to run the File daemon.
The File daemon must be started as root, and in most cases, it must be run as
- root, however, after doing preliminary initializations, it can ``drop'' to
+ root, however, after doing preliminary initializations, it can "drop" to
the GroupId specified on this option.
\end{description}
If you want to install Bacula in an installation directory rather than run it
out of the build directory (as developers will do most of the time), you
should also include the \verb:--:sbindir and \verb:--:sysconfdir options with appropriate
-paths. Neither are necessary if you do not use ``make install'' as is the case
+paths. Neither are necessary if you do not use "make install" as is the case
for most development work. The install process will create the sbindir and
sysconfdir if they do not exist, but it will not automatically create the
pid-dir, subsys-dir, or working-dir, so you must ensure that they exist before
\index[general]{Kern's Configure Script }
\addcontentsline{toc}{subsection}{Kern's Configure Script}
-The script that I use for building on my ``production'' Linux machines is:
+The script that I use for building on my "production" Linux machines is:
\footnotesize
\begin{verbatim}
\normalsize
If you have previously installed Bacula, the old binaries will be overwritten,
-but the old configuration files will remain unchanged, and the ``new''
+but the old configuration files will remain unchanged, and the "new"
configuration files will be appended with a {\bf .new}. Generally if you have
previously installed and run Bacula you will want to discard or ignore the
configuration files with the appended {\bf .new}.
\index[general]{Testing The Traceback }
\addcontentsline{toc}{subsection}{Testing The Traceback}
-To ``manually'' test the traceback feature, you simply start {\bf Bacula} then
+To "manually" test the traceback feature, you simply start {\bf Bacula} then
obtain the {\bf PID} of the main daemon thread (there are multiple threads).
Unfortunately, the output had to be split to fit on this page:
criteria of freedom. The Lesser General Public License permits more lax
criteria for linking other code with the library.
-We call this license the ``Lesser'' General Public License because it does
+We call this license the "Lesser" General Public License because it does
Less to protect the user's freedom than the ordinary General Public License.
It also provides other free software developers Less of an advantage over
competing non-free programs. These disadvantages are the reason we use the
modified version of the Library.
The precise terms and conditions for copying, distribution and modification
-follow. Pay close attention to the difference between a ``work based on the
-library'' and a ``work that uses the library''. The former contains code
+follow. Pay close attention to the difference between a "work based on the
+library" and a "work that uses the library". The former contains code
derived from the library, whereas the latter must be combined with the library
in order to run.
{\bf 0.} This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or other
authorized party saying it may be distributed under the terms of this Lesser
-General Public License (also called ``this License''). Each licensee is
-addressed as ``you''.
+General Public License (also called "this License"). Each licensee is
+addressed as "you".
-A ``library'' means a collection of software functions and/or data prepared so
+A "library" means a collection of software functions and/or data prepared so
as to be conveniently linked with application programs (which use some of
those functions and data) to form executables.
-The ``Library'', below, refers to any such software library or work which has
-been distributed under these terms. A ``work based on the Library'' means
+The "Library", below, refers to any such software library or work which has
+been distributed under these terms. A "work based on the Library" means
either the Library or any derivative work under copyright law: that is to say,
a work containing the Library or a portion of it, either verbatim or with
modifications and/or translated straightforwardly into another language.
(Hereinafter, translation is included without limitation in the term
-``modification''.)
+"modification".)
-``Source code'' for a work means the preferred form of the work for making
+"Source code" for a work means the preferred form of the work for making
modifications to it. For a library, complete source code means all the source
code for all modules it contains, plus any associated interface definition
files, plus the scripts used to control compilation and installation of the
{\bf 5.} A program that contains no derivative of any portion of the Library,
but is designed to work with the Library by being compiled or linked with it,
-is called a ``work that uses the Library''. Such a work, in isolation, is not
+is called a "work that uses the Library". Such a work, in isolation, is not
a derivative work of the Library, and therefore falls outside the scope of
this License.
-However, linking a ``work that uses the Library'' with the Library creates an
+However, linking a "work that uses the Library" with the Library creates an
executable that is a derivative of the Library (because it contains portions
-of the Library), rather than a ``work that uses the library''. The executable
+of the Library), rather than a "work that uses the library". The executable
is therefore covered by this License. Section 6 states terms for distribution
of such executables.
-When a ``work that uses the Library'' uses material from a header file that is
+When a "work that uses the Library" uses material from a header file that is
part of the Library, the object code for the work may be a derivative work of
the Library even though the source code is not. Whether this is true is
especially significant if the work can be linked without the Library, or if
directly with the Library itself.
{\bf 6.} As an exception to the Sections above, you may also combine or link a
-``work that uses the Library'' with the Library to produce a work containing
+"work that uses the Library" with the Library to produce a work containing
portions of the Library, and distribute that work under terms of your choice,
provided that the terms permit modification of the work for the customer's own
use and reverse engineering for debugging such modifications.
machine-readable source code for the Library including whatever changes were
used in the work (which must be distributed under Sections 1 and 2 above);
and, if the work is an executable linked with the Library, with the complete
-machine-readable ``work that uses the Library'', as object code and/or source
+machine-readable "work that uses the Library", as object code and/or source
code, so that the user can modify the Library and then relink to produce a
modified executable containing the modified Library. (It is understood that
the user who changes the contents of definitions files in the Library will
materials or that you have already sent this user a copy.
\end{itemize}
-For an executable, the required form of the ``work that uses the Library''
+For an executable, the required form of the "work that uses the Library"
must include any data and utility programs needed for reproducing the
executable from it. However, as a special exception, the materials to be
distributed need not include anything that is normally distributed (in either
address new problems or concerns.
Each version is given a distinguishing version number. If the Library
-specifies a version number of this License which applies to it and ``any later
-version'', you have the option of following the terms and conditions either of
+specifies a version number of this License which applies to it and "any later
+version", you have the option of following the terms and conditions either of
that version or of any later version published by the Free Software
Foundation. If the Library does not specify a license version number, you may
choose any version ever published by the Free Software Foundation.
{\bf 15.} BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE
-THE LIBRARY ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
+THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO
THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
-``copyright'' line and a pointer to where the full notice is found.
+"copyright" line and a pointer to where the full notice is found.
\footnotesize
\begin{verbatim}
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a ``copyright disclaimer'' for the library, if
+school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
\footnotesize
\begin{verbatim}
Yoyodyne, Inc., hereby disclaims all copyright interest in
-the library `Frob' (a library for tweaking knobs) written
+the library "Frob" (a library for tweaking knobs) written
by James Random Hacker.
{\it signature of Ty Coon}, 1 April 1990
Ty Coon, President of Vice
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE
-PROGRAM ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
+PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE,
In the absence of this resource, Bacula will send all mail using the
following command:
-{\bf mail -s ``Bacula Message'' \lt{}recipients\gt{}}
+{\bf mail -s "Bacula Message" \lt{}recipients\gt{}}
In many cases, depending on your machine, this command may not work. Using
the {\bf MailCommand}, you can specify exactly how to send the mail. During
appear on a single line in the configuration file rather than split as is
done here for presentation:
-{\bf mailcommand = ``/home/kern/bacula/bin/bsmtp -h mail.example.com -f
-\textbackslash{}''\textbackslash{}(Bacula\textbackslash{})
-\%r\textbackslash{}`` -s \textbackslash{}''Bacula: \%t \%e of \%c
-\%l\textbackslash{}`` \%r'' }
+{\bf mailcommand = "/home/kern/bacula/bin/bsmtp -h mail.example.com -f
+\textbackslash{}"\textbackslash{}(Bacula\textbackslash{})
+\%r\textbackslash{}" -s \textbackslash{}"Bacula: \%t \%e of \%c
+\%l\textbackslash{}" \%r" }
Note, the {\bf bsmtp} program is provided as part of {\bf Bacula}. For
additional details, please see the
Bacula otherwise you are likely to get bizarre failures. If you
install from rpms and you upgrade MySQL, you must also rebuild Bacula.
You can do so by rebuilding from the source rpm. To do so, you may need
-eo modify the bacula.spec file to account for the new MySQL version.
+to modify the bacula.spec file to account for the new MySQL version.
This will not be the case if you are invoking a script as in the second
example below. Also, you must take care to escape wild-cards and ensure that
any spaces in your command are escaped as well. If you use a single quotes
-(') within a double quote (``), Bacula will treat everything between the
+(') within a double quote ("), Bacula will treat everything between the
single quotes as one field so it will not be necessary to escape the spaces.
In general, getting all the quotes and escapes correct is a real pain as you
can see by the next example. As a consequence, it is often easier to put
will produce a list of all the local partitions on a RedHat Linux system.
Note, the above line was split, but should normally be written on one line.
Quoting is a real problem because you must quote for Bacula which consists of
-preceding every \textbackslash{} and every '' with a \textbackslash{}, and
+preceding every \textbackslash{} and every " with a \textbackslash{}, and
you must also quote for the shell command. In the end, it is probably easier
just to execute a small file with:
after one minute of waiting, it will go on to the next file. The data read
can be anything since Bacula treats it as a stream.
-This feature can be an excellent way to do a ``hot'' backup of a very large
+This feature can be an excellent way to do a "hot" backup of a very large
database. You can use the {\bf RunBeforeJob} to create the fifo and to start
a program that dynamically reads your database and writes it to the fifo.
Bacula will then write it to the Volume.
\item To exclude a directory, you must not have a trailing slash on the
directory name.
\item If you have spaces in your filename, you must enclose the entire name
-in double-quote characters (``). Trying to use a backslash before the space
+in double-quote characters ("). Trying to use a backslash before the space
will not work.
\item You must not precede the excluded file or directory with a drive letter
(such as {\bf c:}) otherwise it will not work.
specified in Unix convention (i.e. forward slash (/)). If you wish to include
a quote in a file name, precede the quote with a backslash
(\textbackslash{}\textbackslash{}). For example you might use the following
-for a Windows machine to backup the ''My Documents`` directory:
+for a Windows machine to backup the "My Documents" directory:
\footnotesize
\begin{verbatim}
\addcontentsline{toc}{subsubsection}{bls Listing Blocks}
Normally, except for debugging purposes, you will not need to list Bacula
-blocks (the ``primitive'' unit of Bacula data on the Volume). However, you can
+blocks (the "primitive" unit of Bacula data on the Volume). However, you can
do so with:
\footnotesize
database name ({\bf -b} option), the user name ({\bf -u} option), and/or the
password ({\bf -p}) options.
-As an example, let's suppose that you did a backup to Volumes ``Vol001''
-and ``Vol002'', then sometime later all records of one or both those
+As an example, let's suppose that you did a backup to Volumes "Vol001"
+and "Vol002", then sometime later all records of one or both those
Volumes
were pruned or purged from the
database. By using {\bf bscan} you can recreate the catalog entries for
database, and optionally fix them. The {\bf dbcheck} program can be found in
the {\bf \lt{}bacula-source\gt{}/src/tools} directory of the source
distribution. Though it is built with the make process, it is not normally
-``installed''.
+"installed".
It is called:
However, you may find it useful to see what bacula would do with a given {\bf
Include} resource. The {\bf testfind} program can be found in the {\bf
\lt{}bacula-source\gt{}/src/tools} directory of the source distribution.
-Though it is built with the make process, it is not normally ``installed''.
+Though it is built with the make process, it is not normally "installed".
It is called:
internal file type, or the link (if any). Debug levels of 10 or greater cause
the filename and the path to be separated using the same algorithm that is
used when putting filenames into the Catalog database.
-
\section*{Python Scripting}
\label{_ChapterStart60}
\index[general]{Python Scripting}
-\index[general]{Scripting!Pyton}
+\index[general]{Scripting!Python}
\addcontentsline{toc}{section}{Python Scripting}
You may be asking what Python is and why a scripting language is
labels to the Volumes, may seem tedious at first, but in fact, they are quite
simple to do, and they allow you to use multiple Volumes (rather than being
limited to the size of a single tape). Pools also give you significant
-flexibility in your backup process. For example, you can have a ``Daily'' Pool
-of Volumes for Incremental backups and a ``Weekly'' Pool of Volumes for Full
+flexibility in your backup process. For example, you can have a "Daily" Pool
+of Volumes for Incremental backups and a "Weekly" Pool of Volumes for Full
backups. By specifying the appropriate Pool in the daily and weekly backup
Jobs, you thereby insure that no daily Job ever writes to a Volume in the
Weekly Pool and vice versa, and Bacula will tell you what tape is needed and
will only recycle purged Volumes if there is no other appendable Volume
available, otherwise, it will always write to an appendable Volume before
recycling even if there are Volume marked as Purged. This preserves your data
-as long as possible. So, if you wish to ``force'' Bacula to use a purged
+as long as possible. So, if you wish to "force" Bacula to use a purged
Volume, you must first ensure that no other Volume in the Pool is marked {\bf
Append}. If necessary, you can manually set a volume to {\bf Full}. The reason
for this is that Bacula wants to preserve the data on your old tapes (even
cannot use the Console restore command to restore the files.
When a Job record is pruned, the Volume (Media record) for that Job can still
-remain in the database, and if you do a ``list volumes'', you will see the
+remain in the database, and if you do a "list volumes", you will see the
volume information, but the Job records (and its File records) will no longer
be available.
retention periods in function of how many files you are backing up and the
time periods you want to keep those records online, and the size of the
database. You can always re-insert the records (with 98\% of the original data)
-by using ``bscan'' to scan in a whole Volume or any part of the volume that
+by using "bscan" to scan in a whole Volume or any part of the volume that
you want.
By setting {\bf AutoPrune} to {\bf yes} you will permit {\bf Bacula} to
all previous data will be lost.
\end{description}
-Note, it is also possible to ``force'' pruning of all Volumes in the Pool
+Note, it is also possible to "force" pruning of all Volumes in the Pool
associated with a Job by adding {\bf Prune Files = yes} to the Job resource.
\label{Recycling}
\normalsize
Depending on the number of {\bf JobFiles} for each JobId, the {\bf Building
-directory tree ...``} can take a bit of time. If you notice ath all the
+directory tree ..."} can take a bit of time. If you notice ath all the
JobFiles are zero, your Files have probably been pruned and you will not be
able to select any individual files -- it will be restore everything or
nothing.
contents to be restored, you can still select items within the directory to
be restored by individually marking those files, but in that case, you
should
- individually use the ''markdir`` command to select all higher level
+ individually use the "markdir" command to select all higher level
directory entries (one at a time) to be restored if you want the directory
entries properly restored.
\end{itemize}
what it is now after each individual test:
\begin{enumerate}
-\item Set ''Block Positioning = no`` in your Device resource and try the
+\item Set "Block Positioning = no" in your Device resource and try the
restore. This is a new directive and untested.
-\item Set ''Minimum Block Size = 512`` and ''Maximum Block Size = 512`` and
+\item Set "Minimum Block Size = 512" and "Maximum Block Size = 512" and
try the restore. Again send me the full job report output. If you are able
to
determine the block size your drive was previously using, you should try
the file. These defines basically just control the dependency information that
gets coded into the finished rpm package.
The platform define may be edited in the spec file directly (by default all
-defines are set to 0 or ``not set''). For example, to build the RedHat 7.x
+defines are set to 0 or "not set"). For example, to build the RedHat 7.x
package find the line in the spec file which reads
\footnotesize
\normalsize
where director.example.org is the host which will be contacting the client
-(ie. the box on which the Bacula Director daemon runs). The use of ``ALL :
-deny'' ensures that the twist option (if present) is not invoked. To properly
+(ie. the box on which the Bacula Director daemon runs). The use of "ALL :
+deny" ensures that the twist option (if present) is not invoked. To properly
test your configuration, start the daemon(s), then attempt to connect from an
IP address which should be able to connect. You should see something like
this:
reducing downtime, and/or interference with users.
\end{itemize}
-Data spooling is exactly that ``spooling''. It is not a way to first write a
-``backup'' to a disk file and then to a tape. When the backup has only been spooled to disk,
+Data spooling is exactly that "spooling". It is not a way to first write a
+"backup" to a disk file and then to a tape. When the backup has only been spooled to disk,
it is not complete yet and cannot be restored until it is written to tape. In a
future version, Bacula will support writing a backup to disk then later {\bf
Migrating} or {\bf Copying} it to a tape.
\index[general]{Testing SQLite }
\addcontentsline{toc}{subsection}{Testing SQLite}
-We have much less ``production'' experience
+We have much less "production" experience
using SQLite than using MySQL. SQLite has
performed flawlessly for us in all our testing. However,
several users have reported corrupted databases while using
\item Access control lists for Consoles that permit restricting user access
to only their data.
\item Data spooling to disk during backup with subsequent write to tape from
- the spooled disk files. This prevents tape ``shoe shine'' during
+ the spooled disk files. This prevents tape "shoe shine" during
Incremental/Differential backups.
\item Support for save/restore of files larger than 2GB.
\item Support for 64 bit machines, e.g. amd64.
\index[sd]{Archive Device }
The specified {\bf name-string} gives the system file name of the storage
device managed by this storage daemon. This will usually be the device file
- name of a removable storage device (tape drive), for example ``{\bf
- /dev/nst0}'' or ``{\bf /dev/rmt/0mbn}''. For a DVD-writer, it will be for
+ name of a removable storage device (tape drive), for example "{\bf
+ /dev/nst0}" or "{\bf /dev/rmt/0mbn}". For a DVD-writer, it will be for
example {\bf /dev/hdc}. It may also be a directory name if you are archiving
to disk storage. In this case, you must supply the full absolute path to the
directory. When specifying a tape device, it is preferable that the
- ``non-rewind'' variant of the device file name be given. In addition, on
+ "non-rewind" variant of the device file name be given. In addition, on
systems such as Sun, which have multiple tape access methods, you must be
sure to specify to use Berkeley I/O conventions with the device. The {\bf b}
in the Solaris (Sun) archive specification {\bf /dev/rmt/0mbn} is what is
\item [Media Type = {\it name-string}]
\index[sd]{Media Type }
The specified {\bf name-string} names the type of media supported by this
- device, for example, ``DLT7000''. Media type names are arbitrary in that you
+ device, for example, "DLT7000". Media type names are arbitrary in that you
set it to anything you want, but must be known to the volume database to keep
track of which storage daemons can read which volumes. The same {\bf
name-string} must appear in the appropriate Storage resource definition in
have a single Storage daemon, but it is with multiple Storage daemons,
especially if they have incompatible media.
- For example, if you specify a Media Type of ``DDS-4'' then during the
+ For example, if you specify a Media Type of "DDS-4" then during the
restore, Bacula will be able to choose any Storage Daemon that handles
- ``DDS-4''. If you have an autochanger, you might want to name the Media Type
+ "DDS-4". If you have an autochanger, you might want to name the Media Type
in a way that is unique to the autochanger, unless you wish to possibly use
the Volumes in other drives. You should also ensure to have unique Media
Type names if the Media is not compatible between drives. This specification
\index[general]{Practical Details }
\addcontentsline{toc}{subsubsection}{Practical Details}
-The simplest way to ``force'' Bacula to use a different tape each day is to
+The simplest way to "force" Bacula to use a different tape each day is to
define a different Pool for each day of the the week a backup is done. In
addition, you will need to specify appropriate Job and File retention periods
so that Bacula will relabel and overwrite the tape each week rather than
#
OPENSSL=openssl
umask 77
- PEM1=`/bin/mktemp openssl.XXXXXX`
- PEM2=`/bin/mktemp openssl.XXXXXX`
+ PEM1="/bin/mktemp openssl.XXXXXX"
+ PEM2="/bin/mktemp openssl.XXXXXX"
${OPENSSL} req -newkey rsa:1024 -keyout $PEM1 -nodes \
-x509 -days 365 -out $PEM2
cat $PEM1 > stunnel.pem
can simply change the name to {\bf /lib/tls-broken}) then you must reboot
your machine (one of the few times Linux must be rebooted). If you are not
able to remove/rename /lib/tls, an alternative is to set the environment
-variable ``LD\_ASSUME\_KERNEL=2.4.19'' prior to executing Bacula. For this
+variable "LD\_ASSUME\_KERNEL=2.4.19" prior to executing Bacula. For this
option, you do not need to reboot, and all programs other than Bacula will
continue to use /lib/tls.
\index[general]{Autochangers!Supported}
\addcontentsline{toc}{subsection}{Supported Autochanger Models}
-I hesitate to call these ``supported'' autochangers because the only
+I hesitate to call these "supported" autochangers because the only
autochangers that I have in my possession and am able to test are the HP
SureStore DAT40X6 and the Overland PowerLoader LTO-2. All the other
autochangers have been reported to work by Bacula users. Note, in the
\begin{tabular}{|c|c|c|c}
Media Type & Drive Type & Media Capacity & Transfer Rate \\ \hline
-DDS-1 & DAT & 2 GB & ?? GB/hr \\ \hline
-DDS-2 & DAT & 4 GB & ?? GB/hr \\ \hline
-DDS-3 & DAT & 12 GB & 5.4 GB/hr \\ \hline
-Travan 40 & Travan & 20 GB & ?? GB/hr \\ \hline
-DDS-4 & DAT & 20 GB & 11 GB/hr \\ \hline
-VXA-1 & Exabyte & 33 GB & 11 GB/hr \\ \hline
-DAT-72 & DAT & 36 GB & 13 GB/hr \\ \hline
-DLT IV & DLT8000 & 40 GB & 22 GB/hr \\ \hline
-VXA-2 & Exabyte & 80 GB & 22 GB/hr \\ \hline
-Half-high Ultrum 1 & LTO 1 & 100 GB & 27 GB/hr \\ \hline
-Ultrium 1 & LTO 1 & 100 GB & 54 GB/hr \\ \hline
-Super DLT 1 & SDLT 220 & 110 GB & 40 GB/hr \\ \hline
-VXA-3 & Exabyte & 160 GB & 43 GB/hr \\ \hline
-Super DLT I & SDLT 320 & 160 GB & 58 GB/hr \\ \hline
-Ultrium 2 & LTO 2 & 200 GB & 108 GB/hr \\ \hline
-Super DLT II & SDLT 600 & 300 GB & 127 GB/hr \\ \hline
-VXA-4 & Exabyte & 320 GB & 86 GB/hr \\ \hline
-Ultrium 3 & LTO 3 & 400 GB & 216 GB/hr \\ \hline
+DDS-1 & DAT & 2 GB & ?? GB/hr \\ \hline
+DDS-2 & DAT & 4 GB & ?? GB/hr \\ \hline
+DDS-3 & DAT & 12 GB & 5.4 GB/hr \\ \hline
+Travan 40 & Travan & 20 GB & ?? GB/hr \\ \hline
+DDS-4 & DAT & 20 GB & 11 GB/hr \\ \hline
+VXA-1 & Exabyte & 33 GB & 11 GB/hr \\ \hline
+DAT-72 & DAT & 36 GB & 13 GB/hr \\ \hline
+DLT IV & DLT8000 & 40 GB & 22 GB/hr \\ \hline
+VXA-2 & Exabyte & 80 GB & 22 GB/hr \\ \hline
+Half-high Ultrum 1 & LTO 1 & 100 GB & 27 GB/hr \\ \hline
+Ultrium 1 & LTO 1 & 100 GB & 54 GB/hr \\ \hline
+Super DLT 1 & SDLT 220 & 110 GB & 40 GB/hr \\ \hline
+VXA-3 & Exabyte & 160 GB & 43 GB/hr \\ \hline
+Super DLT I & SDLT 320 & 160 GB & 58 GB/hr \\ \hline
+Ultrium 2 & LTO 2 & 200 GB & 108 GB/hr \\ \hline
+Super DLT II & SDLT 600 & 300 GB & 127 GB/hr \\ \hline
+VXA-4 & Exabyte & 320 GB & 86 GB/hr \\ \hline
+Ultrium 3 & LTO 3 & 400 GB & 216 GB/hr \\ \hline
\end{tabular}
-
can simply change the name to {\bf /lib/tls-broken}) then you must reboot
your machine (one of the few times Linux must be rebooted). If you are not
able to remove/rename /lib/tls, an alternative is to set the environment
-variable ``LD\_ASSUME\_KERNEL=2.4.19'' prior to executing Bacula. For this
+variable "LD\_ASSUME\_KERNEL=2.4.19" prior to executing Bacula. For this
option, you do not need to reboot, and all programs other than Bacula will
continue to use /lib/tls.
retrieve the current file position from the {\bf mt\_fileno} field. Some SCSI
tape drivers will use a fast means of seeking to the end of the medium and in
doing so, they will not know the current file position and hence return a {\bf
--1}. As a consequence, if you get {\bf ``This is NOT correct!''} in the
+-1}. As a consequence, if you get {\bf "This is NOT correct!"} in the
positioning tests, this may be the cause. You must correct this condition in
order for Bacula to work.
\end{verbatim}
\normalsize
-which runs my ``watchdog'' script. As an example, I have added the Job codes
+which runs my "watchdog" script. As an example, I have added the Job codes
\%c and \%d which will cause the Client name and the Director's name to be
passed to the script. For example, if the Client's name is {\bf Watchdog} and
the Director's name is {\bf main-dir} then referencing \$1 in the script would
\index[general]{Autochanger!Automatic Labeling Using Your }
\addcontentsline{toc}{subsection}{Automatic Labeling Using Your Autochanger}
-If you have an autochanger but it does not support barcodes, using a ``trick''
+If you have an autochanger but it does not support barcodes, using a "trick"
you can make Bacula automatically label all the volumes in your autochanger's
magazine.
This tip also comes from Marc Brueckner. (Note, this tip is probably outdated
by the addition of {\bf ClientRunBeforJob} and {\bf ClientRunAfterJob} Job
-records, but the technique still could be useful.) First I thought the ``Run
-Before Job'' statement in the Job-resource is for executing a script on the
+records, but the technique still could be useful.) First I thought the "Run
+Before Job" statement in the Job-resource is for executing a script on the
remote machine(the machine to be backed up). It could be usefull to execute
scripts on the remote machine e.g. for stopping databases or other services
while doing the backup. (Of course I have to start the services again when the
\end{verbatim}
\normalsize
-This should execute the ``ls -la'' command on the remote machine.
+This should execute the "ls -la" command on the remote machine.
Now you could add lines like the following to your Director's conf file:
So you can schedule and run backups without ever having to log on or see the
console.
To make the whole thing work you need to create a Device resource which looks
-something like this (``Archive Device'', ``Maximum Changer Wait'', ``Media
-Type'' and ``Label media'' may have different values):
+something like this ("Archive Device", "Maximum Changer Wait", "Media
+Type" and "Label media" may have different values):
\footnotesize
\begin{verbatim}
\normalsize
As the script has to emulate the complete wisdom of a mtx-changer it has an
-internal ``database'' containing where which tape is stored, you can see this on
+internal "database" containing where which tape is stored, you can see this on
the following line:
\footnotesize
\normalsize
The above should be all on one line, and it effectivly tells Bacula that
-volume ``VOL-0001'' is located in slot 1 (which is our lowest slot), that
-volume ``VOL-0002'' is located in slot 2 and so on..
+volume "VOL-0001" is located in slot 1 (which is our lowest slot), that
+volume "VOL-0002" is located in slot 2 and so on..
The script also maintains a logfile (/var/log/mtx.log) where you can monitor
its operation.
\item Forward Secrecy Support via Diffie-Hellman Ephemeral Keying
\end{itemize}
-This document will refer to both ``server'' and ``client'' contexts. These
+This document will refer to both "server" and "client" contexts. These
terms refer to the accepting and initiating peer, respectively.
Diffie-Hellman anonymous ciphers are not supported by this code. The
\normalsize
Then make sure that the Address parameter in the Storage resource is set to
-the fully qualified domain name and not to something like ``localhost''. The
+the fully qualified domain name and not to something like "localhost". The
address specified is sent to the File daemon (client) and it must be a fully
-qualified domain name. If you pass something like ``localhost'' it will not
+qualified domain name. If you pass something like "localhost" it will not
resolve correctly and will result in a time out when the File daemon fails to
connect to the Storage daemon.
the new Volume.
If you have a Pool of volumes and Bacula is cycling through them, instead of
-the above message ``Cannot find any appendable volumes.'', Bacula may ask you
+the above message "Cannot find any appendable volumes.", Bacula may ask you
to mount a specific volume. In that case, you should attempt to do just that.
If you do not have the volume any more (for any of a number of reasons), you
can simply mount another volume from the same Pool, providing it is
this manual.
If you run a Bacula job, and you have no labeled tapes in the Pool, Bacula
-will inform you, and you can create them ``on-the-fly'' so to speak. In my
+will inform you, and you can create them "on-the-fly" so to speak. In my
case, I label my tapes with the date, for example: {\bf DLT-18April02}. See
below for the details of using the {\bf label} command.
end conditions, and recursive expansion.
When using variable expansion characters in a Volume Label Format record, the
-format should always be enclosed in double quotes ({\bf ``}).
+format should always be enclosed in double quotes ({\bf "}).
For example, {\bf \$\{HOME\}} will be replaced by your home directory as
defined in the environment. If you have defined the variable {\bf xxx} to be
array, where the elements of the array are referenced by subscripting the
variable name (e.g. {\bf \$\{Months[3]\}}). Environment variable arrays are
defined by separating the elements with a vertical bar ({\bf |}), thus {\bf
-set Months=''Jan|Feb|Mar|Apr|...``} defines an environment variable named
+set Months="Jan|Feb|Mar|Apr|..."} defines an environment variable named
{\bf Month} that will be treated as an array, and the reference {\bf
\$\{Months[3]\}} will yield {\bf Mar}. The elements of the array can have
differing lengths.
catalog and to report any differences. See the example below for the format of
the output.
-You decide what files you want to form your ``snapshot'' by specifying them in
+You decide what files you want to form your "snapshot" by specifying them in
a {\bf FileSet} resource, and normally, they will be system files that do not
change, or that only certain features change.
}
\end{verbatim}
\normalsize
-
-1.37.32 (26 July 2005)
+1.37.34 (03 August 2005)
\hline {WinMe } & {Linux } & {Works (SYSTEM permissions) } \\
\hline {\ } & {\ } & {\ } \\
\hline {WinXP } & {WinXP } & {Works } \\
- \hline {WinXP } & {WinNT } & {Works (all files OK, but got ``The data is invalid''
+ \hline {WinXP } & {WinNT } & {Works (all files OK, but got "The data is invalid"
message) } \\
\hline {WinXP } & {WinMe } & {Error: Win32 data stream not supported. } \\
\hline {WinXP } & {WinMe } & {Works if {\bf Portable=yes} specified during backup.} \\
SDReadSeqNo=5 fd=352
\end{verbatim}
\normalsize
-Here, you see under Running Jobs that JobId 1 is ``VSS Backup Job started ...''
+Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
This means that VSS is enabled for that job. If VSS is not enabled, it will
-simply show ``Backup Job started ...'' without the letters VSS.
+simply show "Backup Job started ..." without the letters VSS.
The second way to know that the job was backed up with VSS is to look at the
Job Report, which will look something like the following:
the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
they should apply to most Win32 platforms. The procedure outlines how to deal
with a problem which arises when a restore creates a top-level new directory.
-In this example, ``top-level'' means something like {\bf
+In this example, "top-level" means something like {\bf
c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
as the {\bf Where:} value, this problem will arise.
{\bf SYSTEM} in this example as shown below).
\includegraphics{./properties-security-advanced-owner.eps}
-\item ensure the ``Replace owner on subcontainers and objects'' box is
+\item ensure the "Replace owner on subcontainers and objects" box is
checked
\item click on OK
-\item When the message ``You do not have permission to read the contents of
+\item When the message "You do not have permission to read the contents of
directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
- the directory permissions with permissions granting you Full Control?'', click
+ the directory permissions with permissions granting you Full Control?", click
on Yes.
\includegraphics{./confirm.eps}
projects / bacula / docs / commitdiff