been thouroughly tested on Windows and is suitable for a
production environment. As a consequence, when we
speak of the Windows version of Bacula below, we are referring to
-the File daemon (client) only.
+the File daemon (client) only.
The Windows version of the Bacula File daemon has been tested on WinXP,
-Win2000, Windows Server 2003, Windows Server 2008, Vista, and Windows 7
-systems. The Windows version of Bacula is a native Win32 port, but there
-are very few source code changes to the Unix code, which means that the
-Windows version is for the most part running code that has long proved
-stable on Unix systems. When running, it is perfectly integrated with
-Windows and displays its icon in the system icon tray, and provides a
-system tray menu to obtain additional information on how Bacula is running
-(status and events dialog boxes). If so desired, it can also be stopped by
-using the system tray menu, though this should normally never be necessary.
-
-Once installed Bacula normally runs as a system service. This means that it is
-immediately started by the operating system when the system is booted, and
-runs in the background even if there is no user logged into the system.
-
-\section{Win32 Installation}
+Win2000, Windows Server 2003, Windows Server 2008, Vista, Windows 7, and
+Windows 2012 systems. The Windows version of Bacula is a native Windows
+port, but there are very few source code changes to the Unix code, which
+means that the Windows version is for the most part running code that has
+long proved stable on Unix systems. When running, it is perfectly
+integrated with Windows.
+
+Once installed Bacula normally runs as a system service. This means that
+it is immediately started by the operating system when the system is
+booted, and runs in the background even if there is no user logged into the
+system.
+
+\section{Windows Installation}
\label{installation}
\index[general]{Installation}
-\index[general]{Win32!Installation}
+\index[general]{Windows!Installation}
Normally, you will install the Windows version of Bacula from the binaries.
This install is standard Windows .exe that runs an install wizard using the
NSIS Free Software installer, so if you have already installed Windows
-software, it should be very familiar to you.
+software, it should be very familiar to you.
If you have a previous version of Bacula
installed, you should stop the service, uninstall it, and remove
uses a different directory structure (see below).
Providing you do not already have Bacula installed,
-the installer installs the binaries and dlls in
-c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
+the installer 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
the document, and starting bwx-console or bconsole.
-Finally, proceed with the installation.
+Finally, proceed with the installation.
-\begin{itemize}
+\begin{bsysitemize}
\item You must be logged in as Administrator to the local machine
to do a correct installation, if not, please do so before continuing.
Some users have attempted to install logged in as a domain administrator
account and experienced permissions problems attempting to run
Bacula, so we don't recommend that option.
-
-\item Simply double click on the {\bf bacula-win32-5.xx.0.exe} NSIS install
- icon. The actual name of the icon will vary from one release version to
- another.
-\includegraphics{\idir win32-nsis.eps} bacula-win32-5.xx.0.exe
-
-\item Once launched, the installer wizard will ask you if you want to install
- Bacula.
+\item Simply double click on the {\bf bacula-win64-6.xx.0.exe} NSIS install
+ icon. The actual name of the icon will vary from one release version to
+ another.
+
+\includegraphics{nsis} bacula-win64-6.xx.0.exe
-\addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
-\includegraphics{\idir win32-welcome.eps}
+\item Once launched, the installer wizard will ask you if you want to install
+ Bacula.
-\item Next you will be asked to select the installation type.
+\bsysimageH{win32-welcome}{Windows Client Setup Wizard}{fig:win32clientsetupwizard}
-\addcontentsline{lof}{figure}{Win32 Installation Type}
-\includegraphics{\idir win32-installation-type.eps}
+\item Next you will be asked to select the installation type.
+\bsysimageH{win32-installation-type}{Windows Installation Type}{fig:win32installationtype}
-\item If you proceed, you will be asked to select the components to be
+\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
location that you choose later. The components dialog looks like the
- following:
+ following:
-\addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
-\includegraphics{\idir win32-pkg.eps}
+\bsysimageH{win32-pkg}{Win32 Component Selection Dialog}{fig:win32componentselectiondialog}
\index[general]{Upgrading}
\item If you are installing for the first time, you will be asked to
not be displayed.
-\addcontentsline{lof}{figure}{Win32 Configure}
-\includegraphics{\idir win32-config.eps}
-
+\bsysimageH{win32-config}{Win32 Configure}{fig:win32configure}
+
\item While the various files are being loaded, you will see the following
dialog:
- \addcontentsline{lof}{figure}{Win32 Install Progress}
- \includegraphics{\idir win32-installing.eps}
+\bsysimageH{win32-installing}{Windows Install Progress}{fig:win32installing}
+\item Finally, the finish dialog will appear:
-\item Finally, the finish dialog will appear:
+\bsysimageH{win32-finish}{Windows Client Setup Completed}{fig:win32setupcompleted}
- \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
- \includegraphics{\idir win32-finish.eps}
+\end{bsysitemize}
-\
-\end{itemize}
+That should complete the installation process.
-That should complete the installation process. When the Bacula File Server is
-ready to serve files, an icon \includegraphics{\idir idle.eps} representing a
+\section{Tray Icon}
+\index[general]{Tray Icon}
+
+Note: this section does not apply to all Windows versions
+later than Windows XP, since in those later versions Microsoft
+explicitly prohibits a system service such as Bacula from interacting
+with the user.
+
+When the Bacula File Server is
+ready to serve files, an icon \raisebox{-1ex}{\includegraphics{k7-idle}} representing a
cassette (or tape) will appear in the system tray
-\includegraphics{\idir tray-icon.eps}; right click on it and a menu will appear.\\
-\includegraphics{\idir menu.eps}\\
+\raisebox{-2ex}{\includegraphics{tray-icon}}; right click on it and a menu will appear.\\
+\bsysimageN{menu}{Menu on right click}{fig:win32menuonrightclick}\\
The {\bf Events} item is currently unimplemented, by selecting the {\bf
-Status} item, you can verify whether any jobs are running or not.
+Status} item, you can verify whether any jobs are running or not.
When the Bacula File Server begins saving files, the color of the holes in the
-cassette icon will change from white to green \includegraphics{\idir running.eps},
+cassette icon will change from white to green \raisebox{-1ex}{\includegraphics{k7-ok}},
and if there is an error, the holes in the cassette icon will change to red
-\includegraphics{\idir error.eps}.
+\raisebox{-1ex}{\includegraphics{k7-error}}.
If you are using remote desktop connections between your Windows boxes, be
warned that that tray icon does not always appear. It will always be visible
-when you log into the console, but the remote desktop may not display it.
+when you log into the console, but the remote desktop may not display it.
-\section{Post Win32 Installation}
-\index[general]{Post Win32 Installation}
-\index[general]{Win32!Post Installation}
+\section{Post Windows Installation}
+\index[general]{Post Windows Installation}
+\index[general]{Windows!Post Installation}
After installing Bacula and before running it, you should check the contents
of the configuration files to ensure that they correspond to your
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
+is running as a process (not an Application) with User Name SYSTEM. If this is
not the case, you probably have not installed Bacula while running as
Administrator, and hence it will be unlikely that Bacula can access
all the system files.
-\section{Uninstalling Bacula on Win32}
-\index[general]{Win32!Uninstalling Bacula}
-\index[general]{Uninstalling Bacula on Win32}
+\section{Uninstalling Bacula on Windows}
+\index[general]{Windows!Uninstalling Bacula}
+\index[general]{Uninstalling Bacula on Windows}
Once Bacula has been installed, it can be uninstalled using the standard
-Windows Add/Remove Programs dialog found on the Control panel.
+Windows Add/Remove Programs dialog found on the Control panel.
-\section{Dealing with Win32 Problems}
+\section{Dealing with Windows Problems}
\label{problems}
-\index[general]{Win32!Dealing with Problems}
-\index[general]{Dealing with Win32 Problems}
+\index[general]{Windows!Dealing with Problems}
+\index[general]{Dealing with Windows Problems}
-Sometimes Win32 machines the File daemon may have very slow
+Sometimes Windows 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. The default size is larger,
-and apparently some Windows ethernet controllers do not deal with
+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
+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
+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
{\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.
+server.
More specifically, the password found in the {\bf Client} resource in the
Director's configuration file must be the same as the password in the {\bf
Director} resource of the File daemon's configuration file. In addition, the
name of the {\bf Director} resource in the File daemon's configuration file
must be the same as the name in the {\bf Director} resource of the Director's
-configuration file.
+configuration file.
It is a bit hard to explain in words, but if you understand that a Director
normally has multiple Clients and a Client (or File daemon) may permit access
by multiple Directors, you can see that the names and the passwords on both
-sides must match for proper authentication.
+sides must match for proper authentication.
One user had serious problems with the configuration file until he realized
that the Unix end of line conventions were used and Bacula wanted them in
-Windows format. This has not been confirmed though, and Bacula version 2.0.0
-and above should now accept all end of line conventions (Win32,
+Windows format. This has not been confirmed though, and Bacula version 2.0.0
+and above should now accept all end of line conventions (Windows,
Unix, Mac).
Running Unix like programs on Windows machines is a bit frustrating because
consequence, it is not generally possible to see the debug information and
certain error messages that Bacula prints. With a bit of work, however, it is
possible. When everything else fails and you want to {\bf see} what is going
-on, try the following:
+on, try the following:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
Start a DOS shell Window.
c:\Program Files\bacula\bacula-fd -t >out
type out
-\end{verbatim}
+\end{lstlisting}
\normalsize
The precise path to bacula-fd depends on where it is installed.
The {\bf -t} option will cause Bacula to read the configuration file, print
any error messages and then exit. the {\bf \gt{}} redirects the output to the
-file named {\bf out}, which you can list with the {\bf type} command.
+file named {\bf out}, which you can list with the {\bf type} command.
If something is going wrong later, or you want to run {\bf Bacula} with a
-debug option, you might try starting it as:
+debug option, you might try starting it as:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
c:\Program Files\bacula\bin\bacula-fd -d 100 >out
-\end{verbatim}
+\end{lstlisting}
\normalsize
In this case, Bacula will run until you explicitly stop it, which will give
-you a chance to connect to it from your Unix/Linux server. In later versions
-of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
-can write the output to a trace file {\bf bacula.trace} in the current
-directory. To enable this, before running a job, use the console, and enter:
+you a chance to connect to it from your Unix/Linux server. When you start
+the File daemon in debug mode it can write the output to a trace file {\bf
+bacula.trace} in the current directory. To enable this, before running a
+job, use the console, and enter:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
trace on
-\end{verbatim}
+\end{lstlisting}
\normalsize
then run the job, and once you have terminated the File daemon, you will find
-the debug output in the {\bf bacula.trace} file, which will probably be
+the debug output in the {\bf bacula.trace} file, which will probably be
located in the same directory as bacula-fd.exe.
In addition, you should look in the System Applications log on the Control
-Panel to find any Windows errors that Bacula got during the startup process.
+Panel to find any Windows errors that Bacula got during the startup process.
Finally, due to the above problems, when you turn on debugging, and specify
trace=1 on a setdebug command in the Console, Bacula will write the debug
information to the file {\bf bacula.trace} in the directory from which Bacula
-is executing.
+is executing.
-If you are having problems with ClientRunBeforeJob scripts randomly dying,
+If you are having problems with ClientRunBeforeJob scripts randomly dying,
it is possible that you have run into an Oracle bug. See bug number 622 in
the bugs.bacula.org database. The following information has been
provided by a user on this issue:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
The information in this document applies to:
Oracle HTTP Server - Version: 9.0.4
Microsoft Windows Server 2003
Symptoms
When starting an OC4J instance, the System Clock runs faster, about 7
seconds per minute.
-
+
Cause
-
+
+ This is caused by the Sun JVM bug 4500388, which states that "Calling
Thread.sleep() with a small argument affects the system clock". Although
this is reported as fixed in JDK 1.4.0_02, several reports contradict this
(see the bug in
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
-
+
+ Also reported by Microsoft as "The system clock may run fast when you
use the ACPI power management timer as a high-resolution counter on Windows
2000-based computers" (See http://support.microsoft.com/?id=821893)
-\end{verbatim}
+\end{lstlisting}
\normalsize
You may wish to start the daemon with debug mode on rather than doing it
using bconsole. To do so, edit the following registry key:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
-\end{verbatim}
+\end{lstlisting}
\normalsize
using regedit, then add -dnn after the /service option, where nn represents
Microsoft applications do not open files exclusively so that they can be
backed up. However, you will need to experiment. In any case, if Bacula
cannot open the file, it will print an error message, so you will always
-know which files were not backed up. For version 1.37.25 and greater, see
-the section below on Volume Shadow Copy Service that permits backing up any
-file.
+know which files were not backed up. See the section below on Volume
+Shadow Copy Service that permits backing up any file.
During backup, Bacula doesn't know about the system registry, so you will
-either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
-program specifically designed to make a copy or backup the registry.
+either need to write it out to an ASCII file using {\bf regedit~~/e} or use
+a program specifically designed to make a copy or backup the registry.
-In Bacula version 1.31 and later, we use Windows backup API calls by
-default. Typical of Windows, programming these special BackupRead and
-BackupWrite calls is a real nightmare of complications. The end result
-gives some distinct advantages and some disadvantages.
+Bacula uses Windows backup API calls by default. Typical of Windows,
+programming these special BackupRead and BackupWrite calls is a real
+nightmare of complications. The end result gives some distinct advantages
+and some disadvantages.
First, the advantages are that Windows systems, the security and
ownership information is now backed up. In addition, with the exception of
can be restored, the Windows security and access control data will not be
restored. This means that a standard set of access permissions will be set
for such restored files.
-
+
As a default, Bacula backs up Windows systems using the Windows API calls.
If you want to backup data on a Windows system and restore it on a
ownership information will be backed up or restored. The file data can,
however, be restored on any system.
-You should always be able to restore any file backed up on Unix or Win95/98/Me
-to any other system. On some older Windows systems, you may have to
-reset the ownership of such restored files.
+You should always be able to restore any file backed up on Unix or
+Win95/98/Me to any other system. On some older Windows systems, you may
+have to reset the ownership of such restored files.
Finally, if you specify the {\bf portable=yes} option on the files you back
-up. Bacula will be able to restore them on any other system. However, any
-Windows specific security and ownership information will be lost.
+up. Bacula will be able to restore them on any other system. However, any
+Windows specific security and ownership information will be lost.
The following matrix will give you an idea of what you can expect. Thanks to
-Marc Brueckner for doing the tests:
-
-\addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
-\begin{longtable}{|l|l|p{2.8in}|}
- \hline
-\multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
-& \multicolumn{1}{c|}{\bf Results } \\
- \hline {WinMe} & {WinMe} & {Works } \\
- \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
- \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
- \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
- \hline {\ } & {\ } & {\ } \\
- \hline {WinXP} & {WinXP} & {Works } \\
- \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.} \\
- \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
- \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
- \hline {\ } & {\ } & {\ } \\
- \hline {WinNT} & {WinNT} & {Works } \\
- \hline {WinNT} & {WinXP} & {Works } \\
- \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
- \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
- \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
- \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
- \hline {\ } & {\ } & {\ } \\
- \hline {Linux} & {Linux} & {Works } \\
- \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
- \hline {Linux} & {WinMe} & {Works } \\
- \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
-\\ \hline
-\end{longtable}
-
-Note: with Bacula versions 1.39.x and later, non-portable Windows data can
-be restore to any machine.
+Marc Brueckner for doing the tests:
+
+\LTXtable{\linewidth}{table_restoreportabilitystatus}
+Note: Non-portable Windows data can be restore to any machine. In
+addition, with recent Bacula versions, Bacula is able to extract data
+part from Windows backup streams when restoring on a non-Windows
+machine.
\label{VSS}
\section{Volume Shadow Copy Service}
\index[general]{Volume Shadow Copy Service}
\index[general]{VSS}
-In version 1.37.30 and greater, you can turn on Microsoft's Volume
-Shadow Copy Service (VSS).
-
Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
a backup-solution for Windows, this is an extremely important step. VSS
allows Bacula to backup open files and even to interact with applications like
when it is doing a VSS backup so you know which ones are correctly backed
up.
-Bacula supports VSS on both Windows 2003 and Windows XP.
Technically Bacula creates a shadow copy as soon as the backup process
starts. It does then backup all files from the shadow copy and destroys the
shadow copy after the backup process. Please have in mind, that VSS
\index[dir]{Enable VSS}
\index[general]{Enable VSS}
-\begin{verbatim}
+\begin{lstlisting}
Enable VSS = yes
-\end{verbatim}
+\end{lstlisting}
-in your FileSet resource.
+in your FileSet resource.
The VSS aware File daemon has the letters VSS on the signon line that
it produces when contacted by the console. For example:
-\begin{verbatim}
+\begin{lstlisting}
Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
-\end{verbatim}
+\end{lstlisting}
the VSS is shown in the line above. This only means that the File daemon
is capable of doing VSS not that VSS is turned on for a particular backup.
There are two ways of telling if VSS is actually turned on during a backup.
The first is to look at the status output for a job, e.g.:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
Running Jobs:
JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
VSS Backup Job started: 23-Jul-05 13:25
Files Examined=75,021
Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
SDReadSeqNo=5 fd=352
-\end{verbatim}
+\end{lstlisting}
\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.
-The second way to know that the job was backed up with VSS is to look at the
+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:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
23-Jul 13:26 rufus-sd: Spooling data ...
23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
-\end{verbatim}
+\end{lstlisting}
\normalsize
In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
know that the problem is in your Windows machine and not with Bacula.
The FD hang problems were reported with {\bf MSDEwriter} when:
-\begin{itemize}
+\begin{bsysitemize}
\item a local firewall locked local access to the MSDE TCP port (MSDEwriter
-seems to use TCP/IP and not Named Pipes).
+seems to use TCP/IP and not Named Pipes).
\item msdtcs was installed to run under "localsystem": try running msdtcs
under networking account (instead of local system) (com+ seems to work
better with this configuration).
-\end{itemize}
+\end{bsysitemize}
\section{Windows Firewalls}
\index[general]{Firewalls!Windows}
\index[general]{Windows Firewalls}
-If you turn on the firewalling feature on Windows (default in WinXP SP2), you
-are likely to find that the Bacula ports are blocked and you cannot
-communicate to the other daemons. This can be deactivated through the {\bf
+If you turn on the firewalling feature on Windows (default in WinXP SP2),
+you are likely to find that the Bacula ports are blocked and you cannot
+communicate to the other daemons. This can be deactivated through the {\bf
Security Notification} dialog, which is apparently somewhere in the {\bf
-Security Center}. I don't have this on my computer, so I cannot give the exact
-details.
+Security Center}. I don't have this on my computer, so I cannot give the
+exact details.
-The command:
+The command:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
netsh firewall set opmode disable
-\end{verbatim}
+\end{lstlisting}
\normalsize
is purported to disable the firewall, but this command is not accepted on my
-WinXP Home machine.
+WinXP Home machine.
\section{Windows Port Usage}
\index[general]{Windows Port Usage}
\index[general]{Usage!Windows Port}
If you want to see if the File daemon has properly opened the port and is
-listening, you can enter the following command in a shell window:
+listening, you can enter the following command in a shell window:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
netstat -an | findstr 910[123]
-\end{verbatim}
+\end{lstlisting}
\normalsize
TopView is another program that has been recommend, but it is not a
-standard Win32 program, so you must find and download it from the Internet.
+standard Windows program, so you must find and download it from the Internet.
\section{Windows Disaster Recovery}
\index[general]{Recovery!Windows Disaster}
\index[general]{Windows Disaster Recovery}
-We don't currently have a good solution for disaster recovery on Windows as we
-do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
+Bacula Systems provides a special WinBMR (Windows Bare Metal Recovery)
+program that allows you to perform a bare metal disaster recovery
+of your system.
+
+If you do not have the WinBMR program, we do not have a good solution for
+disaster recovery on Windows. The main piece lacking, which is available
+in the Bacula Enterprise WinBMR, is a Windows boot floppy or a Windows boot
CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
-that could possibly work, but we have not investigated it. This means that
-until someone figures out the correct procedure, you must restore the OS from
-the installation disks, then you can load a Bacula client and restore files.
-Please don't count on using {\bf bextract} to extract files from your backup
-tapes during a disaster recovery unless you have backed up those files using
-the {\bf portable} option. {\bf bextract} does not run on Windows, and the
-normal way Bacula saves files using the Windows API prevents the files from
-being restored on a Unix machine. Once you have an operational Windows OS
-loaded, you can run the File daemon and restore your user files.
-
-Please see
-\ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
-suggestion, which looks very promising.
-
-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/}{http://www.nu2.nu/pebuilder/}.
+that could possibly work, but we have not investigated it. This means that
+until someone figures out the correct procedure, you must restore the OS
+from the installation disks, then you can load a Bacula client and restore
+files. Please don't count on using {\bf bextract} to extract files from
+your backup tapes during a disaster recovery unless you have backed up
+those files using the {\bf portable} option. {\bf bextract} does not run
+on Windows, and the normal way Bacula saves files using the Windows API
+prevents the files from being restored on a Unix machine. Once you have an
+operational Windows OS loaded, you can run the File daemon and restore your
+user files.
+
+\section{Windows FD Restrictions}
+\index[general]{Windows FD Restrictions}
+In recent versions of Windows, Microsoft has implemented
+Volume Mount Points, Encrypted Volumes, and Deduplicated Volumes.
+Current versions of the Windows File daemon support Volume Mount
+Points much like on Linux systems. That is you must explicitly
+add a File= line in your FileSet so that it will decend into the
+mount point. In addition, during the restore of a mount point, the
+mount point must already be defined.
+
+Current Bacula File daemons do not support Encrypted Volumes
+or Deduplicated Volumes.
+
\section{Windows Restore Problems}
\index[general]{Problems!Windows Restore}
\index[general]{Windows Restore Problems}
-Please see the
+Please see the
\ilink{Restore Chapter}{Windows} of this manual for problems
that you might encounter doing a restore.
section{Windows Backup Problems}
\index[general]{Problems!Windows Backup}
\index[general]{Windows Backup Problems}
-If during a Backup, you get the message:
+If during a Backup, you get the message:
{\bf ERR=Access is denied} and you are using the portable option,
you should try both adding both the non-portable (backup API) and
the Volume Shadow Copy options to your Director's conf file.
In the Options resource:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
portable = no
-\end{verbatim}
+\end{lstlisting}
\normalsize
In the FileSet resource:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
enablevss = yes
-\end{verbatim}
+\end{lstlisting}
\normalsize
In general, specifying these two options should allow you to backup
If you restore files backed up from Windows to an alternate directory,
Bacula may need to create some higher level directories that were not saved
-(or restored). In this case, the File daemon will create them under the SYSTEM
-account because that is the account that Bacula runs under as a service. As of
-version 1.32f-3, Bacula creates these files with full access permission.
-However, there may be cases where you have problems accessing those files even
-if you run as administrator. In principle, Microsoft supplies you with the way
-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/}{http://setacl.sourceforge.net/}.
+(or restored). In this case, the File daemon will create them under the
+SYSTEM account because that is the account that Bacula runs under as a
+service. As of version 1.32f-3, Bacula creates these files with full
+access permission. However, there may be cases where you have problems
+accessing those files even if you run as administrator. In principle,
+Microsoft supplies you with the way to cease the ownership of those files
+and thus change the permissions. However, a much better solution to
+working with and changing Windows permissions is the program {\bf SetACL},
+which can be found at
+\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,
+and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
then it is very unlikely that it will have sufficient permission to
-access all your files.
+access all your files.
Some users have experienced problems restoring files that participate in
the Active Directory. They also report that changing the userid under which
The following solution was provided by Dan Langille \lt{}dan at langille in
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
+they should apply to most Windows 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
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.
+as the {\bf Where:} value, this problem will arise.
The problem appears as a directory which cannot be browsed with Windows
Explorer. The symptoms include the following message when you try to click on
-that directory:
+that directory:
-\includegraphics{\idir access-is-denied.eps}
+\bsysimageN{access-is-denied}{Popup on permission issue}{fig:accessdenied}
If you encounter this message, the following steps will change the permissions
-to allow full access.
+to allow full access.
\begin{enumerate}
\item right click on the top level directory (in this example, {\bf c:/src})
- and select {\bf Properties}.
-\item click on the Security tab.
+ and select {\bf Properties}.
+\item click on the Security tab.
\item If the following message appears, you can ignore it, and click on {\bf
- OK}.
+ OK}.
-\includegraphics{\idir view-only.eps}
+\bsysimageH{view-only}{Message to ignore}{fig:messagetoignore}
-You should see something like this:
+You should see something like this:
-\includegraphics{\idir properties-security.eps}
-\item click on Advanced
-\item click on the Owner tab
+\bsysimageH{properties-security}{Properties security}{fig:propertiessecurity}
+\item click on Advanced
+\item click on the Owner tab
\item Change the owner to something other than the current owner (which is
- {\bf SYSTEM} in this example as shown below).
+ {\bf SYSTEM} in this example as shown below).
-\includegraphics{\idir properties-security-advanced-owner.eps}
-\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
+\bsysimageH{properties-security-advanced-owner}{Properties security advanced owner}{fig:propertiessecurityadvancedowner}
+\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
directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
- the directory permissions with permissions granting you Full Control?", click
-on Yes.
+ the directory permissions with permissions granting you Full Control?'', click
+on Yes.
-\includegraphics{\idir confirm.eps}
-\item Click on OK to close the Properties tab
+\bsysimageH{confirm}{Confirm granting permissions}{fig:confirmgrantingpermissions}
+\item Click on OK to close the Properties tab
\end{enumerate}
With the above procedure, you should now have full control over your restored
-directory.
+directory.
In addition to the above methods of changing permissions, there is a Microsoft
program named {\bf cacls} that can perform similar functions.
Note, most of this section applies to the older Windows OSes that
do not have VSS. On newer Windows OSes that have VSS, all files
including the System State will by default be properly backed
-up by Bacula.
-
-A suggestion by Damian Coutts using Microsoft's NTBackup utility in
-conjunction with Bacula should permit a full restore of any damaged system
-files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
-state prior to running a Bacula backup with the following command:
+up by Bacula. In addition, if you want special Backup of the
+System State (rather than just backup of everything) or backup
+of MSSQL or MS Exchange, you should consider the Bacula Systems
+VSS plugin (not to be confused with enabling VSS snapshots in the
+FileSet). The VSS plugin has explicit knowledge that allow
+you to make special backups of Microsoft System components that
+have VSS writers. Bacula Systems provides specific white papers
+on the components that are available for the VSS plugin.
+
+If you want to do this on your own, a suggestion by Damian Coutts using
+Microsoft's NTBackup utility in conjunction with Bacula should permit a
+full restore of any damaged system files on Win2K/XP. His suggestion is to
+do an NTBackup of the critical system state prior to running a Bacula
+backup with the following command:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
ntbackup backup systemstate /F c:\systemstate.bkf
-\end{verbatim}
+\end{lstlisting}
\normalsize
-The {\bf backup} is the command, the {\bf systemstate} says to backup only the
-system state and not all the user files, and the {\bf /F
+The {\bf backup} is the command, the {\bf systemstate} says to backup only
+the system state and not all the user files, and the {\bf /F
c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
-this file must then be saved and restored by Bacula.
+this file must then be saved and restored by Bacula.
-To restore the system state, you first reload a base operating system if the
-OS is damaged, otherwise, this is not necessary, then you would use Bacula to
-restore all the damaged or lost user's files and to recover the {\bf
-c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
-missing system files or registry problems, you run {\bf NTBackup} and {\bf
-catalogue} the system statefile, and then select it for restore. The
-documentation says you can't run a command line restore of the systemstate.
+To restore the system state, you first reload a base operating system if
+the OS is damaged, otherwise, this is not necessary, then you would use
+Bacula to restore all the damaged or lost user's files and to recover the
+{\bf c:\textbackslash{}systemstate.bkf} file. Finally if there are any
+damaged or missing system files or registry problems, you run {\bf
+NTBackup} and {\bf catalogue} the system statefile, and then select it for
+restore. The documentation says you can't run a command line restore of
+the systemstate.
To the best of my knowledge, this has not yet been tested. If you test it,
-please report your results to the Bacula email list.
+please report your results to the Bacula email list.
Note, Bacula uses VSS to backup and restore open files and
system files, but on older Windows machines such as WinNT and
hard drive and restore the backup. Then run the
recovery CD and run
-\begin{verbatim}
+\begin{lstlisting}
diskpart
select disk 0
select part 1
bootrec /rebuldbcd
bootrec /fixboot
bootrec /fixmbr
-\end{verbatim}
+\end{lstlisting}
\section{Considerations for Filename Specifications}
\index[general]{Windows!Considerations for Filename Specifications}
-Please see the
-\ilink{Director's Configuration chapter}{win32} of this manual
-for important considerations on how to specify Windows paths in Bacula FileSet
-Include and Exclude directives.
+Please see the \ilink{Director's Configuration chapter}{win32} of this
+manual for important considerations on how to specify Windows paths in
+Bacula FileSet Include and Exclude directives.
\index[general]{Unicode}
-Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
-As of that version, both {\bf bconsole} and {\bf bwx-console} support Windows
+The Window Bacula File daemon as well as
+{\bf bconsole} and {\bf bwx-console} support Windows
Unicode filenames. There may still be some problems with multiple byte
characters (e.g. Chinese, ...) where it is a two byte character but the
displayed character is not two characters wide.
-\index[general]{Win32 Path Length Restriction}
-Path/filenames longer than 260 characters (up to 32,000) are supported
-beginning with Bacula version 1.39.20. Older Bacula versions support
-only 260 character path/filenames.
+\index[general]{Windows Path Length Restriction}
+Path/filenames longer than 260 characters (up to 32,000) are supported.
-\section{Win32 Specific File daemon Command Line}
-\index[general]{Client!Win32 Specific File daemon Command Line Options}
-\index[general]{Win32 Specific File daemon Command Line Options}
+\section{Windows Specific File daemon Command Line}
+\index[general]{Client!Windows Specific File daemon Command Line Options}
+\index[general]{Windows Specific File daemon Command Line Options}
These options are not normally seen or used by the user, and are documented
here only for information purposes. At the current time, to change the default
options, you must either manually run {\bf Bacula} or you must manually edit
-the system registry and modify the appropriate entries.
+the system registry and modify the appropriate entries.
In order to avoid option clashes between the options necessary for {\bf
Bacula} to run on Windows and the standard Bacula options, all Windows
specific options are signaled with a forward slash character (/), while as
usual, the standard Bacula options are signaled with a minus (-), or a minus
-minus (\verb:--:). All the standard Bacula options can be used on the Windows
-version. In addition, the following Windows only options are implemented:
+minus (\lstinline:--:). All the standard Bacula options can be used on the Windows
+version. In addition, the following Windows only options are implemented:
\begin{description}
\item [/service ]
\index[fd]{/service}
- Start Bacula as a service
+ Start Bacula as a service
\item [/run ]
\index[fd]{/run}
- Run the Bacula application
+ Run the Bacula application
\item [/install ]
\index[fd]{/install}
- Install Bacula as a service in the system registry
+ Install Bacula as a service in the system registry
\item [/remove ]
\index[fd]{/remove}
- Uninstall Bacula from the system registry
+ Uninstall Bacula from the system registry
\item [/about ]
\index[fd]{/about}
- Show the Bacula about dialogue box
+ Show the Bacula about dialogue box
\item [/status ]
\index[fd]{/status}
- Show the Bacula status dialogue box
+ Show the Bacula status dialogue box
\item [/events ]
\index[fd]{/events}
- Show the Bacula events dialogue box (not yet implemented)
+ Show the Bacula events dialogue box (not yet implemented)
\item [/kill ]
\index[fd]{/kill}
- Stop any running {\bf Bacula}
+ Stop any running {\bf Bacula}
\item [/help ]
\index[fd]{/help}
- Show the Bacula help dialogue box
+ Show the Bacula help dialogue box
\end{description}
It is important to note that under normal circumstances the user should never
need to use these options as they are normally handled by the system
automatically once Bacula is installed. However, you may note these options in
-some of the .bat files that have been created for your use.
+some of the .bat files that have been created for your use.
\section{Shutting down Windows Systems}
\index[general]{Shutting down Windows Systems}
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}{http://www.apcupsd.com} or one from the
+take the shutdown program from the
+\elink{apcupsd project}{http://www.apcupsd.com} or one from the
\elink{Sysinternals project}
{http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.
projects / bacula / docs / blobdiff