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
+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
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
\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}
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
\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
\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}{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
+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}
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
+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/}.
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}
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
projects / bacula / docs / commitdiff