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 Cygwin of Bacula (1.32 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 file for use with the new version you will
51 install. Current versions of Bacula do not use Cygwin and has
52 far fewer files than the old Cygwin version, so it is better to
53 start with a clean directory.
55 If you have Bacula version 1.38 or lower, we recommend the same procedure
56 as mentioned in the paragraph above. This is because Bacula 1.39 and
57 greater installs a bit differently from previous versions. There are
58 different registry keys, ... that are better cleaned up before installing
62 Finally, proceed with the installation.
65 \item You must be logged in as Administrator to do a correct installation,
66 if not, please do so before continuing.
68 \item Simply double click on the {\bf winbacula-1.xx.0.exe} NSIS install
69 icon. The actual name of the icon will vary from one release version to
72 \includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe
74 \item Once launched, the installer wizard will ask you if you want to install
77 \addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
78 \includegraphics{./win32-welcome.eps}
80 \item If you proceed, you will be asked to select the components to be
81 installed. You may install the Bacula program (Bacula File Service) and or
82 the documentation. Both will be installed in sub-directories of the install
83 location that you choose later. The components dialog looks like the
86 \addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
87 \includegraphics{./win32-pkg.eps}
89 \item Next you will be asked to select an installation directory.
91 \addcontentsline{lof}{figure}{Win32 Directory Selection Dialog}
92 \includegraphics{./win32-location.eps}
94 \item If you are installing for the first time, you will be asked if you want
95 to edit the bacula-fd.conf file, and if you respond with yes, it will be
96 opened in notepad. Note, if you have installed Bacula to a drive other
97 than C: you probably should prefix the installation drive name to each
98 of the directory references in the bacula-fd.conf file, in particular
99 the {\bf WorkingDirectory} and the {\bf Pid Directory} directives.
101 Also, if you do not wish to see the full listing of all files restored
102 in the job output after running a restore job, you can add {\bf ,
103 !restored} to the {\bf director} directive in the {\bf Messages}
106 \addcontentsline{lof}{figure}{Win32 Configure}
107 \includegraphics{./win32-config.eps}
109 \item Then the installer will display a dialog that allows you to
110 to install Bacula as a service. You should always choose to do so.
111 It also permits you to start the service. Normally you should check
112 the box, and any running Bacula will be shutdown and the new one started. You
113 may see a DOS box momentarily appear on the screen as the service is started.
114 It should disappear in a second or two:
116 \addcontentsline{lof}{figure}{Win32 Client Service Selection}
117 \includegraphics{./win32-service.eps}
120 \item If everything goes well, you will receive the following confirmation:
122 \addcontentsline{lof}{figure}{Win32 Client Service Confirmation}
123 \includegraphics{./win32-service-ok.eps}
125 \item While the various files are being loaded, you will see the following
128 \addcontentsline{lof}{figure}{Win32 Install Progress}
129 \includegraphics{./win32-installing.eps}
132 \item Finally, the finish dialog will appear:
134 \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
135 \includegraphics{./win32-finish.eps}
140 That should complete the installation process. When the Bacula File Server is
141 ready to serve files, an icon \includegraphics{./idle.eps} representing a
142 cassette (or tape) will appear in the system tray
143 \includegraphics{./tray-icon.eps}; right click on it and a menu will appear.\\
144 \includegraphics{./menu.eps}\\
145 The {\bf Events} item is currently unimplemented, by selecting the {\bf
146 Status} item, you can verify whether any jobs are running or not.
148 When the Bacula File Server begins saving files, the color of the holes in the
149 cassette icon will change from white to green \includegraphics{./running.eps},
150 and if there is an error, the holes in the cassette icon will change to red
151 \includegraphics{./error.eps}.
153 If you are using remote desktop connections between your windows boxes, be
154 warned that that tray icon does not always appear. It will always be visible
155 when you log into the console, but the remote desktop may not display it.
157 \subsection*{Post Win32 Installation}
158 \index[general]{Post Win32 Installation}
159 \index[general]{Win32!Post Installation}
160 \addcontentsline{toc}{subsection}{Post Win32 Installation}
162 After installing Bacula and before running it, you should check the contents
164 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} to
165 ensure that it corresponds to your configuration.
167 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
168 is running as a process (not an Application) with User Name SYSTEM. If this is
169 not the case, you probably have not installed Bacula while running as
170 Administrator, and hence it will be unlikely that Bacula can access
171 all the system files.
173 \subsection*{Uninstalling Bacula on Win32}
174 \index[general]{Win32!Uninstalling Bacula}
175 \index[general]{Uninstalling Bacula on Win32}
176 \addcontentsline{toc}{subsection}{Uninstalling Bacula on Win32}
178 Once Bacula has been installed, it can be uninstalled using the standard
179 Windows Add/Remove Programs dialog found on the Control panel.
181 \subsection*{Dealing with Win32 Problems}
183 \index[general]{Win32!Dealing with Problems}
184 \index[general]{Dealing with Win32 Problems}
185 \addcontentsline{toc}{subsection}{Dealing with Win32 Problems}
187 The most likely source of problems is authentication when the Director
188 attempts to connect to the File daemon that you installed. This can occur if
189 the names and the passwords defined in the File daemon's configuration file
191 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} on
192 the Windows machine do not match with the names and the passwords in the
193 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
196 More specifically, the password found in the {\bf Client} resource in the
197 Director's configuration file must be the same as the password in the {\bf
198 Director} resource of the File daemon's configuration file. In addition, the
199 name of the {\bf Director} resource in the File daemon's configuration file
200 must be the same as the name in the {\bf Director} resource of the Director's
203 It is a bit hard to explain in words, but if you understand that a Director
204 normally has multiple Clients and a Client (or File daemon) may permit access
205 by multiple Directors, you can see that the names and the passwords on both
206 sides must match for proper authentication.
208 One user had serious problems with the configuration file until he realized
209 that the Unix end of line conventions were used and Bacula wanted them in
210 Windows format. This has not been confirmed though.
212 Running Unix like programs on Windows machines is a bit frustrating because
213 the Windows command line shell (DOS Window) is rather primitive. As a
214 consequence, it is not generally possible to see the debug information and
215 certain error messages that Bacula prints. With a bit of work, however, it is
216 possible. When everything else fails and you want to {\bf see} what is going
217 on, try the following:
221 Start a DOS shell Window.
228 The {\bf -t} option will cause Bacula to read the configuration file, print
229 any error messages and then exit. the {\bf \gt{}} redirects the output to the
230 file named {\bf out}, which you can list with the {\bf type} command.
232 If something is going wrong later, or you want to run {\bf Bacula} with a
233 debug option, you might try starting it as:
237 bacula-fd -d 100 >out
241 In this case, Bacula will run until you explicitly stop it, which will give
242 you a chance to connect to it from your Unix/Linux server. In later versions
243 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
244 can write the output to a trace file {\bf bacula.trace} in the current
245 directory. To enable this, before running a job, use the console, and enter:
253 then run the job, and once you have terminated the File daemon, you will find
254 the debug output in the {\bf bacula.trace} file.
256 In addition, you should look in the System Applications log on the Control
257 Panel to find any Windows errors that Bacula got during the startup process.
259 Finally, due to the above problems, when you turn on debugging, and specify
260 trace=1 on a setdebug command in the Console, Bacula will write the debug
261 information to the file {\bf bacula.trace} in the directory from which Bacula
264 If you are having problems with ClientRunBeforeJob scripts randomly dying,
265 it is possible that you have run into an Oracle bug. See bug number 622 in
266 the bugs.bacula.org database. The following information has been
267 provided by a user on this issue:
271 The information in this document applies to:
272 Oracle HTTP Server - Version: 9.0.4
273 Microsoft Windows Server 2003
275 When starting an OC4J instance, the System Clock runs faster, about 7
280 + This is caused by the Sun JVM bug 4500388, which states that "Calling
281 Thread.sleep() with a small argument affects the system clock". Although
282 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
284 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
286 + Also reported by Microsoft as "The system clock may run fast when you
287 use the ACPI power management timer as a high-resolution counter on Windows
288 2000-based computers" (See http://support.microsoft.com/?id=821893)
292 \label{Compatibility}
293 \subsection*{Windows Compatibility Considerations}
294 \index[general]{Windows Compatibility Considerations}
295 \index[general]{Considerations!Windows Compatibility}
296 \addcontentsline{toc}{subsection}{Windows Compatibility Considerations}
298 If any applications are running during the backup and they have files
299 opened exclusively, Bacula will not be able to backup those files, so be
300 sure you close your applications (or tell your users to close their
301 applications) before the backup. Fortunately,
302 most Microsoft applications do not open
303 files exclusively so that they can be backed up. However, you will need to
304 experiment. In any case, if Bacula cannot open the file, it will print an
305 error message, so you will always know which files were not backed up.
306 For version 1.37.25 and greater, see the section below on
307 Volume Shadow Copy Service.
309 During backup, Bacula doesn't know about the system registry, so you will
310 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
311 program specifically designed to make a copy or backup the registry.
313 In Bacula version 1.31 and later, we use Windows backup API calls by
314 default. Typical of Windows, programming these special BackupRead and
315 BackupWrite calls is a real nightmare of complications. The end result
316 gives some distinct advantages and some disadvantages.
318 First, the advantages are that on WinNT/2K/XP systems, the security and
319 ownership information is now backed up. In addition, with the exception of
320 files in exclusive use by another program (a major disaster for backup
321 programs on Windows), Bacula can now access all system files. This means
322 that when you restore files, the security and ownership information will be
323 restored on WinNT/2K/XP along with the data.
325 The disadvantage of the Windows backup API calls is that it produces
326 non-portable backups. That is files and their data that are backed up on
327 WinNT using the native API calls (BackupRead/BackupWrite) cannot be
328 restored on Win95/98/Me or Unix systems. In principle, a file backed up on
329 WinNT can be restored on WinXP, but this remains to be seen in practice
330 (not yet tested). In addition, the stand-alone tools such as {\bf bls} and
331 {\bf bextract} cannot be used to retrieve the data for those files because
332 those tools are not available on Windows. All restores must use the Bacula
333 {\bf restore} command. This restriction is mentioned for completeness, but
334 in practice should not create any problems.
336 As a default, Bacula backs up Windows systems using the Windows API calls.
337 If you want to backup data on a WinNT/2K/XP system and restore it on a
338 Unix/Win95/98/Me system, we have provided a special {\bf portable} option
339 that backs up the data in a portable fashion by using portable API calls.
340 See the \ilink{portable option}{portable} on the Include statement in a
341 FileSet resource in the Director's configuration chapter for the details on
342 setting this option. However, using the portable option means you may have
343 permissions problems accessing files, and none of the security and
344 ownership information will be backed up or restored. The file data can,
345 however, be restored on any system.
347 You should always be able to restore any file backed up on Unix or Win95/98/Me
348 to any other system. On some systems, such as WinNT/2K/XP, you may have to
349 reset the ownership of such restored files. Any file backed up on WinNT/2K/XP
350 should in principle be able to be restored to a similar system (i.e.
351 WinNT/2K/XP), however, I am unsure of the consequences if the owner
352 information and accounts are not identical on both systems. Bacula will not
353 let you restore files backed up on WinNT/2K/XP to any other system (i.e. Unix
354 Win95/98/Me) if you have used the defaults.
356 Finally, if you specify the {\bf portable=yes} option on the files you back
357 up. Bacula will be able to restore them on any other system. However, any
358 WinNT/2K/XP specific security and ownership information will be lost.
360 The following matrix will give you an idea of what you can expect. Thanks to
361 Marc Brueckner for doing the tests:
365 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
366 \begin{longtable}{|l|l|p{2.8in}|}
368 \multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
369 & \multicolumn{1}{c|}{\bf Results } \\
370 \hline {WinMe} & {WinMe} & {Works } \\
371 \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
372 \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
373 \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
374 \hline {\} & {\} & {\ } \\
375 \hline {WinXP} & {WinXP} & {Works } \\
376 \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
378 \hline {WinXP} & {WinMe} & {Error: Win32 data stream not supported. } \\
379 \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
380 \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
381 \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
382 \hline {\} & {\} & {\ } \\
383 \hline {WinNT} & {WinNT} & {Works } \\
384 \hline {WinNT} & {WinXP} & {Works } \\
385 \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
386 \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
387 \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
388 \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
389 \hline {\} & {\} & {\ } \\
390 \hline {Linux} & {Linux} & {Works } \\
391 \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
392 \hline {Linux} & {WinMe} & {Works } \\
393 \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
399 \subsection*{Volume Shadow Copy Service}
400 \index[general]{Volume Shadow Copy Service}
402 \addcontentsline{toc}{subsection}{Volume Shadow Copy Service}
403 In version 1.37.30 and greater, you can turn on Microsoft's Volume
404 Shadow Copy Service (VSS).
406 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
407 a backup-solution for Windows, this is an extremely important step. VSS
408 allows Bacula to backup open files and even to interact with applications like
409 RDBMS to produce consistent file copies. VSS aware applications are called
410 VSS Writers, they register with the OS so that when Bacula wants to do a
411 Snapshot, the OS will notify the register Writer programs, which may then
412 create a consistent state in their application, which will be backed up.
413 Examples for these writers are "MSDE" (Microsoft database
414 engine), "Event Log Writer", "Registry Writer" plus 3rd
415 party-writers. If you have a non-vss aware application (e.g.
416 SQL Anywhere or probably MySQL), a shadow copy is still generated
417 and the open files can be backed up, but there is no guarantee
418 that the file is consistent.
420 Bacula produces a message from each of the registered writer programs
421 when it is doing a VSS backup so you know which ones are correctly backed
424 Bacula supports VSS on both Windows 2003 and Windows XP.
425 Technically Bacula creates a shadow copy as soon as the backup process
426 starts. It does then backup all files from the shadow copy and destroys the
427 shadow copy after the backup process. Please have in mind, that VSS
428 creates a snapshot and thus backs up the system at the state it had
429 when starting the backup. It will disregard file changes which occur during
432 VSS can be turned on by placing an
434 \index[dir]{Enable VSS}
435 \index[general]{Enable VSS}
440 in your FileSet resource.
442 The VSS aware File daemon has the letters VSS on the signon line that
443 it produces when contacted by the console. For example:
445 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
447 the VSS is shown in the line above. This only means that the File daemon
448 is capable of doing VSS not that VSS is turned on for a particular backup.
449 There are two ways of telling if VSS is actually turned on during a backup.
450 The first is to look at the status output for a job, e.g.:
454 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
455 VSS Backup Job started: 23-Jul-05 13:25
456 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
457 Files Examined=75,021
458 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
462 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
463 This means that VSS is enabled for that job. If VSS is not enabled, it will
464 simply show "Backup Job started ..." without the letters VSS.
466 The second way to know that the job was backed up with VSS is to look at the
467 Job Report, which will look something like the following:
470 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
471 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
472 23-Jul 13:26 rufus-sd: Spooling data ...
473 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
474 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
475 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
476 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
477 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
480 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
481 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
482 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
483 that you will get a consistent snapshot of the data handled by that writer.
485 \subsection*{VSS Problems}
486 \index[general]{Problems!VSS}
487 \index[fd] {Problems!VSS}
488 \index[general]{VSS Problems}
489 \index[fd]{VSS Problems}
490 \addcontentsline{toc}{subsection}{VSS Problems}
492 If you are experiencing problems such as VSS hanging on MSDE, first try
493 running {\bf vssadmin} to check for problems, then try running {\bf
494 ntbackup} which also uses VSS to see if it has similar problems. If so, you
495 know that the problem is in your Windows machine and not with Bacula.
497 The FD hang problems were reported with {\bf MSDEwriter} when:
499 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
500 seems to use TCP/IP and not Named Pipes).
501 \item msdtcs was installed to run under "localsystem": try running msdtcs
502 under networking account (instead of local system) (com+ seems to work
503 better with this configuration).
507 \subsection*{Windows Firewalls}
508 \index[general]{Firewalls!Windows}
509 \index[general]{Windows Firewalls}
510 \addcontentsline{toc}{subsection}{Windows Firewalls}
512 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
513 are likely to find that the Bacula ports are blocked and you cannot
514 communicate to the other daemons. This can be deactivated through the {\bf
515 Security Notification} dialog, which is apparently somewhere in the {\bf
516 Security Center}. I don't have this on my computer, so I cannot give the exact
523 netsh firewall set opmode disable
527 is purported to disable the firewall, but this command is not accepted on my
530 \subsection*{Windows Port Usage}
531 \index[general]{Windows Port Usage}
532 \index[general]{Usage!Windows Port}
533 \addcontentsline{toc}{subsection}{Windows Port Usage}
535 If you want to see if the File daemon has properly opened the port and is
536 listening, you can enter the following command in a shell window:
540 netstat -an | findstr 910[123]
544 \subsection*{Windows Disaster Recovery}
545 \index[general]{Recovery!Windows Disaster}
546 \index[general]{Windows Disaster Recovery}
547 \addcontentsline{toc}{subsection}{Windows Disaster Recovery}
549 We don't currently have a good solution for disaster recovery on Windows as we
550 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
551 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
552 that could possibly work, but we have not investigated it. This means that
553 until someone figures out the correct procedure, you must restore the OS from
554 the installation disks, then you can load a Bacula client and restore files.
555 Please don't count on using {\bf bextract} to extract files from your backup
556 tapes during a disaster recovery unless you have backed up those files using
557 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
558 normal way Bacula saves files using the Windows API prevents the files from
559 being restored on a Unix machine. Once you have an operational Windows OS
560 loaded, you can run the File daemon and restore your user files.
563 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
564 suggestion, which looks very promising.
566 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
567 Environment) Boot-CD, may be just what is needed to build a complete disaster
568 recovery system for Win32. This distribution can be found at
569 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
571 \subsection*{Windows Restore Problems}
572 \index[general]{Problems!Windows Restore}
573 \index[general]{Windows Restore Problems}
574 \addcontentsline{toc}{subsection}{Windows Restore Problems}
576 \ilink{Restore Chapter}{Windows} of this manual for problems
577 that you might encounter doing a restore.
580 \subsection*{Windows Ownership and Permissions Problems}
581 \index[general]{Problems!Windows Ownership and Permissions}
582 \index[general]{Windows Ownership and Permissions Problems}
583 \addcontentsline{toc}{subsection}{Windows Ownership and Permissions
586 If you restore files backed up from WinNT/XP/2K to an alternate directory,
587 Bacula may need to create some higher level directories that were not saved
588 (or restored). In this case, the File daemon will create them under the SYSTEM
589 account because that is the account that Bacula runs under as a service. As of
590 version 1.32f-3, Bacula creates these files with full access permission.
591 However, there may be cases where you have problems accessing those files even
592 if you run as administrator. In principle, Microsoft supplies you with the way
593 to cease the ownership of those files and thus change the permissions.
594 However, a much better solution to working with and changing Win32 permissions
595 is the program {\bf SetACL}, which can be found at
596 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
598 If you have not installed Bacula while running as Administrator
599 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
600 then it is very unlikely that it will have sufficient permission to
601 access all your files.
603 Some users have experienced problems restoring files that participate in
604 the Active Directory. They also report that changing the userid under which
605 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
609 \subsection*{Manually resetting the Permissions}
610 \index[general]{Manually resetting the Permissions}
611 \index[general]{Permissions!Manually resetting the}
612 \addcontentsline{toc}{subsection}{Manually resetting the Permissions}
614 The following solution was provided by Dan Langille \lt{}dan at langille in
615 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
616 they should apply to most Win32 platforms. The procedure outlines how to deal
617 with a problem which arises when a restore creates a top-level new directory.
618 In this example, "top-level" means something like {\bf
619 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
620 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
621 as the {\bf Where:} value, this problem will arise.
623 The problem appears as a directory which cannot be browsed with Windows
624 Explorer. The symptoms include the following message when you try to click on
627 \includegraphics{./access-is-denied.eps}
629 If you encounter this message, the following steps will change the permissions
630 to allow full access.
633 \item right click on the top level directory (in this example, {\bf c:/src})
634 and select {\bf Properties}.
635 \item click on the Security tab.
636 \item If the following message appears, you can ignore it, and click on {\bf
639 \includegraphics{./view-only.eps}
641 You should see something like this:
643 \includegraphics{./properties-security.eps}
644 \item click on Advanced
645 \item click on the Owner tab
646 \item Change the owner to something other than the current owner (which is
647 {\bf SYSTEM} in this example as shown below).
649 \includegraphics{./properties-security-advanced-owner.eps}
650 \item ensure the "Replace owner on subcontainers and objects" box is
653 \item When the message "You do not have permission to read the contents of
654 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
655 the directory permissions with permissions granting you Full Control?", click
658 \includegraphics{./confirm.eps}
659 \item Click on OK to close the Properties tab
662 With the above procedure, you should now have full control over your restored
665 In addition to the above methods of changing permissions, there is a Microsoft
666 program named {\bf cacls} that can perform similar functions.
668 \subsection*{Backing Up the WinNT/XP/2K System State}
669 \index[general]{State!Backing Up the WinNT/XP/2K System}
670 \index[general]{Backing Up the WinNT/XP/2K System State}
671 \addcontentsline{toc}{subsection}{Backing Up the WinNT/XP/2K System State}
673 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
674 conjunction with Bacula should permit a full restore of any damaged system
675 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
676 state prior to running a Bacula backup with the following command:
680 ntbackup backup systemstate /F c:\systemstate.bkf
684 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
685 system state and not all the user files, and the {\bf /F
686 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
687 this file must then be saved and restored by Bacula.
689 To restore the system state, you first reload a base operating system if the
690 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
691 restore all the damaged or lost user's files and to recover the {\bf
692 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
693 missing system files or registry problems, you run {\bf NTBackup} and {\bf
694 catalogue} the system statefile, and then select it for restore. The
695 documentation says you can't run a command line restore of the systemstate.
697 To the best of my knowledge, this has not yet been tested. If you test it,
698 please report your results to the Bacula email list.
700 \subsection*{Windows Considerations for Filename Specifications}
701 \index[general]{Specifications!Windows Considerations for Filename}
702 \index[general]{Windows Considerations for Filename Specifications}
703 \addcontentsline{toc}{subsection}{Windows Considerations for Filename
707 \ilink{Director's Configuration chapter}{win32} of this manual
708 for important considerations on how to specify Windows paths in Bacula FileSet
709 Include and Exclude directives.
711 \index[general]{Unicode}
712 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
713 As of that version, both {\bf bconsole} and {\bf wx-console} support Windows
714 Unicode filenames. There may still be some problems with multiple byte
715 characters (e.g. Chinese, ...) where it is a two byte character but the
716 displayed character is not two characters wide.
718 \index[general]{Win32 Path Length Restriction}
719 Path/filenames longer than 260 characters (up to 32,000) are supported
720 beginning with Bacula version 1.39.20.
722 \subsection*{Win32 Specific File daemon Command Line Options}
723 \index[general]{Client!Win32 Specific File daemon Command Line Options}
724 \index[general]{Win32 Specific File daemon Command Line Options}
725 \addcontentsline{toc}{subsection}{Win32 Specific File daemon Command Line
728 These options are not normally seen or used by the user, and are documented
729 here only for information purposes. At the current time, to change the default
730 options, you must either manually run {\bf Bacula} or you must manually edit
731 the system registry and modify the appropriate entries.
733 In order to avoid option clashes between the options necessary for {\bf
734 Bacula} to run on Windows and the standard Bacula options, all Windows
735 specific options are signaled with a forward slash character (/), while as
736 usual, the standard Bacula options are signaled with a minus (-), or a minus
737 minus (\verb:--:). All the standard Bacula options can be used on the Windows
738 version. In addition, the following Windows only options are implemented:
744 Start Bacula as a service
748 Run the Bacula application
752 Install Bacula as a service in the system registry
756 Uninstall Bacula from the system registry
760 Show the Bacula about dialogue box
764 Show the Bacula status dialogue box
768 Show the Bacula events dialogue box (not yet implemented)
772 Stop any running {\bf Bacula}
776 Show the Bacula help dialogue box
779 It is important to note that under normal circumstances the user should never
780 need to use these options as they are normally handled by the system
781 automatically once Bacula is installed. However, you may note these options in
782 some of the .bat files that have been created for your use.
784 \subsection*{Shutting down Windows Systems}
785 \index[general]{Shutting down Windows Systems}
786 \index[general]{Systems!Shutting down Windows}
787 \addcontentsline{toc}{subsection}{Shutting down Windows Systems}
789 Some users like to shutdown their windows machines after a backup using a
790 Client Run After Job directive. If you want to do something similar, you might
791 take the shutdown program from the
792 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
793 \elink{Sysinternals project}{http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml}.