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
+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
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
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:
\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
\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{Considerations for Filename Specifications}
\index[general]{Windows!Considerations for Filename Specifications}
projects / bacula / docs / blobdiff