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, WinXP, Win2000, and Windows 2003 systems. We have coded to support
19 Win95, but no longer have a system for testing. The Windows version of
20 Bacula is a native Win32 port, but there are very few source code changes
21 to the Unix code, which means that the Windows version is for the most part
22 running code that has long proved stable on Unix systems. When running, it
23 is perfectly integrated with Windows and displays its icon in the system
24 icon tray, and provides a system tray menu to obtain additional information
25 on how Bacula is running (status and events dialog boxes). If so desired,
26 it can also be stopped by using the system tray menu, though this should
27 normally never be necessary.
29 Once installed Bacula normally runs as a system service. This means that it is
30 immediately started by the operating system when the system is booted, and
31 runs in the background even if there is no user logged into the system.
33 \subsection*{Win32 Installation}
35 \index[general]{Installation }
36 \index[general]{Win32!Installation }
37 \addcontentsline{toc}{subsection}{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 Cygwin of Bacula (1.32 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 file for use with the new version you will
48 install. Current versions of Bacula do not use Cygwin and has
49 far fewer files than the old Cygwin version, so it is better to
50 start with a clean directory.
52 Finally, proceed with the installation.
55 \item You must be logged in as Administrator to do a correct installation,
56 if not, please do so before continuing.
58 \item Simply double click on the {\bf winbacula-1.xx.0.exe} NSIS install
59 icon. The actual name of the icon will vary from one release version to
62 \includegraphics{./win32-nsis.eps} winbacula-1.xx.0.exe
64 \item Once launched, the installer wizard will ask you if you want to install
67 \addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
68 \includegraphics{./win32-welcome.eps}
70 \item If you proceed, you will be asked to select the components to be
71 installed. You may install the Bacula program (Bacula File Service) and or
72 the documentation. Both will be installed in sub-directories of the install
73 location that you choose later. The components dialog looks like the
76 \addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
77 \includegraphics{./win32-pkg.eps}
79 \item Next you will be asked to select an installation directory.
81 \addcontentsline{lof}{figure}{Win32 Directory Selection Dialog}
82 \includegraphics{./win32-location.eps}
84 \item If you are installing for the first time, you will be asked if you want
85 to edit the bacula-fd.conf file, and if you respond with yes, it will be
86 opened in notepad. Note, if you have installed Bacula to a drive other
87 than C: you probably should prefix the installation drive name to each
88 of the directory references in the bacula-fd.conf file, in particular
89 the {\bf WorkingDirectory} and the {\bf Pid Directory} directives.
91 Also, if you do not wish to see the full listing of all files restored
92 in the job output after running a restore job, you can add {\bf ,
93 !restored} to the {\bf director} directive in the {\bf Messages}
96 \item Then the installer will ask if you wish to install Bacula as a service. You
97 should always choose to do so:
99 \addcontentsline{lof}{figure}{Win32 Client Service Selection}
100 \includegraphics{./win32-service.eps}
103 \item If everything goes well, you will receive the following confirmation:
105 \addcontentsline{lof}{figure}{Win32 Client Service Confirmation}
106 \includegraphics{./win32-service-ok.eps}
109 \item Then you will be asked if you wish to start the service. If you respond
110 with yes, any running Bacula will be shutdown and the new one started. You
111 may see a DOS box momentarily appear on the screen as the service is started.
112 It should disappear in a second or two:
114 \addcontentsline{lof}{figure}{Win32 Client Start}
115 \includegraphics{./win32-start.eps}
118 \item Finally, the finish dialog will appear:
119 \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
120 \includegraphics{./win32-finish.eps}
125 That should complete the installation process. When the Bacula File Server is
126 ready to serve files, an icon \includegraphics{./idle.eps} representing a
127 cassette (or tape) will appear in the system tray
128 \includegraphics{./tray-icon.eps}; right click on it and a menu will appear.\\
129 \includegraphics{./menu.eps}\\
130 The {\bf Events} item is currently unimplemented, by selecting the {\bf
131 Status} item, you can verify whether any jobs are running or not.
133 When the Bacula File Server begins saving files, the color of the holes in the
134 cassette icon will change from white to green \includegraphics{./running.eps},
135 and if there is an error, the holes in the cassette icon will change to red
136 \includegraphics{./error.eps}.
138 If you are using remote desktop connections between your windows boxes, be
139 warned that that tray icon does not always appear. It will always be visible
140 when you log into the console, but the remote desktop may not display it.
142 \subsection*{Post Win32 Installation}
143 \index[general]{Post Win32 Installation }
144 \index[general]{Win32!Post Installation }
145 \addcontentsline{toc}{subsection}{Post Win32 Installation}
147 After installing Bacula and before running it, you should check the contents
149 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} to
150 ensure that it corresponds to your configuration.
152 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
153 is running as a process (not an Application) with User Name SYSTEM. If this is
154 not the case, you probably have not installed Bacula while running as
155 Administrator, and hence it will be unlikely that Bacula can access
156 all the system files.
158 \subsection*{Uninstalling Bacula on Win32}
159 \index[general]{Win32!Uninstalling Bacula }
160 \index[general]{Uninstalling Bacula on Win32 }
161 \addcontentsline{toc}{subsection}{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 \subsection*{Dealing with Win32 Problems}
168 \index[general]{Win32!Dealing with Problems }
169 \index[general]{Dealing with Win32 Problems }
170 \addcontentsline{toc}{subsection}{Dealing with Win32 Problems}
172 The most likely source of problems is authentication when the Director
173 attempts to connect to the File daemon that you installed. This can occur if
174 the names and the passwords defined in the File daemon's configuration file
176 c:\textbackslash{}bacula\textbackslash{}bin\textbackslash{}bacula-fd.conf} on
177 the Windows machine do not match with the names and the passwords in the
178 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
181 More specifically, the password found in the {\bf Client} resource in the
182 Director's configuration file must be the same as the password in the {\bf
183 Director} resource of the File daemon's configuration file. In addition, the
184 name of the {\bf Director} resource in the File daemon's configuration file
185 must be the same as the name in the {\bf Director} resource of the Director's
188 It is a bit hard to explain in words, but if you understand that a Director
189 normally has multiple Clients and a Client (or File daemon) may permit access
190 by multiple Directors, you can see that the names and the passwords on both
191 sides must match for proper authentication.
193 One user had serious problems with the configuration file until he realized
194 that the Unix end of line conventions were used and Bacula wanted them in
195 Windows format. This has not been confirmed though.
197 Running Unix like programs on Windows machines is a bit frustrating because
198 the Windows command line shell (DOS Window) is rather primitive. As a
199 consequence, it is not generally possible to see the debug information and
200 certain error messages that Bacula prints. With a bit of work, however, it is
201 possible. When everything else fails and you want to {\bf see} what is going
202 on, try the following:
206 Start a DOS shell Window.
213 The {\bf -t} option will cause Bacula to read the configuration file, print
214 any error messages and then exit. the {\bf \gt{}} redirects the output to the
215 file named {\bf out}, which you can list with the {\bf type} command.
217 If something is going wrong later, or you want to run {\bf Bacula} with a
218 debug option, you might try starting it as:
222 bacula-fd -d 100 >out
226 In this case, Bacula will run until you explicitly stop it, which will give
227 you a chance to connect to it from your Unix/Linux server. In later versions
228 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
229 can write the output to a trace file {\bf bacula.trace} in the current
230 directory. To enable this, before running a job, use the console, and enter:
238 then run the job, and once you have terminated the File daemon, you will find
239 the debug output in the {\bf bacula.trace} file.
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 \subsection*{Windows Compatibility Considerations}
279 \index[general]{Windows Compatibility Considerations }
280 \index[general]{Considerations!Windows Compatibility }
281 \addcontentsline{toc}{subsection}{Windows Compatibility Considerations}
283 If any applications are running during the backup and they have files
284 opened exclusively, Bacula will not be able to backup those files, so be
285 sure you close your applications (or tell your users to close their
286 applications) before the backup. Fortunately,
287 most Microsoft applications do not open
288 files exclusively so that they can be backed up. However, you will need to
289 experiment. In any case, if Bacula cannot open the file, it will print an
290 error message, so you will always know which files were not backed up.
291 For version 1.37.25 and greater, see the section below on
292 Volume Shadow Copy Service.
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 (a major disaster for backup
306 programs on Windows), Bacula can now access all system files. This means
307 that when you restore files, the security and ownership information will be
308 restored on WinNT/2K/XP along with the data.
310 The disadvantage of the Windows backup API calls is that it produces
311 non-portable backups. That is files and their data that are backed up on
312 WinNT using the native API calls (BackupRead/BackupWrite) cannot be
313 restored on Win95/98/Me or Unix systems. In principle, a file backed up on
314 WinNT can be restored on WinXP, but this remains to be seen in practice
315 (not yet tested). In addition, the stand-alone tools such as {\bf bls} and
316 {\bf bextract} cannot be used to retrieve the data for those files because
317 those tools are not available on Windows. All restores must use the Bacula
318 {\bf restore} command. This restriction is mentioned for completeness, but
319 in practice should not create any problems.
321 As a default, Bacula backs up Windows systems using the Windows API calls.
322 If you want to backup data on a WinNT/2K/XP system and restore it on a
323 Unix/Win95/98/Me system, we have provided a special {\bf portable} option
324 that backs up the data in a portable fashion by using portable API calls.
325 See the \ilink{portable option}{portable} on the Include statement in a
326 FileSet resource in the Director's configuration chapter for the details on
327 setting this option. However, using the portable option means you may have
328 permissions problems accessing files, and none of the security and
329 ownership information will be backed up or restored. The file data can,
330 however, be restored on any system.
332 You should always be able to restore any file backed up on Unix or Win95/98/Me
333 to any other system. On some systems, such as WinNT/2K/XP, you may have to
334 reset the ownership of such restored files. Any file backed up on WinNT/2K/XP
335 should in principle be able to be restored to a similar system (i.e.
336 WinNT/2K/XP), however, I am unsure of the consequences if the owner
337 information and accounts are not identical on both systems. Bacula will not
338 let you restore files backed up on WinNT/2K/XP to any other system (i.e. Unix
339 Win95/98/Me) if you have used the defaults.
341 Finally, if you specify the {\bf portable=yes} option on the files you back
342 up. Bacula will be able to restore them on any other system. However, any
343 WinNT/2K/XP specific security and ownership information will be lost.
345 The following matrix will give you an idea of what you can expect. Thanks to
346 Marc Brueckner for doing the tests:
350 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
351 \begin{longtable}{|l|l|p{2.8in}|}
353 \multicolumn{1}{|c| }{\bf Backup OS } & \multicolumn{1}{c| }{\bf Restore OS }
354 & \multicolumn{1}{c| }{\bf Results } \\
355 \hline {WinMe } & {WinMe } & {Works } \\
356 \hline {WinMe } & {WinNT } & {Works (SYSTEM permissions) } \\
357 \hline {WinMe } & {WinXP } & {Works (SYSTEM permissions) } \\
358 \hline {WinMe } & {Linux } & {Works (SYSTEM permissions) } \\
359 \hline {\ } & {\ } & {\ } \\
360 \hline {WinXP } & {WinXP } & {Works } \\
361 \hline {WinXP } & {WinNT } & {Works (all files OK, but got "The data is invalid"
363 \hline {WinXP } & {WinMe } & {Error: Win32 data stream not supported. } \\
364 \hline {WinXP } & {WinMe } & {Works if {\bf Portable=yes} specified during backup.} \\
365 \hline {WinXP } & {Linux } & {Error: Win32 data stream not supported. } \\
366 \hline {WinXP } & {Linux } & {Works if {\bf Portable=yes} specified during backup.}\\
367 \hline {\ } & {\ } & {\ } \\
368 \hline {WinNT } & {WinNT } & {Works } \\
369 \hline {WinNT } & {WinXP } & {Works } \\
370 \hline {WinNT } & {WinMe } & {Error: Win32 data stream not supported. } \\
371 \hline {WinNT } & {WinMe } & {Works if {\bf Portable=yes} specified during backup.}\\
372 \hline {WinNT } & {Linux } & {Error: Win32 data stream not supported. } \\
373 \hline {WinNT } & {Linux } & {Works if {\bf Portable=yes} specified during backup. }\\
374 \hline {\ } & {\ } & {\ } \\
375 \hline {Linux } & {Linux } & {Works } \\
376 \hline {Linux } & {WinNT } & {Works (SYSTEM permissions) } \\
377 \hline {Linux } & {WinMe } & {Works } \\
378 \hline {Linux } & {WinXP } & {Works (SYSTEM permissions) }
384 \subsection*{Volume Shadow Copy Service}
385 \index[general]{Volume Shadow Copy Service}
387 \addcontentsline{toc}{subsection}{Volume Shadow Copy Service}
388 In version 1.37.30 and greater, you can turn on Microsoft's Volume
389 Shadow Copy Service (VSS).
391 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
392 a backup-solution for Windows, this is an extremely important step. VSS
393 allows Bacula to backup open files and even to interact with applications like
394 RDBMS to produce consistent file copies. VSS aware applications are called
395 VSS Writers, they register with the OS so that when Bacula wants to do a
396 Snapshot, the OS will notify the register Writer programs, which may then
397 create a consistent state in their application, which will be backed up.
398 Examples for these writers are "MSDE" (Microsoft database
399 engine), "Event Log Writer", "Registry Writer" plus 3rd
400 party-writers. If you have a non-vss aware application (e.g.
401 SQL Anywhere or probably MySQL), a shadow copy is still generated
402 and the open files can be backed up, but there is no guarantee
403 that the file is consistent.
405 Bacula produces a message from each of the registered writer programs
406 when it is doing a VSS backup so you know which ones are correctly backed
409 Bacula supports VSS on both Windows 2003 and Windows XP.
410 Technically Bacula creates a shadow copy as soon as the backup process
411 starts. It does then backup all files from the shadow copy and destroys the
412 shadow copy after the backup process. Please have in mind, that VSS
413 creates a snapshot and thus backs up the system at the state it had
414 when starting the backup. It will disregard file changes which occur during
417 VSS can be turned on by placing an
419 \index[dir]{Enable VSS}
420 \index[general]{Enable VSS}
425 in your FileSet resource.
427 The VSS aware File daemon has the letters VSS on the signon line that
428 it produces when contacted by the console. For example:
430 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
432 the VSS is shown in the line above. This only means that the File daemon
433 is capable of doing VSS not that VSS is turned on for a particular backup.
434 There are two ways of telling if VSS is actually turned on during a backup.
435 The first is to look at the status output for a job, e.g.:
439 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
440 VSS Backup Job started: 23-Jul-05 13:25
441 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
442 Files Examined=75,021
443 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
447 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
448 This means that VSS is enabled for that job. If VSS is not enabled, it will
449 simply show "Backup Job started ..." without the letters VSS.
451 The second way to know that the job was backed up with VSS is to look at the
452 Job Report, which will look something like the following:
455 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
456 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
457 23-Jul 13:26 rufus-sd: Spooling data ...
458 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
459 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
460 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
461 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
462 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
465 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
466 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
467 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
468 that you will get a consistent snapshot of the data handled by that writer.
470 \subsection*{VSS Problems}
471 \index[general]{Problems!VSS}
472 \index[fd] {Problems!VSS}
473 \index[general]{VSS Problems}
474 \index[fd]{VSS Problems}
475 \addcontentsline{toc}{subsection}{VSS Problems}
477 If you are experiencing problems such as VSS hanging on MSDE, first try
478 running {\bf vssadmin} to check for problems, then try running {\bf
479 ntbackup} which also uses VSS to see if it has similar problems. If so, you
480 know that the problem is in your Windows machine and not with Bacula.
482 The FD hang problems were reported with {\bf MSDEwriter} when:
484 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
485 seems to use TCP/IP and not Named Pipes).
486 \item msdtcs was installed to run under "localsystem": try running msdtcs
487 under networking account (instead of local system) (com+ seems to work
488 better with this configuration).
492 \subsection*{Windows Firewalls}
493 \index[general]{Firewalls!Windows }
494 \index[general]{Windows Firewalls }
495 \addcontentsline{toc}{subsection}{Windows Firewalls}
497 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
498 are likely to find that the Bacula ports are blocked and you cannot
499 communicate to the other daemons. This can be deactivated through the {\bf
500 Security Notification} dialog, which is apparently somewhere in the {\bf
501 Security Center}. I don't have this on my computer, so I cannot give the exact
508 netsh firewall set opmode disable
512 is purported to disable the firewall, but this command is not accepted on my
515 \subsection*{Windows Port Usage}
516 \index[general]{Windows Port Usage }
517 \index[general]{Usage!Windows Port }
518 \addcontentsline{toc}{subsection}{Windows Port Usage}
520 If you want to see if the File daemon has properly opened the port and is
521 listening, you can enter the following command in a shell window:
525 netstat -an | findstr 910[123]
529 \subsection*{Windows Disaster Recovery}
530 \index[general]{Recovery!Windows Disaster }
531 \index[general]{Windows Disaster Recovery }
532 \addcontentsline{toc}{subsection}{Windows Disaster Recovery}
534 We don't currently have a good solution for disaster recovery on Windows as we
535 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
536 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
537 that could possibly work, but we have not investigated it. This means that
538 until someone figures out the correct procedure, you must restore the OS from
539 the installation disks, then you can load a Bacula client and restore files.
540 Please don't count on using {\bf bextract} to extract files from your backup
541 tapes during a disaster recovery unless you have backed up those files using
542 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
543 normal way Bacula saves files using the Windows API prevents the files from
544 being restored on a Unix machine. Once you have an operational Windows OS
545 loaded, you can run the File daemon and restore your user files.
548 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
549 suggestion, which looks very promising.
551 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
552 Environment) Boot-CD, may be just what is needed to build a complete disaster
553 recovery system for Win32. This distribution can be found at
554 \elink{http://www.nu2.nu/pebuilder/ }{http://www.nu2.nu/pebuilder/}.
556 \subsection*{Windows Restore Problems}
557 \index[general]{Problems!Windows Restore}
558 \index[general]{Windows Restore Problems}
559 \addcontentsline{toc}{subsection}{Windows Restore Problems}
561 \ilink{Restore Chapter}{Windows} of this manual for problems
562 that you might encounter doing a restore.
565 \subsection*{Windows Ownership and Permissions Problems}
566 \index[general]{Problems!Windows Ownership and Permissions }
567 \index[general]{Windows Ownership and Permissions Problems }
568 \addcontentsline{toc}{subsection}{Windows Ownership and Permissions
571 If you restore files backed up from WinNT/XP/2K to an alternate directory,
572 Bacula may need to create some higher level directories that were not saved
573 (or restored). In this case, the File daemon will create them under the SYSTEM
574 account because that is the account that Bacula runs under as a service. As of
575 version 1.32f-3, Bacula creates these files with full access permission.
576 However, there may be cases where you have problems accessing those files even
577 if you run as administrator. In principle, Microsoft supplies you with the way
578 to cease the ownership of those files and thus change the permissions.
579 However, a much better solution to working with and changing Win32 permissions
580 is the program {\bf SetACL}, which can be found at
581 \elink{http://setacl.sourceforge.net/ }{http://setacl.sourceforge.net/}.
583 If you have not installed Bacula while running as Administrator
584 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
585 then it is very unlikely that it will have sufficient permission to
586 access all your files.
588 Some users have experienced problems restoring files that participate in
589 the Active Directory. They also report that changing the userid under which
590 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
594 \subsection*{Manually resetting the Permissions}
595 \index[general]{Manually resetting the Permissions }
596 \index[general]{Permissions!Manually resetting the }
597 \addcontentsline{toc}{subsection}{Manually resetting the Permissions}
599 The following solution was provided by Dan Langille \lt{}dan at langille in
600 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
601 they should apply to most Win32 platforms. The procedure outlines how to deal
602 with a problem which arises when a restore creates a top-level new directory.
603 In this example, "top-level" means something like {\bf
604 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
605 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
606 as the {\bf Where:} value, this problem will arise.
608 The problem appears as a directory which cannot be browsed with Windows
609 Explorer. The symptoms include the following message when you try to click on
612 \includegraphics{./access-is-denied.eps}
614 If you encounter this message, the following steps will change the permissions
615 to allow full access.
618 \item right click on the top level directory (in this example, {\bf c:/src})
619 and select {\bf Properties}.
620 \item click on the Security tab.
621 \item If the following message appears, you can ignore it, and click on {\bf
624 \includegraphics{./view-only.eps}
626 You should see something like this:
628 \includegraphics{./properties-security.eps}
629 \item click on Advanced
630 \item click on the Owner tab
631 \item Change the owner to something other than the current owner (which is
632 {\bf SYSTEM} in this example as shown below).
634 \includegraphics{./properties-security-advanced-owner.eps}
635 \item ensure the "Replace owner on subcontainers and objects" box is
638 \item When the message "You do not have permission to read the contents of
639 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
640 the directory permissions with permissions granting you Full Control?", click
643 \includegraphics{./confirm.eps}
644 \item Click on OK to close the Properties tab
647 With the above procedure, you should now have full control over your restored
650 In addition to the above methods of changing permissions, there is a Microsoft
651 program named {\bf cacls} that can perform similar functions.
653 \subsection*{Backing Up the WinNT/XP/2K System State}
654 \index[general]{State!Backing Up the WinNT/XP/2K System }
655 \index[general]{Backing Up the WinNT/XP/2K System State }
656 \addcontentsline{toc}{subsection}{Backing Up the WinNT/XP/2K System State}
658 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
659 conjunction with Bacula should permit a full restore of any damaged system
660 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
661 state prior to running a Bacula backup with the following command:
665 ntbackup backup systemstate /F c:\systemstate.bkf
669 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
670 system state and not all the user files, and the {\bf /F
671 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
672 this file must then be saved and restored by Bacula.
674 To restore the system state, you first reload a base operating system if the
675 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
676 restore all the damaged or lost user's files and to recover the {\bf
677 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
678 missing system files or registry problems, you run {\bf NTBackup} and {\bf
679 catalogue} the system statefile, and then select it for restore. The
680 documentation says you can't run a command line restore of the systemstate.
682 To the best of my knowledge, this has not yet been tested. If you test it,
683 please report your results to the Bacula email list.
685 \subsection*{Windows Considerations for Filename Specifications}
686 \index[general]{Specifications!Windows Considerations for Filename }
687 \index[general]{Windows Considerations for Filename Specifications }
688 \addcontentsline{toc}{subsection}{Windows Considerations for Filename
692 \ilink{Director's Configuration chapter}{win32} of this manual
693 for important considerations on how to specify Windows paths in Bacula FileSet
694 Include and Exclude directives.
696 \index[general]{Unicode}
697 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
698 As of that version, both {\bf bconsole} and {\bf wx-console} support Windows
699 Unicode filenames. There may still be some problems with multiple byte
700 characters (e.g. Chinese, ...) where it is a two byte character but the
701 displayed character is not two characters wide.
703 \index[general]{Win32 path length restriction}
704 Path/filenames longer than 260 characters are not supported. This may be
705 possible in a future version.
707 \subsection*{Command Line Options Specific to the Bacula Windows File
709 \index[general]{Client!Command Line Options Specific to the Bacula Windows
711 \index[general]{Command Line Options Specific to the Bacula Windows File
713 \addcontentsline{toc}{subsection}{Command Line Options Specific to the
714 Bacula Windows File Daemon (Client)}
716 These options are not normally seen or used by the user, and are documented
717 here only for information purposes. At the current time, to change the default
718 options, you must either manually run {\bf Bacula} or you must manually edit
719 the system registry and modify the appropriate entries.
721 In order to avoid option clashes between the options necessary for {\bf
722 Bacula} to run on Windows and the standard Bacula options, all Windows
723 specific options are signaled with a forward slash character (/), while as
724 usual, the standard Bacula options are signaled with a minus (-), or a minus
725 minus (\verb:--:). All the standard Bacula options can be used on the Windows
726 version. In addition, the following Windows only options are implemented:
730 \item [/servicehelper ]
731 \index[fd]{/servicehelper }
732 Run the service helper application (don't use this it is deprecated.).
735 \index[fd]{/service }
736 Start Bacula as a service
740 Run the Bacula application
743 \index[fd]{/install }
744 Install Bacula as a service in the system registry
748 Uninstall Bacula from the system registry
752 Show the Bacula about dialogue box
756 Show the Bacula status dialogue box
760 Show the Bacula events dialogue box (not yet implemented)
764 Stop any running {\bf Bacula}
768 Show the Bacula help dialogue box
771 It is important to note that under normal circumstances the user should never
772 need to use these options as they are normally handled by the system
773 automatically once Bacula is installed. However, you may note these options in
774 some of the .bat files that have been created for your use.
776 \subsection*{Shutting down Windows Systems}
777 \index[general]{Shutting down Windows Systems }
778 \index[general]{Systems!Shutting down Windows }
779 \addcontentsline{toc}{subsection}{Shutting down Windows Systems}
781 Some users like to shutdown their windows machines after a backup using a
782 Client Run After Job directive. If you want to do something similar, you might
783 take the shutdown program from the
784 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
785 \elink{Sysinternals project}{http://www.sysinternals.com/ntw2k/freeware/psshutdown.shtml}.