\item [bacula-docs-1.38.0.tar.gz]
This file contains a copy of the docs directory with the
- documents prebuild. English html directory, single html
+ documents prebuild. English HTML directory, single HTML
file, and pdf file. The French and German translations
are in progress, but are not built.
\addcontentsline{toc}{subsection}{Upgrading Bacula}
If you are upgrading from one Bacula version to another, you should first
-carefully read the ReleaseNotes of all versions between your current version
-and the version to which you are upgrading. If the Bacula catalog database has
-been upgraded (as it is almost every major release),
-you will either need to reinitialize your database starting
-from scratch, or save an ASCII copy of your database, then proceed to upgrade
-it. This is normally done after Bacula is build and installed by:
+carefully read the ReleaseNotes of all versions between your current
+version and the version to which you are upgrading. If the Bacula catalog
+database has been upgraded (as it is almost every major release), you will
+either need to reinitialize your database starting from scratch (not
+normally a good idea), or save an ASCII copy of your database, then proceed
+to upgrade it. This is normally done after Bacula is build and installed
+by:
\begin{verbatim}
cd <installed-scripts-dir> (default /etc/bacula)
For additional information on upgrading, please see the \ilink{Upgrading Bacula
Versions}{upgrading} in the Tips chapter of this manual.
+\subsection*{Beta Releases}
+\index[general]{Beta Releases}
+\addcontentsline{toc}{subsection}{Beta Releases}
+Towards the end of the development cycle, which typically runs
+one year from a major release to another, there will be several beta
+releases of the development code prior to a production release. The
+purpose of the beta releases is to allow users to test the new code.
+Beta releases are made with the following considerations:
+\begin{itemize}
+\item The code passes the regression testing on Linux,
+ FreeBSD, and Solaris machines. Including tape drive testing
+ on Linux and FreeBSD (not currently on Solaris).
+\item There are no known major bugs.
+\item Some of the new code/features will not yet be tested.
+\item Bugs are expected to be found, especially in the new
+ code before the final production release.
+\item The code will be in production in at least one small
+ site (mine).
+\item The Win32 client will have been run in production at least
+ one night at that small site.
+\item The documentation is unlikely to be complete especially
+ for the new features, and the Release Notes may not be fully
+ organized.
+\item Beta code is not generally recommended for everyone, but
+ rather for early adopters.
+\end{itemize}
+
+
+
\subsection*{Dependency Packages}
\label{Dependency}
To install the binary Win32 version of the File daemon please see the
\ilink{Win32 Installation Chapter}{_ChapterStart7} in this document.
-\subsection*{Windows Systems with CYGWIN Installed}
-\label{Win32}
-\index[general]{Windows Systems with CYGWIN Installed }
-\index[general]{Installed!Windows Systems with CYGWIN }
-\addcontentsline{toc}{subsection}{Windows Systems with CYGWIN Installed}
-
-As of version 1.34, Bacula no longer uses CYGWIN for the Win32 File daemon.
-However, it is still built under a CYGWIN build environment -- though you
-can probably do it with VC Studio only. If you wish to build the Win32
-File daemon from the source, you will need Microsoft C++ version 7.1.
-Details for building the Win32 FD are in the README.win32 file of the
-src/win32 directory.
-
-Note, although most parts of Bacula build on Windows systems, the only part
-that we have tested and used is the File daemon.
-
-Finally, you should follow the installation instructions in the
-\ilink{Win32 Installation}{_ChapterStart7} section of this document.
-
\subsection*{Kern's Configure Script}
\index[general]{Script!Kern's Configure }
\index[general]{Kern's Configure Script }
./configure \
--sbindir=$HOME/bacula/bin \
--sysconfdir=$HOME/bacula/bin \
+ --mandir=$HOME/bacula/bin \
--enable-smartalloc \
--enable-gnome \
+ --enable-wx-console \
+ --enable-tray-monitor \
--with-pid-dir=$HOME/bacula/bin/working \
--with-subsys-dir=$HOME/bacula/bin/working \
- --with-mysql=$HOME/mysql \
+ --with-mysql \
--with-working-dir=$HOME/bacula/bin/working \
- --with-dump-email=$USER \
- --with-smtp-host=mail.your-site.com \
- --with-baseport=9101
+ --with-dump-email=$USER@your-site.com \
+ --with-job-email=$USER@your-site.com \
+ --with-smtp-host=mail.your-site.com
exit 0
\end{verbatim}
\normalsize
-Note that I define the base port as 9101, which means that Bacula will use
-port 9101 for the Director console, port 9102 for the File daemons, and port
-9103 for the Storage daemons. These ports should be available on all systems
-because they have been officially assigned to Bacula by IANA (Internet
-Assigned Numbers Authority). We strongly recommend that you use only these
-ports to prevent any conflicts with other programs. This is in fact the
-default if you do not specify a {\bf \verb:--:with-baseport} option.
-
You may also want to put the following entries in your {\bf /etc/services}
file as it will make viewing the connections made by Bacula easier to
recognize (i.e. netstat -a):
the conf file to be unique. Be sure to make corresponding additions to the
Director's configuration file ({\bf bacula-dir.conf}).
-If the architecture or the O/S level are different, you will need to build a
+If the architecture or the OS level are different, you will need to build a
File daemon on the Client machine. To do so, you can use the same {\bf
./configure} command as you did for your main program, starting either from a
fresh copy of the source tree, or using {\bf make\ distclean} before the {\bf
stopmysql
wx-console
wx-console.conf
+9 man pages
\end{verbatim}
\normalsize
\item Restore Features
\begin{itemize}
- \item Restore of one or more files selected interactively either for the
+ \item Restore of one or more files selected interactively either for the
current backup or a backup prior to a specified time and date.
\item Restore of a complete system starting from bare metal. This is mostly
automated for Linux systems and partially automated for Solaris. See
when Bacula and/or the catalog are not available. Note, the recommended way
to restore files is using the restore command in the Console. These programs
are designed for use as a last resort.
+ \item Ability to restore the catalog database rapidly by using bootstrap
+ files (previously saved).
\item Ability to recreate the catalog database by scanning backup Volumes
using the {\bf bscan} program.
\end{itemize}
\begin{itemize}
\item Catalog database facility for remembering Volumes, Pools, Jobs, and
Files backed up.
- \item Support for SQLite, PostgreSQL, and MySQL Catalog databases.
- \item User extensible queries to the SQLite, PostgreSQL and MySQL databases.
+ \item Support for MySQL, PostgreSQL, and SQLite Catalog databases.
+ \item User extensible queries to the MySQL, PostgreSQL and SQLite databases.
\end{itemize}
\item Advanced Volume and Pool Management
sets segregated by Client, ...).
\item Machine independent Volume data format. Linux, Solaris, and Windows
clients can all be backed up to the same Volume if desired.
+ \item The Volume data format is upwards compatible so that old Volumes
+ can always be read.
\item A flexible
\ilink{ message}{MessageResource} handler including routing
of messages from any daemon back to the Director and automatic email
\item Access control lists for Consoles that permit restricting user access
to only their data.
\item Support for save/restore of files larger than 2GB.
- \item Support for 64 bit machines, e.g. amd64.
- \item Ability to encrypt communications between daemons using stunnel.
+ \item Support for 64 bit machines, e.g. amd64, Sparc.
\item Support ANSI and IBM tape labels.
\item Support for Unicode filenames (e.g. Chinese) on Win32 machines on
version 1.37.28 and greater.
-1.39.22 (07 Septermber 2006)
+1.39.22 (08 September 2006)
NSIS Free Software installer, so if you have already installed Windows
software, it should be very familiar to you.
-If you have a previous version Cygwin of Bacula (1.32 or lower)
+If you have a previous version Bacula (1.39.20 or lower)
installed, you should stop the service, uninstall it, and remove
the Bacula installation directory possibly saving your
-bacula-fd.conf file for use with the new version you will
-install. Current versions of Bacula do not use Cygwin and has
-far fewer files than the old Cygwin version, so it is better to
-start with a clean directory.
-
-If you have Bacula version 1.38 or lower, we recommend the same procedure
-as mentioned in the paragraph above. This is because Bacula 1.39 and
-greater installs a bit differently from previous versions. There are
-different registry keys, ... that are better cleaned up before installing
-the new version.
+bacula-fd.conf, bconsole.conf, and wx-console.conf files
+for use with the new version you will install. The Uninstall
+program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
+We also recommend that you completely remove the directory
+{\bf c:\textbackslash{}bacula}, because the current installer
+uses a different directory structure (see below).
+
+Providing you do not already have Bacula installed,
+the new installer (1.39.22 and later) installs the binaries and dlls in
+c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
+and the configuration files
+in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
+In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
+will be created during the installation, and on that menu, you
+will find items for editing the configuration files, displaying
+the document, and starting wx-console or bconsole.
Finally, proceed with the installation.
another.
\includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe
-\
+
\item Once launched, the installer wizard will ask you if you want to install
Bacula.
\addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
\includegraphics{./win32-welcome.eps}
-\
+
+\item Next you will be asked to select the installation type.
+
+\addcontentsline{lof}{figure}{Win32 Installation Type}
+\includegraphics{./win32-installation-type.eps}
+
+
\item If you proceed, you will be asked to select the components to be
installed. You may install the Bacula program (Bacula File Service) and or
the documentation. Both will be installed in sub-directories of the install
\addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
\includegraphics{./win32-pkg.eps}
-\item Next you will be asked to select an installation directory.
-
-\addcontentsline{lof}{figure}{Win32 Directory Selection Dialog}
-\includegraphics{./win32-location.eps}
+\item If you are installing for the first time, you will be asked to
+ enter some very basic information about your configuration. If
+ you are not sure what to enter, or have previously saved configuration
+ files, you can put anything you want into the fields, then either
+ replace the configuration files later with the ones saved, or edit
+ the file.
-\item If you are installing for the first time, you will be asked if you want
- to edit the bacula-fd.conf file, and if you respond with yes, it will be
- opened in notepad. Note, if you have installed Bacula to a drive other
- than C: you probably should prefix the installation drive name to each
- of the directory references in the bacula-fd.conf file, in particular
- the {\bf WorkingDirectory} and the {\bf Pid Directory} directives.
+ If you are upgrading an existing installation, the following will
+ not be displayed.
- Also, if you do not wish to see the full listing of all files restored
- in the job output after running a restore job, you can add {\bf ,
- !restored} to the {\bf director} directive in the {\bf Messages}
- resource.
\addcontentsline{lof}{figure}{Win32 Configure}
\includegraphics{./win32-config.eps}
-\item Then the installer will display a dialog that allows you to
- to install Bacula as a service. You should always choose to do so.
- It also permits you to start the service. Normally you should check
- the box, and any running Bacula will be shutdown and the new one started. You
- may see a DOS box momentarily appear on the screen as the service is started.
- It should disappear in a second or two:
-
-\addcontentsline{lof}{figure}{Win32 Client Service Selection}
-\includegraphics{./win32-service.eps}
-
-
-\item If everything goes well, you will receive the following confirmation:
-
- \addcontentsline{lof}{figure}{Win32 Client Service Confirmation}
- \includegraphics{./win32-service-ok.eps}
-
\item While the various files are being loaded, you will see the following
dialog:
\addcontentsline{toc}{subsection}{Post Win32 Installation}
After installing Bacula and before running it, you should check the contents
-of {\bf
-c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} to
-ensure that it corresponds to your configuration.
+of the configuration files to ensure that they correspond to your
+installation. You can get to them by using:
+the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
is running as a process (not an Application) with User Name SYSTEM. If this is
The most likely source of problems is authentication when the Director
attempts to connect to the File daemon that you installed. This can occur if
the names and the passwords defined in the File daemon's configuration file
-{\bf
-c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} on
+{\bf bacula-fd.conf} file on
the Windows machine do not match with the names and the passwords in the
Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
server.
projects / bacula / docs / commitdiff