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 As of Bacula version 1.39.20 or greater, the installer is capable
15 of installing not just the Client program, but also the Director
16 and the Storage daemon and all the other programs that were
17 previously available only on Unix systems. These additional
18 programs, notably the Director and Storage daemon, have been partially
19 tested, are reported to have some bugs, and still need to be documented.
20 They are not yet supported, and we cannot currently accept or fix
21 bug reports on them. Consequently, please test them carefully before putting
22 them into a critical production environment.
24 The Windows version of the Bacula File daemon has been tested on Win98, WinMe,
25 WinNT, WinXP, Win2000, and Windows 2003 systems. We have coded to support
26 Win95, but no longer have a system for testing. The Windows version of
27 Bacula is a native Win32 port, but there are very few source code changes
28 to the Unix code, which means that the Windows version is for the most part
29 running code that has long proved stable on Unix systems. When running, it
30 is perfectly integrated with Windows and displays its icon in the system
31 icon tray, and provides a system tray menu to obtain additional information
32 on how Bacula is running (status and events dialog boxes). If so desired,
33 it can also be stopped by using the system tray menu, though this should
34 normally never be necessary.
36 Once installed Bacula normally runs as a system service. This means that it is
37 immediately started by the operating system when the system is booted, and
38 runs in the background even if there is no user logged into the system.
40 \section{Win32 Installation}
42 \index[general]{Installation}
43 \index[general]{Win32!Installation}
45 Normally, you will install the Windows version of Bacula from the binaries.
46 This install is standard Windows .exe that runs an install wizard using the
47 NSIS Free Software installer, so if you have already installed Windows
48 software, it should be very familiar to you.
50 If you have a previous version Bacula (1.39.20 or lower)
51 installed, you should stop the service, uninstall it, and remove
52 the Bacula installation directory possibly saving your
53 bacula-fd.conf, bconsole.conf, and bwx-console.conf files
54 for use with the new version you will install. The Uninstall
55 program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
56 We also recommend that you completely remove the directory
57 {\bf c:\textbackslash{}bacula}, because the current installer
58 uses a different directory structure (see below).
60 Providing you do not already have Bacula installed,
61 the new installer (1.39.22 and later) installs the binaries and dlls in
62 c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
63 and the configuration files
64 in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
65 In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
66 will be created during the installation, and on that menu, you
67 will find items for editing the configuration files, displaying
68 the document, and starting bwx-console or bconsole.
71 Finally, proceed with the installation.
74 \item You must be logged in as Administrator to the local machine
75 to do a correct installation, if not, please do so before continuing.
76 Some users have attempted to install logged in as a domain administrator
77 account and experienced permissions problems attempting to run
78 Bacula, so we don't recommend that option.
80 \item Simply double click on the {\bf winbacula-1.xx.0.exe} NSIS install
81 icon. The actual name of the icon will vary from one release version to
84 \includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe
86 \item Once launched, the installer wizard will ask you if you want to install
89 \addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
90 \includegraphics{./win32-welcome.eps}
92 \item Next you will be asked to select the installation type.
94 \addcontentsline{lof}{figure}{Win32 Installation Type}
95 \includegraphics{./win32-installation-type.eps}
98 \item If you proceed, you will be asked to select the components to be
99 installed. You may install the Bacula program (Bacula File Service) and or
100 the documentation. Both will be installed in sub-directories of the install
101 location that you choose later. The components dialog looks like the
104 \addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
105 \includegraphics{./win32-pkg.eps}
106 \index[general]{Upgrading}
108 \item If you are installing for the first time, you will be asked to
109 enter some very basic information about your configuration. If
110 you are not sure what to enter, or have previously saved configuration
111 files, you can put anything you want into the fields, then either
112 replace the configuration files later with the ones saved, or edit
115 If you are upgrading an existing installation, the following will
119 \addcontentsline{lof}{figure}{Win32 Configure}
120 \includegraphics{./win32-config.eps}
122 \item While the various files are being loaded, you will see the following
125 \addcontentsline{lof}{figure}{Win32 Install Progress}
126 \includegraphics{./win32-installing.eps}
129 \item Finally, the finish dialog will appear:
131 \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
132 \includegraphics{./win32-finish.eps}
137 That should complete the installation process. When the Bacula File Server is
138 ready to serve files, an icon \includegraphics{./idle.eps} representing a
139 cassette (or tape) will appear in the system tray
140 \includegraphics{./tray-icon.eps}; right click on it and a menu will appear.\\
141 \includegraphics{./menu.eps}\\
142 The {\bf Events} item is currently unimplemented, by selecting the {\bf
143 Status} item, you can verify whether any jobs are running or not.
145 When the Bacula File Server begins saving files, the color of the holes in the
146 cassette icon will change from white to green \includegraphics{./running.eps},
147 and if there is an error, the holes in the cassette icon will change to red
148 \includegraphics{./error.eps}.
150 If you are using remote desktop connections between your Windows boxes, be
151 warned that that tray icon does not always appear. It will always be visible
152 when you log into the console, but the remote desktop may not display it.
154 \section{Post Win32 Installation}
155 \index[general]{Post Win32 Installation}
156 \index[general]{Win32!Post Installation}
158 After installing Bacula and before running it, you should check the contents
159 of the configuration files to ensure that they correspond to your
160 installation. You can get to them by using:
161 the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
163 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
164 is running as a process (not an Application) with User Name SYSTEM. If this is
165 not the case, you probably have not installed Bacula while running as
166 Administrator, and hence it will be unlikely that Bacula can access
167 all the system files.
169 \section{Uninstalling Bacula on Win32}
170 \index[general]{Win32!Uninstalling Bacula}
171 \index[general]{Uninstalling Bacula on Win32}
173 Once Bacula has been installed, it can be uninstalled using the standard
174 Windows Add/Remove Programs dialog found on the Control panel.
176 \section{Dealing with Win32 Problems}
178 \index[general]{Win32!Dealing with Problems}
179 \index[general]{Dealing with Win32 Problems}
181 Sometimes Win32 machines the File daemon may have very slow
182 backup transfer rates compared to other machines. To you might
183 try setting the Maximum Network Buffer Size to 32,768 in both the
184 File daemon and in the Storage daemon. The default size is larger,
185 and apparently some Windows ethernet controllers do not deal with
186 a larger network buffer size.
188 Many Windows ethernet drivers have a tendency to either run slowly
189 due to old broken firmware, or because they are running in half-duplex
190 mode. Please check with the ethernet card manufacturer for the latest
191 firmware and use whatever techniques are necessary to ensure that the
192 card is running in duplex.
194 If you are not using the portable option, and you have VSS
195 (Volume Shadow Copy) enabled in the Director, and you experience
196 problems with Bacula not being able to open files, it is most
197 likely that you are running an antivirus program that blocks
198 Bacula from doing certain operations. In this case, disable the
199 antivirus program and try another backup. If it succeeds, either
200 get a different (better) antivirus program or use something like
201 RunClientJobBefore/After to turn off the antivirus program while
202 the backup is running.
204 If turning off anti-virus software does not resolve your VSS
205 problems, you might have to turn on VSS debugging. The following
206 link describes how to do this:
207 \elink{http://support.microsoft.com/kb/887013/en-us}{\url{http://support.microsoft.com/kb/887013/en-us}}.
209 In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
210 is turned off by default. To turn it on, please see the following link:
211 \elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{\url{
212 http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}}
215 The most likely source of problems is authentication when the Director
216 attempts to connect to the File daemon that you installed. This can occur if
217 the names and the passwords defined in the File daemon's configuration file
218 {\bf bacula-fd.conf} file on
219 the Windows machine do not match with the names and the passwords in the
220 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
223 More specifically, the password found in the {\bf Client} resource in the
224 Director's configuration file must be the same as the password in the {\bf
225 Director} resource of the File daemon's configuration file. In addition, the
226 name of the {\bf Director} resource in the File daemon's configuration file
227 must be the same as the name in the {\bf Director} resource of the Director's
230 It is a bit hard to explain in words, but if you understand that a Director
231 normally has multiple Clients and a Client (or File daemon) may permit access
232 by multiple Directors, you can see that the names and the passwords on both
233 sides must match for proper authentication.
235 One user had serious problems with the configuration file until he realized
236 that the Unix end of line conventions were used and Bacula wanted them in
237 Windows format. This has not been confirmed though, and Bacula version 2.0.0
238 and above should now accept all end of line conventions (Win32,
241 Running Unix like programs on Windows machines is a bit frustrating because
242 the Windows command line shell (DOS Window) is rather primitive. As a
243 consequence, it is not generally possible to see the debug information and
244 certain error messages that Bacula prints. With a bit of work, however, it is
245 possible. When everything else fails and you want to {\bf see} what is going
246 on, try the following:
250 Start a DOS shell Window.
251 c:\Program Files\bacula\bin\bacula-fd -t >out
256 The precise path to bacula-fd depends on where it is installed. The
257 example above is the default used in 1.39.22 and later.
258 The {\bf -t} option will cause Bacula to read the configuration file, print
259 any error messages and then exit. the {\bf \gt{}} redirects the output to the
260 file named {\bf out}, which you can list with the {\bf type} command.
262 If something is going wrong later, or you want to run {\bf Bacula} with a
263 debug option, you might try starting it as:
267 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
271 In this case, Bacula will run until you explicitly stop it, which will give
272 you a chance to connect to it from your Unix/Linux server. In later versions
273 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
274 can write the output to a trace file {\bf bacula.trace} in the current
275 directory. To enable this, before running a job, use the console, and enter:
283 then run the job, and once you have terminated the File daemon, you will find
284 the debug output in the {\bf bacula.trace} file, which will probably be
285 located in the same directory as bacula-fd.exe.
287 In addition, you should look in the System Applications log on the Control
288 Panel to find any Windows errors that Bacula got during the startup process.
290 Finally, due to the above problems, when you turn on debugging, and specify
291 trace=1 on a setdebug command in the Console, Bacula will write the debug
292 information to the file {\bf bacula.trace} in the directory from which Bacula
295 If you are having problems with ClientRunBeforeJob scripts randomly dying,
296 it is possible that you have run into an Oracle bug. See bug number 622 in
297 the bugs.bacula.org database. The following information has been
298 provided by a user on this issue:
302 The information in this document applies to:
303 Oracle HTTP Server - Version: 9.0.4
304 Microsoft Windows Server 2003
306 When starting an OC4J instance, the System Clock runs faster, about 7
311 + This is caused by the Sun JVM bug 4500388, which states that "Calling
312 Thread.sleep() with a small argument affects the system clock". Although
313 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
315 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
317 + Also reported by Microsoft as "The system clock may run fast when you
318 use the ACPI power management timer as a high-resolution counter on Windows
319 2000-based computers" (See http://support.microsoft.com/?id=821893)
323 You may wish to start the daemon with debug mode on rather than doing it
324 using bconsole. To do so, edit the following registry key:
328 HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
332 using regedit, then add -dnn after the /service option, where nn represents
333 the debug level you want.
335 \label{Compatibility}
336 \section{Windows Compatibility Considerations}
337 \index[general]{Windows Compatibility Considerations}
338 \index[general]{Considerations!Windows Compatibility}
340 If you are not using the VSS (Volume Shadow Copy) option described in the
341 next section of this chapter, and if any applications are running during
342 the backup and they have files opened exclusively, Bacula will not be able
343 to backup those files, so be sure you close your applications (or tell your
344 users to close their applications) before the backup. Fortunately, most
345 Microsoft applications do not open files exclusively so that they can be
346 backed up. However, you will need to experiment. In any case, if Bacula
347 cannot open the file, it will print an error message, so you will always
348 know which files were not backed up. For version 1.37.25 and greater, see
349 the section below on Volume Shadow Copy Service that permits backing up any
352 During backup, Bacula doesn't know about the system registry, so you will
353 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
354 program specifically designed to make a copy or backup the registry.
356 In Bacula version 1.31 and later, we use Windows backup API calls by
357 default. Typical of Windows, programming these special BackupRead and
358 BackupWrite calls is a real nightmare of complications. The end result
359 gives some distinct advantages and some disadvantages.
361 First, the advantages are that on WinNT/2K/XP systems, the security and
362 ownership information is now backed up. In addition, with the exception of
363 files in exclusive use by another program, Bacula can now access all system
364 files. This means that when you restore files, the security and ownership
365 information will be restored on WinNT/2K/XP along with the data.
367 The disadvantage of the Windows backup API calls is that it produces
368 non-portable backups. That is files and their data that are backed up on
369 WinNT using the native API calls (BackupRead/BackupWrite) cannot be
370 restored on Win95/98/Me or Unix systems. In principle, a file backed up on
371 WinNT can be restored on WinXP, but this remains to be seen in practice
372 (not yet tested). In addition, the stand-alone tools such as {\bf bls} and
373 {\bf bextract} cannot be used to retrieve the data for those files because
374 those tools are not available on Windows. All restores must use the Bacula
375 {\bf restore} command. As of Bacula 1.39.x, thanks to Thorsten Engel, this
376 restriction is removed, and Bacula should be able to read non-portable
377 backups on any system and restore the data appropriately. However,
378 on a system that does not have the BackupRead/BackupWrite calls (older
379 Windows versions and all Unix/Linux machines), though the file data
380 can be restored, the Windows security and access control data will not be restored.
381 This means that a standard set of access permissions will be set for
385 As a default, Bacula backs up Windows systems using the Windows API calls.
386 If you want to backup data on a WinNT/2K/XP system and restore it on a
387 Unix/Win95/98/Me system, we have provided a special {\bf portable} option
388 that backs up the data in a portable fashion by using portable API calls.
389 See the \ilink{portable option}{portable} on the Include statement in a
390 FileSet resource in the Director's configuration chapter for the details on
391 setting this option. However, using the portable option means you may have
392 permissions problems accessing files, and none of the security and
393 ownership information will be backed up or restored. The file data can,
394 however, be restored on any system.
396 You should always be able to restore any file backed up on Unix or Win95/98/Me
397 to any other system. On some systems, such as WinNT/2K/XP, you may have to
398 reset the ownership of such restored files. Any file backed up on WinNT/2K/XP
399 should in principle be able to be restored to a similar system (i.e.
400 WinNT/2K/XP), however, I am unsure of the consequences if the owner
401 information and accounts are not identical on both systems. Bacula will not
402 let you restore files backed up on WinNT/2K/XP to any other system (i.e. Unix
403 Win95/98/Me) if you have used the defaults.
405 Finally, if you specify the {\bf portable=yes} option on the files you back
406 up. Bacula will be able to restore them on any other system. However, any
407 WinNT/2K/XP specific security and ownership information will be lost.
409 The following matrix will give you an idea of what you can expect. Thanks to
410 Marc Brueckner for doing the tests:
412 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
413 \begin{longtable}{|l|l|p{2.8in}|}
415 \multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
416 & \multicolumn{1}{c|}{\bf Results } \\
417 \hline {WinMe} & {WinMe} & {Works } \\
418 \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
419 \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
420 \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
421 \hline {\ } & {\ } & {\ } \\
422 \hline {WinXP} & {WinXP} & {Works } \\
423 \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
425 \hline {WinXP} & {WinMe} & {Error: Win32 data stream not supported. } \\
426 \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
427 \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
428 \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
429 \hline {\ } & {\ } & {\ } \\
430 \hline {WinNT} & {WinNT} & {Works } \\
431 \hline {WinNT} & {WinXP} & {Works } \\
432 \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
433 \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
434 \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
435 \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
436 \hline {\ } & {\ } & {\ } \\
437 \hline {Linux} & {Linux} & {Works } \\
438 \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
439 \hline {Linux} & {WinMe} & {Works } \\
440 \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
444 Note: with Bacula versions 1.39.x and later, non-portable Windows data can
445 be restore to any machine.
449 \section{Volume Shadow Copy Service}
450 \index[general]{Volume Shadow Copy Service}
452 In version 1.37.30 and greater, you can turn on Microsoft's Volume
453 Shadow Copy Service (VSS).
455 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
456 a backup-solution for Windows, this is an extremely important step. VSS
457 allows Bacula to backup open files and even to interact with applications like
458 RDBMS to produce consistent file copies. VSS aware applications are called
459 VSS Writers, they register with the OS so that when Bacula wants to do a
460 Snapshot, the OS will notify the register Writer programs, which may then
461 create a consistent state in their application, which will be backed up.
462 Examples for these writers are "MSDE" (Microsoft database
463 engine), "Event Log Writer", "Registry Writer" plus 3rd
464 party-writers. If you have a non-vss aware application (e.g.
465 SQL Anywhere or probably MySQL), a shadow copy is still generated
466 and the open files can be backed up, but there is no guarantee
467 that the file is consistent.
469 Bacula produces a message from each of the registered writer programs
470 when it is doing a VSS backup so you know which ones are correctly backed
473 Bacula supports VSS on both Windows 2003 and Windows XP.
474 Technically Bacula creates a shadow copy as soon as the backup process
475 starts. It does then backup all files from the shadow copy and destroys the
476 shadow copy after the backup process. Please have in mind, that VSS
477 creates a snapshot and thus backs up the system at the state it had
478 when starting the backup. It will disregard file changes which occur during
481 VSS can be turned on by placing an
483 \index[dir]{Enable VSS}
484 \index[general]{Enable VSS}
489 in your FileSet resource.
491 The VSS aware File daemon has the letters VSS on the signon line that
492 it produces when contacted by the console. For example:
494 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
496 the VSS is shown in the line above. This only means that the File daemon
497 is capable of doing VSS not that VSS is turned on for a particular backup.
498 There are two ways of telling if VSS is actually turned on during a backup.
499 The first is to look at the status output for a job, e.g.:
503 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
504 VSS Backup Job started: 23-Jul-05 13:25
505 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
506 Files Examined=75,021
507 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
511 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
512 This means that VSS is enabled for that job. If VSS is not enabled, it will
513 simply show "Backup Job started ..." without the letters VSS.
515 The second way to know that the job was backed up with VSS is to look at the
516 Job Report, which will look something like the following:
519 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
520 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
521 23-Jul 13:26 rufus-sd: Spooling data ...
522 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
523 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
524 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
525 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
526 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
529 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
530 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
531 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
532 that you will get a consistent snapshot of the data handled by that writer.
534 \section{VSS Problems}
535 \index[general]{Problems!VSS}
536 \index[fd] {Problems!VSS}
537 \index[general]{VSS Problems}
538 \index[fd]{VSS Problems}
540 If you are experiencing problems such as VSS hanging on MSDE, first try
541 running {\bf vssadmin} to check for problems, then try running {\bf
542 ntbackup} which also uses VSS to see if it has similar problems. If so, you
543 know that the problem is in your Windows machine and not with Bacula.
545 The FD hang problems were reported with {\bf MSDEwriter} when:
547 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
548 seems to use TCP/IP and not Named Pipes).
549 \item msdtcs was installed to run under "localsystem": try running msdtcs
550 under networking account (instead of local system) (com+ seems to work
551 better with this configuration).
555 \section{Windows Firewalls}
556 \index[general]{Firewalls!Windows}
557 \index[general]{Windows Firewalls}
559 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
560 are likely to find that the Bacula ports are blocked and you cannot
561 communicate to the other daemons. This can be deactivated through the {\bf
562 Security Notification} dialog, which is apparently somewhere in the {\bf
563 Security Center}. I don't have this on my computer, so I cannot give the exact
570 netsh firewall set opmode disable
574 is purported to disable the firewall, but this command is not accepted on my
577 \section{Windows Port Usage}
578 \index[general]{Windows Port Usage}
579 \index[general]{Usage!Windows Port}
581 If you want to see if the File daemon has properly opened the port and is
582 listening, you can enter the following command in a shell window:
586 netstat -an | findstr 910[123]
590 TopView is another program that has been recommend, but it is not a
591 standard Win32 program, so you must find and download it from the Internet.
593 \section{Windows Disaster Recovery}
594 \index[general]{Recovery!Windows Disaster}
595 \index[general]{Windows Disaster Recovery}
597 We don't currently have a good solution for disaster recovery on Windows as we
598 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
599 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
600 that could possibly work, but we have not investigated it. This means that
601 until someone figures out the correct procedure, you must restore the OS from
602 the installation disks, then you can load a Bacula client and restore files.
603 Please don't count on using {\bf bextract} to extract files from your backup
604 tapes during a disaster recovery unless you have backed up those files using
605 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
606 normal way Bacula saves files using the Windows API prevents the files from
607 being restored on a Unix machine. Once you have an operational Windows OS
608 loaded, you can run the File daemon and restore your user files.
611 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
612 suggestion, which looks very promising.
614 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
615 Environment) Boot-CD, may be just what is needed to build a complete disaster
616 recovery system for Win32. This distribution can be found at
617 \elink{http://www.nu2.nu/pebuilder/}{\url{http://www.nu2.nu/pebuilder/}}.
619 \section{Windows Restore Problems}
620 \index[general]{Problems!Windows Restore}
621 \index[general]{Windows Restore Problems}
623 \ilink{Restore Chapter}{Windows} of this manual for problems
624 that you might encounter doing a restore.
626 section{Windows Backup Problems}
627 \index[general]{Problems!Windows Backup}
628 \index[general]{Windows Backup Problems}
629 If during a Backup, you get the message:
630 {\bf ERR=Access is denied} and you are using the portable option,
631 you should try both adding both the non-portable (backup API) and
632 the Volume Shadow Copy options to your Director's conf file.
634 In the Options resource:
641 In the FileSet resource:
648 In general, specifying these two options should allow you to backup
649 any file on a Windows system. However, in some cases, if users
650 have allowed to have full control of their folders, even system programs
651 such a Bacula can be locked out. In this case, you must identify
652 which folders or files are creating the problem and do the following:
655 \item Grant ownership of the file/folder to the Administrators group,
656 with the option to replace the owner on all child objects.
657 \item Grant full control permissions to the Administrators group,
658 and change the user's group to only have Modify permission to
659 the file/folder and all child objects.
662 Thanks to Georger Araujo for the above information.
664 \section{Windows Ownership and Permissions Problems}
665 \index[general]{Problems!Windows Ownership and Permissions}
666 \index[general]{Windows Ownership and Permissions Problems}
668 If you restore files backed up from WinNT/XP/2K to an alternate directory,
669 Bacula may need to create some higher level directories that were not saved
670 (or restored). In this case, the File daemon will create them under the SYSTEM
671 account because that is the account that Bacula runs under as a service. As of
672 version 1.32f-3, Bacula creates these files with full access permission.
673 However, there may be cases where you have problems accessing those files even
674 if you run as administrator. In principle, Microsoft supplies you with the way
675 to cease the ownership of those files and thus change the permissions.
676 However, a much better solution to working with and changing Win32 permissions
677 is the program {\bf SetACL}, which can be found at
678 \elink{http://setacl.sourceforge.net/}{\url{http://setacl.sourceforge.net/}}.
680 If you have not installed Bacula while running as Administrator
681 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
682 then it is very unlikely that it will have sufficient permission to
683 access all your files.
685 Some users have experienced problems restoring files that participate in
686 the Active Directory. They also report that changing the userid under which
687 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
691 \section{Manually resetting the Permissions}
692 \index[general]{Manually resetting the Permissions}
693 \index[general]{Permissions!Manually resetting the}
695 The following solution was provided by Dan Langille \lt{}dan at langille in
696 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
697 they should apply to most Win32 platforms. The procedure outlines how to deal
698 with a problem which arises when a restore creates a top-level new directory.
699 In this example, "top-level" means something like {\bf
700 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
701 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
702 as the {\bf Where:} value, this problem will arise.
704 The problem appears as a directory which cannot be browsed with Windows
705 Explorer. The symptoms include the following message when you try to click on
708 \includegraphics{./access-is-denied.eps}
710 If you encounter this message, the following steps will change the permissions
711 to allow full access.
714 \item right click on the top level directory (in this example, {\bf c:/src})
715 and select {\bf Properties}.
716 \item click on the Security tab.
717 \item If the following message appears, you can ignore it, and click on {\bf
720 \includegraphics{./view-only.eps}
722 You should see something like this:
724 \includegraphics{./properties-security.eps}
725 \item click on Advanced
726 \item click on the Owner tab
727 \item Change the owner to something other than the current owner (which is
728 {\bf SYSTEM} in this example as shown below).
730 \includegraphics{./properties-security-advanced-owner.eps}
731 \item ensure the "Replace owner on subcontainers and objects" box is
734 \item When the message "You do not have permission to read the contents of
735 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
736 the directory permissions with permissions granting you Full Control?", click
739 \includegraphics{./confirm.eps}
740 \item Click on OK to close the Properties tab
743 With the above procedure, you should now have full control over your restored
746 In addition to the above methods of changing permissions, there is a Microsoft
747 program named {\bf cacls} that can perform similar functions.
749 \section{Backing Up the WinNT/XP/2K System State}
750 \index[general]{State!Backing Up the WinNT/XP/2K System}
751 \index[general]{Backing Up the WinNT/XP/2K System State}
753 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
754 conjunction with Bacula should permit a full restore of any damaged system
755 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
756 state prior to running a Bacula backup with the following command:
760 ntbackup backup systemstate /F c:\systemstate.bkf
764 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
765 system state and not all the user files, and the {\bf /F
766 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
767 this file must then be saved and restored by Bacula.
769 To restore the system state, you first reload a base operating system if the
770 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
771 restore all the damaged or lost user's files and to recover the {\bf
772 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
773 missing system files or registry problems, you run {\bf NTBackup} and {\bf
774 catalogue} the system statefile, and then select it for restore. The
775 documentation says you can't run a command line restore of the systemstate.
777 To the best of my knowledge, this has not yet been tested. If you test it,
778 please report your results to the Bacula email list.
780 \section{Considerations for Filename Specifications}
781 \index[general]{Windows!Considerations for Filename Specifications}
784 \ilink{Director's Configuration chapter}{win32} of this manual
785 for important considerations on how to specify Windows paths in Bacula FileSet
786 Include and Exclude directives.
788 \index[general]{Unicode}
789 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
790 As of that version, both {\bf bconsole} and {\bf bwx-console} support Windows
791 Unicode filenames. There may still be some problems with multiple byte
792 characters (e.g. Chinese, ...) where it is a two byte character but the
793 displayed character is not two characters wide.
795 \index[general]{Win32 Path Length Restriction}
796 Path/filenames longer than 260 characters (up to 32,000) are supported
797 beginning with Bacula version 1.39.20. Older Bacula versions support
798 only 260 character path/filenames.
800 \section{Win32 Specific File daemon Command Line}
801 \index[general]{Client!Win32 Specific File daemon Command Line Options}
802 \index[general]{Win32 Specific File daemon Command Line Options}
804 These options are not normally seen or used by the user, and are documented
805 here only for information purposes. At the current time, to change the default
806 options, you must either manually run {\bf Bacula} or you must manually edit
807 the system registry and modify the appropriate entries.
809 In order to avoid option clashes between the options necessary for {\bf
810 Bacula} to run on Windows and the standard Bacula options, all Windows
811 specific options are signaled with a forward slash character (/), while as
812 usual, the standard Bacula options are signaled with a minus (-), or a minus
813 minus (\verb:--:). All the standard Bacula options can be used on the Windows
814 version. In addition, the following Windows only options are implemented:
820 Start Bacula as a service
824 Run the Bacula application
828 Install Bacula as a service in the system registry
832 Uninstall Bacula from the system registry
836 Show the Bacula about dialogue box
840 Show the Bacula status dialogue box
844 Show the Bacula events dialogue box (not yet implemented)
848 Stop any running {\bf Bacula}
852 Show the Bacula help dialogue box
855 It is important to note that under normal circumstances the user should never
856 need to use these options as they are normally handled by the system
857 automatically once Bacula is installed. However, you may note these options in
858 some of the .bat files that have been created for your use.
860 \section{Shutting down Windows Systems}
861 \index[general]{Shutting down Windows Systems}
862 \index[general]{Systems!Shutting down Windows}
864 Some users like to shutdown their Windows machines after a backup using a
865 Client Run After Job directive. If you want to do something similar, you might
866 take the shutdown program from the
867 \elink{apcupsd project}{\url{http://www.apcupsd.com}} or one from the
868 \elink{Sysinternals project}
869 {\url{http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}}.