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, Windows 7,
16 and Windows 8 systems. The Windows version of Bacula is a native Windows 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{Windows Installation}
31 \index[general]{Installation}
32 \index[general]{Windows!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-7.xx.0.exe} NSIS install
70 icon. The actual name of the icon will vary from one release version to
73 \includegraphics{win32-nsis} bacula-win32-7.xx.0.exe
75 \item Once launched, the installer wizard will ask you if you want to install
78 \addcontentsline{lof}{figure}{Windows Client Setup Wizard}
80 \includegraphics[width=0.8\linewidth]{win32-welcome}
83 \item Next you will be asked to select the installation type.
85 \addcontentsline{lof}{figure}{Windows Installation Type}
87 \includegraphics[width=0.8\linewidth]{win32-installation-type}
90 \item If you proceed, you will be asked to select the components to be
91 installed. You may install the Bacula program (Bacula File Service) and or
92 the documentation. Both will be installed in sub-directories of the install
93 location that you choose later. The components dialog looks like the
96 \addcontentsline{lof}{figure}{Windows Component Selection Dialog}
98 \includegraphics[width=0.8\linewidth]{win32-pkg}
101 \index[general]{Upgrading}
103 \item If you are installing for the first time, you will be asked to
104 enter some very basic information about your configuration. If
105 you are not sure what to enter, or have previously saved configuration
106 files, you can put anything you want into the fields, then either
107 replace the configuration files later with the ones saved, or edit
110 If you are upgrading an existing installation, the following will
114 \addcontentsline{lof}{figure}{Windows Configure}
116 \includegraphics[width=0.8\linewidth]{win32-config}
119 \item While the various files are being loaded, you will see the following
122 \addcontentsline{lof}{figure}{Windows Install Progress}
124 \includegraphics[width=0.8\linewidth]{win32-installing}
127 \item Finally, the finish dialog will appear:
129 \addcontentsline{lof}{figure}{Windows Client Setup Completed}
131 \includegraphics[width=0.8\linewidth]{win32-finish}
136 That should complete the installation process. When the Bacula File Server is
137 ready to serve files, an icon \includegraphics{idle} representing a
138 cassette (or tape) will appear in the system tray
139 \includegraphics{tray-icon}; right click on it and a menu will appear.\\
140 \includegraphics{menu}\\
141 The {\bf Events} item is currently unimplemented, by selecting the {\bf
142 Status} item, you can verify whether any jobs are running or not.
144 When the Bacula File Server begins saving files, the color of the holes in the
145 cassette icon will change from white to green \includegraphics{running},
146 and if there is an error, the holes in the cassette icon will change to red
147 \includegraphics{error}.
149 If you are using remote desktop connections between your Windows boxes, be
150 warned that that tray icon does not always appear. It will always be visible
151 when you log into the console, but the remote desktop may not display it.
153 \section{Post Windows Installation}
154 \index[general]{Post Windows Installation}
155 \index[general]{Windows!Post Installation}
157 After installing Bacula and before running it, you should check the contents
158 of the configuration files to ensure that they correspond to your
159 installation. You can get to them by using:
160 the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
162 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
163 is running as a process (not an Application) with User Name SYSTEM. If this is
164 not the case, you probably have not installed Bacula while running as
165 Administrator, and hence it will be unlikely that Bacula can access
166 all the system files.
168 \section{Uninstalling Bacula on Windows}
169 \index[general]{Windows!Uninstalling Bacula}
170 \index[general]{Uninstalling Bacula on Windows}
172 Once Bacula has been installed, it can be uninstalled using the standard
173 Windows Add/Remove Programs dialog found on the Control panel.
175 \section{Dealing with Windows Problems}
177 \index[general]{Windows!Dealing with Problems}
178 \index[general]{Dealing with Windows Problems}
180 Sometimes Windows machines the File daemon may have very slow
181 backup transfer rates compared to other machines. To you might
182 try setting the Maximum Network Buffer Size to 32,768 in both the
183 File daemon and in the Storage daemon. The default size is larger,
184 and apparently some Windows ethernet controllers do not deal with
185 a larger network buffer size.
187 Many Windows ethernet drivers have a tendency to either run slowly
188 due to old broken firmware, or because they are running in half-duplex
189 mode. Please check with the ethernet card manufacturer for the latest
190 firmware and use whatever techniques are necessary to ensure that the
191 card is running in duplex.
193 If you are not using the portable option, and you have VSS
194 (Volume Shadow Copy) enabled in the Director, and you experience
195 problems with Bacula not being able to open files, it is most
196 likely that you are running an antivirus program that blocks
197 Bacula from doing certain operations. In this case, disable the
198 antivirus program and try another backup. If it succeeds, either
199 get a different (better) antivirus program or use something like
200 RunClientJobBefore/After to turn off the antivirus program while
201 the backup is running.
203 If turning off anti-virus software does not resolve your VSS
204 problems, you might have to turn on VSS debugging. The following
205 link describes how to do this:
206 \elink{http://support.microsoft.com/kb/887013/en-us}{http://support.microsoft.com/kb/887013/en-us}.
208 In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
209 is turned off by default. To turn it on, please see the following link:
210 \elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}
213 The most likely source of problems is authentication when the Director
214 attempts to connect to the File daemon that you installed. This can occur if
215 the names and the passwords defined in the File daemon's configuration file
216 {\bf bacula-fd.conf} file on
217 the Windows machine do not match with the names and the passwords in the
218 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
221 More specifically, the password found in the {\bf Client} resource in the
222 Director's configuration file must be the same as the password in the {\bf
223 Director} resource of the File daemon's configuration file. In addition, the
224 name of the {\bf Director} resource in the File daemon's configuration file
225 must be the same as the name in the {\bf Director} resource of the Director's
228 It is a bit hard to explain in words, but if you understand that a Director
229 normally has multiple Clients and a Client (or File daemon) may permit access
230 by multiple Directors, you can see that the names and the passwords on both
231 sides must match for proper authentication.
233 One user had serious problems with the configuration file until he realized
234 that the Unix end of line conventions were used and Bacula wanted them in
235 Windows format. This has not been confirmed though, and Bacula version 2.0.0
236 and above should now accept all end of line conventions (Windows,
239 Running Unix like programs on Windows machines is a bit frustrating because
240 the Windows command line shell (DOS Window) is rather primitive. As a
241 consequence, it is not generally possible to see the debug information and
242 certain error messages that Bacula prints. With a bit of work, however, it is
243 possible. When everything else fails and you want to {\bf see} what is going
244 on, try the following:
248 Start a DOS shell Window.
249 c:\Program Files\bacula\bacula-fd -t >out
254 The precise path to bacula-fd depends on where it is installed.
255 The {\bf -t} option will cause Bacula to read the configuration file, print
256 any error messages and then exit. the {\bf \gt{}} redirects the output to the
257 file named {\bf out}, which you can list with the {\bf type} command.
259 If something is going wrong later, or you want to run {\bf Bacula} with a
260 debug option, you might try starting it as:
264 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
268 In this case, Bacula will run until you explicitly stop it, which will give
269 you a chance to connect to it from your Unix/Linux server. In later versions
270 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
271 can write the output to a trace file {\bf bacula.trace} in the current
272 directory. To enable this, before running a job, use the console, and enter:
280 then run the job, and once you have terminated the File daemon, you will find
281 the debug output in the {\bf bacula.trace} file, which will probably be
282 located in the same directory as bacula-fd.exe.
284 In addition, you should look in the System Applications log on the Control
285 Panel to find any Windows errors that Bacula got during the startup process.
287 Finally, due to the above problems, when you turn on debugging, and specify
288 trace=1 on a setdebug command in the Console, Bacula will write the debug
289 information to the file {\bf bacula.trace} in the directory from which Bacula
292 If you are having problems with ClientRunBeforeJob scripts randomly dying,
293 it is possible that you have run into an Oracle bug. See bug number 622 in
294 the bugs.bacula.org database. The following information has been
295 provided by a user on this issue:
299 The information in this document applies to:
300 Oracle HTTP Server - Version: 9.0.4
301 Microsoft Windows Server 2003
303 When starting an OC4J instance, the System Clock runs faster, about 7
308 + This is caused by the Sun JVM bug 4500388, which states that "Calling
309 Thread.sleep() with a small argument affects the system clock". Although
310 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
312 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
314 + Also reported by Microsoft as "The system clock may run fast when you
315 use the ACPI power management timer as a high-resolution counter on Windows
316 2000-based computers" (See http://support.microsoft.com/?id=821893)
320 You may wish to start the daemon with debug mode on rather than doing it
321 using bconsole. To do so, edit the following registry key:
325 HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
329 using regedit, then add -dnn after the /service option, where nn represents
330 the debug level you want.
332 \label{Compatibility}
333 \section{Windows Compatibility Considerations}
334 \index[general]{Windows Compatibility Considerations}
335 \index[general]{Considerations!Windows Compatibility}
337 If you are not using the VSS (Volume Shadow Copy) option described in the
338 next section of this chapter, and if any applications are running during
339 the backup and they have files opened exclusively, Bacula will not be able
340 to backup those files, so be sure you close your applications (or tell your
341 users to close their applications) before the backup. Fortunately, most
342 Microsoft applications do not open files exclusively so that they can be
343 backed up. However, you will need to experiment. In any case, if Bacula
344 cannot open the file, it will print an error message, so you will always
345 know which files were not backed up. For version 1.37.25 and greater, see
346 the section below on Volume Shadow Copy Service that permits backing up any
349 During backup, Bacula doesn't know about the system registry, so you will
350 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
351 program specifically designed to make a copy or backup the registry.
353 In Bacula version 1.31 and later, we use Windows backup API calls by
354 default. Typical of Windows, programming these special BackupRead and
355 BackupWrite calls is a real nightmare of complications. The end result
356 gives some distinct advantages and some disadvantages.
358 First, the advantages are that Windows systems, the security and
359 ownership information is now backed up. In addition, with the exception of
360 files in exclusive use by another program, Bacula can now access all system
361 files. This means that when you restore files, the security and ownership
362 information will be restored on Windows along with the data.
364 The disadvantage of the Windows backup API calls is that it produces
365 non-portable backups. That is files and their data that are backed up on
366 Windows using the native API calls (BackupRead/BackupWrite) cannot be
367 directly restored on Linux or Unix systems. Bacula should be able to read
368 non-portable backups on any system and restore the data appropriately.
369 However, on a system that does not have the BackupRead/BackupWrite calls
370 (older Windows versions and all Unix/Linux machines), though the file data
371 can be restored, the Windows security and access control data will not be
372 restored. This means that a standard set of access permissions will be set
373 for such restored files.
376 As a default, Bacula backs up Windows systems using the Windows API calls.
377 If you want to backup data on a Windows system and restore it on a
378 Unix or Linux system, we have provided a special {\bf portable} option
379 that backs up the data in a portable fashion by using portable API calls.
380 See the \ilink{portable option}{portable} on the Include statement in a
381 FileSet resource in the Director's configuration chapter for the details on
382 setting this option. However, using the portable option means you may have
383 permissions problems accessing files, and none of the security and
384 ownership information will be backed up or restored. The file data can,
385 however, be restored on any system.
387 You should always be able to restore any file backed up on Unix or Win95/98/Me
388 to any other system. On some older Windows systems, you may have to
389 reset the ownership of such restored files.
391 Finally, if you specify the {\bf portable=yes} option on the files you back
392 up. Bacula will be able to restore them on any other system. However, any
393 Windows specific security and ownership information will be lost.
395 The following matrix will give you an idea of what you can expect. Thanks to
396 Marc Brueckner for doing the tests:
398 \LTXtable{\linewidth}{table_restoreportabilitystatus}
400 Note: with Bacula versions 1.39.x and later, non-portable Windows data can
401 be restore to any machine.
405 \section{Volume Shadow Copy Service}
406 \index[general]{Volume Shadow Copy Service}
408 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
409 a backup-solution for Windows, this is an extremely important step. VSS
410 allows Bacula to backup open files and even to interact with applications like
411 RDBMS to produce consistent file copies. VSS aware applications are called
412 VSS Writers, they register with the OS so that when Bacula wants to do a
413 Snapshot, the OS will notify the register Writer programs, which may then
414 create a consistent state in their application, which will be backed up.
415 Examples for these writers are "MSDE" (Microsoft database
416 engine), "Event Log Writer", "Registry Writer" plus 3rd
417 party-writers. If you have a non-vss aware application (e.g.
418 SQL Anywhere or probably MySQL), a shadow copy is still generated
419 and the open files can be backed up, but there is no guarantee
420 that the file is consistent.
422 Bacula produces a message from each of the registered writer programs
423 when it is doing a VSS backup so you know which ones are correctly backed
426 Technically Bacula creates a shadow copy as soon as the backup process
427 starts. It does then backup all files from the shadow copy and destroys the
428 shadow copy after the backup process. Please have in mind, that VSS
429 creates a snapshot and thus backs up the system at the state it had
430 when starting the backup. It will disregard file changes which occur during
433 VSS can be turned on by placing an
435 \index[dir]{Enable VSS}
436 \index[general]{Enable VSS}
441 in your FileSet resource.
443 The VSS aware File daemon has the letters VSS on the signon line that
444 it produces when contacted by the console. For example:
446 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
448 the VSS is shown in the line above. This only means that the File daemon
449 is capable of doing VSS not that VSS is turned on for a particular backup.
450 There are two ways of telling if VSS is actually turned on during a backup.
451 The first is to look at the status output for a job, e.g.:
455 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
456 VSS Backup Job started: 23-Jul-05 13:25
457 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
458 Files Examined=75,021
459 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
463 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
464 This means that VSS is enabled for that job. If VSS is not enabled, it will
465 simply show "Backup Job started ..." without the letters VSS.
467 The second way to know that the job was backed up with VSS is to look at the
468 Job Report, which will look something like the following:
471 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
472 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
473 23-Jul 13:26 rufus-sd: Spooling data ...
474 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
475 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
476 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
477 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
478 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
481 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
482 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
483 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
484 that you will get a consistent snapshot of the data handled by that writer.
486 \section{VSS Problems}
487 \index[general]{Problems!VSS}
488 \index[fd] {Problems!VSS}
489 \index[general]{VSS Problems}
490 \index[fd]{VSS Problems}
492 If you are experiencing problems such as VSS hanging on MSDE, first try
493 running {\bf vssadmin} to check for problems, then try running {\bf
494 ntbackup} which also uses VSS to see if it has similar problems. If so, you
495 know that the problem is in your Windows machine and not with Bacula.
497 The FD hang problems were reported with {\bf MSDEwriter} when:
499 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
500 seems to use TCP/IP and not Named Pipes).
501 \item msdtcs was installed to run under "localsystem": try running msdtcs
502 under networking account (instead of local system) (com+ seems to work
503 better with this configuration).
507 \section{Windows Firewalls}
508 \index[general]{Firewalls!Windows}
509 \index[general]{Windows Firewalls}
511 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
512 are likely to find that the Bacula ports are blocked and you cannot
513 communicate to the other daemons. This can be deactivated through the {\bf
514 Security Notification} dialog, which is apparently somewhere in the {\bf
515 Security Center}. I don't have this on my computer, so I cannot give the exact
522 netsh firewall set opmode disable
526 is purported to disable the firewall, but this command is not accepted on my
529 \section{Windows Port Usage}
530 \index[general]{Windows Port Usage}
531 \index[general]{Usage!Windows Port}
533 If you want to see if the File daemon has properly opened the port and is
534 listening, you can enter the following command in a shell window:
538 netstat -an | findstr 910[123]
542 TopView is another program that has been recommend, but it is not a
543 standard Windows program, so you must find and download it from the Internet.
545 \section{Windows Disaster Recovery}
546 \index[general]{Recovery!Windows Disaster}
547 \index[general]{Windows Disaster Recovery}
549 We don't currently have a good solution for disaster recovery on Windows as we
550 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
551 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
552 that could possibly work, but we have not investigated it. This means that
553 until someone figures out the correct procedure, you must restore the OS from
554 the installation disks, then you can load a Bacula client and restore files.
555 Please don't count on using {\bf bextract} to extract files from your backup
556 tapes during a disaster recovery unless you have backed up those files using
557 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
558 normal way Bacula saves files using the Windows API prevents the files from
559 being restored on a Unix machine. Once you have an operational Windows OS
560 loaded, you can run the File daemon and restore your user files.
563 \ilink{Disaster Recovery of Windows Systems}{Windows33} for the latest
564 suggestion, which looks very promising.
566 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
567 Environment) Boot-CD, may be just what is needed to build a complete disaster
568 recovery system for Windows. This distribution can be found at
569 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
571 \section{Windows Restore Problems}
572 \index[general]{Problems!Windows Restore}
573 \index[general]{Windows Restore Problems}
575 \ilink{Restore Chapter}{Windows} of this manual for problems
576 that you might encounter doing a restore.
578 section{Windows Backup Problems}
579 \index[general]{Problems!Windows Backup}
580 \index[general]{Windows Backup Problems}
581 If during a Backup, you get the message:
582 {\bf ERR=Access is denied} and you are using the portable option,
583 you should try both adding both the non-portable (backup API) and
584 the Volume Shadow Copy options to your Director's conf file.
586 In the Options resource:
593 In the FileSet resource:
600 In general, specifying these two options should allow you to backup
601 any file on a Windows system. However, in some cases, if users
602 have allowed to have full control of their folders, even system programs
603 such a Bacula can be locked out. In this case, you must identify
604 which folders or files are creating the problem and do the following:
607 \item Grant ownership of the file/folder to the Administrators group,
608 with the option to replace the owner on all child objects.
609 \item Grant full control permissions to the Administrators group,
610 and change the user's group to only have Modify permission to
611 the file/folder and all child objects.
614 Thanks to Georger Araujo for the above information.
616 \section{Windows Ownership and Permissions Problems}
617 \index[general]{Problems!Windows Ownership and Permissions}
618 \index[general]{Windows Ownership and Permissions Problems}
620 If you restore files backed up from Windows to an alternate directory,
621 Bacula may need to create some higher level directories that were not saved
622 (or restored). In this case, the File daemon will create them under the SYSTEM
623 account because that is the account that Bacula runs under as a service. As of
624 version 1.32f-3, Bacula creates these files with full access permission.
625 However, there may be cases where you have problems accessing those files even
626 if you run as administrator. In principle, Microsoft supplies you with the way
627 to cease the ownership of those files and thus change the permissions.
628 However, a much better solution to working with and changing Windows permissions
629 is the program {\bf SetACL}, which can be found at
630 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
632 If you have not installed Bacula while running as Administrator
633 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
634 then it is very unlikely that it will have sufficient permission to
635 access all your files.
637 Some users have experienced problems restoring files that participate in
638 the Active Directory. They also report that changing the userid under which
639 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
643 \section{Manually resetting the Permissions}
644 \index[general]{Manually resetting the Permissions}
645 \index[general]{Permissions!Manually resetting the}
647 The following solution was provided by Dan Langille \lt{}dan at langille in
648 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
649 they should apply to most Windows platforms. The procedure outlines how to deal
650 with a problem which arises when a restore creates a top-level new directory.
651 In this example, "top-level" means something like {\bf
652 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
653 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
654 as the {\bf Where:} value, this problem will arise.
656 The problem appears as a directory which cannot be browsed with Windows
657 Explorer. The symptoms include the following message when you try to click on
661 \includegraphics{access-is-denied}
664 If you encounter this message, the following steps will change the permissions
665 to allow full access.
668 \item right click on the top level directory (in this example, {\bf c:/src})
669 and select {\bf Properties}.
670 \item click on the Security tab.
671 \item If the following message appears, you can ignore it, and click on {\bf
675 \includegraphics{view-only}
677 You should see something like this:
680 \includegraphics{properties-security}
682 \item click on Advanced
683 \item click on the Owner tab
684 \item Change the owner to something other than the current owner (which is
685 {\bf SYSTEM} in this example as shown below).
688 \includegraphics{properties-security-advanced-owner}
690 \item ensure the "Replace owner on subcontainers and objects" box is
693 \item When the message "You do not have permission to read the contents of
694 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
695 the directory permissions with permissions granting you Full Control?", click
699 \includegraphics[width=0.8\linewidth]{confirm}
701 \item Click on OK to close the Properties tab
704 With the above procedure, you should now have full control over your restored
707 In addition to the above methods of changing permissions, there is a Microsoft
708 program named {\bf cacls} that can perform similar functions.
710 \section{Backing Up the Windows System State}
711 \index[general]{State!Backing Up the WinNT/XP/2K System}
712 \index[general]{Backing Up the WinNT/XP/2K System State}
714 Note, most of this section applies to the older Windows OSes that
715 do not have VSS. On newer Windows OSes that have VSS, all files
716 including the System State will by default be properly backed
719 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
720 conjunction with Bacula should permit a full restore of any damaged system
721 files on Windows machines. His suggestion is to do an NTBackup of the critical system
722 state prior to running a Bacula backup with the following command:
726 ntbackup backup systemstate /F c:\systemstate.bkf
730 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
731 system state and not all the user files, and the {\bf /F
732 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
733 this file must then be saved and restored by Bacula.
735 To restore the system state, you first reload a base operating system if the
736 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
737 restore all the damaged or lost user's files and to recover the {\bf
738 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
739 missing system files or registry problems, you run {\bf NTBackup} and {\bf
740 catalogue} the system statefile, and then select it for restore. The
741 documentation says you can't run a command line restore of the systemstate.
743 To the best of my knowledge, this has not yet been tested. If you test it,
744 please report your results to the Bacula email list.
746 Note, Bacula uses VSS to backup and restore open files and
747 system files, but on older Windows machines such as WinNT and
748 Win2000, VSS is not implemented by Microsoft so that you must
749 use some special techniques to back them up as described
750 above. On new Windows machines, Bacula will backup and restore
751 all files including the system state providing you have
752 VSS enabled in your Bacula FileSet (default).
754 \section{Fixing the Windows Boot Record}
755 \index[general]{Fixing the Windows Boot Record}
756 \index[general]{Windows!Fixing the Boot Record}
758 An effective way to restore a Windows backup for
759 those who do not purchase the bare metal restore
760 capability is to install Windows on a different
761 hard drive and restore the backup. Then run the
777 \section{Considerations for Filename Specifications}
778 \index[general]{Windows!Considerations for Filename Specifications}
781 \ilink{Director's Configuration chapter}{win32} of this manual
782 for important considerations on how to specify Windows paths in Bacula FileSet
783 Include and Exclude directives.
785 \index[general]{Unicode}
786 Very old Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
787 As of that version, both {\bf bconsole} and {\bf bat} support Windows
788 Unicode filenames. There may still be some problems with multiple byte
789 characters (e.g. Chinese, ...) where it is a two byte character but the
790 displayed character is not two characters wide.
792 \index[general]{Windows Path Length Restriction}
793 Path/filenames longer than 260 characters (up to 32,000) are supported
794 beginning with Bacula version 1.39.20. Older Bacula versions support
795 only 260 character path/filenames.
797 \section{Windows Specific File daemon Command Line}
798 \index[general]{Client!Windows Specific File daemon Command Line Options}
799 \index[general]{Windows Specific File daemon Command Line Options}
801 These options are not normally seen or used by the user, and are documented
802 here only for information purposes. At the current time, to change the default
803 options, you must either manually run {\bf Bacula} or you must manually edit
804 the system registry and modify the appropriate entries.
806 In order to avoid option clashes between the options necessary for {\bf
807 Bacula} to run on Windows and the standard Bacula options, all Windows
808 specific options are signaled with a forward slash character (/), while as
809 usual, the standard Bacula options are signaled with a minus (-), or a minus
810 minus (\verb:--:). All the standard Bacula options can be used on the Windows
811 version. In addition, the following Windows only options are implemented:
817 Start Bacula as a service
821 Run the Bacula application
825 Install Bacula as a service in the system registry
829 Uninstall Bacula from the system registry
833 Show the Bacula about dialogue box
837 Show the Bacula status dialogue box
841 Show the Bacula events dialogue box (not yet implemented)
845 Stop any running {\bf Bacula}
849 Show the Bacula help dialogue box
852 It is important to note that under normal circumstances the user should never
853 need to use these options as they are normally handled by the system
854 automatically once Bacula is installed. However, you may note these options in
855 some of the .bat files that have been created for your use.
857 \section{Shutting down Windows Systems}
858 \index[general]{Shutting down Windows Systems}
859 \index[general]{Systems!Shutting down Windows}
861 Some users like to shutdown their Windows machines after a backup using a
862 Client Run After Job directive. If you want to do something similar, you might
863 take the shutdown program from the
864 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
865 \elink{Sysinternals project}{http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.