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
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
+\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-win32-5.xx.0.exe
+\includegraphics{nsis} bacula-win64-6.xx.0.exe
\item Once launched, the installer wizard will ask you if you want to install
Bacula.
-\bsysimageH{win32-welcome}{Win32 Client Setup Wizard}{fig:win32clientsetupwizard}
+\bsysimageH{win32-welcome}{Windows Client Setup Wizard}{fig:win32clientsetupwizard}
\item Next you will be asked to select the installation type.
-\bsysimageH{win32-installation-type}{Win32 Installation Type}{fig:win32installationtype}
+\bsysimageH{win32-installation-type}{Windows Installation Type}{fig:win32installationtype}
\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
\item While the various files are being loaded, you will see the following
dialog:
-\bsysimageH{win32-installing}{Win32 Install Progress}{fig:win32installing}
+\bsysimageH{win32-installing}{Windows Install Progress}{fig:win32installing}
\item Finally, the finish dialog will appear:
-\bsysimageH{win32-finish}{Win32 Client Setup Completed}{fig:win32setupcompleted}
+\bsysimageH{win32-finish}{Windows Client Setup Completed}{fig:win32setupcompleted}
\end{bsysitemize}
-That should complete the installation process. When the Bacula File Server is
+That should complete the installation process.
+
+\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
\raisebox{-2ex}{\includegraphics{tray-icon}}; right click on it and a menu will appear.\\
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
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.
-\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,
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
\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{lstlisting}
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
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
+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:
\LTXtable{\linewidth}{table_restoreportabilitystatus}
-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
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[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:
\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}
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
+(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
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}
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{lstlisting}
\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.
-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.
\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
projects / bacula / docs / blobdiff