4 \section*{The Windows Version of Bacula}
6 \index[general]{Windows Version of Bacula}
7 \addcontentsline{toc}{section}{Windows Version of Bacula}
10 \index[general]{General}
11 \addcontentsline{toc}{subsection}{General}
13 At the current time only the File daemon or Client program has been tested on
14 Windows. As a consequence, when we speak of the Windows version of Bacula
15 below, we are referring to the File daemon only. Please note that as of
16 version 1.39.20, the installer is capable of installing not just the Client
17 program, but also the Director and the Storage daemon and all the other
18 programs that were previously available only on Unix systems.
20 The Windows version of the Bacula File daemon has been tested on Win98, WinMe,
21 WinNT, WinXP, Win2000, and Windows 2003 systems. We have coded to support
22 Win95, but no longer have a system for testing. The Windows version of
23 Bacula is a native Win32 port, but there are very few source code changes
24 to the Unix code, which means that the Windows version is for the most part
25 running code that has long proved stable on Unix systems. When running, it
26 is perfectly integrated with Windows and displays its icon in the system
27 icon tray, and provides a system tray menu to obtain additional information
28 on how Bacula is running (status and events dialog boxes). If so desired,
29 it can also be stopped by using the system tray menu, though this should
30 normally never be necessary.
32 Once installed Bacula normally runs as a system service. This means that it is
33 immediately started by the operating system when the system is booted, and
34 runs in the background even if there is no user logged into the system.
36 \subsection*{Win32 Installation}
38 \index[general]{Installation}
39 \index[general]{Win32!Installation}
40 \addcontentsline{toc}{subsection}{Win32 Installation}
42 Normally, you will install the Windows version of Bacula from the binaries.
43 This install is standard Windows .exe that runs an install wizard using the
44 NSIS Free Software installer, so if you have already installed Windows
45 software, it should be very familiar to you.
47 If you have a previous version Bacula (1.39.20 or lower)
48 installed, you should stop the service, uninstall it, and remove
49 the Bacula installation directory possibly saving your
50 bacula-fd.conf, bconsole.conf, and wx-console.conf files
51 for use with the new version you will install. The Uninstall
52 program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
53 We also recommend that you completely remove the directory
54 {\bf c:\textbackslash{}bacula}, because the current installer
55 uses a different directory structure (see below).
57 Providing you do not already have Bacula installed,
58 the new installer (1.39.22 and later) installs the binaries and dlls in
59 c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
60 and the configuration files
61 in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
62 In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
63 will be created during the installation, and on that menu, you
64 will find items for editing the configuration files, displaying
65 the document, and starting wx-console or bconsole.
68 Finally, proceed with the installation.
71 \item You must be logged in as Administrator to do a correct installation,
72 if not, please do so before continuing.
74 \item Simply double click on the {\bf winbacula-1.xx.0.exe} NSIS install
75 icon. The actual name of the icon will vary from one release version to
78 \includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe
80 \item Once launched, the installer wizard will ask you if you want to install
83 \addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
84 \includegraphics{./win32-welcome.eps}
86 \item Next you will be asked to select the installation type.
88 \addcontentsline{lof}{figure}{Win32 Installation Type}
89 \includegraphics{./win32-installation-type.eps}
92 \item If you proceed, you will be asked to select the components to be
93 installed. You may install the Bacula program (Bacula File Service) and or
94 the documentation. Both will be installed in sub-directories of the install
95 location that you choose later. The components dialog looks like the
98 \addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
99 \includegraphics{./win32-pkg.eps}
101 \item If you are installing for the first time, you will be asked to
102 enter some very basic information about your configuration. If
103 you are not sure what to enter, or have previously saved configuration
104 files, you can put anything you want into the fields, then either
105 replace the configuration files later with the ones saved, or edit
108 If you are upgrading an existing installation, the following will
112 \addcontentsline{lof}{figure}{Win32 Configure}
113 \includegraphics{./win32-config.eps}
115 \item While the various files are being loaded, you will see the following
118 \addcontentsline{lof}{figure}{Win32 Install Progress}
119 \includegraphics{./win32-installing.eps}
122 \item Finally, the finish dialog will appear:
124 \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
125 \includegraphics{./win32-finish.eps}
130 That should complete the installation process. When the Bacula File Server is
131 ready to serve files, an icon \includegraphics{./idle.eps} representing a
132 cassette (or tape) will appear in the system tray
133 \includegraphics{./tray-icon.eps}; right click on it and a menu will appear.\\
134 \includegraphics{./menu.eps}\\
135 The {\bf Events} item is currently unimplemented, by selecting the {\bf
136 Status} item, you can verify whether any jobs are running or not.
138 When the Bacula File Server begins saving files, the color of the holes in the
139 cassette icon will change from white to green \includegraphics{./running.eps},
140 and if there is an error, the holes in the cassette icon will change to red
141 \includegraphics{./error.eps}.
143 If you are using remote desktop connections between your windows boxes, be
144 warned that that tray icon does not always appear. It will always be visible
145 when you log into the console, but the remote desktop may not display it.
147 \subsection*{Post Win32 Installation}
148 \index[general]{Post Win32 Installation}
149 \index[general]{Win32!Post Installation}
150 \addcontentsline{toc}{subsection}{Post Win32 Installation}
152 After installing Bacula and before running it, you should check the contents
153 of the configuration files to ensure that they correspond to your
154 installation. You can get to them by using:
155 the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
157 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
158 is running as a process (not an Application) with User Name SYSTEM. If this is
159 not the case, you probably have not installed Bacula while running as
160 Administrator, and hence it will be unlikely that Bacula can access
161 all the system files.
163 \subsection*{Uninstalling Bacula on Win32}
164 \index[general]{Win32!Uninstalling Bacula}
165 \index[general]{Uninstalling Bacula on Win32}
166 \addcontentsline{toc}{subsection}{Uninstalling Bacula on Win32}
168 Once Bacula has been installed, it can be uninstalled using the standard
169 Windows Add/Remove Programs dialog found on the Control panel.
171 \subsection*{Dealing with Win32 Problems}
173 \index[general]{Win32!Dealing with Problems}
174 \index[general]{Dealing with Win32 Problems}
175 \addcontentsline{toc}{subsection}{Dealing with Win32 Problems}
177 The most likely source of problems is authentication when the Director
178 attempts to connect to the File daemon that you installed. This can occur if
179 the names and the passwords defined in the File daemon's configuration file
180 {\bf bacula-fd.conf} file on
181 the Windows machine do not match with the names and the passwords in the
182 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
185 More specifically, the password found in the {\bf Client} resource in the
186 Director's configuration file must be the same as the password in the {\bf
187 Director} resource of the File daemon's configuration file. In addition, the
188 name of the {\bf Director} resource in the File daemon's configuration file
189 must be the same as the name in the {\bf Director} resource of the Director's
192 It is a bit hard to explain in words, but if you understand that a Director
193 normally has multiple Clients and a Client (or File daemon) may permit access
194 by multiple Directors, you can see that the names and the passwords on both
195 sides must match for proper authentication.
197 One user had serious problems with the configuration file until he realized
198 that the Unix end of line conventions were used and Bacula wanted them in
199 Windows format. This has not been confirmed though.
201 Running Unix like programs on Windows machines is a bit frustrating because
202 the Windows command line shell (DOS Window) is rather primitive. As a
203 consequence, it is not generally possible to see the debug information and
204 certain error messages that Bacula prints. With a bit of work, however, it is
205 possible. When everything else fails and you want to {\bf see} what is going
206 on, try the following:
210 Start a DOS shell Window.
211 c:\Program Files\bacula\bin\bacula-fd -t >out
216 The precise path to bacula-fd depends on where it is installed. The
217 example above is the default used in 1.39.22 and later.
218 The {\bf -t} option will cause Bacula to read the configuration file, print
219 any error messages and then exit. the {\bf \gt{}} redirects the output to the
220 file named {\bf out}, which you can list with the {\bf type} command.
222 If something is going wrong later, or you want to run {\bf Bacula} with a
223 debug option, you might try starting it as:
227 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
231 In this case, Bacula will run until you explicitly stop it, which will give
232 you a chance to connect to it from your Unix/Linux server. In later versions
233 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
234 can write the output to a trace file {\bf bacula.trace} in the current
235 directory. To enable this, before running a job, use the console, and enter:
243 then run the job, and once you have terminated the File daemon, you will find
244 the debug output in the {\bf bacula.trace} file, which will probably be
245 located in the same directory as bacula-fd.exe.
247 In addition, you should look in the System Applications log on the Control
248 Panel to find any Windows errors that Bacula got during the startup process.
250 Finally, due to the above problems, when you turn on debugging, and specify
251 trace=1 on a setdebug command in the Console, Bacula will write the debug
252 information to the file {\bf bacula.trace} in the directory from which Bacula
255 If you are having problems with ClientRunBeforeJob scripts randomly dying,
256 it is possible that you have run into an Oracle bug. See bug number 622 in
257 the bugs.bacula.org database. The following information has been
258 provided by a user on this issue:
262 The information in this document applies to:
263 Oracle HTTP Server - Version: 9.0.4
264 Microsoft Windows Server 2003
266 When starting an OC4J instance, the System Clock runs faster, about 7
271 + This is caused by the Sun JVM bug 4500388, which states that "Calling
272 Thread.sleep() with a small argument affects the system clock". Although
273 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
275 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
277 + Also reported by Microsoft as "The system clock may run fast when you
278 use the ACPI power management timer as a high-resolution counter on Windows
279 2000-based computers" (See http://support.microsoft.com/?id=821893)
283 \label{Compatibility}
284 \subsection*{Windows Compatibility Considerations}
285 \index[general]{Windows Compatibility Considerations}
286 \index[general]{Considerations!Windows Compatibility}
287 \addcontentsline{toc}{subsection}{Windows Compatibility Considerations}
289 If you are not using the VSS (Volume Shadow Copy) option described in the
290 next section of this chapter, and if any applications are running during
291 the backup and they have files opened exclusively, Bacula will not be able
292 to backup those files, so be sure you close your applications (or tell your
293 users to close their applications) before the backup. Fortunately, most
294 Microsoft applications do not open files exclusively so that they can be
295 backed up. However, you will need to experiment. In any case, if Bacula
296 cannot open the file, it will print an error message, so you will always
297 know which files were not backed up. For version 1.37.25 and greater, see
298 the section below on Volume Shadow Copy Service that permits backing up any
301 During backup, Bacula doesn't know about the system registry, so you will
302 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
303 program specifically designed to make a copy or backup the registry.
305 In Bacula version 1.31 and later, we use Windows backup API calls by
306 default. Typical of Windows, programming these special BackupRead and
307 BackupWrite calls is a real nightmare of complications. The end result
308 gives some distinct advantages and some disadvantages.
310 First, the advantages are that on WinNT/2K/XP systems, the security and
311 ownership information is now backed up. In addition, with the exception of
312 files in exclusive use by another program, Bacula can now access all system
313 files. This means that when you restore files, the security and ownership
314 information will be restored on WinNT/2K/XP along with the data.
316 The disadvantage of the Windows backup API calls is that it produces
317 non-portable backups. That is files and their data that are backed up on
318 WinNT using the native API calls (BackupRead/BackupWrite) cannot be
319 restored on Win95/98/Me or Unix systems. In principle, a file backed up on
320 WinNT can be restored on WinXP, but this remains to be seen in practice
321 (not yet tested). In addition, the stand-alone tools such as {\bf bls} and
322 {\bf bextract} cannot be used to retrieve the data for those files because
323 those tools are not available on Windows. All restores must use the Bacula
324 {\bf restore} command. As of Bacula 1.39.x, thanks to Thorsten Engel, this
325 restriction is removed, and Bacula should be able to read non-portable
326 backups on any system and restore the data appropriately. However,
327 on a system that does not have the BackupRead/BackupWrite calls (older
328 Windows versions and all Unix/Linux machines), though the file data
329 can be restored, the Windows security and access control data will not be restored.
330 This means that a standard set of access permissions will be set for
334 As a default, Bacula backs up Windows systems using the Windows API calls.
335 If you want to backup data on a WinNT/2K/XP system and restore it on a
336 Unix/Win95/98/Me system, we have provided a special {\bf portable} option
337 that backs up the data in a portable fashion by using portable API calls.
338 See the \ilink{portable option}{portable} on the Include statement in a
339 FileSet resource in the Director's configuration chapter for the details on
340 setting this option. However, using the portable option means you may have
341 permissions problems accessing files, and none of the security and
342 ownership information will be backed up or restored. The file data can,
343 however, be restored on any system.
345 You should always be able to restore any file backed up on Unix or Win95/98/Me
346 to any other system. On some systems, such as WinNT/2K/XP, you may have to
347 reset the ownership of such restored files. Any file backed up on WinNT/2K/XP
348 should in principle be able to be restored to a similar system (i.e.
349 WinNT/2K/XP), however, I am unsure of the consequences if the owner
350 information and accounts are not identical on both systems. Bacula will not
351 let you restore files backed up on WinNT/2K/XP to any other system (i.e. Unix
352 Win95/98/Me) if you have used the defaults.
354 Finally, if you specify the {\bf portable=yes} option on the files you back
355 up. Bacula will be able to restore them on any other system. However, any
356 WinNT/2K/XP specific security and ownership information will be lost.
358 The following matrix will give you an idea of what you can expect. Thanks to
359 Marc Brueckner for doing the tests:
361 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
362 \begin{longtable}{|l|l|p{2.8in}|}
364 \multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
365 & \multicolumn{1}{c|}{\bf Results } \\
366 \hline {WinMe} & {WinMe} & {Works } \\
367 \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
368 \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
369 \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
370 \hline {\ } & {\ } & {\ } \\
371 \hline {WinXP} & {WinXP} & {Works } \\
372 \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
374 \hline {WinXP} & {WinMe} & {Error: Win32 data stream not supported. } \\
375 \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
376 \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
377 \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
378 \hline {\ } & {\ } & {\ } \\
379 \hline {WinNT} & {WinNT} & {Works } \\
380 \hline {WinNT} & {WinXP} & {Works } \\
381 \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
382 \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
383 \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
384 \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
385 \hline {\ } & {\ } & {\ } \\
386 \hline {Linux} & {Linux} & {Works } \\
387 \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
388 \hline {Linux} & {WinMe} & {Works } \\
389 \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
393 Note: with Bacula versions 1.39.x and later, non-portable Windows data can
394 be restore to any machine.
398 \subsection*{Volume Shadow Copy Service}
399 \index[general]{Volume Shadow Copy Service}
401 \addcontentsline{toc}{subsection}{Volume Shadow Copy Service}
402 In version 1.37.30 and greater, you can turn on Microsoft's Volume
403 Shadow Copy Service (VSS).
405 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
406 a backup-solution for Windows, this is an extremely important step. VSS
407 allows Bacula to backup open files and even to interact with applications like
408 RDBMS to produce consistent file copies. VSS aware applications are called
409 VSS Writers, they register with the OS so that when Bacula wants to do a
410 Snapshot, the OS will notify the register Writer programs, which may then
411 create a consistent state in their application, which will be backed up.
412 Examples for these writers are "MSDE" (Microsoft database
413 engine), "Event Log Writer", "Registry Writer" plus 3rd
414 party-writers. If you have a non-vss aware application (e.g.
415 SQL Anywhere or probably MySQL), a shadow copy is still generated
416 and the open files can be backed up, but there is no guarantee
417 that the file is consistent.
419 Bacula produces a message from each of the registered writer programs
420 when it is doing a VSS backup so you know which ones are correctly backed
423 Bacula supports VSS on both Windows 2003 and Windows XP.
424 Technically Bacula creates a shadow copy as soon as the backup process
425 starts. It does then backup all files from the shadow copy and destroys the
426 shadow copy after the backup process. Please have in mind, that VSS
427 creates a snapshot and thus backs up the system at the state it had
428 when starting the backup. It will disregard file changes which occur during
431 VSS can be turned on by placing an
433 \index[dir]{Enable VSS}
434 \index[general]{Enable VSS}
439 in your FileSet resource.
441 The VSS aware File daemon has the letters VSS on the signon line that
442 it produces when contacted by the console. For example:
444 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
446 the VSS is shown in the line above. This only means that the File daemon
447 is capable of doing VSS not that VSS is turned on for a particular backup.
448 There are two ways of telling if VSS is actually turned on during a backup.
449 The first is to look at the status output for a job, e.g.:
453 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
454 VSS Backup Job started: 23-Jul-05 13:25
455 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
456 Files Examined=75,021
457 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
461 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
462 This means that VSS is enabled for that job. If VSS is not enabled, it will
463 simply show "Backup Job started ..." without the letters VSS.
465 The second way to know that the job was backed up with VSS is to look at the
466 Job Report, which will look something like the following:
469 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
470 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
471 23-Jul 13:26 rufus-sd: Spooling data ...
472 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
473 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
474 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
475 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
476 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
479 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
480 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
481 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
482 that you will get a consistent snapshot of the data handled by that writer.
484 \subsection*{VSS Problems}
485 \index[general]{Problems!VSS}
486 \index[fd] {Problems!VSS}
487 \index[general]{VSS Problems}
488 \index[fd]{VSS Problems}
489 \addcontentsline{toc}{subsection}{VSS Problems}
491 If you are experiencing problems such as VSS hanging on MSDE, first try
492 running {\bf vssadmin} to check for problems, then try running {\bf
493 ntbackup} which also uses VSS to see if it has similar problems. If so, you
494 know that the problem is in your Windows machine and not with Bacula.
496 The FD hang problems were reported with {\bf MSDEwriter} when:
498 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
499 seems to use TCP/IP and not Named Pipes).
500 \item msdtcs was installed to run under "localsystem": try running msdtcs
501 under networking account (instead of local system) (com+ seems to work
502 better with this configuration).
506 \subsection*{Windows Firewalls}
507 \index[general]{Firewalls!Windows}
508 \index[general]{Windows Firewalls}
509 \addcontentsline{toc}{subsection}{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 \subsection*{Windows Port Usage}
530 \index[general]{Windows Port Usage}
531 \index[general]{Usage!Windows Port}
532 \addcontentsline{toc}{subsection}{Windows Port Usage}
534 If you want to see if the File daemon has properly opened the port and is
535 listening, you can enter the following command in a shell window:
539 netstat -an | findstr 910[123]
543 \subsection*{Windows Disaster Recovery}
544 \index[general]{Recovery!Windows Disaster}
545 \index[general]{Windows Disaster Recovery}
546 \addcontentsline{toc}{subsection}{Windows Disaster Recovery}
548 We don't currently have a good solution for disaster recovery on Windows as we
549 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
550 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
551 that could possibly work, but we have not investigated it. This means that
552 until someone figures out the correct procedure, you must restore the OS from
553 the installation disks, then you can load a Bacula client and restore files.
554 Please don't count on using {\bf bextract} to extract files from your backup
555 tapes during a disaster recovery unless you have backed up those files using
556 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
557 normal way Bacula saves files using the Windows API prevents the files from
558 being restored on a Unix machine. Once you have an operational Windows OS
559 loaded, you can run the File daemon and restore your user files.
562 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
563 suggestion, which looks very promising.
565 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
566 Environment) Boot-CD, may be just what is needed to build a complete disaster
567 recovery system for Win32. This distribution can be found at
568 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
570 \subsection*{Windows Restore Problems}
571 \index[general]{Problems!Windows Restore}
572 \index[general]{Windows Restore Problems}
573 \addcontentsline{toc}{subsection}{Windows Restore Problems}
575 \ilink{Restore Chapter}{Windows} of this manual for problems
576 that you might encounter doing a restore.
578 subsection*{Windows Backup Problems}
579 \index[general]{Problems!Windows Backup}
580 \index[general]{Windows Backup Problems}
581 \addcontentsline{toc}{subsection}{Windows Backup Problems}
582 If during a Backup, you get the message:
583 {\bf ERR=Access is denied} and you are using the portable option,
584 you should try both adding both the non-portable (backup API) and
585 the Volume Shadow Copy options to your Director's conf file.
587 In the Options resource:
594 In the FileSet resource:
601 In general, specifying these two options should allow you to backup
602 any file on a Windows system. However, in some cases, if users
603 have allowed to have full control of their folders, even system programs
604 such a Bacula can be locked out. In this case, you must identify
605 which folders or files are creating the problem and do the following:
608 \item Grant ownership of the file/folder to the Administrators group,
609 with the option to replace the owner on all child objects.
610 \item Grant full control permissions to the Administrators group,
611 and change the user's group to only have Modify permission to
612 the file/folder and all child objects.
614 Thanks to Georger Araujo for the above information.
616 \subsection*{Windows Ownership and Permissions Problems}
617 \index[general]{Problems!Windows Ownership and Permissions}
618 \index[general]{Windows Ownership and Permissions Problems}
619 \addcontentsline{toc}{subsection}{Windows Ownership and Permissions
622 If you restore files backed up from WinNT/XP/2K to an alternate directory,
623 Bacula may need to create some higher level directories that were not saved
624 (or restored). In this case, the File daemon will create them under the SYSTEM
625 account because that is the account that Bacula runs under as a service. As of
626 version 1.32f-3, Bacula creates these files with full access permission.
627 However, there may be cases where you have problems accessing those files even
628 if you run as administrator. In principle, Microsoft supplies you with the way
629 to cease the ownership of those files and thus change the permissions.
630 However, a much better solution to working with and changing Win32 permissions
631 is the program {\bf SetACL}, which can be found at
632 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
634 If you have not installed Bacula while running as Administrator
635 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
636 then it is very unlikely that it will have sufficient permission to
637 access all your files.
639 Some users have experienced problems restoring files that participate in
640 the Active Directory. They also report that changing the userid under which
641 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
645 \subsection*{Manually resetting the Permissions}
646 \index[general]{Manually resetting the Permissions}
647 \index[general]{Permissions!Manually resetting the}
648 \addcontentsline{toc}{subsection}{Manually resetting the Permissions}
650 The following solution was provided by Dan Langille \lt{}dan at langille in
651 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
652 they should apply to most Win32 platforms. The procedure outlines how to deal
653 with a problem which arises when a restore creates a top-level new directory.
654 In this example, "top-level" means something like {\bf
655 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
656 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
657 as the {\bf Where:} value, this problem will arise.
659 The problem appears as a directory which cannot be browsed with Windows
660 Explorer. The symptoms include the following message when you try to click on
663 \includegraphics{./access-is-denied.eps}
665 If you encounter this message, the following steps will change the permissions
666 to allow full access.
669 \item right click on the top level directory (in this example, {\bf c:/src})
670 and select {\bf Properties}.
671 \item click on the Security tab.
672 \item If the following message appears, you can ignore it, and click on {\bf
675 \includegraphics{./view-only.eps}
677 You should see something like this:
679 \includegraphics{./properties-security.eps}
680 \item click on Advanced
681 \item click on the Owner tab
682 \item Change the owner to something other than the current owner (which is
683 {\bf SYSTEM} in this example as shown below).
685 \includegraphics{./properties-security-advanced-owner.eps}
686 \item ensure the "Replace owner on subcontainers and objects" box is
689 \item When the message "You do not have permission to read the contents of
690 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
691 the directory permissions with permissions granting you Full Control?", click
694 \includegraphics{./confirm.eps}
695 \item Click on OK to close the Properties tab
698 With the above procedure, you should now have full control over your restored
701 In addition to the above methods of changing permissions, there is a Microsoft
702 program named {\bf cacls} that can perform similar functions.
704 \subsection*{Backing Up the WinNT/XP/2K System State}
705 \index[general]{State!Backing Up the WinNT/XP/2K System}
706 \index[general]{Backing Up the WinNT/XP/2K System State}
707 \addcontentsline{toc}{subsection}{Backing Up the WinNT/XP/2K System State}
709 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
710 conjunction with Bacula should permit a full restore of any damaged system
711 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
712 state prior to running a Bacula backup with the following command:
716 ntbackup backup systemstate /F c:\systemstate.bkf
720 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
721 system state and not all the user files, and the {\bf /F
722 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
723 this file must then be saved and restored by Bacula.
725 To restore the system state, you first reload a base operating system if the
726 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
727 restore all the damaged or lost user's files and to recover the {\bf
728 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
729 missing system files or registry problems, you run {\bf NTBackup} and {\bf
730 catalogue} the system statefile, and then select it for restore. The
731 documentation says you can't run a command line restore of the systemstate.
733 To the best of my knowledge, this has not yet been tested. If you test it,
734 please report your results to the Bacula email list.
736 \subsection*{Windows Considerations for Filename Specifications}
737 \index[general]{Specifications!Windows Considerations for Filename}
738 \index[general]{Windows Considerations for Filename Specifications}
739 \addcontentsline{toc}{subsection}{Windows Considerations for Filename
743 \ilink{Director's Configuration chapter}{win32} of this manual
744 for important considerations on how to specify Windows paths in Bacula FileSet
745 Include and Exclude directives.
747 \index[general]{Unicode}
748 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
749 As of that version, both {\bf bconsole} and {\bf wx-console} support Windows
750 Unicode filenames. There may still be some problems with multiple byte
751 characters (e.g. Chinese, ...) where it is a two byte character but the
752 displayed character is not two characters wide.
754 \index[general]{Win32 Path Length Restriction}
755 Path/filenames longer than 260 characters (up to 32,000) are supported
756 beginning with Bacula version 1.39.20.
758 \subsection*{Win32 Specific File daemon Command Line Options}
759 \index[general]{Client!Win32 Specific File daemon Command Line Options}
760 \index[general]{Win32 Specific File daemon Command Line Options}
761 \addcontentsline{toc}{subsection}{Win32 Specific File daemon Command Line
764 These options are not normally seen or used by the user, and are documented
765 here only for information purposes. At the current time, to change the default
766 options, you must either manually run {\bf Bacula} or you must manually edit
767 the system registry and modify the appropriate entries.
769 In order to avoid option clashes between the options necessary for {\bf
770 Bacula} to run on Windows and the standard Bacula options, all Windows
771 specific options are signaled with a forward slash character (/), while as
772 usual, the standard Bacula options are signaled with a minus (-), or a minus
773 minus (\verb:--:). All the standard Bacula options can be used on the Windows
774 version. In addition, the following Windows only options are implemented:
780 Start Bacula as a service
784 Run the Bacula application
788 Install Bacula as a service in the system registry
792 Uninstall Bacula from the system registry
796 Show the Bacula about dialogue box
800 Show the Bacula status dialogue box
804 Show the Bacula events dialogue box (not yet implemented)
808 Stop any running {\bf Bacula}
812 Show the Bacula help dialogue box
815 It is important to note that under normal circumstances the user should never
816 need to use these options as they are normally handled by the system
817 automatically once Bacula is installed. However, you may note these options in
818 some of the .bat files that have been created for your use.
820 \subsection*{Shutting down Windows Systems}
821 \index[general]{Shutting down Windows Systems}
822 \index[general]{Systems!Shutting down Windows}
823 \addcontentsline{toc}{subsection}{Shutting down Windows Systems}
825 Some users like to shutdown their windows machines after a backup using a
826 Client Run After Job directive. If you want to do something similar, you might
827 take the shutdown program from the
828 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
829 \elink{Sysinternals project}{http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml}.