speak of the Windows version of Bacula below, we are referring to
the File daemon (client) only.
-As of Bacula version 1.39.20 or greater, the installer is capable
-of installing not just the Client program, but also the Director
-and the Storage daemon and all the other programs that were
-previously available only on Unix systems. These additional
-programs, notably the Director and Storage daemon, have been partially
-tested, are reported to have some bugs, and still need to be documented.
-They are not yet supported, and we cannot currently accept or fix
-bug reports on them. Consequently, please test them carefully before putting
-them into a critical production environment.
-
-The Windows version of the Bacula File daemon has been tested on Win98, WinMe,
-WinNT, WinXP, Win2000, and Windows 2003 systems. We have coded to support
-Win95, but no longer have a system for testing. 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.
+The Windows version of the Bacula File daemon has been tested on WinXP,
+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 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}
+\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.
-If you have a previous version Bacula (1.39.20 or lower)
+If you have a previous version of Bacula
installed, you should stop the service, uninstall it, and remove
the Bacula installation directory possibly saving your
-bacula-fd.conf, bconsole.conf, and bwx-console.conf files
+bacula-fd.conf, bconsole.conf, and bat.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
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
+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
account and experienced permissions problems attempting to run
Bacula, so we don't recommend that option.
-\item Simply double click on the {\bf winbacula-1.xx.0.exe} NSIS install
- icon. The actual name of the icon will vary from one release version to
- another.
+\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} winbacula-1.xx.0.exe
+\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.
-\addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
+\addcontentsline{lof}{figure}{Windows Client Setup Wizard}
\includegraphics{\idir win32-welcome.eps}
\item Next you will be asked to select the installation type.
-\addcontentsline{lof}{figure}{Win32 Installation Type}
+\addcontentsline{lof}{figure}{Windows Installation Type}
\includegraphics{\idir win32-installation-type.eps}
location that you choose later. The components dialog looks like the
following:
-\addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
+\addcontentsline{lof}{figure}{Windows Component Selection Dialog}
\includegraphics{\idir win32-pkg.eps}
\index[general]{Upgrading}
not be displayed.
-\addcontentsline{lof}{figure}{Win32 Configure}
+\addcontentsline{lof}{figure}{Windows Configure}
\includegraphics{\idir win32-config.eps}
\item While the various files are being loaded, you will see the following
dialog:
- \addcontentsline{lof}{figure}{Win32 Install Progress}
+ \addcontentsline{lof}{figure}{Windows Install Progress}
\includegraphics{\idir win32-installing.eps}
\item Finally, the finish dialog will appear:
- \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
+ \addcontentsline{lof}{figure}{Windows Client Setup Completed}
\includegraphics{\idir win32-finish.eps}
\
\end{itemize}
-That should complete the installation process. When the Bacula File Server is
-ready to serve files, an icon \includegraphics{\idir idle.eps} 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}\\
-The {\bf Events} item is currently unimplemented, by selecting the {\bf
-Status} item, you can verify whether any jobs are running or not.
+That should complete the installation process.
-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},
-and if there is an error, the holes in the cassette icon will change to red
-\includegraphics{\idir error.eps}.
+\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.
+
+On Windows XP, when the Bacula File Server
+is ready to serve files, an icon \includegraphics{\idir idle.eps}
+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}\\ The {\bf Events} item is
+currently unimplemented, by selecting the {\bf 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}, and if there is an error, the holes in the cassette icon will
+change to red \includegraphics{\idir error.eps}.
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.
+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.
-\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
-installation. You can get to them by using:
-the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
+After installing Bacula and before running it, you should check the
+contents 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
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{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 do not support
+any of these special Volume formats.
+
+\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.
-\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,
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
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,
+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
\footnotesize
\begin{verbatim}
Start a DOS shell Window.
- c:\Program Files\bacula\bin\bacula-fd -t >out
+ c:\Program Files\bacula\bacula-fd -t >out
type out
\end{verbatim}
\normalsize
-The precise path to bacula-fd depends on where it is installed. The
-example above is the default used in 1.39.22 and later.
+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.
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
+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 on WinNT/2K/XP systems, the security and
+First, the advantages are that Windows systems, the security and
ownership information is now backed up. In addition, with the exception of
files in exclusive use by another program, Bacula can now access all system
files. This means that when you restore files, the security and ownership
-information will be restored on WinNT/2K/XP along with the data.
+information will be restored on Windows along with the data.
The disadvantage of the Windows backup API calls is that it produces
non-portable backups. That is files and their data that are backed up on
-WinNT using the native API calls (BackupRead/BackupWrite) cannot be
-restored on Win95/98/Me or Unix systems. In principle, a file backed up on
-WinNT can be restored on WinXP, but this remains to be seen in practice
-(not yet tested). Bacula should be able to read non-portable
-backups on any system and restore the data appropriately. However,
-on a system that does not have the BackupRead/BackupWrite calls (older
-Windows versions and all Unix/Linux machines), though the file data
-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.
+Windows using the native API calls (BackupRead/BackupWrite) cannot be
+directly restored on Linux or Unix systems. Bacula should be able to read
+non-portable backups on any system and restore the data appropriately.
+However, on a system that does not have the BackupRead/BackupWrite calls
+(older Windows versions and all Unix/Linux machines), though the file data
+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 WinNT/2K/XP system and restore it on a
-Unix/Win95/98/Me system, we have provided a special {\bf portable} option
+If you want to backup data on a Windows system and restore it on a
+Unix or Linux system, we have provided a special {\bf portable} option
that backs up the data in a portable fashion by using portable API calls.
See the \ilink{portable option}{portable} on the Include statement in a
FileSet resource in the Director's configuration chapter for the details on
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 systems, such as WinNT/2K/XP, you may have to
-reset the ownership of such restored files. Any file backed up on WinNT/2K/XP
-should in principle be able to be restored to a similar system (i.e.
-WinNT/2K/XP), however, I am unsure of the consequences if the owner
-information and accounts are not identical on both systems. Bacula will not
-let you restore files backed up on WinNT/2K/XP to any other system (i.e. Unix
-Win95/98/Me) if you have used the defaults.
+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
-WinNT/2K/XP specific security and ownership information will be lost.
+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:
\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} & {Error: Windows 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} & {Error: Windows 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} & {Error: Windows 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} & {Error: Windows data stream not supported. } \\
\hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
\hline {\ } & {\ } & {\ } \\
\hline {Linux} & {Linux} & {Works } \\
\\ \hline
\end{longtable}
-Note: with Bacula versions 1.39.x and later, non-portable Windows data can
-be restore to any machine.
-
+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
-RDBMS to produce consistent file copies. VSS aware applications are called
-VSS Writers, they register with the OS so that when Bacula wants to do a
-Snapshot, the OS will notify the register Writer programs, which may then
-create a consistent state in their application, which will be backed up.
-Examples for these writers are "MSDE" (Microsoft database
-engine), "Event Log Writer", "Registry Writer" plus 3rd
-party-writers. If you have a non-vss aware application (e.g.
-SQL Anywhere or probably MySQL), a shadow copy is still generated
-and the open files can be backed up, but there is no guarantee
-that the file is consistent.
+Microsoft added VSS to Windows XP and later systems. 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 RDBMS to produce consistent file copies. VSS aware applications are
+called VSS Writers, they register with the OS so that when Bacula wants to
+do a Snapshot, the OS will notify the register Writer programs, which may
+then create a consistent state in their application, which will be backed
+up. Examples for these writers are "MSDE" (Microsoft database engine),
+"Event Log Writer", "Registry Writer" plus 3rd party-writers. If you have
+a non-vss aware application (e.g. SQL Anywhere or probably MySQL), a
+shadow copy is still generated and the open files can be backed up, but
+there is no guarantee that the file is consistent.
Bacula produces a message from each of the registered writer programs
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
\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}
loaded, you can run the File daemon and restore your user files.
Please see
-\ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
+\ilink{ Disaster Recovery of Windows Systems}{Windows33} 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/}{\url{http://www.nu2.nu/pebuilder/}}.
+recovery system for Windows. This distribution can be found at
+\elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
\section{Windows Restore Problems}
\index[general]{Problems!Windows Restore}
\index[general]{Problems!Windows Ownership and Permissions}
\index[general]{Windows Ownership and Permissions Problems}
-If you restore files backed up from WinNT/XP/2K to an alternate directory,
+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/}{\url{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,
-then it is very unlikely that it will have sufficient permission to
-access all your files.
+(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, then
+it is very unlikely that it will have sufficient permission to 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}
\index[general]{State!Backing Up the WinNT/XP/2K System}
\index[general]{Backing Up the WinNT/XP/2K System State}
+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
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.
+Note, Bacula uses VSS to backup and restore open files and
+system files, but on older Windows machines such as WinNT and
+Win2000, VSS is not implemented by Microsoft so that you must
+use some special techniques to back them up as described
+above. On new Windows machines, Bacula will backup and restore
+all files including the system state providing you have
+VSS enabled in your Bacula FileSet (default).
+
+\section{Fixing the Windows Boot Record}
+\index[general]{Fixing the Windows Boot Record}
+\index[general]{Windows!Fixing the Boot Record}
+A tip from a user:
+An effective way to restore a Windows backup for
+those who do not purchase the bare metal restore
+capability is to install Windows on a different
+hard drive and restore the backup. Then run the
+recovery CD and run
+
+\begin{verbatim}
+diskpart
+ select disk 0
+ select part 1
+ active
+ exit
+
+bootrec /rebuldbcd
+bootrec /fixboot
+bootrec /fixmbr
+\end{verbatim}
+
+
\section{Considerations for Filename Specifications}
\index[general]{Windows!Considerations for Filename Specifications}
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}
+\index[general]{Windows 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.
-\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
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}.
projects / bacula / docs / blobdiff