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