4 \chapter{The Windows Version of Bacula}
6 \index[general]{Windows Version of Bacula}
8 At the current time only the File daemon or Client program has
9 been thouroughly tested on Windows and is suitable for a
10 production environment. As a consequence, when we
11 speak of the Windows version of Bacula below, we are referring to
12 the File daemon (client) only.
14 The Windows version of the Bacula File daemon has been tested on WinXP,
15 Win2000, Windows Server 2003, Windows Server 2008, Vista, and Windows 7
16 systems. The Windows version of Bacula is a native Win32 port, but there
17 are very few source code changes to the Unix code, which means that the
18 Windows version is for the most part running code that has long proved
19 stable on Unix systems. When running, it is perfectly integrated with
20 Windows and displays its icon in the system icon tray, and provides a
21 system tray menu to obtain additional information on how Bacula is running
22 (status and events dialog boxes). If so desired, it can also be stopped by
23 using the system tray menu, though this should normally never be necessary.
25 Once installed Bacula normally runs as a system service. This means that it is
26 immediately started by the operating system when the system is booted, and
27 runs in the background even if there is no user logged into the system.
29 \section{Win32 Installation}
31 \index[general]{Installation}
32 \index[general]{Win32!Installation}
34 Normally, you will install the Windows version of Bacula from the binaries.
35 This install is standard Windows .exe that runs an install wizard using the
36 NSIS Free Software installer, so if you have already installed Windows
37 software, it should be very familiar to you.
39 If you have a previous version of Bacula
40 installed, you should stop the service, uninstall it, and remove
41 the Bacula installation directory possibly saving your
42 bacula-fd.conf, bconsole.conf, and bat.conf files
43 for use with the new version you will install. The Uninstall
44 program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
45 We also recommend that you completely remove the directory
46 {\bf c:\textbackslash{}bacula}, because the current installer
47 uses a different directory structure (see below).
49 Providing you do not already have Bacula installed,
50 the installer installs the binaries and dlls in
51 c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
52 and the configuration files
53 in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
54 In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
55 will be created during the installation, and on that menu, you
56 will find items for editing the configuration files, displaying
57 the document, and starting bwx-console or bconsole.
60 Finally, proceed with the installation.
63 \item You must be logged in as Administrator to the local machine
64 to do a correct installation, if not, please do so before continuing.
65 Some users have attempted to install logged in as a domain administrator
66 account and experienced permissions problems attempting to run
67 Bacula, so we don't recommend that option.
69 \item Simply double click on the {\bf bacula-win32-5.xx.0.exe} NSIS install
70 icon. The actual name of the icon will vary from one release version to
73 \includegraphics{nsis} bacula-win32-5.xx.0.exe
75 \item Once launched, the installer wizard will ask you if you want to install
78 %\addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
79 %\includegraphics{\idir win32-welcome}
80 \bsysimageH{win32-welcome}{Win32 Client Setup Wizard}{fig:win32clientsetupwizard}
82 \item Next you will be asked to select the installation type.
84 %\addcontentsline{lof}{figure}{Win32 Installation Type}
85 %\includegraphics{\idir win32-installation-type}
86 \bsysimageH{win32-installation-type}{Win32 Installation Type}{fig:win32installationtype}
88 \item If you proceed, you will be asked to select the components to be
89 installed. You may install the Bacula program (Bacula File Service) and or
90 the documentation. Both will be installed in sub-directories of the install
91 location that you choose later. The components dialog looks like the
94 %\addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
95 %\includegraphics{\idir win32-pkg}
96 \bsysimageH{win32-pkg}{Win32 Component Selection Dialog}{fig:win32componentselectiondialog}
97 \index[general]{Upgrading}
99 \item If you are installing for the first time, you will be asked to
100 enter some very basic information about your configuration. If
101 you are not sure what to enter, or have previously saved configuration
102 files, you can put anything you want into the fields, then either
103 replace the configuration files later with the ones saved, or edit
106 If you are upgrading an existing installation, the following will
110 %\addcontentsline{lof}{figure}{Win32 Configure}
111 %\includegraphics{\idir win32-config}
112 \bsysimageH{win32-config}{Win32 Configure}{fig:win32configure}
114 \item While the various files are being loaded, you will see the following
117 % \addcontentsline{lof}{figure}{Win32 Install Progress}
118 % \includegraphics{\idir win32-installing}
119 \bsysimageH{win32-installing}{Win32 Install Progress}{fig:win32installing}
121 \item Finally, the finish dialog will appear:
123 % \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
124 % \includegraphics{\idir win32-finish}
125 \bsysimageH{win32-finish}{Win32 Client Setup Completed}{fig:win32setupcompleted}
129 That should complete the installation process. When the Bacula File Server is
130 ready to serve files, an icon \raisebox{-1ex}{\includegraphics{k7-idle}} representing a
131 cassette (or tape) will appear in the system tray
132 \raisebox{-2ex}{\includegraphics{tray-icon}}; right click on it and a menu will appear.\\
133 \bsysimageN{menu}{Menu on right click}{}\\
134 The {\bf Events} item is currently unimplemented, by selecting the {\bf
135 Status} item, you can verify whether any jobs are running or not.
137 When the Bacula File Server begins saving files, the color of the holes in the
138 cassette icon will change from white to green \raisebox{-1ex}{\includegraphics{k7-ok}},
139 and if there is an error, the holes in the cassette icon will change to red
140 \raisebox{-1ex}{\includegraphics{k7-error}}.
142 If you are using remote desktop connections between your Windows boxes, be
143 warned that that tray icon does not always appear. It will always be visible
144 when you log into the console, but the remote desktop may not display it.
146 \section{Post Win32 Installation}
147 \index[general]{Post Win32 Installation}
148 \index[general]{Win32!Post Installation}
150 After installing Bacula and before running it, you should check the contents
151 of the configuration files to ensure that they correspond to your
152 installation. You can get to them by using:
153 the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
155 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
156 is running as a process (not an Application) with User Name SYSTEM. If this is
157 not the case, you probably have not installed Bacula while running as
158 Administrator, and hence it will be unlikely that Bacula can access
159 all the system files.
161 \section{Uninstalling Bacula on Win32}
162 \index[general]{Win32!Uninstalling Bacula}
163 \index[general]{Uninstalling Bacula on Win32}
165 Once Bacula has been installed, it can be uninstalled using the standard
166 Windows Add/Remove Programs dialog found on the Control panel.
168 \section{Dealing with Win32 Problems}
170 \index[general]{Win32!Dealing with Problems}
171 \index[general]{Dealing with Win32 Problems}
173 Sometimes Win32 machines the File daemon may have very slow
174 backup transfer rates compared to other machines. To you might
175 try setting the Maximum Network Buffer Size to 32,768 in both the
176 File daemon and in the Storage daemon. The default size is larger,
177 and apparently some Windows ethernet controllers do not deal with
178 a larger network buffer size.
180 Many Windows ethernet drivers have a tendency to either run slowly
181 due to old broken firmware, or because they are running in half-duplex
182 mode. Please check with the ethernet card manufacturer for the latest
183 firmware and use whatever techniques are necessary to ensure that the
184 card is running in duplex.
186 If you are not using the portable option, and you have VSS
187 (Volume Shadow Copy) enabled in the Director, and you experience
188 problems with Bacula not being able to open files, it is most
189 likely that you are running an antivirus program that blocks
190 Bacula from doing certain operations. In this case, disable the
191 antivirus program and try another backup. If it succeeds, either
192 get a different (better) antivirus program or use something like
193 RunClientJobBefore/After to turn off the antivirus program while
194 the backup is running.
196 If turning off anti-virus software does not resolve your VSS
197 problems, you might have to turn on VSS debugging. The following
198 link describes how to do this:
199 \elink{http://support.microsoft.com/kb/887013/en-us}{http://support.microsoft.com/kb/887013/en-us}.
201 In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
202 is turned off by default. To turn it on, please see the following link:
203 \elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{
204 http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}
207 The most likely source of problems is authentication when the Director
208 attempts to connect to the File daemon that you installed. This can occur if
209 the names and the passwords defined in the File daemon's configuration file
210 {\bf bacula-fd.conf} file on
211 the Windows machine do not match with the names and the passwords in the
212 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
215 More specifically, the password found in the {\bf Client} resource in the
216 Director's configuration file must be the same as the password in the {\bf
217 Director} resource of the File daemon's configuration file. In addition, the
218 name of the {\bf Director} resource in the File daemon's configuration file
219 must be the same as the name in the {\bf Director} resource of the Director's
222 It is a bit hard to explain in words, but if you understand that a Director
223 normally has multiple Clients and a Client (or File daemon) may permit access
224 by multiple Directors, you can see that the names and the passwords on both
225 sides must match for proper authentication.
227 One user had serious problems with the configuration file until he realized
228 that the Unix end of line conventions were used and Bacula wanted them in
229 Windows format. This has not been confirmed though, and Bacula version 2.0.0
230 and above should now accept all end of line conventions (Win32,
233 Running Unix like programs on Windows machines is a bit frustrating because
234 the Windows command line shell (DOS Window) is rather primitive. As a
235 consequence, it is not generally possible to see the debug information and
236 certain error messages that Bacula prints. With a bit of work, however, it is
237 possible. When everything else fails and you want to {\bf see} what is going
238 on, try the following:
242 Start a DOS shell Window.
243 c:\Program Files\bacula\bacula-fd -t >out
248 The precise path to bacula-fd depends on where it is installed.
249 The {\bf -t} option will cause Bacula to read the configuration file, print
250 any error messages and then exit. the {\bf \gt{}} redirects the output to the
251 file named {\bf out}, which you can list with the {\bf type} command.
253 If something is going wrong later, or you want to run {\bf Bacula} with a
254 debug option, you might try starting it as:
258 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
262 In this case, Bacula will run until you explicitly stop it, which will give
263 you a chance to connect to it from your Unix/Linux server. In later versions
264 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
265 can write the output to a trace file {\bf bacula.trace} in the current
266 directory. To enable this, before running a job, use the console, and enter:
274 then run the job, and once you have terminated the File daemon, you will find
275 the debug output in the {\bf bacula.trace} file, which will probably be
276 located in the same directory as bacula-fd.exe.
278 In addition, you should look in the System Applications log on the Control
279 Panel to find any Windows errors that Bacula got during the startup process.
281 Finally, due to the above problems, when you turn on debugging, and specify
282 trace=1 on a setdebug command in the Console, Bacula will write the debug
283 information to the file {\bf bacula.trace} in the directory from which Bacula
286 If you are having problems with ClientRunBeforeJob scripts randomly dying,
287 it is possible that you have run into an Oracle bug. See bug number 622 in
288 the bugs.bacula.org database. The following information has been
289 provided by a user on this issue:
293 The information in this document applies to:
294 Oracle HTTP Server - Version: 9.0.4
295 Microsoft Windows Server 2003
297 When starting an OC4J instance, the System Clock runs faster, about 7
302 + This is caused by the Sun JVM bug 4500388, which states that "Calling
303 Thread.sleep() with a small argument affects the system clock". Although
304 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
306 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
308 + Also reported by Microsoft as "The system clock may run fast when you
309 use the ACPI power management timer as a high-resolution counter on Windows
310 2000-based computers" (See http://support.microsoft.com/?id=821893)
314 You may wish to start the daemon with debug mode on rather than doing it
315 using bconsole. To do so, edit the following registry key:
319 HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
323 using regedit, then add -dnn after the /service option, where nn represents
324 the debug level you want.
326 \label{Compatibility}
327 \section{Windows Compatibility Considerations}
328 \index[general]{Windows Compatibility Considerations}
329 \index[general]{Considerations!Windows Compatibility}
331 If you are not using the VSS (Volume Shadow Copy) option described in the
332 next section of this chapter, and if any applications are running during
333 the backup and they have files opened exclusively, Bacula will not be able
334 to backup those files, so be sure you close your applications (or tell your
335 users to close their applications) before the backup. Fortunately, most
336 Microsoft applications do not open files exclusively so that they can be
337 backed up. However, you will need to experiment. In any case, if Bacula
338 cannot open the file, it will print an error message, so you will always
339 know which files were not backed up. For version 1.37.25 and greater, see
340 the section below on Volume Shadow Copy Service that permits backing up any
343 During backup, Bacula doesn't know about the system registry, so you will
344 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
345 program specifically designed to make a copy or backup the registry.
347 In Bacula version 1.31 and later, we use Windows backup API calls by
348 default. Typical of Windows, programming these special BackupRead and
349 BackupWrite calls is a real nightmare of complications. The end result
350 gives some distinct advantages and some disadvantages.
352 First, the advantages are that Windows systems, the security and
353 ownership information is now backed up. In addition, with the exception of
354 files in exclusive use by another program, Bacula can now access all system
355 files. This means that when you restore files, the security and ownership
356 information will be restored on Windows along with the data.
358 The disadvantage of the Windows backup API calls is that it produces
359 non-portable backups. That is files and their data that are backed up on
360 Windows using the native API calls (BackupRead/BackupWrite) cannot be
361 directly restored on Linux or Unix systems. Bacula should be able to read
362 non-portable backups on any system and restore the data appropriately.
363 However, on a system that does not have the BackupRead/BackupWrite calls
364 (older Windows versions and all Unix/Linux machines), though the file data
365 can be restored, the Windows security and access control data will not be
366 restored. This means that a standard set of access permissions will be set
367 for such restored files.
370 As a default, Bacula backs up Windows systems using the Windows API calls.
371 If you want to backup data on a Windows system and restore it on a
372 Unix or Linux system, we have provided a special {\bf portable} option
373 that backs up the data in a portable fashion by using portable API calls.
374 See the \ilink{portable option}{portable} on the Include statement in a
375 FileSet resource in the Director's configuration chapter for the details on
376 setting this option. However, using the portable option means you may have
377 permissions problems accessing files, and none of the security and
378 ownership information will be backed up or restored. The file data can,
379 however, be restored on any system.
381 You should always be able to restore any file backed up on Unix or Win95/98/Me
382 to any other system. On some older Windows systems, you may have to
383 reset the ownership of such restored files.
385 Finally, if you specify the {\bf portable=yes} option on the files you back
386 up. Bacula will be able to restore them on any other system. However, any
387 Windows specific security and ownership information will be lost.
389 The following matrix will give you an idea of what you can expect. Thanks to
390 Marc Brueckner for doing the tests:
392 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
393 \begin{longtable}{|l|l|p{2.8in}|}
395 \multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
396 & \multicolumn{1}{c|}{\bf Results } \\
397 \hline {WinMe} & {WinMe} & {Works } \\
398 \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
399 \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
400 \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
401 \hline {\ } & {\ } & {\ } \\
402 \hline {WinXP} & {WinXP} & {Works } \\
403 \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
405 \hline {WinXP} & {WinMe} & {Error: Win32 data stream not supported. } \\
406 \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
407 \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
408 \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
409 \hline {\ } & {\ } & {\ } \\
410 \hline {WinNT} & {WinNT} & {Works } \\
411 \hline {WinNT} & {WinXP} & {Works } \\
412 \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
413 \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
414 \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
415 \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
416 \hline {\ } & {\ } & {\ } \\
417 \hline {Linux} & {Linux} & {Works } \\
418 \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
419 \hline {Linux} & {WinMe} & {Works } \\
420 \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
424 Note: with Bacula versions 1.39.x and later, non-portable Windows data can
425 be restore to any machine.
429 \section{Volume Shadow Copy Service}
430 \index[general]{Volume Shadow Copy Service}
432 In version 1.37.30 and greater, you can turn on Microsoft's Volume
433 Shadow Copy Service (VSS).
435 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
436 a backup-solution for Windows, this is an extremely important step. VSS
437 allows Bacula to backup open files and even to interact with applications like
438 RDBMS to produce consistent file copies. VSS aware applications are called
439 VSS Writers, they register with the OS so that when Bacula wants to do a
440 Snapshot, the OS will notify the register Writer programs, which may then
441 create a consistent state in their application, which will be backed up.
442 Examples for these writers are "MSDE" (Microsoft database
443 engine), "Event Log Writer", "Registry Writer" plus 3rd
444 party-writers. If you have a non-vss aware application (e.g.
445 SQL Anywhere or probably MySQL), a shadow copy is still generated
446 and the open files can be backed up, but there is no guarantee
447 that the file is consistent.
449 Bacula produces a message from each of the registered writer programs
450 when it is doing a VSS backup so you know which ones are correctly backed
453 Bacula supports VSS on both Windows 2003 and Windows XP.
454 Technically Bacula creates a shadow copy as soon as the backup process
455 starts. It does then backup all files from the shadow copy and destroys the
456 shadow copy after the backup process. Please have in mind, that VSS
457 creates a snapshot and thus backs up the system at the state it had
458 when starting the backup. It will disregard file changes which occur during
461 VSS can be turned on by placing an
463 \index[dir]{Enable VSS}
464 \index[general]{Enable VSS}
469 in your FileSet resource.
471 The VSS aware File daemon has the letters VSS on the signon line that
472 it produces when contacted by the console. For example:
474 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
476 the VSS is shown in the line above. This only means that the File daemon
477 is capable of doing VSS not that VSS is turned on for a particular backup.
478 There are two ways of telling if VSS is actually turned on during a backup.
479 The first is to look at the status output for a job, e.g.:
483 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
484 VSS Backup Job started: 23-Jul-05 13:25
485 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
486 Files Examined=75,021
487 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
491 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
492 This means that VSS is enabled for that job. If VSS is not enabled, it will
493 simply show "Backup Job started ..." without the letters VSS.
495 The second way to know that the job was backed up with VSS is to look at the
496 Job Report, which will look something like the following:
499 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
500 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
501 23-Jul 13:26 rufus-sd: Spooling data ...
502 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
503 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
504 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
505 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
506 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
509 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
510 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
511 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
512 that you will get a consistent snapshot of the data handled by that writer.
514 \section{VSS Problems}
515 \index[general]{Problems!VSS}
516 \index[fd] {Problems!VSS}
517 \index[general]{VSS Problems}
518 \index[fd]{VSS Problems}
520 If you are experiencing problems such as VSS hanging on MSDE, first try
521 running {\bf vssadmin} to check for problems, then try running {\bf
522 ntbackup} which also uses VSS to see if it has similar problems. If so, you
523 know that the problem is in your Windows machine and not with Bacula.
525 The FD hang problems were reported with {\bf MSDEwriter} when:
527 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
528 seems to use TCP/IP and not Named Pipes).
529 \item msdtcs was installed to run under "localsystem": try running msdtcs
530 under networking account (instead of local system) (com+ seems to work
531 better with this configuration).
535 \section{Windows Firewalls}
536 \index[general]{Firewalls!Windows}
537 \index[general]{Windows Firewalls}
539 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
540 are likely to find that the Bacula ports are blocked and you cannot
541 communicate to the other daemons. This can be deactivated through the {\bf
542 Security Notification} dialog, which is apparently somewhere in the {\bf
543 Security Center}. I don't have this on my computer, so I cannot give the exact
550 netsh firewall set opmode disable
554 is purported to disable the firewall, but this command is not accepted on my
557 \section{Windows Port Usage}
558 \index[general]{Windows Port Usage}
559 \index[general]{Usage!Windows Port}
561 If you want to see if the File daemon has properly opened the port and is
562 listening, you can enter the following command in a shell window:
566 netstat -an | findstr 910[123]
570 TopView is another program that has been recommend, but it is not a
571 standard Win32 program, so you must find and download it from the Internet.
573 \section{Windows Disaster Recovery}
574 \index[general]{Recovery!Windows Disaster}
575 \index[general]{Windows Disaster Recovery}
577 We don't currently have a good solution for disaster recovery on Windows as we
578 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
579 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
580 that could possibly work, but we have not investigated it. This means that
581 until someone figures out the correct procedure, you must restore the OS from
582 the installation disks, then you can load a Bacula client and restore files.
583 Please don't count on using {\bf bextract} to extract files from your backup
584 tapes during a disaster recovery unless you have backed up those files using
585 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
586 normal way Bacula saves files using the Windows API prevents the files from
587 being restored on a Unix machine. Once you have an operational Windows OS
588 loaded, you can run the File daemon and restore your user files.
591 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
592 suggestion, which looks very promising.
594 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
595 Environment) Boot-CD, may be just what is needed to build a complete disaster
596 recovery system for Win32. This distribution can be found at
597 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
599 \section{Windows Restore Problems}
600 \index[general]{Problems!Windows Restore}
601 \index[general]{Windows Restore Problems}
603 \ilink{Restore Chapter}{Windows} of this manual for problems
604 that you might encounter doing a restore.
606 section{Windows Backup Problems}
607 \index[general]{Problems!Windows Backup}
608 \index[general]{Windows Backup Problems}
609 If during a Backup, you get the message:
610 {\bf ERR=Access is denied} and you are using the portable option,
611 you should try both adding both the non-portable (backup API) and
612 the Volume Shadow Copy options to your Director's conf file.
614 In the Options resource:
621 In the FileSet resource:
628 In general, specifying these two options should allow you to backup
629 any file on a Windows system. However, in some cases, if users
630 have allowed to have full control of their folders, even system programs
631 such a Bacula can be locked out. In this case, you must identify
632 which folders or files are creating the problem and do the following:
635 \item Grant ownership of the file/folder to the Administrators group,
636 with the option to replace the owner on all child objects.
637 \item Grant full control permissions to the Administrators group,
638 and change the user's group to only have Modify permission to
639 the file/folder and all child objects.
642 Thanks to Georger Araujo for the above information.
644 \section{Windows Ownership and Permissions Problems}
645 \index[general]{Problems!Windows Ownership and Permissions}
646 \index[general]{Windows Ownership and Permissions Problems}
648 If you restore files backed up from Windows to an alternate directory,
649 Bacula may need to create some higher level directories that were not saved
650 (or restored). In this case, the File daemon will create them under the SYSTEM
651 account because that is the account that Bacula runs under as a service. As of
652 version 1.32f-3, Bacula creates these files with full access permission.
653 However, there may be cases where you have problems accessing those files even
654 if you run as administrator. In principle, Microsoft supplies you with the way
655 to cease the ownership of those files and thus change the permissions.
656 However, a much better solution to working with and changing Win32 permissions
657 is the program {\bf SetACL}, which can be found at
658 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
660 If you have not installed Bacula while running as Administrator
661 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
662 then it is very unlikely that it will have sufficient permission to
663 access all your files.
665 Some users have experienced problems restoring files that participate in
666 the Active Directory. They also report that changing the userid under which
667 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
671 \section{Manually resetting the Permissions}
672 \index[general]{Manually resetting the Permissions}
673 \index[general]{Permissions!Manually resetting the}
675 The following solution was provided by Dan Langille \lt{}dan at langille in
676 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
677 they should apply to most Win32 platforms. The procedure outlines how to deal
678 with a problem which arises when a restore creates a top-level new directory.
679 In this example, "top-level" means something like {\bf
680 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
681 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
682 as the {\bf Where:} value, this problem will arise.
684 The problem appears as a directory which cannot be browsed with Windows
685 Explorer. The symptoms include the following message when you try to click on
688 \bsysimageN{access-is-denied}{Popup on permission issue}{fig:accessdenied}
690 If you encounter this message, the following steps will change the permissions
691 to allow full access.
694 \item right click on the top level directory (in this example, {\bf c:/src})
695 and select {\bf Properties}.
696 \item click on the Security tab.
697 \item If the following message appears, you can ignore it, and click on {\bf
700 \bsysimageH{view-only}{Message to ignore}{fig:messagetoignore}
701 %\includegraphics{\idir view-only}
703 You should see something like this:
705 \bsysimageH{properties-security}{Properties security}{fig:propertiessecurity}
706 %\includegraphics{\idir properties-security}
707 \item click on Advanced
708 \item click on the Owner tab
709 \item Change the owner to something other than the current owner (which is
710 {\bf SYSTEM} in this example as shown below).
712 \bsysimageH{properties-security-advanced-owner}{Properties security advanced owner}{fig:propertiessecurityadvancedowner}
713 %\includegraphics{\idir properties-security-advanced-owner}
714 \item ensure the ``Replace owner on subcontainers and objects'' box is
717 \item When the message ``You do not have permission to read the contents of
718 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
719 the directory permissions with permissions granting you Full Control?'', click
722 \bsysimageH{confirm}{Confirm granting permissions}{fig:confirmgrantingpermissions}
723 %\includegraphics{\idir confirm}
724 \item Click on OK to close the Properties tab
727 With the above procedure, you should now have full control over your restored
730 In addition to the above methods of changing permissions, there is a Microsoft
731 program named {\bf cacls} that can perform similar functions.
733 \section{Backing Up the WinNT/XP/2K System State}
734 \index[general]{State!Backing Up the WinNT/XP/2K System}
735 \index[general]{Backing Up the WinNT/XP/2K System State}
737 Note, most of this section applies to the older Windows OSes that
738 do not have VSS. On newer Windows OSes that have VSS, all files
739 including the System State will by default be properly backed
742 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
743 conjunction with Bacula should permit a full restore of any damaged system
744 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
745 state prior to running a Bacula backup with the following command:
749 ntbackup backup systemstate /F c:\systemstate.bkf
753 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
754 system state and not all the user files, and the {\bf /F
755 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
756 this file must then be saved and restored by Bacula.
758 To restore the system state, you first reload a base operating system if the
759 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
760 restore all the damaged or lost user's files and to recover the {\bf
761 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
762 missing system files or registry problems, you run {\bf NTBackup} and {\bf
763 catalogue} the system statefile, and then select it for restore. The
764 documentation says you can't run a command line restore of the systemstate.
766 To the best of my knowledge, this has not yet been tested. If you test it,
767 please report your results to the Bacula email list.
769 Note, Bacula uses VSS to backup and restore open files and
770 system files, but on older Windows machines such as WinNT and
771 Win2000, VSS is not implemented by Microsoft so that you must
772 use some special techniques to back them up as described
773 above. On new Windows machines, Bacula will backup and restore
774 all files including the system state providing you have
775 VSS enabled in your Bacula FileSet (default).
777 \section{Fixing the Windows Boot Record}
778 \index[general]{Fixing the Windows Boot Record}
779 \index[general]{Windows!Fixing the Boot Record}
781 An effective way to restore a Windows backup for
782 those who do not purchase the bare metal restore
783 capability is to install Windows on a different
784 hard drive and restore the backup. Then run the
800 \section{Considerations for Filename Specifications}
801 \index[general]{Windows!Considerations for Filename Specifications}
804 \ilink{Director's Configuration chapter}{win32} of this manual
805 for important considerations on how to specify Windows paths in Bacula FileSet
806 Include and Exclude directives.
808 \index[general]{Unicode}
809 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
810 As of that version, both {\bf bconsole} and {\bf bwx-console} support Windows
811 Unicode filenames. There may still be some problems with multiple byte
812 characters (e.g. Chinese, ...) where it is a two byte character but the
813 displayed character is not two characters wide.
815 \index[general]{Win32 Path Length Restriction}
816 Path/filenames longer than 260 characters (up to 32,000) are supported
817 beginning with Bacula version 1.39.20. Older Bacula versions support
818 only 260 character path/filenames.
820 \section{Win32 Specific File daemon Command Line}
821 \index[general]{Client!Win32 Specific File daemon Command Line Options}
822 \index[general]{Win32 Specific File daemon Command Line Options}
824 These options are not normally seen or used by the user, and are documented
825 here only for information purposes. At the current time, to change the default
826 options, you must either manually run {\bf Bacula} or you must manually edit
827 the system registry and modify the appropriate entries.
829 In order to avoid option clashes between the options necessary for {\bf
830 Bacula} to run on Windows and the standard Bacula options, all Windows
831 specific options are signaled with a forward slash character (/), while as
832 usual, the standard Bacula options are signaled with a minus (-), or a minus
833 minus (\lstinline:--:). All the standard Bacula options can be used on the Windows
834 version. In addition, the following Windows only options are implemented:
840 Start Bacula as a service
844 Run the Bacula application
848 Install Bacula as a service in the system registry
852 Uninstall Bacula from the system registry
856 Show the Bacula about dialogue box
860 Show the Bacula status dialogue box
864 Show the Bacula events dialogue box (not yet implemented)
868 Stop any running {\bf Bacula}
872 Show the Bacula help dialogue box
875 It is important to note that under normal circumstances the user should never
876 need to use these options as they are normally handled by the system
877 automatically once Bacula is installed. However, you may note these options in
878 some of the .bat files that have been created for your use.
880 \section{Shutting down Windows Systems}
881 \index[general]{Shutting down Windows Systems}
882 \index[general]{Systems!Shutting down Windows}
884 Some users like to shutdown their Windows machines after a backup using a
885 Client Run After Job directive. If you want to do something similar, you might
886 take the shutdown program from the
887 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
888 \elink{Sysinternals project}
889 {http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.