\section{Upgrading Bacula}
\index[general]{Bacula!Upgrading}
\index[general]{Upgrading Bacula}
+\index[general]{Upgrading}
If you are upgrading from one Bacula version to another, you should first
-carefully read the ReleaseNotes of all versions between your current
+carefully read the ReleaseNotes of all major 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
+to upgrade it. If you are upgrading two major versions (e.g. 1.36 to 2.0)
+then life will be more complicated because you must do two database
+upgrades. See below for more on this.
+
+Upgrading the catalog is normally done after Bacula is build and installed
by:
\begin{verbatim}
they will note if all daemons must be upgraded at the same time.
Finally, please note that in general it is not necessary to do a
-{\bf make uninstall} before doing an upgrade. In fact, if you do so, you will
+{\bf make uninstall} before doing an upgrade providing you are careful
+not to change the installation directories. In fact, if you do so, you will
most likely delete all your conf files, which could be disastrous.
The normal procedure during an upgrade is simply:
\section{Linking Bacula with MySQL}
\index[general]{Linking Bacula with MySQL }
\index[general]{MySQL!Linking Bacula with }
+\index[general]{Upgrading}
After configuring Bacula with
\section{Upgrading MySQL}
\index[general]{Upgrading MySQL }
\index[general]{Upgrading!MySQL }
+\index[general]{Upgrading}
If you upgrade MySQL, you must reconfigure, rebuild, and re-install
Bacula otherwise you are likely to get bizarre failures. If you
install from rpms and you upgrade MySQL, you must also rebuild Bacula.
\label{PostgreSqlChapter}
\index[general]{PostgreSQL!Installing and Configuring }
\index[general]{Installing and Configuring PostgreSQL }
+\index[general]{Upgrading}
Warning!!! If you are considering using PostreSQL, you should be aware
of their philosophy of upgrades, which could be
\section{Upgrading PostgreSQL}
\index[general]{Upgrading PostgreSQL }
\index[general]{Upgrading!PostgreSQL }
+\index[general]{Upgrading}
If you upgrade PostgreSQL, you must reconfigure, rebuild, and re-install
Bacula otherwise you are likely to get bizarre failures. If you
to modify the bacula.spec file to account for the new PostgreSQL version.
\index[general]{Requirements!System }
\begin{itemize}
-\item {\bf Bacula} has been compiled and run on Red Hat Linux, FreeBSD, and
+\item {\bf Bacula} has been compiled and run on OpenSuSE Linux, FreeBSD, and
Solaris systems.
\item It requires GNU C++ version 2.95 or higher to compile. You can try with
other compilers and older versions, but you are on your own. We have
- successfully compiled and used Bacula on RH8.0/RH9/RHEL 3.0/FC3 with GCC 3.4.
-Note, in general GNU C++ is a separate package (e.g. RPM) from GNU C, so you
-need them both loaded. On Red Hat systems, the C++ compiler is part of the
-{\bf gcc-c++} rpm package.
-\item There are certain third party packages that Bacula needs. Except for
+ successfully compiled and used Bacula using GNU C++ version 4.1.3.
+ Note, in general GNU C++ is a separate package (e.g. RPM) from GNU C, so you
+ need them both loaded. On Red Hat systems, the C++ compiler is part of the
+ {\bf gcc-c++} rpm package.
+\item There are certain third party packages that Bacula may need. Except for
MySQL and PostgreSQL, they can all be found in the {\bf depkgs} and {\bf
- depkgs1} releases.
-\item If you want to build the Win32 binaries, you will need a Microsoft
- Visual C++ compiler (or Visual Studio). Although all components build
- (console has some warnings), only the File daemon has been tested.
+ depkgs1} releases. However, most current Linux and FreeBSD systems
+ provide these as system packages.
+\item If you want to build the Win32 binaries, please see the
+ README.mingw32 file in the src/win32 directory. We cross-compile the
+ Win32 release on Linux. We provide documentation on building the Win32
+ version, but due to the complexity, you are pretty much on your own
+ if you want to build it yourself.
\item {\bf Bacula} requires a good implementation of pthreads to work. This
is not the case on some of the BSD systems.
\item The source code has been written with portability in mind and is mostly
POSIX compatible. Thus porting to any POSIX compatible operating system
should be relatively easy.
-\item The GNOME Console program is developed and tested under GNOME 2.x. It
- also runs under GNOME 1.4 but this version is deprecated and thus no longer
- maintained.
+\item The GNOME Console program is developed and tested under GNOME 2.x.
+ GNOME 1.4 is no longer supported.
\item The wxWidgets Console program is developed and tested with the latest
stable ANSI or Unicode version of
\elink{wxWidgets}{http://www.wxwidgets.org/} (2.6.1). It works fine with the
loaded (libtermcap-devel or ncurses-devel).
\item If you want to use DVD as backup medium, you will need to download the
\elink{dvd+rw-tools 5.21.4.10.8}{http://fy.chalmers.se/~appro/linux/DVD+RW/},
- apply the \elink{patch}{http://cvs.sourceforge.net/viewcvs.py/*checkout*/bacula/bacula/patches/dvd+rw-tools-5.21.4.10.8.bacula.patch}
+ apply the patch that is in the {\bf patches} directory of the main
+ source tree
to make these tools compatible with Bacula, then compile and install them.
- Do not use the dvd+rw-tools provided by your distribution, they will not work
- with Bacula.
+ There is also a patch for dvd+rw-tools version 6.1, and we hope that the
+ patch is integrated into a later version.
+ Do not use the dvd+rw-tools provided by your distribution, unless you
+ are sure it contains the patch. dvd+rw-tools without the patch will not
+ work with Bacula. DVD media is not recommended for serious or important
+ backups because of its low reliability.
\end{itemize}
\label{upgrading}
\index[general]{Upgrading Bacula Versions }
\index[general]{Versions!Upgrading Bacula }
+\index[general]{Upgrading}
The first thing to do before upgrading from one version to another is to
-ensure that you don't overwrite or delete your production (current) version of Bacula until
-you have tested that the new version works.
+ensure that you don't overwrite or delete your production (current) version
+of Bacula until you have tested that the new version works.
If you have installed Bacula into a single directory, this is simple: simply
make a copy of your Bacula directory.
{\bf add} command, then go into the catalog and manually set the VolStatus of
every tape to {\bf Recycle}.
-The SQL command to do this is very simple:
+The SQL command to do this is very simple, either use your vendor's
+command line interface (mysql, postgres, sqlite, ...) or use the sql
+command in the Bacula console:
\footnotesize
\begin{verbatim}
-update Media set VolStatus = "Recycle";
+update Media set VolStatus='Recycle';
\end{verbatim}
\normalsize
\addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
\includegraphics{./win32-pkg.eps}
+\index[general]{Upgrading}
\item If you are installing for the first time, you will be asked to
enter some very basic information about your configuration. If
Sometimes Win32 machines the File daemon may have very slow
backup transfer rates compared to other machines. To you might
try setting the Maximum Network Buffer Size to 32,768 in both the
-File daemon and in the Storage daemon.
+File daemon and in the Storage daemon. The default size is larger,
+and apparently some Windows ethernet controllers do not deal with
+a larger network buffer size.
+
+Many Windows ethernet drivers have a tendency to either run slowly
+due to old broken firmware, or because they are running in half-duplex
+mode. Please check with the ethernet card manufacturer for the latest
+firmware and use whatever techniques are necessary to ensure that the
+card is running in duplex.
If you are not using the portable option, and you have VSS
(Volume Shadow Copy) enabled in the Director, and you experience
link describes how to do this:
\elink{http://support.microsoft.com/kb/887013/en-us}{\url{http://support.microsoft.com/kb/887013/en-us}}.
+In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
+is turned off by default. To turn it on, please see the following link:
+\elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{\url{
+http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}}
+
+
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
projects / bacula / docs / commitdiff