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.
-\subsubsection*{Win32 Installation}
+\subsection*{Win32 Installation}
\label{installation}
\index[general]{Installation }
\index[general]{Win32!Installation }
-\addcontentsline{toc}{subsubsection}{Win32 Installation}
+\addcontentsline{toc}{subsection}{Win32 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
to edit the bacula-fd.conf file, and if you respond with yes, it will be
opened in notepad.
\
-\item Then the installer will ask if wish to install Bacula as a service. You
+\item Then the installer will ask if you wish to install Bacula as a service. You
should always choose to do so:
\addcontentsline{lof}{figure}{Win32 Client Service Selection}
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.
-\subsubsection*{Post Win32 Installation}
+\subsection*{Post Win32 Installation}
\index[general]{Post Win32 Installation }
\index[general]{Win32!Post Installation }
-\addcontentsline{toc}{subsubsection}{Post Win32 Installation}
+\addcontentsline{toc}{subsection}{Post Win32 Installation}
After installing Bacula and before running it, you should check the contents
of {\bf
c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} to
ensure that it corresponds to your configuration.
-\subsubsection*{Uninstalling Bacula on Win32}
+\subsection*{Uninstalling Bacula on Win32}
\index[general]{Win32!Uninstalling Bacula }
\index[general]{Uninstalling Bacula on Win32 }
-\addcontentsline{toc}{subsubsection}{Uninstalling Bacula on Win32}
+\addcontentsline{toc}{subsection}{Uninstalling Bacula on Win32}
Once Bacula has been installed, it can be uninstalled using the standard
Windows Add/Remove Programs dialog found on the Control panel.
-\subsubsection*{Dealing with Win32 Problems}
+\subsection*{Dealing with Win32 Problems}
\label{problems}
\index[general]{Win32!Dealing with Problems }
\index[general]{Dealing with Win32 Problems }
-\addcontentsline{toc}{subsubsection}{Dealing with Win32 Problems}
+\addcontentsline{toc}{subsection}{Dealing with Win32 Problems}
The most likely source of problems is authentication when the Director
attempts to connect to the File daemon that you installed. This can occur if
\label{Compatibility}
-\subsubsection*{Windows Compatibility Considerations}
+\subsection*{Windows Compatibility Considerations}
\index[general]{Windows Compatibility Considerations }
\index[general]{Considerations!Windows Compatibility }
-\addcontentsline{toc}{subsubsection}{Windows Compatibility Considerations}
+\addcontentsline{toc}{subsection}{Windows Compatibility Considerations}
If any applications are running during the backup and they have files
opened exclusively, Bacula will not be able to backup those files, so be
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
-that backups the data in a portable fashion by using portable API calls.
+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
setting this option. However, using the portable option means you may have
\end{longtable}
-\subsubsection*{Windows Firewalls}
+\subsection*{Windows Firewalls}
\index[general]{Firewalls!Windows }
\index[general]{Windows Firewalls }
-\addcontentsline{toc}{subsubsection}{Windows Firewalls}
+\addcontentsline{toc}{subsection}{Windows Firewalls}
-If you turn on the firewalling feature on Windows (default in WinXP SR2), you
+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
-communicated to the other daemons. This can be deactivated through the {\bf
+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.
is purported to disable the firewall, but this command is not accepted on my
WinXP Home machine.
-\subsubsection*{Windows Port Usage}
+\subsection*{Windows Port Usage}
\index[general]{Windows Port Usage }
\index[general]{Usage!Windows Port }
-\addcontentsline{toc}{subsubsection}{Windows Port Usage}
+\addcontentsline{toc}{subsection}{Windows Port Usage}
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:
\end{verbatim}
\normalsize
-\subsubsection*{Windows Disaster Recovery}
+\subsection*{Windows Disaster Recovery}
\index[general]{Recovery!Windows Disaster }
\index[general]{Windows Disaster Recovery }
-\addcontentsline{toc}{subsubsection}{Windows Disaster Recovery}
+\addcontentsline{toc}{subsection}{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
recovery system for Win32. This distribution can be found at
\elink{http://www.nu2.nu/pebuilder/ }{http://www.nu2.nu/pebuilder/}.
-\subsubsection*{Windows Ownership and Permissions Problems}
+\subsection*{Windows Restore Problems}
+\index[general]{Problems!Windows Restore}
+\index[general]{Windows Restore Problems}
+\addcontentsline{toc}{subsection}{Windows Restore Problems}
+Please see the
+\ilink{Restore Chapter}{Windows} of this manual for problems
+that you might encounter doing a restore.
+
+
+\subsection*{Windows Ownership and Permissions Problems}
\index[general]{Problems!Windows Ownership and Permissions }
\index[general]{Windows Ownership and Permissions Problems }
-\addcontentsline{toc}{subsubsection}{Windows Ownership and Permissions
+\addcontentsline{toc}{subsection}{Windows Ownership and Permissions
Problems}
If you restore files backed up from WinNT/XP/2K to an alternate directory,
is the program {\bf SetACL}, which can be found at
\elink{http://setacl.sourceforge.net/ }{http://setacl.sourceforge.net/}.
-\subsubsection*{Manually resetting the Permissions}
+Some users have experienced problems restoring files that participate in
+the Active Directory. They also report that changing the userid under which
+Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
+the problem.
+
+
+\subsection*{Manually resetting the Permissions}
\index[general]{Manually resetting the Permissions }
\index[general]{Permissions!Manually resetting the }
-\addcontentsline{toc}{subsubsection}{Manually resetting the Permissions}
+\addcontentsline{toc}{subsection}{Manually resetting the Permissions}
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
With the above procedure, you should now have full control over your restored
directory.
-\subsubsection*{Backing Up the WinNT/XP/2K System State}
+\subsection*{Backing Up the WinNT/XP/2K System State}
\index[general]{State!Backing Up the WinNT/XP/2K System }
\index[general]{Backing Up the WinNT/XP/2K System State }
-\addcontentsline{toc}{subsubsection}{Backing Up the WinNT/XP/2K System State}
+\addcontentsline{toc}{subsection}{Backing Up the WinNT/XP/2K System State}
A suggestion by Damian Coutts using Microsoft's NTBackup utility in
conjunction with Bacula should permit a full restore of any damaged 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.
-\subsubsection*{Windows Considerations for Filename Specifications}
+\subsection*{Windows Considerations for Filename Specifications}
\index[general]{Specifications!Windows Considerations for Filename }
\index[general]{Windows Considerations for Filename Specifications }
-\addcontentsline{toc}{subsubsection}{Windows Considerations for Filename
+\addcontentsline{toc}{subsection}{Windows Considerations for Filename
Specifications}
Please see the
for important considerations on how to specify Windows paths in Bacula FileSet
Include and Exclude directives.
-\subsubsection*{Command Line Options Specific to the Bacula Windows File
+\subsection*{Command Line Options Specific to the Bacula Windows File
Daemon (Client)}
\index[general]{Client!Command Line Options Specific to the Bacula Windows
File Daemon }
\index[general]{Command Line Options Specific to the Bacula Windows File
Daemon (Client) }
-\addcontentsline{toc}{subsubsection}{Command Line Options Specific to the
+\addcontentsline{toc}{subsection}{Command Line Options Specific to the
Bacula Windows File Daemon (Client)}
These options are not normally seen or used by the user, and are documented
automatically once Bacula is installed. However, you may note these options in
some of the .bat files that have been created for your use.
-\subsubsection*{Shutting down Windows Systems}
+\subsection*{Shutting down Windows Systems}
\index[general]{Shutting down Windows Systems }
\index[general]{Systems!Shutting down Windows }
-\addcontentsline{toc}{subsubsection}{Shutting down Windows Systems}
+\addcontentsline{toc}{subsection}{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
projects / bacula / docs / blobdiff