# autoconf/Make.common.in -*- Makefile -*-
# release date (man), LSM date, version number/name, current maintainer
-DATE="18 August 2005"
+DATE="24 August 2005"
LSMDATE=@LSMDATE@
-VERSION=1.37.36
+VERSION=1.37.37
VERNAME=bacula-$(VERSION)#
MAINT=Kern Sibbald#
MAINTEMAIL=<kern@sibbald.com>#
uninstall:
# -cd $(mandir); $(RMF) $(manprefix)bacula.$(manext)
-distribution:
+release:
rm -rf bacula-doc-*
mkdir -p bacula-doc-$(VERSION)
cp -ap manual/bacula bacula-doc-$(VERSION)/web-manual
tar cvfz bacula-doc-$(VERSION).tar.gz bacula-doc-$(VERSION)
rm -rf bacula-doc-$(VERSION)
@echo " "
- @echo "Distribution document is in: bacula-doc-$(VERSION).tar.gz"
+ @echo "Release document is in: bacula-doc-$(VERSION).tar.gz"
@echo " "
To create a distribution tar file:
cd <docs>
+ ./configure --with-bacula=<bacula-source-directory>
+ make clean
make
- make distribution
+ make release
The output will be a .tar.gz file in the current directory
with the name bacula-doc-<version>.tar.gz
-1.37.36 (18 August 2005)
+1.37.37 (24 August 2005)
+Kern;;;2005/08/23;;;10:20
+Results to date of donations for the Data Encryption project
+24 August 2005
+ Donor: Amount:
+ WingNET Internet $500
+ Timo Neuvonen $250
+ Ed Grether $25
+ Charles Reinehr $100
+ Michael Proto $25
+ Phil Cordier $100
+ Dan Langille $100
+ Tom Plancon $65
+ Felix Schwarz $60
+ ClarkConnect $500
+ Goal: $3000 Total: $1,725
+
+Note, the official list is kept by Landon at:
+
+ http://landonf.bikemonkey.org/code/bacula
+
+Read on for details of the project.
+
Kern;;;2005/07/26;;;14:30
BACULA COMMUNITY NEWS RELEASE
Backup Data Encryption Development Project
-1.37.36 (18 August 2005)
+1.37.37 (24 August 2005)
If you follow the instructions in this chapter, you will have covered most of
the major problems that can occur. It goes without saying that if you ever
-find that we have left out an important point, please point it out to us, so
+find that we have left out an important point, please inform us, so
that we can document it to the benefit of everyone.
\label{Critical}
understand it, you have at least worked through the tutorial or have
equivalent experience, and that you have set up a basic production
configuration. If you haven't done the above, please do so and then come back
-here. The following is a sort of checklist that points you elsewhere in the
-manual with perhaps a brief explanation of why you should do it. The order is
-more or less the order you would use in setting up a production system (if you
-already are in production, use the checklist anyway).
+here. The following is a sort of checklist that points with perhaps a brief
+explanation of why you should do it. You will find the details elsewhere in the
+manual. The order is more or less the order you would use in setting up a
+production system (if you already are in production, use the checklist anyway).
\begin{itemize}
-\item Test your tape drive with compatibility with Bacula by using the test
+\item Test your tape drive for compatibility with Bacula by using the test
command in the \ilink{btape}{btape} program.
\item Better than doing the above is to walk through the nine steps in the
\ilink{Tape Testing}{_ChapterStart27} chapter of the manual. It
may take you a bit of time, but it will eliminate surprises.
-\item Make sure that /lib/tls is disabled. Bacula does not work with this
- library. See the second point under
+\item Test your the end of tape handling of your tape drive by using the
+ fill command in the \ilink{btape}{btape} program.
+\item If you are using a 2.4 kernel, make sure that /lib/tls is disabled. Bacula
+ does not work with this library. See the second point under
\ilink{ Supported Operating Systems.}{SupportedOSes}
\item Do at least one restore of files. If you backup both Unix and Win32
systems, restore files from each system type. The
CDROM}{_ChapterStart38} chapter. It is trivial to make such a CDROM,
and it can make system recovery in the event of a lost hard disk infinitely
easier.
+\item After doing your first backup restore some or all the data. Do this for
+ at least one client on each different OS (e.g. Linux, FreeBSD, Solaris, Win32).
\end{itemize}
\subsection*{Recommended Items}
\item After installing and experimenting with Bacula, read and work carefully
through the examples in the
\ilink{Tutorial}{_ChapterStart1} chapter of this manual.
-\item Learn what each of the \ilink{Bacula Utility Programs}{_ChapterStart9} does.
+\item Learn what each of the \ilink{Bacula Utility Programs}{_ChapterStart9}
+does.
\item Set up reasonable retention periods so that your catalog does not grow
to be too big. See the following three chapters:\\
\ilink{Recycling your Volumes}{_ChapterStart22},\\
\ilink{Basic Volume Management}{_ChapterStart39},\\
\ilink{Using Pools to Manage Volumes}{_ChapterStart11}.
\item Perform a bare metal recovery using the Bacula Rescue CDROM. See the
- \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{_ChapterStart38} chapter.
- \end{itemize}
+ \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{_ChapterStart38}
+ chapter.
+\end{itemize}
+
+If you absolutely must implement a system where you write a different
+tape each night and take it offsite in the morning. We recommend that you do
+several things:
+\begin{itemize}
+\item Write a bootstrap file of your backed up data and a bootstrap file
+ of your catalog backup to a floppy disk or a CDROM, and take that with
+ the tape. If this is not possible, try to write those files to another
+ computer or offsite computer, or send them as email to a friend. If none
+ of that is possible, at least print the bootstrap files and take that
+ offsite with the tape. Having the bootstrap files will make recovery
+ much easier.
+\item It is better not to force Bacula to load a particular tape each day.
+ Instead, let Bacula choose the tape. If you need to know what tape to
+ mount, you can print a list of recycled and appendable tapes daily, and
+ select any tape from that list. Bacula may propose a particular tape
+ for use that it considers optimal, but it will accept any valid tape
+ from the correct pool.
+\end{itemize}
we believe that only the System environment will be available to bacula-fd,
if it is running as a service.)
- System environment variables can be called out using the \%var\% syntax and
+ System environment variables can be referenced with \%var\% and
used as either part of the command name or arguments.
When specifying a full path to an executable if the path or executable name
We {\bf highly} recommend against using this directive, because it is sure that
some day, Bacula will recycle a Volume that contains current data.
-\item [Accept Any Volume = \lt{}yes|no\gt{}]
- \index[dir]{Accept Any Volume }
- This directive specifies whether or not any volume from the Pool may be
-used
-for backup. The default is {\bf yes} as of version 1.27 and later. If it is
-{\bf no} then only the first writable volume in the Pool will be accepted for
-writing backup data, thus Bacula will fill each Volume sequentially in turn
-before using any other appendable volume in the Pool. If this is {\bf no} and
-you mount a volume out of order, Bacula will not accept it. If this is {\bf
-yes} any appendable volume from the pool mounted will be accepted.
-
-If your tape backup procedure dictates that you manually mount the next
-volume, you will almost certainly want to be sure this directive is turned
-on.
-
-If you are going on vacation and you think the current volume may not have
-enough room on it, you can simply label a new tape and leave it in the drive,
-and assuming that {\bf Accept Any Volume} is {\bf yes} Bacula will begin
-writing on it. When you return from vacation, simply remount the last tape,
-and Bacula will continue writing on it until it is full. Then you can remount
- your vacation tape and Bacula will fill it in turn.
-
\item [Cleaning Prefix = \lt{}string\gt{}]
\index[dir]{Cleaning Prefix }
This directive defines a prefix string, which if it matches the beginning
versions prior to 1.32f-5-09Mar04 due to a bug, you will not be able to
restore hard linked files that were backed up twice.
-If you have used Bacula prior to version 1.34.3, you will note three things in
+If you have used Bacula prior to version 1.36.3, you will note three things in
the new FileSet syntax:
\begin{enumerate}
of "default" options, you should put them in an Options resource after
any other Options.
+It is a good idea to put all your wild-card and regex expressions inside
+double quotes to prevent conf file scanning problems.
+
This is perhaps a bit overwhelming, so there are a number of examples included
below to illustrate how this works.
Multiple wild-card directives may be specified, and they will be applied
in turn until the first one that matches. Note, if you exclude a
directory, no files or directories below it will be matched.
+ It is recommended to enclose the string in double quotes.
\item [wildfile=\lt{}string\gt{}]
\index[dir]{wildfile }
which files are to be excluded. Multiple wild-card directives may be
specified, and they will be applied in turn until the first one that
matches.
+ It is recommended to enclose the string in double quotes.
\item [wilddir=\lt{}string\gt{}]
\index[dir]{wilddir }
specified, and they will be applied in turn until the first one that
matches. Note, if you exclude a directory, no files or directories
below it will be matched.
+ It is recommended to enclose the string in double quotes.
\item [regex=\lt{}string\gt{}]
specified within an Options resource, and they will be applied in turn
until the first one that matches. Note, if you exclude a
directory, no files or directories below it will be matched.
+ It is recommended to enclose the string in double quotes.
\item [regexfile=\lt{}string\gt{}]
\index[dir]{regexfile }
which files are to be excluded. Multiple regex directives may be
specified, and they will be applied in turn until the first one that
matches.
+ It is recommended to enclose the string in double quotes.
\item [regexdir=\lt{}string\gt{}]
\index[dir]{regexdir }
regex directives may be specified, and they will be applied in turn
until the first one that matches. Note, if you exclude a directory, no
files or directories below it will be matched.
+ It is recommended to enclose the string in double quotes.
\item [exclude=yes|no]
\index[dir]{exclude }
}
Include {
Options {
- wildfile = *.o
- wildfile = *.exe
+ wildfile = "*.o"
+ wildfile = "*.exe"
Exclude = yes
}
File = /root/myfile
}
Include {
Options {
- wildfile = *.o
- wildfile = *.exe
+ wildfile = "*.o"
+ wildfile = "*.exe"
Exclude = yes
}
File = /root/myfile
Options {
wilddir = /proc
wilddir = /tmp
- wildfile = \.journal
- wildfile = \.autofsck
+ wildfile = ".journal"
+ wildfile = ".autofsck"
exclude = yes
}
File = /
Name = "Full Set"
Include { !!!!!!!!!!!!
Options { This
- wildfile = *.Z example
- wildfile = *.gz doesn't
+ wildfile = "*.Z" example
+ wildfile = "*.gz" doesn't
Include = yes work
} !!!!!!!!!!!!
File = /myfile
Name = "Full Set"
Include {
Options {
- wildfile = *.Z
- wildfile = *.gz
+ wildfile = "*.Z"
+ wildfile = "*.gz"
Include = yes
}
Options {
Name = "Windows Set"
Include {
Options {
- WildFile = *.obj
- WildFile = *.exe
+ WildFile = "*.obj"
+ WildFile = "*.exe"
exclude = yes
}
File = "c:/My Documents"
-1.37.36 (18 August 2005)
+1.37.37 (24 August 2005)
projects / bacula / docs / commitdiff