4 \chapter{The Windows Version of Bacula}
6 \index[general]{Windows Version of Bacula}
8 At the current time only the File daemon or Client program has
9 been thouroughly tested on Windows and is suitable for a
10 production environment. As a consequence, when we
11 speak of the Windows version of Bacula below, we are referring to
12 the File daemon (client) only.
14 The Windows version of the Bacula File daemon has been tested on
15 WinXP, Win2000, Windows Server 2003, Windows Server 2008,
16 Vista, and Windows 7 systems.
17 The Windows version of
18 Bacula is a native Win32 port, but there are very few source code changes
19 to the Unix code, which means that the Windows version is for the most part
20 running code that has long proved stable on Unix systems. When running, it
21 is perfectly integrated with Windows and displays its icon in the system
22 icon tray, and provides a system tray menu to obtain additional information
23 on how Bacula is running (status and events dialog boxes). If so desired,
24 it can also be stopped by using the system tray menu, though this should
25 normally never be necessary.
27 Once installed Bacula normally runs as a system service. This means that it is
28 immediately started by the operating system when the system is booted, and
29 runs in the background even if there is no user logged into the system.
31 \section{Win32 Installation}
33 \index[general]{Installation}
34 \index[general]{Win32!Installation}
36 Normally, you will install the Windows version of Bacula from the binaries.
37 This install is standard Windows .exe that runs an install wizard using the
38 NSIS Free Software installer, so if you have already installed Windows
39 software, it should be very familiar to you.
41 If you have a previous version of Bacula
42 installed, you should stop the service, uninstall it, and remove
43 the Bacula installation directory possibly saving your
44 bacula-fd.conf, bconsole.conf, and bat.conf files
45 for use with the new version you will install. The Uninstall
46 program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
47 We also recommend that you completely remove the directory
48 {\bf c:\textbackslash{}bacula}, because the current installer
49 uses a different directory structure (see below).
51 Providing you do not already have Bacula installed,
52 the installer installs the binaries and dlls in
53 c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
54 and the configuration files
55 in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
56 In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
57 will be created during the installation, and on that menu, you
58 will find items for editing the configuration files, displaying
59 the document, and starting bwx-console or bconsole.
62 Finally, proceed with the installation.
65 \item You must be logged in as Administrator to the local machine
66 to do a correct installation, if not, please do so before continuing.
67 Some users have attempted to install logged in as a domain administrator
68 account and experienced permissions problems attempting to run
69 Bacula, so we don't recommend that option.
71 \item Simply double click on the {\bf bacula-win32-5.xx.0.exe} NSIS install
72 icon. The actual name of the icon will vary from one release version to
75 \includegraphics{\idir win32-nsis.eps} bacula-win32-5.xx.0.exe
77 \item Once launched, the installer wizard will ask you if you want to install
80 \addcontentsline{lof}{figure}{Win32 Client Setup Wizard}
81 \includegraphics{\idir win32-welcome.eps}
83 \item Next you will be asked to select the installation type.
85 \addcontentsline{lof}{figure}{Win32 Installation Type}
86 \includegraphics{\idir win32-installation-type.eps}
89 \item If you proceed, you will be asked to select the components to be
90 installed. You may install the Bacula program (Bacula File Service) and or
91 the documentation. Both will be installed in sub-directories of the install
92 location that you choose later. The components dialog looks like the
95 \addcontentsline{lof}{figure}{Win32 Component Selection Dialog}
96 \includegraphics{\idir win32-pkg.eps}
97 \index[general]{Upgrading}
99 \item If you are installing for the first time, you will be asked to
100 enter some very basic information about your configuration. If
101 you are not sure what to enter, or have previously saved configuration
102 files, you can put anything you want into the fields, then either
103 replace the configuration files later with the ones saved, or edit
106 If you are upgrading an existing installation, the following will
110 \addcontentsline{lof}{figure}{Win32 Configure}
111 \includegraphics{\idir win32-config.eps}
113 \item While the various files are being loaded, you will see the following
116 \addcontentsline{lof}{figure}{Win32 Install Progress}
117 \includegraphics{\idir win32-installing.eps}
120 \item Finally, the finish dialog will appear:
122 \addcontentsline{lof}{figure}{Win32 Client Setup Completed}
123 \includegraphics{\idir win32-finish.eps}
128 That should complete the installation process. When the Bacula File Server is
129 ready to serve files, an icon \includegraphics{\idir idle.eps} representing a
130 cassette (or tape) will appear in the system tray
131 \includegraphics{\idir tray-icon.eps}; right click on it and a menu will appear.\\
132 \includegraphics{\idir menu.eps}\\
133 The {\bf Events} item is currently unimplemented, by selecting the {\bf
134 Status} item, you can verify whether any jobs are running or not.
136 When the Bacula File Server begins saving files, the color of the holes in the
137 cassette icon will change from white to green \includegraphics{\idir running.eps},
138 and if there is an error, the holes in the cassette icon will change to red
139 \includegraphics{\idir error.eps}.
141 If you are using remote desktop connections between your Windows boxes, be
142 warned that that tray icon does not always appear. It will always be visible
143 when you log into the console, but the remote desktop may not display it.
145 \section{Post Win32 Installation}
146 \index[general]{Post Win32 Installation}
147 \index[general]{Win32!Post Installation}
149 After installing Bacula and before running it, you should check the contents
150 of the configuration files to ensure that they correspond to your
151 installation. You can get to them by using:
152 the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
154 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
155 is running as a process (not an Application) with User Name SYSTEM. If this is
156 not the case, you probably have not installed Bacula while running as
157 Administrator, and hence it will be unlikely that Bacula can access
158 all the system files.
160 \section{Uninstalling Bacula on Win32}
161 \index[general]{Win32!Uninstalling Bacula}
162 \index[general]{Uninstalling Bacula on Win32}
164 Once Bacula has been installed, it can be uninstalled using the standard
165 Windows Add/Remove Programs dialog found on the Control panel.
167 \section{Dealing with Win32 Problems}
169 \index[general]{Win32!Dealing with Problems}
170 \index[general]{Dealing with Win32 Problems}
172 Sometimes Win32 machines the File daemon may have very slow
173 backup transfer rates compared to other machines. To you might
174 try setting the Maximum Network Buffer Size to 32,768 in both the
175 File daemon and in the Storage daemon. The default size is larger,
176 and apparently some Windows ethernet controllers do not deal with
177 a larger network buffer size.
179 Many Windows ethernet drivers have a tendency to either run slowly
180 due to old broken firmware, or because they are running in half-duplex
181 mode. Please check with the ethernet card manufacturer for the latest
182 firmware and use whatever techniques are necessary to ensure that the
183 card is running in duplex.
185 If you are not using the portable option, and you have VSS
186 (Volume Shadow Copy) enabled in the Director, and you experience
187 problems with Bacula not being able to open files, it is most
188 likely that you are running an antivirus program that blocks
189 Bacula from doing certain operations. In this case, disable the
190 antivirus program and try another backup. If it succeeds, either
191 get a different (better) antivirus program or use something like
192 RunClientJobBefore/After to turn off the antivirus program while
193 the backup is running.
195 If turning off anti-virus software does not resolve your VSS
196 problems, you might have to turn on VSS debugging. The following
197 link describes how to do this:
198 \elink{http://support.microsoft.com/kb/887013/en-us}{http://support.microsoft.com/kb/887013/en-us}.
200 In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
201 is turned off by default. To turn it on, please see the following link:
202 \elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{
203 http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}
206 The most likely source of problems is authentication when the Director
207 attempts to connect to the File daemon that you installed. This can occur if
208 the names and the passwords defined in the File daemon's configuration file
209 {\bf bacula-fd.conf} file on
210 the Windows machine do not match with the names and the passwords in the
211 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
214 More specifically, the password found in the {\bf Client} resource in the
215 Director's configuration file must be the same as the password in the {\bf
216 Director} resource of the File daemon's configuration file. In addition, the
217 name of the {\bf Director} resource in the File daemon's configuration file
218 must be the same as the name in the {\bf Director} resource of the Director's
221 It is a bit hard to explain in words, but if you understand that a Director
222 normally has multiple Clients and a Client (or File daemon) may permit access
223 by multiple Directors, you can see that the names and the passwords on both
224 sides must match for proper authentication.
226 One user had serious problems with the configuration file until he realized
227 that the Unix end of line conventions were used and Bacula wanted them in
228 Windows format. This has not been confirmed though, and Bacula version 2.0.0
229 and above should now accept all end of line conventions (Win32,
232 Running Unix like programs on Windows machines is a bit frustrating because
233 the Windows command line shell (DOS Window) is rather primitive. As a
234 consequence, it is not generally possible to see the debug information and
235 certain error messages that Bacula prints. With a bit of work, however, it is
236 possible. When everything else fails and you want to {\bf see} what is going
237 on, try the following:
241 Start a DOS shell Window.
242 c:\Program Files\bacula\bacula-fd -t >out
247 The precise path to bacula-fd depends on where it is installed.
248 The {\bf -t} option will cause Bacula to read the configuration file, print
249 any error messages and then exit. the {\bf \gt{}} redirects the output to the
250 file named {\bf out}, which you can list with the {\bf type} command.
252 If something is going wrong later, or you want to run {\bf Bacula} with a
253 debug option, you might try starting it as:
257 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
261 In this case, Bacula will run until you explicitly stop it, which will give
262 you a chance to connect to it from your Unix/Linux server. In later versions
263 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
264 can write the output to a trace file {\bf bacula.trace} in the current
265 directory. To enable this, before running a job, use the console, and enter:
273 then run the job, and once you have terminated the File daemon, you will find
274 the debug output in the {\bf bacula.trace} file, which will probably be
275 located in the same directory as bacula-fd.exe.
277 In addition, you should look in the System Applications log on the Control
278 Panel to find any Windows errors that Bacula got during the startup process.
280 Finally, due to the above problems, when you turn on debugging, and specify
281 trace=1 on a setdebug command in the Console, Bacula will write the debug
282 information to the file {\bf bacula.trace} in the directory from which Bacula
285 If you are having problems with ClientRunBeforeJob scripts randomly dying,
286 it is possible that you have run into an Oracle bug. See bug number 622 in
287 the bugs.bacula.org database. The following information has been
288 provided by a user on this issue:
292 The information in this document applies to:
293 Oracle HTTP Server - Version: 9.0.4
294 Microsoft Windows Server 2003
296 When starting an OC4J instance, the System Clock runs faster, about 7
301 + This is caused by the Sun JVM bug 4500388, which states that "Calling
302 Thread.sleep() with a small argument affects the system clock". Although
303 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
305 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
307 + Also reported by Microsoft as "The system clock may run fast when you
308 use the ACPI power management timer as a high-resolution counter on Windows
309 2000-based computers" (See http://support.microsoft.com/?id=821893)
313 You may wish to start the daemon with debug mode on rather than doing it
314 using bconsole. To do so, edit the following registry key:
318 HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
322 using regedit, then add -dnn after the /service option, where nn represents
323 the debug level you want.
325 \label{Compatibility}
326 \section{Windows Compatibility Considerations}
327 \index[general]{Windows Compatibility Considerations}
328 \index[general]{Considerations!Windows Compatibility}
330 If you are not using the VSS (Volume Shadow Copy) option described in the
331 next section of this chapter, and if any applications are running during
332 the backup and they have files opened exclusively, Bacula will not be able
333 to backup those files, so be sure you close your applications (or tell your
334 users to close their applications) before the backup. Fortunately, most
335 Microsoft applications do not open files exclusively so that they can be
336 backed up. However, you will need to experiment. In any case, if Bacula
337 cannot open the file, it will print an error message, so you will always
338 know which files were not backed up. For version 1.37.25 and greater, see
339 the section below on Volume Shadow Copy Service that permits backing up any
342 During backup, Bacula doesn't know about the system registry, so you will
343 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
344 program specifically designed to make a copy or backup the registry.
346 In Bacula version 1.31 and later, we use Windows backup API calls by
347 default. Typical of Windows, programming these special BackupRead and
348 BackupWrite calls is a real nightmare of complications. The end result
349 gives some distinct advantages and some disadvantages.
351 First, the advantages are that Windows systems, the security and
352 ownership information is now backed up. In addition, with the exception of
353 files in exclusive use by another program, Bacula can now access all system
354 files. This means that when you restore files, the security and ownership
355 information will be restored on Windows along with the data.
357 The disadvantage of the Windows backup API calls is that it produces
358 non-portable backups. That is files and their data that are backed up on
359 Windows using the native API calls (BackupRead/BackupWrite) cannot be
360 directly restored on Linux or Unix systems. Bacula should be able to read
361 non-portable backups on any system and restore the data appropriately.
362 However, on a system that does not have the BackupRead/BackupWrite calls
363 (older Windows versions and all Unix/Linux machines), though the file data
364 can be restored, the Windows security and access control data will not be
365 restored. This means that a standard set of access permissions will be set
366 for such restored files.
369 As a default, Bacula backs up Windows systems using the Windows API calls.
370 If you want to backup data on a Windows system and restore it on a
371 Unix or Linux system, we have provided a special {\bf portable} option
372 that backs up the data in a portable fashion by using portable API calls.
373 See the \ilink{portable option}{portable} on the Include statement in a
374 FileSet resource in the Director's configuration chapter for the details on
375 setting this option. However, using the portable option means you may have
376 permissions problems accessing files, and none of the security and
377 ownership information will be backed up or restored. The file data can,
378 however, be restored on any system.
380 You should always be able to restore any file backed up on Unix or Win95/98/Me
381 to any other system. On some older Windows systems, you may have to
382 reset the ownership of such restored files.
384 Finally, if you specify the {\bf portable=yes} option on the files you back
385 up. Bacula will be able to restore them on any other system. However, any
386 Windows specific security and ownership information will be lost.
388 The following matrix will give you an idea of what you can expect. Thanks to
389 Marc Brueckner for doing the tests:
391 \addcontentsline{lot}{table}{WinNT/2K/XP Restore Portability Status}
392 \begin{longtable}{|l|l|p{2.8in}|}
394 \multicolumn{1}{|c|}{\bf Backup OS} & \multicolumn{1}{c|}{\bf Restore OS}
395 & \multicolumn{1}{c|}{\bf Results } \\
396 \hline {WinMe} & {WinMe} & {Works } \\
397 \hline {WinMe} & {WinNT} & {Works (SYSTEM permissions) } \\
398 \hline {WinMe} & {WinXP} & {Works (SYSTEM permissions) } \\
399 \hline {WinMe} & {Linux} & {Works (SYSTEM permissions) } \\
400 \hline {\ } & {\ } & {\ } \\
401 \hline {WinXP} & {WinXP} & {Works } \\
402 \hline {WinXP} & {WinNT} & {Works (all files OK, but got "The data is invalid"
404 \hline {WinXP} & {WinMe} & {Error: Win32 data stream not supported. } \\
405 \hline {WinXP} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.} \\
406 \hline {WinXP} & {Linux} & {Error: Win32 data stream not supported. } \\
407 \hline {WinXP} & {Linux} & {Works if {\bf Portable=yes} specified during backup.}\\
408 \hline {\ } & {\ } & {\ } \\
409 \hline {WinNT} & {WinNT} & {Works } \\
410 \hline {WinNT} & {WinXP} & {Works } \\
411 \hline {WinNT} & {WinMe} & {Error: Win32 data stream not supported. } \\
412 \hline {WinNT} & {WinMe} & {Works if {\bf Portable=yes} specified during backup.}\\
413 \hline {WinNT} & {Linux} & {Error: Win32 data stream not supported. } \\
414 \hline {WinNT} & {Linux} & {Works if {\bf Portable=yes} specified during backup. }\\
415 \hline {\ } & {\ } & {\ } \\
416 \hline {Linux} & {Linux} & {Works } \\
417 \hline {Linux} & {WinNT} & {Works (SYSTEM permissions) } \\
418 \hline {Linux} & {WinMe} & {Works } \\
419 \hline {Linux} & {WinXP} & {Works (SYSTEM permissions)}
423 Note: with Bacula versions 1.39.x and later, non-portable Windows data can
424 be restore to any machine.
428 \section{Volume Shadow Copy Service}
429 \index[general]{Volume Shadow Copy Service}
431 In version 1.37.30 and greater, you can turn on Microsoft's Volume
432 Shadow Copy Service (VSS).
434 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
435 a backup-solution for Windows, this is an extremely important step. VSS
436 allows Bacula to backup open files and even to interact with applications like
437 RDBMS to produce consistent file copies. VSS aware applications are called
438 VSS Writers, they register with the OS so that when Bacula wants to do a
439 Snapshot, the OS will notify the register Writer programs, which may then
440 create a consistent state in their application, which will be backed up.
441 Examples for these writers are "MSDE" (Microsoft database
442 engine), "Event Log Writer", "Registry Writer" plus 3rd
443 party-writers. If you have a non-vss aware application (e.g.
444 SQL Anywhere or probably MySQL), a shadow copy is still generated
445 and the open files can be backed up, but there is no guarantee
446 that the file is consistent.
448 Bacula produces a message from each of the registered writer programs
449 when it is doing a VSS backup so you know which ones are correctly backed
452 Bacula supports VSS on both Windows 2003 and Windows XP.
453 Technically Bacula creates a shadow copy as soon as the backup process
454 starts. It does then backup all files from the shadow copy and destroys the
455 shadow copy after the backup process. Please have in mind, that VSS
456 creates a snapshot and thus backs up the system at the state it had
457 when starting the backup. It will disregard file changes which occur during
460 VSS can be turned on by placing an
462 \index[dir]{Enable VSS}
463 \index[general]{Enable VSS}
468 in your FileSet resource.
470 The VSS aware File daemon has the letters VSS on the signon line that
471 it produces when contacted by the console. For example:
473 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
475 the VSS is shown in the line above. This only means that the File daemon
476 is capable of doing VSS not that VSS is turned on for a particular backup.
477 There are two ways of telling if VSS is actually turned on during a backup.
478 The first is to look at the status output for a job, e.g.:
482 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
483 VSS Backup Job started: 23-Jul-05 13:25
484 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
485 Files Examined=75,021
486 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
490 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
491 This means that VSS is enabled for that job. If VSS is not enabled, it will
492 simply show "Backup Job started ..." without the letters VSS.
494 The second way to know that the job was backed up with VSS is to look at the
495 Job Report, which will look something like the following:
498 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
499 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
500 23-Jul 13:26 rufus-sd: Spooling data ...
501 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
502 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
503 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
504 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
505 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
508 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
509 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
510 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
511 that you will get a consistent snapshot of the data handled by that writer.
513 \section{VSS Problems}
514 \index[general]{Problems!VSS}
515 \index[fd] {Problems!VSS}
516 \index[general]{VSS Problems}
517 \index[fd]{VSS Problems}
519 If you are experiencing problems such as VSS hanging on MSDE, first try
520 running {\bf vssadmin} to check for problems, then try running {\bf
521 ntbackup} which also uses VSS to see if it has similar problems. If so, you
522 know that the problem is in your Windows machine and not with Bacula.
524 The FD hang problems were reported with {\bf MSDEwriter} when:
526 \item a local firewall locked local access to the MSDE TCP port (MSDEwriter
527 seems to use TCP/IP and not Named Pipes).
528 \item msdtcs was installed to run under "localsystem": try running msdtcs
529 under networking account (instead of local system) (com+ seems to work
530 better with this configuration).
534 \section{Windows Firewalls}
535 \index[general]{Firewalls!Windows}
536 \index[general]{Windows Firewalls}
538 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
539 are likely to find that the Bacula ports are blocked and you cannot
540 communicate to the other daemons. This can be deactivated through the {\bf
541 Security Notification} dialog, which is apparently somewhere in the {\bf
542 Security Center}. I don't have this on my computer, so I cannot give the exact
549 netsh firewall set opmode disable
553 is purported to disable the firewall, but this command is not accepted on my
556 \section{Windows Port Usage}
557 \index[general]{Windows Port Usage}
558 \index[general]{Usage!Windows Port}
560 If you want to see if the File daemon has properly opened the port and is
561 listening, you can enter the following command in a shell window:
565 netstat -an | findstr 910[123]
569 TopView is another program that has been recommend, but it is not a
570 standard Win32 program, so you must find and download it from the Internet.
572 \section{Windows Disaster Recovery}
573 \index[general]{Recovery!Windows Disaster}
574 \index[general]{Windows Disaster Recovery}
576 We don't currently have a good solution for disaster recovery on Windows as we
577 do on Linux. The main piece lacking is a Windows boot floppy or a Windows boot
578 CD. Microsoft releases a Windows Pre-installation Environment ({\bf WinPE})
579 that could possibly work, but we have not investigated it. This means that
580 until someone figures out the correct procedure, you must restore the OS from
581 the installation disks, then you can load a Bacula client and restore files.
582 Please don't count on using {\bf bextract} to extract files from your backup
583 tapes during a disaster recovery unless you have backed up those files using
584 the {\bf portable} option. {\bf bextract} does not run on Windows, and the
585 normal way Bacula saves files using the Windows API prevents the files from
586 being restored on a Unix machine. Once you have an operational Windows OS
587 loaded, you can run the File daemon and restore your user files.
590 \ilink{ Disaster Recovery of Win32 Systems}{Win3233} for the latest
591 suggestion, which looks very promising.
593 It looks like Bart PE Builder, which creates a Windows PE (Pre-installation
594 Environment) Boot-CD, may be just what is needed to build a complete disaster
595 recovery system for Win32. This distribution can be found at
596 \elink{http://www.nu2.nu/pebuilder/}{http://www.nu2.nu/pebuilder/}.
598 \section{Windows Restore Problems}
599 \index[general]{Problems!Windows Restore}
600 \index[general]{Windows Restore Problems}
602 \ilink{Restore Chapter}{Windows} of this manual for problems
603 that you might encounter doing a restore.
605 section{Windows Backup Problems}
606 \index[general]{Problems!Windows Backup}
607 \index[general]{Windows Backup Problems}
608 If during a Backup, you get the message:
609 {\bf ERR=Access is denied} and you are using the portable option,
610 you should try both adding both the non-portable (backup API) and
611 the Volume Shadow Copy options to your Director's conf file.
613 In the Options resource:
620 In the FileSet resource:
627 In general, specifying these two options should allow you to backup
628 any file on a Windows system. However, in some cases, if users
629 have allowed to have full control of their folders, even system programs
630 such a Bacula can be locked out. In this case, you must identify
631 which folders or files are creating the problem and do the following:
634 \item Grant ownership of the file/folder to the Administrators group,
635 with the option to replace the owner on all child objects.
636 \item Grant full control permissions to the Administrators group,
637 and change the user's group to only have Modify permission to
638 the file/folder and all child objects.
641 Thanks to Georger Araujo for the above information.
643 \section{Windows Ownership and Permissions Problems}
644 \index[general]{Problems!Windows Ownership and Permissions}
645 \index[general]{Windows Ownership and Permissions Problems}
647 If you restore files backed up from Windows to an alternate directory,
648 Bacula may need to create some higher level directories that were not saved
649 (or restored). In this case, the File daemon will create them under the SYSTEM
650 account because that is the account that Bacula runs under as a service. As of
651 version 1.32f-3, Bacula creates these files with full access permission.
652 However, there may be cases where you have problems accessing those files even
653 if you run as administrator. In principle, Microsoft supplies you with the way
654 to cease the ownership of those files and thus change the permissions.
655 However, a much better solution to working with and changing Win32 permissions
656 is the program {\bf SetACL}, which can be found at
657 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
659 If you have not installed Bacula while running as Administrator
660 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
661 then it is very unlikely that it will have sufficient permission to
662 access all your files.
664 Some users have experienced problems restoring files that participate in
665 the Active Directory. They also report that changing the userid under which
666 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
670 \section{Manually resetting the Permissions}
671 \index[general]{Manually resetting the Permissions}
672 \index[general]{Permissions!Manually resetting the}
674 The following solution was provided by Dan Langille \lt{}dan at langille in
675 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
676 they should apply to most Win32 platforms. The procedure outlines how to deal
677 with a problem which arises when a restore creates a top-level new directory.
678 In this example, "top-level" means something like {\bf
679 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
680 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
681 as the {\bf Where:} value, this problem will arise.
683 The problem appears as a directory which cannot be browsed with Windows
684 Explorer. The symptoms include the following message when you try to click on
687 \includegraphics{\idir access-is-denied.eps}
689 If you encounter this message, the following steps will change the permissions
690 to allow full access.
693 \item right click on the top level directory (in this example, {\bf c:/src})
694 and select {\bf Properties}.
695 \item click on the Security tab.
696 \item If the following message appears, you can ignore it, and click on {\bf
699 \includegraphics{\idir view-only.eps}
701 You should see something like this:
703 \includegraphics{\idir properties-security.eps}
704 \item click on Advanced
705 \item click on the Owner tab
706 \item Change the owner to something other than the current owner (which is
707 {\bf SYSTEM} in this example as shown below).
709 \includegraphics{\idir properties-security-advanced-owner.eps}
710 \item ensure the "Replace owner on subcontainers and objects" box is
713 \item When the message "You do not have permission to read the contents of
714 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
715 the directory permissions with permissions granting you Full Control?", click
718 \includegraphics{\idir confirm.eps}
719 \item Click on OK to close the Properties tab
722 With the above procedure, you should now have full control over your restored
725 In addition to the above methods of changing permissions, there is a Microsoft
726 program named {\bf cacls} that can perform similar functions.
728 \section{Backing Up the WinNT/XP/2K System State}
729 \index[general]{State!Backing Up the WinNT/XP/2K System}
730 \index[general]{Backing Up the WinNT/XP/2K System State}
732 Note, most of this section applies to the older Windows OSes that
733 do not have VSS. On newer Windows OSes that have VSS, all files
734 including the System State will by default be properly backed
737 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
738 conjunction with Bacula should permit a full restore of any damaged system
739 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
740 state prior to running a Bacula backup with the following command:
744 ntbackup backup systemstate /F c:\systemstate.bkf
748 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
749 system state and not all the user files, and the {\bf /F
750 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
751 this file must then be saved and restored by Bacula.
753 To restore the system state, you first reload a base operating system if the
754 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
755 restore all the damaged or lost user's files and to recover the {\bf
756 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
757 missing system files or registry problems, you run {\bf NTBackup} and {\bf
758 catalogue} the system statefile, and then select it for restore. The
759 documentation says you can't run a command line restore of the systemstate.
761 To the best of my knowledge, this has not yet been tested. If you test it,
762 please report your results to the Bacula email list.
764 Note, Bacula uses VSS to backup and restore open files and
765 system files, but on older Windows machines such as WinNT and
766 Win2000, VSS is not implemented by Microsoft so that you must
767 use some special techniques to back them up as described
768 above. On new Windows machines, Bacula will backup and restore
769 all files including the system state providing you have
770 VSS enabled in your Bacula FileSet (default).
772 \section{Considerations for Filename Specifications}
773 \index[general]{Windows!Considerations for Filename Specifications}
776 \ilink{Director's Configuration chapter}{win32} of this manual
777 for important considerations on how to specify Windows paths in Bacula FileSet
778 Include and Exclude directives.
780 \index[general]{Unicode}
781 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
782 As of that version, both {\bf bconsole} and {\bf bwx-console} support Windows
783 Unicode filenames. There may still be some problems with multiple byte
784 characters (e.g. Chinese, ...) where it is a two byte character but the
785 displayed character is not two characters wide.
787 \index[general]{Win32 Path Length Restriction}
788 Path/filenames longer than 260 characters (up to 32,000) are supported
789 beginning with Bacula version 1.39.20. Older Bacula versions support
790 only 260 character path/filenames.
792 \section{Win32 Specific File daemon Command Line}
793 \index[general]{Client!Win32 Specific File daemon Command Line Options}
794 \index[general]{Win32 Specific File daemon Command Line Options}
796 These options are not normally seen or used by the user, and are documented
797 here only for information purposes. At the current time, to change the default
798 options, you must either manually run {\bf Bacula} or you must manually edit
799 the system registry and modify the appropriate entries.
801 In order to avoid option clashes between the options necessary for {\bf
802 Bacula} to run on Windows and the standard Bacula options, all Windows
803 specific options are signaled with a forward slash character (/), while as
804 usual, the standard Bacula options are signaled with a minus (-), or a minus
805 minus (\verb:--:). All the standard Bacula options can be used on the Windows
806 version. In addition, the following Windows only options are implemented:
812 Start Bacula as a service
816 Run the Bacula application
820 Install Bacula as a service in the system registry
824 Uninstall Bacula from the system registry
828 Show the Bacula about dialogue box
832 Show the Bacula status dialogue box
836 Show the Bacula events dialogue box (not yet implemented)
840 Stop any running {\bf Bacula}
844 Show the Bacula help dialogue box
847 It is important to note that under normal circumstances the user should never
848 need to use these options as they are normally handled by the system
849 automatically once Bacula is installed. However, you may note these options in
850 some of the .bat files that have been created for your use.
852 \section{Shutting down Windows Systems}
853 \index[general]{Shutting down Windows Systems}
854 \index[general]{Systems!Shutting down Windows}
856 Some users like to shutdown their Windows machines after a backup using a
857 Client Run After Job directive. If you want to do something similar, you might
858 take the shutdown program from the
859 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
860 \elink{Sysinternals project}
861 {http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.