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.
17 The Windows version of the Bacula File daemon has been tested on Win98, WinMe,
18 WinNT, and Win2000 systems. We have coded to support Win95, but no longer have
19 a system for testing. The Windows version of Bacula is a native Win32 port,
20 but there are very few source code changes to the Unix code, which means that the Windows
21 version is for the most part running code that has long proved stable on Unix
22 systems. When running, it is perfectly integrated with Windows and displays
23 its icon in the system icon tray, and provides a system tray menu to obtain
24 additional information on how Bacula is running (status and events dialog
25 boxes). If so desired, it can also be stopped by using the system tray menu,
26 though this should normally never be necessary.
28 Once installed Bacula normally runs as a system service. This means that it is
29 immediately started by the operating system when the system is booted, and
30 runs in the background even if there is no user logged into the system.
32 \subsection*{Win32 Installation}
34 \index[general]{Installation }
35 \index[general]{Win32!Installation }
36 \addcontentsline{toc}{subsection}{Win32 Installation}
38 Normally, you will install the Windows version of Bacula from the binaries.
39 This install is standard Windows .exe that runs an install wizard using the
40 NSIS Free Software installer, so if you have already installed Windows
41 software, it should be very familiar to you.
43 If you have a previous version Cygwin of Bacula (1.32 or lower)
44 installed, you should stop the service, uninstall it, and remove
45 the Bacula installation directory possibly saving your
46 bacula-fd.conf file for use with the new version you will
47 install. Current versions of Bacula do not use Cygwin and has
48 far fewer files than the old Cygwin version, so it is better to
49 start with a clean directory.
51 Finally, proceed with the installation.
54 \item You must be logged in as Administrator to do a correct installation,
55 if not, please do so before continuing.
57 \item Simply double click on the {\bf winbacula-1.xx.0.exe} NSIS install
58 icon. The actual name of the icon will vary from one release version to
61 \includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe
63 \item Once launched, the installer wizard will ask you if you want to install
66 \addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
67 \includegraphics{./win32-welcome.eps}
69 \item If you proceed, you will be asked to select the components to be
70 installed. You may install the Bacula program (Bacula File Service) and or
71 the documentation. Both will be installed in sub-directories of the install
72 location that you choose later. The components dialog looks like the
75 \addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
76 \includegraphics{./win32-pkg.eps}
78 \item Next you will be asked to select an installation directory.
80 \addcontentsline{lof}{figure}{Win32 Directory Selection Dialog}
81 \includegraphics{./win32-location.eps}
83 \item If you are installing for the first time, you will be asked if you want
84 to edit the bacula-fd.conf file, and if you respond with yes, it will be
85 opened in notepad. Note, if you have installed Bacula to a drive other
86 than C: you probably should prefix the installation drive name to each
87 of the directory references in the bacula-fd.conf file, in particular
88 the {\bf WorkingDirectory} and the {\bf Pid Directory} directives.
90 Also, if you do not wish to see the full listing of all files restored
91 in the job output after running a restore job, you can add {\bf ,
92 !restored} to the {\bf director} directive in the {\bf Messages}
95 \item Then the installer will ask if you wish to install Bacula as a service. You
96 should always choose to do so:
98 \addcontentsline{lof}{figure}{Win32 Client Service Selection}
99 \includegraphics{./win32-service.eps}
102 \item If everything goes well, you will receive the following confirmation:
104 \addcontentsline{lof}{figure}{Win32 Client Service Confirmation}
105 \includegraphics{./win32-service-ok.eps}
108 \item Then you will be asked if you wish to start the service. If you respond
109 with yes, any running Bacula will be shutdown and the new one started. You
110 may see a DOS box momentarily appear on the screen as the service is started.
111 It should disappear in a second or two:
113 \addcontentsline{lof}{figure}{Win32 Client Start}
114 \includegraphics{./win32-start.eps}
117 \item Finally, the finish dialog will appear:
118 \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
119 \includegraphics{./win32-finish.eps}
124 That should complete the installation process. When the Bacula File Server is
125 ready to serve files, an icon \includegraphics{./idle.eps} representing a
126 cassette (or tape) will appear in the system tray
127 \includegraphics{./tray-icon.eps}; right click on it and a menu will appear.\\
128 \includegraphics{./menu.eps}\\
129 The {\bf Events} item is currently unimplemented, by selecting the {\bf
130 Status} item, you can verify whether any jobs are running or not.
132 When the Bacula File Server begins saving files, the color of the holes in the
133 cassette icon will change from white to green \includegraphics{./running.eps},
134 and if there is an error, the holes in the cassette icon will change to red
135 \includegraphics{./error.eps}.
137 If you are using remote desktop connections between your windows boxes, be
138 warned that that tray icon does not always appear. It will always be visible
139 when you log into the console, but the remote desktop may not display it.
141 \subsection*{Post Win32 Installation}
142 \index[general]{Post Win32 Installation }
143 \index[general]{Win32!Post Installation }
144 \addcontentsline{toc}{subsection}{Post Win32 Installation}
146 After installing Bacula and before running it, you should check the contents
148 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} to
149 ensure that it corresponds to your configuration.
151 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
152 is running as a process (not an Application) with User Name SYSTEM. If this is
153 not the case, you probably have not installed Bacula while running as
154 Administrator, and hence it will be unlikely that Bacula can access
155 all the system files.
157 \subsection*{Uninstalling Bacula on Win32}
158 \index[general]{Win32!Uninstalling Bacula }
159 \index[general]{Uninstalling Bacula on Win32 }
160 \addcontentsline{toc}{subsection}{Uninstalling Bacula on Win32}
162 Once Bacula has been installed, it can be uninstalled using the standard
163 Windows Add/Remove Programs dialog found on the Control panel.
165 \subsection*{Dealing with Win32 Problems}
167 \index[general]{Win32!Dealing with Problems }
168 \index[general]{Dealing with Win32 Problems }
169 \addcontentsline{toc}{subsection}{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
175 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} on
176 the Windows machine do not match with the names and the passwords in the
177 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
180 More specifically, the password found in the {\bf Client} resource in the
181 Director's configuration file must be the same as the password in the {\bf
182 Director} resource of the File daemon's configuration file. In addition, the
183 name of the {\bf Director} resource in the File daemon's configuration file
184 must be the same as the name in the {\bf Director} resource of the Director's
187 It is a bit hard to explain in words, but if you understand that a Director
188 normally has multiple Clients and a Client (or File daemon) may permit access
189 by multiple Directors, you can see that the names and the passwords on both
190 sides must match for proper authentication.
192 One user had serious problems with the configuration file until he realized
193 that the Unix end of line conventions were used and Bacula wanted them in
194 Windows format. This has not been confirmed though.
196 Running Unix like programs on Windows machines is a bit frustrating because
197 the Windows command line shell (DOS Window) is rather primitive. As a
198 consequence, it is not generally possible to see the debug information and
199 certain error messages that Bacula prints. With a bit of work, however, it is
200 possible. When everything else fails and you want to {\bf see} what is going
201 on, try the following:
205 Start a DOS shell Window.
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 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.
240 In addition, you should look in the System Applications log on the Control
241 Panel to find any Windows errors that Bacula got during the startup process.
243 Finally, due to the above problems, when you turn on debugging, and specify
244 trace=1 on a setdebug command in the Console, Bacula will write the debug
245 information to the file {\bf bacula.trace} in the directory from which Bacula
248 \label{Compatibility}
249 \subsection*{Windows Compatibility Considerations}
250 \index[general]{Windows Compatibility Considerations }
251 \index[general]{Considerations!Windows Compatibility }
252 \addcontentsline{toc}{subsection}{Windows Compatibility Considerations}
254 If any applications are running during the backup and they have files
255 opened exclusively, Bacula will not be able to backup those files, so be
256 sure you close your applications (or tell your users to close their
257 applications) before the backup. Fortunately,
258 most Microsoft applications do not open
259 files exclusively so that they can be backed up. However, you will need to
260 experiment. In any case, if Bacula cannot open the file, it will print an
261 error message, so you will always know which files were not backed up.
262 For version 1.37.25 and greater, see the section below on
263 Volume Shadow Copy Service.
265 During backup, Bacula doesn't know about the system registry, so you will
266 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
267 program specifically designed to make a copy or backup the registry.
269 In Bacula version 1.31 and later, we use Windows backup API calls by
270 default. Typical of Windows, programming these special BackupRead and
271 BackupWrite calls is a real nightmare of complications. The end result
272 gives some distinct advantages and some disadvantages.
274 First, the advantages are that on WinNT/2K/XP systems, the security and
275 ownership information is now backed up. In addition, with the exception of
276 files in exclusive use by another program (a major disaster for backup
277 programs on Windows), Bacula can now access all system files. This means
278 that when you restore files, the security and ownership information will be
279 restored on WinNT/2K/XP along with the data.
281 The disadvantage of the Windows backup API calls is that it produces
282 non-portable backups. That is files and their data that are backed up on
283 WinNT using the native API calls (BackupRead/BackupWrite) cannot be
284 restored on Win95/98/Me or Unix systems. In principle, a file backed up on
285 WinNT can be restored on WinXP, but this remains to be seen in practice
286 (not yet tested). In addition, the stand-alone tools such as {\bf bls} and
287 {\bf bextract} cannot be used to retrieve the data for those files because
288 those tools are not available on Windows. All restores must use the Bacula
289 {\bf restore} command. This restriction is mentioned for completeness, but
290 in practice should not create any problems.
292 As a default, Bacula backs up Windows systems using the Windows API calls.
293 If you want to backup data on a WinNT/2K/XP system and restore it on a
294 Unix/Win95/98/Me system, we have provided a special {\bf portable} option
295 that backs up the data in a portable fashion by using portable API calls.
296 See the \ilink{portable option}{portable} on the Include statement in a
297 FileSet resource in the Director's configuration chapter for the details on
298 setting this option. However, using the portable option means you may have
299 permissions problems accessing files, and none of the security and
300 ownership information will be backed up or restored. The file data can,
301 however, be restored on any system.
303 You should always be able to restore any file backed up on Unix or Win95/98/Me
304 to any other system. On some systems, such as WinNT/2K/XP, you may have to
305 reset the ownership of such restored files. Any file backed up on WinNT/2K/XP
306 should in principle be able to be restored to a similar system (i.e.
307 WinNT/2K/XP), however, I am unsure of the consequences if the owner
308 information and accounts are not identical on both systems. Bacula will not
309 let you restore files backed up on WinNT/2K/XP to any other system (i.e. Unix
310 Win95/98/Me) if you have used the defaults.
312 Finally, if you specify the {\bf portable=yes} option on the files you back
313 up. Bacula will be able to restore them on any other system. However, any
314 WinNT/2K/XP specific security and ownership information will be lost.
316 The following matrix will give you an idea of what you can expect. Thanks to
317 Marc Brueckner for doing the tests:
321 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
322 \begin{longtable}{|l|l|p{2.8in}|}
324 \multicolumn{1}{|c| }{\bf Backup OS } & \multicolumn{1}{c| }{\bf Restore OS }
325 & \multicolumn{1}{c| }{\bf Results } \\
326 \hline {WinMe } & {WinMe } & {Works } \\
327 \hline {WinMe } & {WinNT } & {Works (SYSTEM permissions) } \\
328 \hline {WinMe } & {WinXP } & {Works (SYSTEM permissions) } \\
329 \hline {WinMe } & {Linux } & {Works (SYSTEM permissions) } \\
330 \hline {\ } & {\ } & {\ } \\
331 \hline {WinXP } & {WinXP } & {Works } \\
332 \hline {WinXP } & {WinNT } & {Works (all files OK, but got "The data is invalid"
334 \hline {WinXP } & {WinMe } & {Error: Win32 data stream not supported. } \\
335 \hline {WinXP } & {WinMe } & {Works if {\bf Portable=yes} specified during backup.} \\
336 \hline {WinXP } & {Linux } & {Error: Win32 data stream not supported. } \\
337 \hline {WinXP } & {Linux } & {Works if {\bf Portable=yes} specified during backup.}\\
338 \hline {\ } & {\ } & {\ } \\
339 \hline {WinNT } & {WinNT } & {Works } \\
340 \hline {WinNT } & {WinXP } & {Works } \\
341 \hline {WinNT } & {WinMe } & {Error: Win32 data stream not supported. } \\
342 \hline {WinNT } & {WinMe } & {Works if {\bf Portable=yes} specified during backup.}\\
343 \hline {WinNT } & {Linux } & {Error: Win32 data stream not supported. } \\
344 \hline {WinNT } & {Linux } & {Works if {\bf Portable=yes} specified during backup. }\\
345 \hline {\ } & {\ } & {\ } \\
346 \hline {Linux } & {Linux } & {Works } \\
347 \hline {Linux } & {WinNT } & {Works (SYSTEM permissions) } \\
348 \hline {Linux } & {WinMe } & {Works } \\
349 \hline {Linux } & {WinXP } & {Works (SYSTEM permissions) }
355 \subsection*{Volume Shadow Copy Service}
356 \index[general]{Volume Shadow Copy Service}
358 \addcontentsline{toc}{subsection}{Volume Shadow Copy Service}
359 In version 1.37.30 and greater, you can turn on Microsoft's Volume
360 Shadow Copy Service (VSS).
362 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
363 a backup-solution for Windows, this is an extremely important step. VSS
364 allows Bacula to backup open files and even to interact with applications like
365 RDBMS to produce consistent file copies. VSS aware applications are called
366 VSS Writers, they register with the OS so that when Bacula wants to do a
367 Snapshot, the OS will notify the register Writer programs, which may then
368 create a consistent state in their application, which will be backed up.
369 Examples for these writers are "MSDE" (Microsoft database
370 engine), "Event Log Writer", "Registry Writer" plus 3rd
371 party-writers. If you have a non-vss aware application (e.g.
372 SQL Anywhere or probably MySQL), a shadow copy is still generated
373 and the open files can be backed up, but there is no guarantee
374 that the file is consistent.
376 Bacula produces a message from each of the registered writer programs
377 when it is doing a VSS backup so you know which ones are correctly backed
380 Bacula supports VSS on both Windows 2003 and Windows XP.
381 Technically Bacula creates a shadow copy as soon as the backup process
382 starts. It does then backup all files from the shadow copy and destroys the
383 shadow copy after the backup process. Please have in mind, that VSS
384 creates a snapshot and thus backs up the system at the state it had
385 when starting the backup. It will disregard file changes which occur during
388 VSS can be turned on by placing an
390 \index[dir]{Enable VSS}
391 \index[general]{Enable VSS}
396 in your FileSet resource.
398 Important Note!! Under the current implementation, you may only
399 run a single job at a time in any Win32 File daemon that has VSS
400 active. Running multiple simultanous jobs in the File daemon
401 will most likely cause jobs to fail. This restriction does not apply
402 to the Director, Storage daemons, or any File daemons not running
405 The VSS aware File daemon has the letters VSS on the signon line that
406 it produces when contacted by the console. For example:
408 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
410 the VSS is shown in the line above. This only means that the File daemon
411 is capable of doing VSS not that VSS is turned on for a particular backup.
412 There are two ways of telling if VSS is actually turned on during a backup.
413 The first is to look at the status output for a job, e.g.:
417 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
418 VSS Backup Job started: 23-Jul-05 13:25
419 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
420 Files Examined=75,021
421 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
425 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
426 This means that VSS is enabled for that job. If VSS is not enabled, it will
427 simply show "Backup Job started ..." without the letters VSS.
429 The second way to know that the job was backed up with VSS is to look at the
430 Job Report, which will look something like the following:
433 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
434 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
435 23-Jul 13:26 rufus-sd: Spooling data ...
436 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
437 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
438 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
439 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
440 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
443 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
444 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
445 reports from each of the writer program. Here they all report VSS_WS_STABLE, which means
446 that you will get a consistent snapshot of the data handled by that writer.
448 \subsection*{Windows Firewalls}
449 \index[general]{Firewalls!Windows }
450 \index[general]{Windows Firewalls }
451 \addcontentsline{toc}{subsection}{Windows Firewalls}
453 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
454 are likely to find that the Bacula ports are blocked and you cannot
455 communicate to the other daemons. This can be deactivated through the {\bf
456 Security Notification} dialog, which is apparently somewhere in the {\bf
457 Security Center}. I don't have this on my computer, so I cannot give the exact
464 netsh firewall set opmode disable
468 is purported to disable the firewall, but this command is not accepted on my
471 \subsection*{Windows Port Usage}
472 \index[general]{Windows Port Usage }
473 \index[general]{Usage!Windows Port }
474 \addcontentsline{toc}{subsection}{Windows Port Usage}
476 If you want to see if the File daemon has properly opened the port and is
477 listening, you can enter the following command in a shell window:
481 netstat -an | findstr 910[123]
485 \subsection*{Windows Disaster Recovery}
486 \index[general]{Recovery!Windows Disaster }
487 \index[general]{Windows Disaster Recovery }
488 \addcontentsline{toc}{subsection}{Windows Disaster Recovery}
490 We don't currently have a good solution for disaster recovery on Windows as we
491 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
492 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
493 that could possibly work, but we have not investigated it. This means that
494 until someone figures out the correct procedure, you must restore the OS from
495 the installation disks, then you can load a Bacula client and restore files.
496 Please don't count on using {\bf bextract} to extract files from your backup
497 tapes during a disaster recovery unless you have backed up those files using
498 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
499 normal way Bacula saves files using the Windows API prevents the files from
500 being restored on a Unix machine. Once you have an operational Windows OS
501 loaded, you can run the File daemon and restore your user files.
504 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
505 suggestion, which looks very promising.
507 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
508 Environment) Boot-CD, may be just what is needed to build a complete disaster
509 recovery system for Win32. This distribution can be found at
510 \elink{http://www.nu2.nu/pebuilder/ }{http://www.nu2.nu/pebuilder/}.
512 \subsection*{Windows Restore Problems}
513 \index[general]{Problems!Windows Restore}
514 \index[general]{Windows Restore Problems}
515 \addcontentsline{toc}{subsection}{Windows Restore Problems}
517 \ilink{Restore Chapter}{Windows} of this manual for problems
518 that you might encounter doing a restore.
521 \subsection*{Windows Ownership and Permissions Problems}
522 \index[general]{Problems!Windows Ownership and Permissions }
523 \index[general]{Windows Ownership and Permissions Problems }
524 \addcontentsline{toc}{subsection}{Windows Ownership and Permissions
527 If you restore files backed up from WinNT/XP/2K to an alternate directory,
528 Bacula may need to create some higher level directories that were not saved
529 (or restored). In this case, the File daemon will create them under the SYSTEM
530 account because that is the account that Bacula runs under as a service. As of
531 version 1.32f-3, Bacula creates these files with full access permission.
532 However, there may be cases where you have problems accessing those files even
533 if you run as administrator. In principle, Microsoft supplies you with the way
534 to cease the ownership of those files and thus change the permissions.
535 However, a much better solution to working with and changing Win32 permissions
536 is the program {\bf SetACL}, which can be found at
537 \elink{http://setacl.sourceforge.net/ }{http://setacl.sourceforge.net/}.
539 If you have not installed Bacula while running as Administrator
540 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
541 then it is very unlikely that it will have sufficient permission to
542 access all your files.
544 Some users have experienced problems restoring files that participate in
545 the Active Directory. They also report that changing the userid under which
546 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
550 \subsection*{Manually resetting the Permissions}
551 \index[general]{Manually resetting the Permissions }
552 \index[general]{Permissions!Manually resetting the }
553 \addcontentsline{toc}{subsection}{Manually resetting the Permissions}
555 The following solution was provided by Dan Langille \lt{}dan at langille in
556 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
557 they should apply to most Win32 platforms. The procedure outlines how to deal
558 with a problem which arises when a restore creates a top-level new directory.
559 In this example, "top-level" means something like {\bf
560 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
561 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
562 as the {\bf Where:} value, this problem will arise.
564 The problem appears as a directory which cannot be browsed with Windows
565 Explorer. The symptoms include the following message when you try to click on
568 \includegraphics{./access-is-denied.eps}
570 If you encounter this message, the following steps will change the permissions
571 to allow full access.
574 \item right click on the top level directory (in this example, {\bf c:/src})
575 and select {\bf Properties}.
576 \item click on the Security tab.
577 \item If the following message appears, you can ignore it, and click on {\bf
580 \includegraphics{./view-only.eps}
582 You should see something like this:
584 \includegraphics{./properties-security.eps}
585 \item click on Advanced
586 \item click on the Owner tab
587 \item Change the owner to something other than the current owner (which is
588 {\bf SYSTEM} in this example as shown below).
590 \includegraphics{./properties-security-advanced-owner.eps}
591 \item ensure the "Replace owner on subcontainers and objects" box is
594 \item When the message "You do not have permission to read the contents of
595 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
596 the directory permissions with permissions granting you Full Control?", click
599 \includegraphics{./confirm.eps}
600 \item Click on OK to close the Properties tab
603 With the above procedure, you should now have full control over your restored
606 In addition to the above methods of changing permissions, there is a Microsoft
607 program named {\bf cacls} that can perform similar functions.
609 \subsection*{Backing Up the WinNT/XP/2K System State}
610 \index[general]{State!Backing Up the WinNT/XP/2K System }
611 \index[general]{Backing Up the WinNT/XP/2K System State }
612 \addcontentsline{toc}{subsection}{Backing Up the WinNT/XP/2K System State}
614 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
615 conjunction with Bacula should permit a full restore of any damaged system
616 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
617 state prior to running a Bacula backup with the following command:
621 ntbackup backup systemstate /F c:\systemstate.bkf
625 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
626 system state and not all the user files, and the {\bf /F
627 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
628 this file must then be saved and restored by Bacula.
630 To restore the system state, you first reload a base operating system if the
631 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
632 restore all the damaged or lost user's files and to recover the {\bf
633 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
634 missing system files or registry problems, you run {\bf NTBackup} and {\bf
635 catalogue} the system statefile, and then select it for restore. The
636 documentation says you can't run a command line restore of the systemstate.
638 To the best of my knowledge, this has not yet been tested. If you test it,
639 please report your results to the Bacula email list.
641 \subsection*{Windows Considerations for Filename Specifications}
642 \index[general]{Specifications!Windows Considerations for Filename }
643 \index[general]{Windows Considerations for Filename Specifications }
644 \addcontentsline{toc}{subsection}{Windows Considerations for Filename
648 \ilink{Director's Configuration chapter}{win32} of this manual
649 for important considerations on how to specify Windows paths in Bacula FileSet
650 Include and Exclude directives.
652 \index[general]{Unicode}
653 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
654 As of that version, both {\bf bconsole} and {\bf wx-console} support Windows
655 Unicode filenames. There may still be some problems with multiple byte
656 characters (e.g. Chinese, ...) where it is a two byte character but the
657 displayed character is not two characters wide.
659 \index[general]{Win32 path length restriction}
660 Path/filenames longer than 260 characters are not supported. This may be
661 possible in a future version.
663 \subsection*{Command Line Options Specific to the Bacula Windows File
665 \index[general]{Client!Command Line Options Specific to the Bacula Windows
667 \index[general]{Command Line Options Specific to the Bacula Windows File
669 \addcontentsline{toc}{subsection}{Command Line Options Specific to the
670 Bacula Windows File Daemon (Client)}
672 These options are not normally seen or used by the user, and are documented
673 here only for information purposes. At the current time, to change the default
674 options, you must either manually run {\bf Bacula} or you must manually edit
675 the system registry and modify the appropriate entries.
677 In order to avoid option clashes between the options necessary for {\bf
678 Bacula} to run on Windows and the standard Bacula options, all Windows
679 specific options are signaled with a forward slash character (/), while as
680 usual, the standard Bacula options are signaled with a minus (-), or a minus
681 minus (\verb:--:). All the standard Bacula options can be used on the Windows
682 version. In addition, the following Windows only options are implemented:
686 \item [/servicehelper ]
687 \index[fd]{/servicehelper }
688 Run the service helper application (don't use this it is deprecated.).
691 \index[fd]{/service }
692 Start Bacula as a service
696 Run the Bacula application
699 \index[fd]{/install }
700 Install Bacula as a service in the system registry
704 Uninstall Bacula from the system registry
708 Show the Bacula about dialogue box
712 Show the Bacula status dialogue box
716 Show the Bacula events dialogue box (not yet implemented)
720 Stop any running {\bf Bacula}
724 Show the Bacula help dialogue box
727 It is important to note that under normal circumstances the user should never
728 need to use these options as they are normally handled by the system
729 automatically once Bacula is installed. However, you may note these options in
730 some of the .bat files that have been created for your use.
732 \subsection*{Shutting down Windows Systems}
733 \index[general]{Shutting down Windows Systems }
734 \index[general]{Systems!Shutting down Windows }
735 \addcontentsline{toc}{subsection}{Shutting down Windows Systems}
737 Some users like to shutdown their windows machines after a backup using a
738 Client Run After Job directive. If you want to do something similar, you might
739 take the shutdown program from the
740 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
741 \elink{Sysinternals project}{http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml}.