If you have a printed copy of this manual, the details of each of
the licenses referred to in this chapter can be found in the
online version of the manual at
-\elink{http://www.bacula.org}{\url{http://www.bacula.org}}.
+\elink{http://www.bacula.org}{http://www.bacula.org}.
\section{FDL}
\index[general]{FDL }
if you would send any corrections or changes to the Bacula project.
The most recent version of the manual can always be found online
-at \elink{http://www.bacula.org}{\url{http://www.bacula.org}}.
+at \elink{http://www.bacula.org}{http://www.bacula.org}.
\section{GPL}
\index[general]{GPL }
Bacula\raisebox{.6ex}{\textsuperscript{\textregistered}} is a registered
trademark of Kern Sibbald.
-We have trademarked the Bacula name to ensure that any program using the
-name Bacula will be exactly compatible with the program that we have
-released. The use of the name Bacula is restricted to software systems
-that agree exactly with the program presented here. If you have made
-modifications to the Bacula source code that alter in any significant
-way the way the program functions, you may not distribute it using the
-Bacula name.
-
\section{Fiduciary License Agreement}
\index[general]{Fiduciary License Agreement }
Developers who have contributed significant changes to the Bacula code
project) has the rights to the code. This Fiduciary License Agreement
is found on the Bacula web site at:
-\elink{http://www.bacula.org/en/FLA-bacula.en.pdf}{\url{http://www.bacula.org/en/FLA-bacula.en.pdf}}
+\elink{http://www.bacula.org/en/FLA-bacula.en.pdf}{http://www.bacula.org/en/FLA-bacula.en.pdf}
and if you are submitting code, you should fill it out then sent to:
but better test than be sorry. For FreeBSD (and probably other xBSD
flavors), reading the above mentioned tape testing chapter is a must.
Also, for FreeBSD, please see \elink{The FreeBSD
-Diary}{\url{http://www.freebsddiary.org/bacula.php}} for a detailed description
+Diary}{http://www.freebsddiary.org/bacula.php} for a detailed description
%TODO: fix elink so it shows URL in PDF
on how to make Bacula work on your system. In addition, users of FreeBSD
prior to 4.9-STABLE dated Mon Dec 29 15:18:01 2003 UTC who plan to use tape
\item El programa de consola en GNOME fue desarrollado y probado en GNOME 2.x. La
versión de GNOME 1.4 no está soportada por completo.
\item El programa de consola de wxWidgets fue desarrollado y probado con la ultima
-versión estable ANSI o UNICODE de \elink{wxWidgets}{\url{http://www.wxwidgets.org/}}
+versión estable ANSI o UNICODE de \elink{wxWidgets}{http://www.wxwidgets.org/}
(2.6.1). Esta aplicación trabaja muy bien con la versión de Windows y GTK+\_2.x
de wxWidgets, y debería funcionar en otras plataformas soportadas por wxWidgets.
\item El programa de Tray Monitor fue desarrollado en GTK+-2.x. Necesita la versión
de GNOME menor o igual a 2.2, KDE mayor o igual a 3.1 o cualquier manejador
-de ventanas que soporte el sistema de bandeja estándar para \elink{ FreeDesktop}{\url{http://www.freedesktop.org/Standards/systemtray-spec}}.
+de ventanas que soporte el sistema de bandeja estándar para \elink{ FreeDesktop}{http://www.freedesktop.org/Standards/systemtray-spec}.
\item Si se desea activar la edición de linea de comandos y el historial, se necesita
/usr/include/termcap.h y el paquete termcap o la librería ncurses instalada
(libtermcap-devel o ncurses-devel).
\item Si se desea utilizar DVDs como medios de respaldo, se necesita descargar el
paquete \elink{dvd+rw-tools
-5.21.4.10.8}{\url{http://fy.chalmers.se/~appro/linux/DVD+RW/}},
+5.21.4.10.8}{http://fy.chalmers.se/~appro/linux/DVD+RW/},
aplicar el patch, ubicado en el directorio \textbf{patches} del árbol de fuentes
original, para hacer que estas herramientas sean compatibles con Bacula, luego
se debe compilarlas e instalarlas. Hay un patch de dvd+rw-tools con versión
A new tool is provided in the form of a bacula plugin for the BartPE rescue
CD. BartPE is a self-contained WindowsXP boot CD which you can make using the
PeBuilder tools available at
-\elink{http://www.nu2.nu/pebuilder/}{\url{http://www.nu2.nu/pebuilder/}} and a valid
+\elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/} and a valid
Windows XP SP1 CDROM. The plugin is provided as a zip archive. Unzip the file
and copy the bacula directory into the plugin directory of your BartPE
installation. Edit the configuration files to suit your installation and build
restores to alternate directories because higher level directories were not
backed up by Bacula, you can correct any problems with the {\bf SetACL}
available under the GPL license at:
-\elink{http://sourceforge.net/projects/setacl/}{\url{http://sourceforge.net/project%
-s/setacl/}}.
+\elink{http://sourceforge.net/projects/setacl/}{http://sourceforge.net/project%
+s/setacl/}.
\section{Alternate Disaster Recovery Suggestion for Win32 Systems}
\index[general]{Systems!Alternate Disaster Recovery Suggestion for Win32}
Many thanks to Charles Curley who wrote
\elink{Linux Complete Backup and Recovery HOWTO}
-{\url{http://www.tldp.org/HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO/index.html%
-}} for the
-\elink{The Linux Documentation Project}{\url{http://www.tldp.org/}}. This is an
+{http://www.tldp.org/HOWTO/Linux-Complete-Backup-and-Recovery-HOWTO/index.html%
+} for the
+\elink{The Linux Documentation Project}{http://www.tldp.org/}. This is an
excellent document on how to do Bare Metal Recovery on Linux systems, and it
was this document that made me realize that Bacula could do the same thing.
You can find quite a few additional resources, both commercial and free at
-\elink{Storage Mountain}{\url{http://www.backupcentral.com}}, formerly known as
+\elink{Storage Mountain}{http://www.backupcentral.com}, formerly known as
Backup Central.
And finally, the O'Reilly book, "Unix Backup \& Recovery" by W. Curtis
already adapted) for proper interfacing. You can find a list of
autochangers supported by {\bf mtx} at the following link:
\elink{http://mtx.opensource-sw.net/compatibility.php}
-{\url{http://mtx.opensource-sw.net/compatibility.php}}.
+{http://mtx.opensource-sw.net/compatibility.php}.
The home page for the {\bf mtx} project can be found at:
-\elink{http://mtx.opensource-sw.net/}{\url{http://mtx.opensource-sw.net/}}.
+\elink{http://mtx.opensource-sw.net/}{http://mtx.opensource-sw.net/}.
\addcontentsline{lot}{table}{Autochangers Known to Work with Bacula}
If turning off anti-virus software does not resolve your VSS
problems, you might have to turn on VSS debugging. The following
link describes how to do this:
-\elink{http://support.microsoft.com/kb/887013/en-us}{\url{http://support.microsoft.com/kb/887013/en-us}}.
+\elink{http://support.microsoft.com/kb/887013/en-us}{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}}
+\elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{
+http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}
The most likely source of problems is authentication when the Director
It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
Environment) Boot-CD, may be just what is needed to build a complete disaster
recovery system for Win32. This distribution can be found at
-\elink{http://www.nu2.nu/pebuilder/}{\url{http://www.nu2.nu/pebuilder/}}.
+\elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
\section{Windows Restore Problems}
\index[general]{Problems!Windows Restore}
to cease the ownership of those files and thus change the permissions.
However, a much better solution to working with and changing Win32 permissions
is the program {\bf SetACL}, which can be found at
-\elink{http://setacl.sourceforge.net/}{\url{http://setacl.sourceforge.net/}}.
+\elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
If you have not installed Bacula while running as Administrator
and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
Some users like to shutdown their Windows machines after a backup using a
Client Run After Job directive. If you want to do something similar, you might
take the shutdown program from the
-\elink{apcupsd project}{\url{http://www.apcupsd.com}} or one from the
+\elink{apcupsd project}{http://www.apcupsd.com} or one from the
\elink{Sysinternals project}
-{\url{http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}}.
+{http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.