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, and
16 Windows 2012 systems. The Windows version of Bacula is a native Windows
17 port, but there are very few source code changes to the Unix code, which
18 means that the Windows version is for the most part running code that has
19 long proved stable on Unix systems. When running, it is perfectly
20 integrated with Windows and displays its icon in the system icon tray, and
21 provides a system tray menu to obtain additional information on how Bacula
22 is running (status and events dialog boxes). If so desired, it can also be
23 stopped by using the system tray menu, though this should normally never be
26 Once installed Bacula normally runs as a system service. This means that it is
27 immediately started by the operating system when the system is booted, and
28 runs in the background even if there is no user logged into the system.
30 \section{Windows Installation}
32 \index[general]{Installation}
33 \index[general]{Windows!Installation}
35 Normally, you will install the Windows version of Bacula from the binaries.
36 This install is standard Windows .exe that runs an install wizard using the
37 NSIS Free Software installer, so if you have already installed Windows
38 software, it should be very familiar to you.
40 If you have a previous version of Bacula
41 installed, you should stop the service, uninstall it, and remove
42 the Bacula installation directory possibly saving your
43 bacula-fd.conf, bconsole.conf, and bat.conf files
44 for use with the new version you will install. The Uninstall
45 program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
46 We also recommend that you completely remove the directory
47 {\bf c:\textbackslash{}bacula}, because the current installer
48 uses a different directory structure (see below).
50 Providing you do not already have Bacula installed,
51 the installer installs the binaries and dlls in
52 c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
53 and the configuration files
54 in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
55 In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
56 will be created during the installation, and on that menu, you
57 will find items for editing the configuration files, displaying
58 the document, and starting bwx-console or bconsole.
61 Finally, proceed with the installation.
64 \item You must be logged in as Administrator to the local machine
65 to do a correct installation, if not, please do so before continuing.
66 Some users have attempted to install logged in as a domain administrator
67 account and experienced permissions problems attempting to run
68 Bacula, so we don't recommend that option.
70 \item Simply double click on the {\bf bacula-win32-5.xx.0.exe} NSIS install
71 icon. The actual name of the icon will vary from one release version to
74 \includegraphics{\idir win32-nsis.eps} bacula-win32-5.xx.0.exe
76 \item Once launched, the installer wizard will ask you if you want to install
79 \addcontentsline{lof}{figure}{Windows Client Setup Wizard}
80 \includegraphics{\idir win32-welcome.eps}
82 \item Next you will be asked to select the installation type.
84 \addcontentsline{lof}{figure}{Windows Installation Type}
85 \includegraphics{\idir win32-installation-type.eps}
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}{Windows Component Selection Dialog}
95 \includegraphics{\idir win32-pkg.eps}
96 \index[general]{Upgrading}
98 \item If you are installing for the first time, you will be asked to
99 enter some very basic information about your configuration. If
100 you are not sure what to enter, or have previously saved configuration
101 files, you can put anything you want into the fields, then either
102 replace the configuration files later with the ones saved, or edit
105 If you are upgrading an existing installation, the following will
109 \addcontentsline{lof}{figure}{Windows Configure}
110 \includegraphics{\idir win32-config.eps}
112 \item While the various files are being loaded, you will see the following
115 \addcontentsline{lof}{figure}{Windows Install Progress}
116 \includegraphics{\idir win32-installing.eps}
119 \item Finally, the finish dialog will appear:
121 \addcontentsline{lof}{figure}{Windows Client Setup Completed}
122 \includegraphics{\idir win32-finish.eps}
127 That should complete the installation process.
130 \index[general]{Tray Icon}
132 Note: this section does not apply to all Windows versions
133 later than Windows XP, since in those later versions Microsoft
134 explicitly prohibits a system service such as Bacula from interacting
137 On Windows XP, when the Bacula File Server
138 is ready to serve files, an icon \includegraphics{\idir idle.eps}
139 representing a cassette (or tape) will appear in the system tray
140 \includegraphics{\idir tray-icon.eps}; right click on it and a menu will
141 appear.\\ \includegraphics{\idir menu.eps}\\ The {\bf Events} item is
142 currently unimplemented, by selecting the {\bf Status} item, you can verify
143 whether any jobs are running or not.
145 When the Bacula File Server begins saving files, the color of the holes in
146 the cassette icon will change from white to green \includegraphics{\idir
147 running.eps}, and if there is an error, the holes in the cassette icon will
148 change to red \includegraphics{\idir 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
152 visible when you log into the console, but the remote desktop may not
155 \section{Post Windows Installation}
156 \index[general]{Post Windows Installation}
157 \index[general]{Windows!Post Installation}
159 After installing Bacula and before running it, you should check the
160 contents of the configuration files to ensure that they correspond to your
161 installation. You can get to them by using: the {\bf Start\-\gt{}All
162 Programs\-\gt{}Bacula} menu item.
164 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
165 is running as a process (not an Application) with User Name SYSTEM. If this is
166 not the case, you probably have not installed Bacula while running as
167 Administrator, and hence it will be unlikely that Bacula can access
168 all the system files.
170 \section{Windows FD Restrictions}
171 \index[general]{Windows FD Restrictions}
172 In recent versions of Windows, Microsoft has implemented
173 Volume Mount Points, Encrypted Volumes, and Deduplicated Volumes.
174 Current versions of the Windows File daemon do not support
175 any of these special Volume formats.
177 \section{Uninstalling Bacula on Windows}
178 \index[general]{Windows!Uninstalling Bacula}
179 \index[general]{Uninstalling Bacula on Windows}
181 Once Bacula has been installed, it can be uninstalled using the standard
182 Windows Add/Remove Programs dialog found on the Control panel.
184 \section{Dealing with Windows Problems}
186 \index[general]{Windows!Dealing with Problems}
187 \index[general]{Dealing with Windows Problems}
189 Sometimes Windows machines the File daemon may have very slow
190 backup transfer rates compared to other machines. To you might
191 try setting the Maximum Network Buffer Size to 32,768 in both the
192 File daemon and in the Storage daemon. The default size is larger,
193 and apparently some Windows ethernet controllers do not deal with
194 a larger network buffer size.
196 Many Windows ethernet drivers have a tendency to either run slowly
197 due to old broken firmware, or because they are running in half-duplex
198 mode. Please check with the ethernet card manufacturer for the latest
199 firmware and use whatever techniques are necessary to ensure that the
200 card is running in duplex.
202 If you are not using the portable option, and you have VSS
203 (Volume Shadow Copy) enabled in the Director, and you experience
204 problems with Bacula not being able to open files, it is most
205 likely that you are running an antivirus program that blocks
206 Bacula from doing certain operations. In this case, disable the
207 antivirus program and try another backup. If it succeeds, either
208 get a different (better) antivirus program or use something like
209 RunClientJobBefore/After to turn off the antivirus program while
210 the backup is running.
212 If turning off anti-virus software does not resolve your VSS
213 problems, you might have to turn on VSS debugging. The following
214 link describes how to do this:
215 \elink{http://support.microsoft.com/kb/887013/en-us}{http://support.microsoft.com/kb/887013/en-us}.
217 In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
218 is turned off by default. To turn it on, please see the following link:
219 \elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{
220 http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}
223 The most likely source of problems is authentication when the Director
224 attempts to connect to the File daemon that you installed. This can occur if
225 the names and the passwords defined in the File daemon's configuration file
226 {\bf bacula-fd.conf} file on
227 the Windows machine do not match with the names and the passwords in the
228 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
231 More specifically, the password found in the {\bf Client} resource in the
232 Director's configuration file must be the same as the password in the {\bf
233 Director} resource of the File daemon's configuration file. In addition, the
234 name of the {\bf Director} resource in the File daemon's configuration file
235 must be the same as the name in the {\bf Director} resource of the Director's
238 It is a bit hard to explain in words, but if you understand that a Director
239 normally has multiple Clients and a Client (or File daemon) may permit access
240 by multiple Directors, you can see that the names and the passwords on both
241 sides must match for proper authentication.
243 One user had serious problems with the configuration file until he realized
244 that the Unix end of line conventions were used and Bacula wanted them in
245 Windows format. This has not been confirmed though, and Bacula version 2.0.0
246 and above should now accept all end of line conventions (Windows,
249 Running Unix like programs on Windows machines is a bit frustrating because
250 the Windows command line shell (DOS Window) is rather primitive. As a
251 consequence, it is not generally possible to see the debug information and
252 certain error messages that Bacula prints. With a bit of work, however, it is
253 possible. When everything else fails and you want to {\bf see} what is going
254 on, try the following:
258 Start a DOS shell Window.
259 c:\Program Files\bacula\bacula-fd -t >out
264 The precise path to bacula-fd depends on where it is installed.
265 The {\bf -t} option will cause Bacula to read the configuration file, print
266 any error messages and then exit. the {\bf \gt{}} redirects the output to the
267 file named {\bf out}, which you can list with the {\bf type} command.
269 If something is going wrong later, or you want to run {\bf Bacula} with a
270 debug option, you might try starting it as:
274 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
278 In this case, Bacula will run until you explicitly stop it, which will give
279 you a chance to connect to it from your Unix/Linux server. In later versions
280 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
281 can write the output to a trace file {\bf bacula.trace} in the current
282 directory. To enable this, before running a job, use the console, and enter:
290 then run the job, and once you have terminated the File daemon, you will find
291 the debug output in the {\bf bacula.trace} file, which will probably be
292 located in the same directory as bacula-fd.exe.
294 In addition, you should look in the System Applications log on the Control
295 Panel to find any Windows errors that Bacula got during the startup process.
297 Finally, due to the above problems, when you turn on debugging, and specify
298 trace=1 on a setdebug command in the Console, Bacula will write the debug
299 information to the file {\bf bacula.trace} in the directory from which Bacula
302 If you are having problems with ClientRunBeforeJob scripts randomly dying,
303 it is possible that you have run into an Oracle bug. See bug number 622 in
304 the bugs.bacula.org database. The following information has been
305 provided by a user on this issue:
309 The information in this document applies to:
310 Oracle HTTP Server - Version: 9.0.4
311 Microsoft Windows Server 2003
313 When starting an OC4J instance, the System Clock runs faster, about 7
318 + This is caused by the Sun JVM bug 4500388, which states that "Calling
319 Thread.sleep() with a small argument affects the system clock". Although
320 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
322 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
324 + Also reported by Microsoft as "The system clock may run fast when you
325 use the ACPI power management timer as a high-resolution counter on Windows
326 2000-based computers" (See http://support.microsoft.com/?id=821893)
330 You may wish to start the daemon with debug mode on rather than doing it
331 using bconsole. To do so, edit the following registry key:
335 HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
339 using regedit, then add -dnn after the /service option, where nn represents
340 the debug level you want.
342 \label{Compatibility}
343 \section{Windows Compatibility Considerations}
344 \index[general]{Windows Compatibility Considerations}
345 \index[general]{Considerations!Windows Compatibility}
347 If you are not using the VSS (Volume Shadow Copy) option described in the
348 next section of this chapter, and if any applications are running during
349 the backup and they have files opened exclusively, Bacula will not be able
350 to backup those files, so be sure you close your applications (or tell your
351 users to close their applications) before the backup. Fortunately, most
352 Microsoft applications do not open files exclusively so that they can be
353 backed up. However, you will need to experiment. In any case, if Bacula
354 cannot open the file, it will print an error message, so you will always
355 know which files were not backed up. For version 1.37.25 and greater, see
356 the section below on Volume Shadow Copy Service that permits backing up any
359 During backup, Bacula doesn't know about the system registry, so you will
360 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
361 program specifically designed to make a copy or backup the registry.
363 Bacula uses Windows backup API calls by
364 default. Typical of Windows, programming these special BackupRead and
365 BackupWrite calls is a real nightmare of complications. The end result
366 gives some distinct advantages and some disadvantages.
368 First, the advantages are that Windows systems, the security and
369 ownership information is now backed up. In addition, with the exception of
370 files in exclusive use by another program, Bacula can now access all system
371 files. This means that when you restore files, the security and ownership
372 information will be restored on Windows along with the data.
374 The disadvantage of the Windows backup API calls is that it produces
375 non-portable backups. That is files and their data that are backed up on
376 Windows using the native API calls (BackupRead/BackupWrite) cannot be
377 directly restored on Linux or Unix systems. Bacula should be able to read
378 non-portable backups on any system and restore the data appropriately.
379 However, on a system that does not have the BackupRead/BackupWrite calls
380 (older Windows versions and all Unix/Linux machines), though the file data
381 can be restored, the Windows security and access control data will not be
382 restored. This means that a standard set of access permissions will be set
383 for such restored files.
386 As a default, Bacula backs up Windows systems using the Windows API calls.
387 If you want to backup data on a Windows system and restore it on a
388 Unix or Linux system, we have provided a special {\bf portable} option
389 that backs up the data in a portable fashion by using portable API calls.
390 See the \ilink{portable option}{portable} on the Include statement in a
391 FileSet resource in the Director's configuration chapter for the details on
392 setting this option. However, using the portable option means you may have
393 permissions problems accessing files, and none of the security and
394 ownership information will be backed up or restored. The file data can,
395 however, be restored on any system.
397 You should always be able to restore any file backed up on Unix or Win95/98/Me
398 to any other system. On some older Windows systems, you may have to
399 reset the ownership of such restored files.
401 Finally, if you specify the {\bf portable=yes} option on the files you back
402 up. Bacula will be able to restore them on any other system. However, any
403 Windows specific security and ownership information will be lost.
405 The following matrix will give you an idea of what you can expect. Thanks to
406 Marc Brueckner for doing the tests:
408 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
409 \begin{longtable}{|l|l|p{2.8in}|}
411 \multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
412 & \multicolumn{1}{c|}{\bf Results } \\
413 \hline {WinMe} & {WinMe} & {Works } \\
414 \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
415 \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
416 \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
417 \hline {\ } & {\ } & {\ } \\
418 \hline {WinXP} & {WinXP} & {Works } \\
419 \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
421 \hline {WinXP} & {WinMe} & {Error: Windows data stream not supported. } \\
422 \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
423 \hline {WinXP} & {Linux} & {Error: Windows data stream not supported. } \\
424 \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
425 \hline {\ } & {\ } & {\ } \\
426 \hline {WinNT} & {WinNT} & {Works } \\
427 \hline {WinNT} & {WinXP} & {Works } \\
428 \hline {WinNT} & {WinMe} & {Error: Windows data stream not supported. } \\
429 \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
430 \hline {WinNT} & {Linux} & {Error: Windows data stream not supported. } \\
431 \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
432 \hline {\ } & {\ } & {\ } \\
433 \hline {Linux} & {Linux} & {Works } \\
434 \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
435 \hline {Linux} & {WinMe} & {Works } \\
436 \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
440 Note: Non-portable Windows data can be restore to any machine. In
441 addition, with recent Bacula versions, Bacula is able to extract data
442 part from Windows backup streams when restoring on a non-Windows
446 \section{Volume Shadow Copy Service}
447 \index[general]{Volume Shadow Copy Service}
449 Microsoft added VSS to Windows XP and later systems. From the perspective
450 of a backup-solution for Windows, this is an extremely important step. VSS
451 allows Bacula to backup open files and even to interact with applications
452 like RDBMS to produce consistent file copies. VSS aware applications are
453 called VSS Writers, they register with the OS so that when Bacula wants to
454 do a Snapshot, the OS will notify the register Writer programs, which may
455 then create a consistent state in their application, which will be backed
456 up. Examples for these writers are "MSDE" (Microsoft database engine),
457 "Event Log Writer", "Registry Writer" plus 3rd party-writers. If you have
458 a non-vss aware application (e.g. SQL Anywhere or probably MySQL), a
459 shadow copy is still generated and the open files can be backed up, but
460 there is no guarantee that the file is consistent.
462 Bacula produces a message from each of the registered writer programs
463 when it is doing a VSS backup so you know which ones are correctly backed
466 Technically Bacula creates a shadow copy as soon as the backup process
467 starts. It does then backup all files from the shadow copy and destroys the
468 shadow copy after the backup process. Please have in mind, that VSS
469 creates a snapshot and thus backs up the system at the state it had
470 when starting the backup. It will disregard file changes which occur during
473 VSS can be turned on by placing an
475 \index[dir]{Enable VSS}
476 \index[general]{Enable VSS}
481 in your FileSet resource.
483 The VSS aware File daemon has the letters VSS on the signon line that
484 it produces when contacted by the console. For example:
486 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
488 the VSS is shown in the line above. This only means that the File daemon
489 is capable of doing VSS not that VSS is turned on for a particular backup.
490 There are two ways of telling if VSS is actually turned on during a backup.
491 The first is to look at the status output for a job, e.g.:
495 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
496 VSS Backup Job started: 23-Jul-05 13:25
497 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
498 Files Examined=75,021
499 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
503 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
504 This means that VSS is enabled for that job. If VSS is not enabled, it will
505 simply show "Backup Job started ..." without the letters VSS.
507 The second way to know that the job was backed up with VSS is to look at the
508 Job Report, which will look something like the following:
511 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
512 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
513 23-Jul 13:26 rufus-sd: Spooling data ...
514 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
515 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
516 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
517 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
518 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
521 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
522 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
523 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
524 that you will get a consistent snapshot of the data handled by that writer.
526 \section{VSS Problems}
527 \index[general]{Problems!VSS}
528 \index[fd] {Problems!VSS}
529 \index[general]{VSS Problems}
530 \index[fd]{VSS Problems}
532 If you are experiencing problems such as VSS hanging on MSDE, first try
533 running {\bf vssadmin} to check for problems, then try running {\bf
534 ntbackup} which also uses VSS to see if it has similar problems. If so, you
535 know that the problem is in your Windows machine and not with Bacula.
537 The FD hang problems were reported with {\bf MSDEwriter} when:
539 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
540 seems to use TCP/IP and not Named Pipes).
541 \item msdtcs was installed to run under "localsystem": try running msdtcs
542 under networking account (instead of local system) (com+ seems to work
543 better with this configuration).
547 \section{Windows Firewalls}
548 \index[general]{Firewalls!Windows}
549 \index[general]{Windows Firewalls}
551 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
552 are likely to find that the Bacula ports are blocked and you cannot
553 communicate to the other daemons. This can be deactivated through the {\bf
554 Security Notification} dialog, which is apparently somewhere in the {\bf
555 Security Center}. I don't have this on my computer, so I cannot give the exact
562 netsh firewall set opmode disable
566 is purported to disable the firewall, but this command is not accepted on my
569 \section{Windows Port Usage}
570 \index[general]{Windows Port Usage}
571 \index[general]{Usage!Windows Port}
573 If you want to see if the File daemon has properly opened the port and is
574 listening, you can enter the following command in a shell window:
578 netstat -an | findstr 910[123]
582 TopView is another program that has been recommend, but it is not a
583 standard Windows program, so you must find and download it from the Internet.
585 \section{Windows Disaster Recovery}
586 \index[general]{Recovery!Windows Disaster}
587 \index[general]{Windows Disaster Recovery}
589 We don't currently have a good solution for disaster recovery on Windows as we
590 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
591 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
592 that could possibly work, but we have not investigated it. This means that
593 until someone figures out the correct procedure, you must restore the OS from
594 the installation disks, then you can load a Bacula client and restore files.
595 Please don't count on using {\bf bextract} to extract files from your backup
596 tapes during a disaster recovery unless you have backed up those files using
597 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
598 normal way Bacula saves files using the Windows API prevents the files from
599 being restored on a Unix machine. Once you have an operational Windows OS
600 loaded, you can run the File daemon and restore your user files.
603 \ilink{ Disaster Recovery of Windows Systems}{Windows33} for the latest
604 suggestion, which looks very promising.
606 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
607 Environment) Boot-CD, may be just what is needed to build a complete disaster
608 recovery system for Windows. This distribution can be found at
609 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
611 \section{Windows Restore Problems}
612 \index[general]{Problems!Windows Restore}
613 \index[general]{Windows Restore Problems}
615 \ilink{Restore Chapter}{Windows} of this manual for problems
616 that you might encounter doing a restore.
618 section{Windows Backup Problems}
619 \index[general]{Problems!Windows Backup}
620 \index[general]{Windows Backup Problems}
621 If during a Backup, you get the message:
622 {\bf ERR=Access is denied} and you are using the portable option,
623 you should try both adding both the non-portable (backup API) and
624 the Volume Shadow Copy options to your Director's conf file.
626 In the Options resource:
633 In the FileSet resource:
640 In general, specifying these two options should allow you to backup
641 any file on a Windows system. However, in some cases, if users
642 have allowed to have full control of their folders, even system programs
643 such a Bacula can be locked out. In this case, you must identify
644 which folders or files are creating the problem and do the following:
647 \item Grant ownership of the file/folder to the Administrators group,
648 with the option to replace the owner on all child objects.
649 \item Grant full control permissions to the Administrators group,
650 and change the user's group to only have Modify permission to
651 the file/folder and all child objects.
654 Thanks to Georger Araujo for the above information.
656 \section{Windows Ownership and Permissions Problems}
657 \index[general]{Problems!Windows Ownership and Permissions}
658 \index[general]{Windows Ownership and Permissions Problems}
660 If you restore files backed up from Windows to an alternate directory,
661 Bacula may need to create some higher level directories that were not saved
662 (or restored). In this case, the File daemon will create them under the
663 SYSTEM account because that is the account that Bacula runs under as a
664 service. As of version 1.32f-3, Bacula creates these files with full
665 access permission. However, there may be cases where you have problems
666 accessing those files even if you run as administrator. In principle,
667 Microsoft supplies you with the way to cease the ownership of those files
668 and thus change the permissions. However, a much better solution to
669 working with and changing Windows permissions is the program {\bf SetACL},
670 which can be found at
671 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
673 If you have not installed Bacula while running as Administrator and if
674 Bacula is not running as a Process with the userid (User Name) SYSTEM, then
675 it is very unlikely that it will have sufficient permission to access all
678 Some users have experienced problems restoring files that participate in
679 the Active Directory. They also report that changing the userid under which
680 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
684 \section{Manually resetting the Permissions}
685 \index[general]{Manually resetting the Permissions}
686 \index[general]{Permissions!Manually resetting the}
688 The following solution was provided by Dan Langille \lt{}dan at langille in
689 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
690 they should apply to most Windows platforms. The procedure outlines how to deal
691 with a problem which arises when a restore creates a top-level new directory.
692 In this example, "top-level" means something like {\bf
693 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
694 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
695 as the {\bf Where:} value, this problem will arise.
697 The problem appears as a directory which cannot be browsed with Windows
698 Explorer. The symptoms include the following message when you try to click on
701 \includegraphics{\idir access-is-denied.eps}
703 If you encounter this message, the following steps will change the permissions
704 to allow full access.
707 \item right click on the top level directory (in this example, {\bf c:/src})
708 and select {\bf Properties}.
709 \item click on the Security tab.
710 \item If the following message appears, you can ignore it, and click on {\bf
713 \includegraphics{\idir view-only.eps}
715 You should see something like this:
717 \includegraphics{\idir properties-security.eps}
718 \item click on Advanced
719 \item click on the Owner tab
720 \item Change the owner to something other than the current owner (which is
721 {\bf SYSTEM} in this example as shown below).
723 \includegraphics{\idir properties-security-advanced-owner.eps}
724 \item ensure the "Replace owner on subcontainers and objects" box is
727 \item When the message "You do not have permission to read the contents of
728 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
729 the directory permissions with permissions granting you Full Control?", click
732 \includegraphics{\idir confirm.eps}
733 \item Click on OK to close the Properties tab
736 With the above procedure, you should now have full control over your restored
739 In addition to the above methods of changing permissions, there is a Microsoft
740 program named {\bf cacls} that can perform similar functions.
742 \section{Backing Up the WinNT/XP/2K System State}
743 \index[general]{State!Backing Up the WinNT/XP/2K System}
744 \index[general]{Backing Up the WinNT/XP/2K System State}
746 Note, most of this section applies to the older Windows OSes that
747 do not have VSS. On newer Windows OSes that have VSS, all files
748 including the System State will by default be properly backed
751 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
752 conjunction with Bacula should permit a full restore of any damaged system
753 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
754 state prior to running a Bacula backup with the following command:
758 ntbackup backup systemstate /F c:\systemstate.bkf
762 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
763 system state and not all the user files, and the {\bf /F
764 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
765 this file must then be saved and restored by Bacula.
767 To restore the system state, you first reload a base operating system if the
768 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
769 restore all the damaged or lost user's files and to recover the {\bf
770 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
771 missing system files or registry problems, you run {\bf NTBackup} and {\bf
772 catalogue} the system statefile, and then select it for restore. The
773 documentation says you can't run a command line restore of the systemstate.
775 To the best of my knowledge, this has not yet been tested. If you test it,
776 please report your results to the Bacula email list.
778 Note, Bacula uses VSS to backup and restore open files and
779 system files, but on older Windows machines such as WinNT and
780 Win2000, VSS is not implemented by Microsoft so that you must
781 use some special techniques to back them up as described
782 above. On new Windows machines, Bacula will backup and restore
783 all files including the system state providing you have
784 VSS enabled in your Bacula FileSet (default).
786 \section{Fixing the Windows Boot Record}
787 \index[general]{Fixing the Windows Boot Record}
788 \index[general]{Windows!Fixing the Boot Record}
790 An effective way to restore a Windows backup for
791 those who do not purchase the bare metal restore
792 capability is to install Windows on a different
793 hard drive and restore the backup. Then run the
809 \section{Considerations for Filename Specifications}
810 \index[general]{Windows!Considerations for Filename Specifications}
813 \ilink{Director's Configuration chapter}{win32} of this manual
814 for important considerations on how to specify Windows paths in Bacula FileSet
815 Include and Exclude directives.
817 \index[general]{Unicode}
818 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
819 As of that version, both {\bf bconsole} and {\bf bwx-console} support Windows
820 Unicode filenames. There may still be some problems with multiple byte
821 characters (e.g. Chinese, ...) where it is a two byte character but the
822 displayed character is not two characters wide.
824 \index[general]{Windows Path Length Restriction}
825 Path/filenames longer than 260 characters (up to 32,000) are supported
826 beginning with Bacula version 1.39.20. Older Bacula versions support
827 only 260 character path/filenames.
829 \section{Windows Specific File daemon Command Line}
830 \index[general]{Client!Windows Specific File daemon Command Line Options}
831 \index[general]{Windows Specific File daemon Command Line Options}
833 These options are not normally seen or used by the user, and are documented
834 here only for information purposes. At the current time, to change the default
835 options, you must either manually run {\bf Bacula} or you must manually edit
836 the system registry and modify the appropriate entries.
838 In order to avoid option clashes between the options necessary for {\bf
839 Bacula} to run on Windows and the standard Bacula options, all Windows
840 specific options are signaled with a forward slash character (/), while as
841 usual, the standard Bacula options are signaled with a minus (-), or a minus
842 minus (\verb:--:). All the standard Bacula options can be used on the Windows
843 version. In addition, the following Windows only options are implemented:
849 Start Bacula as a service
853 Run the Bacula application
857 Install Bacula as a service in the system registry
861 Uninstall Bacula from the system registry
865 Show the Bacula about dialogue box
869 Show the Bacula status dialogue box
873 Show the Bacula events dialogue box (not yet implemented)
877 Stop any running {\bf Bacula}
881 Show the Bacula help dialogue box
884 It is important to note that under normal circumstances the user should never
885 need to use these options as they are normally handled by the system
886 automatically once Bacula is installed. However, you may note these options in
887 some of the .bat files that have been created for your use.
889 \section{Shutting down Windows Systems}
890 \index[general]{Shutting down Windows Systems}
891 \index[general]{Systems!Shutting down Windows}
893 Some users like to shutdown their Windows machines after a backup using a
894 Client Run After Job directive. If you want to do something similar, you might
895 take the shutdown program from the
896 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
897 \elink{Sysinternals project}
898 {http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.