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 WinXP,
15 Win2000, Windows Server 2003, Windows Server 2008, Vista, and Windows 7
16 systems. The Windows version of Bacula is a native Win32 port, but there
17 are very few source code changes to the Unix code, which means that the
18 Windows version is for the most part running code that has long proved
19 stable on Unix systems. When running, it is perfectly integrated with
20 Windows and displays its icon in the system icon tray, and provides a
21 system tray menu to obtain additional information on how Bacula is running
22 (status and events dialog boxes). If so desired, it can also be stopped by
23 using the system tray menu, though this should normally never be necessary.
25 Once installed Bacula normally runs as a system service. This means that it is
26 immediately started by the operating system when the system is booted, and
27 runs in the background even if there is no user logged into the system.
29 \section{Win32 Installation}
31 \index[general]{Installation}
32 \index[general]{Win32!Installation}
34 Normally, you will install the Windows version of Bacula from the binaries.
35 This install is standard Windows .exe that runs an install wizard using the
36 NSIS Free Software installer, so if you have already installed Windows
37 software, it should be very familiar to you.
39 If you have a previous version of Bacula
40 installed, you should stop the service, uninstall it, and remove
41 the Bacula installation directory possibly saving your
42 bacula-fd.conf, bconsole.conf, and bat.conf files
43 for use with the new version you will install. The Uninstall
44 program is normally found in {\bf c:\textbackslash{}bacula\textbackslash{}Uninstall.exe}.
45 We also recommend that you completely remove the directory
46 {\bf c:\textbackslash{}bacula}, because the current installer
47 uses a different directory structure (see below).
49 Providing you do not already have Bacula installed,
50 the installer installs the binaries and dlls in
51 c:\textbackslash{}Program Files\textbackslash{}Bacula\textbackslash{}bin
52 and the configuration files
53 in c:\textbackslash{}Documents and Settings\textbackslash{}All Users\textbackslash{}Application Data\textbackslash{}Bacula
54 In addition, the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item
55 will be created during the installation, and on that menu, you
56 will find items for editing the configuration files, displaying
57 the document, and starting bwx-console or bconsole.
60 Finally, proceed with the installation.
63 \item You must be logged in as Administrator to the local machine
64 to do a correct installation, if not, please do so before continuing.
65 Some users have attempted to install logged in as a domain administrator
66 account and experienced permissions problems attempting to run
67 Bacula, so we don't recommend that option.
69 \item Simply double click on the {\bf bacula-win32-5.xx.0.exe} NSIS install
70 icon. The actual name of the icon will vary from one release version to
73 \includegraphics{nsis} bacula-win32-5.xx.0.exe
75 \item Once launched, the installer wizard will ask you if you want to install
78 \bsysimageH{win32-welcome}{Win32 Client Setup Wizard}{fig:win32clientsetupwizard}
80 \item Next you will be asked to select the installation type.
82 \bsysimageH{win32-installation-type}{Win32 Installation Type}{fig:win32installationtype}
84 \item If you proceed, you will be asked to select the components to be
85 installed. You may install the Bacula program (Bacula File Service) and or
86 the documentation. Both will be installed in sub-directories of the install
87 location that you choose later. The components dialog looks like the
90 \bsysimageH{win32-pkg}{Win32 Component Selection Dialog}{fig:win32componentselectiondialog}
91 \index[general]{Upgrading}
93 \item If you are installing for the first time, you will be asked to
94 enter some very basic information about your configuration. If
95 you are not sure what to enter, or have previously saved configuration
96 files, you can put anything you want into the fields, then either
97 replace the configuration files later with the ones saved, or edit
100 If you are upgrading an existing installation, the following will
104 \bsysimageH{win32-config}{Win32 Configure}{fig:win32configure}
106 \item While the various files are being loaded, you will see the following
109 \bsysimageH{win32-installing}{Win32 Install Progress}{fig:win32installing}
111 \item Finally, the finish dialog will appear:
113 \bsysimageH{win32-finish}{Win32 Client Setup Completed}{fig:win32setupcompleted}
117 That should complete the installation process. When the Bacula File Server is
118 ready to serve files, an icon \raisebox{-1ex}{\includegraphics{k7-idle}} representing a
119 cassette (or tape) will appear in the system tray
120 \raisebox{-2ex}{\includegraphics{tray-icon}}; right click on it and a menu will appear.\\
121 \bsysimageN{menu}{Menu on right click}{fig:win32menuonrightclick}\\
122 The {\bf Events} item is currently unimplemented, by selecting the {\bf
123 Status} item, you can verify whether any jobs are running or not.
125 When the Bacula File Server begins saving files, the color of the holes in the
126 cassette icon will change from white to green \raisebox{-1ex}{\includegraphics{k7-ok}},
127 and if there is an error, the holes in the cassette icon will change to red
128 \raisebox{-1ex}{\includegraphics{k7-error}}.
130 If you are using remote desktop connections between your Windows boxes, be
131 warned that that tray icon does not always appear. It will always be visible
132 when you log into the console, but the remote desktop may not display it.
134 \section{Post Win32 Installation}
135 \index[general]{Post Win32 Installation}
136 \index[general]{Win32!Post Installation}
138 After installing Bacula and before running it, you should check the contents
139 of the configuration files to ensure that they correspond to your
140 installation. You can get to them by using:
141 the {\bf Start\-\gt{}All Programs\-\gt{}Bacula} menu item.
143 Finally, but pulling up the Task Manager (ctl-alt-del), verify that Bacula
144 is running as a process (not an Application) with User Name SYSTEM. If this is
145 not the case, you probably have not installed Bacula while running as
146 Administrator, and hence it will be unlikely that Bacula can access
147 all the system files.
149 \section{Uninstalling Bacula on Win32}
150 \index[general]{Win32!Uninstalling Bacula}
151 \index[general]{Uninstalling Bacula on Win32}
153 Once Bacula has been installed, it can be uninstalled using the standard
154 Windows Add/Remove Programs dialog found on the Control panel.
156 \section{Dealing with Win32 Problems}
158 \index[general]{Win32!Dealing with Problems}
159 \index[general]{Dealing with Win32 Problems}
161 Sometimes Win32 machines the File daemon may have very slow
162 backup transfer rates compared to other machines. To you might
163 try setting the Maximum Network Buffer Size to 32,768 in both the
164 File daemon and in the Storage daemon. The default size is larger,
165 and apparently some Windows ethernet controllers do not deal with
166 a larger network buffer size.
168 Many Windows ethernet drivers have a tendency to either run slowly
169 due to old broken firmware, or because they are running in half-duplex
170 mode. Please check with the ethernet card manufacturer for the latest
171 firmware and use whatever techniques are necessary to ensure that the
172 card is running in duplex.
174 If you are not using the portable option, and you have VSS
175 (Volume Shadow Copy) enabled in the Director, and you experience
176 problems with Bacula not being able to open files, it is most
177 likely that you are running an antivirus program that blocks
178 Bacula from doing certain operations. In this case, disable the
179 antivirus program and try another backup. If it succeeds, either
180 get a different (better) antivirus program or use something like
181 RunClientJobBefore/After to turn off the antivirus program while
182 the backup is running.
184 If turning off anti-virus software does not resolve your VSS
185 problems, you might have to turn on VSS debugging. The following
186 link describes how to do this:
187 \elink{http://support.microsoft.com/kb/887013/en-us}{http://support.microsoft.com/kb/887013/en-us}.
189 In Microsoft Windows Small Business Server 2003 the VSS Writer for Exchange
190 is turned off by default. To turn it on, please see the following link:
191 \elink{http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}{
192 http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q838183}
195 The most likely source of problems is authentication when the Director
196 attempts to connect to the File daemon that you installed. This can occur if
197 the names and the passwords defined in the File daemon's configuration file
198 {\bf bacula-fd.conf} file on
199 the Windows machine do not match with the names and the passwords in the
200 Director's configuration file {\bf bacula-dir.conf} located on your Unix/Linux
203 More specifically, the password found in the {\bf Client} resource in the
204 Director's configuration file must be the same as the password in the {\bf
205 Director} resource of the File daemon's configuration file. In addition, the
206 name of the {\bf Director} resource in the File daemon's configuration file
207 must be the same as the name in the {\bf Director} resource of the Director's
210 It is a bit hard to explain in words, but if you understand that a Director
211 normally has multiple Clients and a Client (or File daemon) may permit access
212 by multiple Directors, you can see that the names and the passwords on both
213 sides must match for proper authentication.
215 One user had serious problems with the configuration file until he realized
216 that the Unix end of line conventions were used and Bacula wanted them in
217 Windows format. This has not been confirmed though, and Bacula version 2.0.0
218 and above should now accept all end of line conventions (Win32,
221 Running Unix like programs on Windows machines is a bit frustrating because
222 the Windows command line shell (DOS Window) is rather primitive. As a
223 consequence, it is not generally possible to see the debug information and
224 certain error messages that Bacula prints. With a bit of work, however, it is
225 possible. When everything else fails and you want to {\bf see} what is going
226 on, try the following:
230 Start a DOS shell Window.
231 c:\Program Files\bacula\bacula-fd -t >out
236 The precise path to bacula-fd depends on where it is installed.
237 The {\bf -t} option will cause Bacula to read the configuration file, print
238 any error messages and then exit. the {\bf \gt{}} redirects the output to the
239 file named {\bf out}, which you can list with the {\bf type} command.
241 If something is going wrong later, or you want to run {\bf Bacula} with a
242 debug option, you might try starting it as:
246 c:\Program Files\bacula\bin\bacula-fd -d 100 >out
250 In this case, Bacula will run until you explicitly stop it, which will give
251 you a chance to connect to it from your Unix/Linux server. In later versions
252 of Bacula (1.34 on, I think), when you start the File daemon in debug mode it
253 can write the output to a trace file {\bf bacula.trace} in the current
254 directory. To enable this, before running a job, use the console, and enter:
262 then run the job, and once you have terminated the File daemon, you will find
263 the debug output in the {\bf bacula.trace} file, which will probably be
264 located in the same directory as bacula-fd.exe.
266 In addition, you should look in the System Applications log on the Control
267 Panel to find any Windows errors that Bacula got during the startup process.
269 Finally, due to the above problems, when you turn on debugging, and specify
270 trace=1 on a setdebug command in the Console, Bacula will write the debug
271 information to the file {\bf bacula.trace} in the directory from which Bacula
274 If you are having problems with ClientRunBeforeJob scripts randomly dying,
275 it is possible that you have run into an Oracle bug. See bug number 622 in
276 the bugs.bacula.org database. The following information has been
277 provided by a user on this issue:
281 The information in this document applies to:
282 Oracle HTTP Server - Version: 9.0.4
283 Microsoft Windows Server 2003
285 When starting an OC4J instance, the System Clock runs faster, about 7
290 + This is caused by the Sun JVM bug 4500388, which states that "Calling
291 Thread.sleep() with a small argument affects the system clock". Although
292 this is reported as fixed in JDK 1.4.0_02, several reports contradict this
294 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4500388).
296 + Also reported by Microsoft as "The system clock may run fast when you
297 use the ACPI power management timer as a high-resolution counter on Windows
298 2000-based computers" (See http://support.microsoft.com/?id=821893)
302 You may wish to start the daemon with debug mode on rather than doing it
303 using bconsole. To do so, edit the following registry key:
307 HKEY_LOCAL_MACHINE\HARDWARE\SYSTEM\CurrentControlSet\Services\Bacula-dir
311 using regedit, then add -dnn after the /service option, where nn represents
312 the debug level you want.
314 \label{Compatibility}
315 \section{Windows Compatibility Considerations}
316 \index[general]{Windows Compatibility Considerations}
317 \index[general]{Considerations!Windows Compatibility}
319 If you are not using the VSS (Volume Shadow Copy) option described in the
320 next section of this chapter, and if any applications are running during
321 the backup and they have files opened exclusively, Bacula will not be able
322 to backup those files, so be sure you close your applications (or tell your
323 users to close their applications) before the backup. Fortunately, most
324 Microsoft applications do not open files exclusively so that they can be
325 backed up. However, you will need to experiment. In any case, if Bacula
326 cannot open the file, it will print an error message, so you will always
327 know which files were not backed up. For version 1.37.25 and greater, see
328 the section below on Volume Shadow Copy Service that permits backing up any
331 During backup, Bacula doesn't know about the system registry, so you will
332 either need to write it out to an ASCII file using {\bf regedit~~/e} or use a
333 program specifically designed to make a copy or backup the registry.
335 In Bacula version 1.31 and later, we use Windows backup API calls by
336 default. Typical of Windows, programming these special BackupRead and
337 BackupWrite calls is a real nightmare of complications. The end result
338 gives some distinct advantages and some disadvantages.
340 First, the advantages are that Windows systems, the security and
341 ownership information is now backed up. In addition, with the exception of
342 files in exclusive use by another program, Bacula can now access all system
343 files. This means that when you restore files, the security and ownership
344 information will be restored on Windows along with the data.
346 The disadvantage of the Windows backup API calls is that it produces
347 non-portable backups. That is files and their data that are backed up on
348 Windows using the native API calls (BackupRead/BackupWrite) cannot be
349 directly restored on Linux or Unix systems. Bacula should be able to read
350 non-portable backups on any system and restore the data appropriately.
351 However, on a system that does not have the BackupRead/BackupWrite calls
352 (older Windows versions and all Unix/Linux machines), though the file data
353 can be restored, the Windows security and access control data will not be
354 restored. This means that a standard set of access permissions will be set
355 for such restored files.
358 As a default, Bacula backs up Windows systems using the Windows API calls.
359 If you want to backup data on a Windows system and restore it on a
360 Unix or Linux system, we have provided a special {\bf portable} option
361 that backs up the data in a portable fashion by using portable API calls.
362 See the \ilink{portable option}{portable} on the Include statement in a
363 FileSet resource in the Director's configuration chapter for the details on
364 setting this option. However, using the portable option means you may have
365 permissions problems accessing files, and none of the security and
366 ownership information will be backed up or restored. The file data can,
367 however, be restored on any system.
369 You should always be able to restore any file backed up on Unix or Win95/98/Me
370 to any other system. On some older Windows systems, you may have to
371 reset the ownership of such restored files.
373 Finally, if you specify the {\bf portable=yes} option on the files you back
374 up. Bacula will be able to restore them on any other system. However, any
375 Windows specific security and ownership information will be lost.
377 The following matrix will give you an idea of what you can expect. Thanks to
378 Marc Brueckner for doing the tests:
380 \LTXtable{\linewidth}{table_restoreportabilitystatus}
381 Note: with Bacula versions 1.39.x and later, non-portable Windows data can
382 be restore to any machine.
386 \section{Volume Shadow Copy Service}
387 \index[general]{Volume Shadow Copy Service}
389 In version 1.37.30 and greater, you can turn on Microsoft's Volume
390 Shadow Copy Service (VSS).
392 Microsoft added VSS to Windows XP and Windows 2003. From the perspective of
393 a backup-solution for Windows, this is an extremely important step. VSS
394 allows Bacula to backup open files and even to interact with applications like
395 RDBMS to produce consistent file copies. VSS aware applications are called
396 VSS Writers, they register with the OS so that when Bacula wants to do a
397 Snapshot, the OS will notify the register Writer programs, which may then
398 create a consistent state in their application, which will be backed up.
399 Examples for these writers are "MSDE" (Microsoft database
400 engine), "Event Log Writer", "Registry Writer" plus 3rd
401 party-writers. If you have a non-vss aware application (e.g.
402 SQL Anywhere or probably MySQL), a shadow copy is still generated
403 and the open files can be backed up, but there is no guarantee
404 that the file is consistent.
406 Bacula produces a message from each of the registered writer programs
407 when it is doing a VSS backup so you know which ones are correctly backed
410 Bacula supports VSS on both Windows 2003 and Windows XP.
411 Technically Bacula creates a shadow copy as soon as the backup process
412 starts. It does then backup all files from the shadow copy and destroys the
413 shadow copy after the backup process. Please have in mind, that VSS
414 creates a snapshot and thus backs up the system at the state it had
415 when starting the backup. It will disregard file changes which occur during
418 VSS can be turned on by placing an
420 \index[dir]{Enable VSS}
421 \index[general]{Enable VSS}
426 in your FileSet resource.
428 The VSS aware File daemon has the letters VSS on the signon line that
429 it produces when contacted by the console. For example:
431 Tibs-fd Version: 1.37.32 (22 July 2005) VSS Windows XP MVS NT 5.1.2600
433 the VSS is shown in the line above. This only means that the File daemon
434 is capable of doing VSS not that VSS is turned on for a particular backup.
435 There are two ways of telling if VSS is actually turned on during a backup.
436 The first is to look at the status output for a job, e.g.:
440 JobId 1 Job NightlySave.2005-07-23_13.25.45 is running.
441 VSS Backup Job started: 23-Jul-05 13:25
442 Files=70,113 Bytes=3,987,180,650 Bytes/sec=3,244,247
443 Files Examined=75,021
444 Processing file: c:/Documents and Settings/kern/My Documents/My Pictures/Misc1/Sans titre - 39.pdd
448 Here, you see under Running Jobs that JobId 1 is "VSS Backup Job started ..."
449 This means that VSS is enabled for that job. If VSS is not enabled, it will
450 simply show "Backup Job started ..." without the letters VSS.
452 The second way to know that the job was backed up with VSS is to look at the
453 Job Report, which will look something like the following:
456 23-Jul 13:25 rufus-dir: Start Backup JobId 1, Job=NightlySave.2005-07-23_13.25.45
457 23-Jul 13:26 rufus-sd: Wrote label to prelabeled Volume "TestVolume001" on device "DDS-4" (/dev/nst0)
458 23-Jul 13:26 rufus-sd: Spooling data ...
459 23-Jul 13:26 Tibs: Generate VSS snapshots. Driver="VSS WinXP", Drive(s)="C"
460 23-Jul 13:26 Tibs: VSS Writer: "MSDEWriter", State: 1 (VSS_WS_STABLE)
461 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Bootable State)", State: 1 (VSS_WS_STABLE)
462 23-Jul 13:26 Tibs: VSS Writer: "WMI Writer", State: 1 (VSS_WS_STABLE)
463 23-Jul 13:26 Tibs: VSS Writer: "Microsoft Writer (Service State)", State: 1 (VSS_WS_STABLE)
466 In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
467 other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
468 reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
469 that you will get a consistent snapshot of the data handled by that writer.
471 \section{VSS Problems}
472 \index[general]{Problems!VSS}
473 \index[fd] {Problems!VSS}
474 \index[general]{VSS Problems}
475 \index[fd]{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 \section{Windows Firewalls}
493 \index[general]{Firewalls!Windows}
494 \index[general]{Windows Firewalls}
496 If you turn on the firewalling feature on Windows (default in WinXP SP2), you
497 are likely to find that the Bacula ports are blocked and you cannot
498 communicate to the other daemons. This can be deactivated through the {\bf
499 Security Notification} dialog, which is apparently somewhere in the {\bf
500 Security Center}. I don't have this on my computer, so I cannot give the exact
507 netsh firewall set opmode disable
511 is purported to disable the firewall, but this command is not accepted on my
514 \section{Windows Port Usage}
515 \index[general]{Windows Port Usage}
516 \index[general]{Usage!Windows Port}
518 If you want to see if the File daemon has properly opened the port and is
519 listening, you can enter the following command in a shell window:
523 netstat -an | findstr 910[123]
527 TopView is another program that has been recommend, but it is not a
528 standard Win32 program, so you must find and download it from the Internet.
530 \section{Windows Disaster Recovery}
531 \index[general]{Recovery!Windows Disaster}
532 \index[general]{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 \section{Windows Restore Problems}
557 \index[general]{Problems!Windows Restore}
558 \index[general]{Windows Restore Problems}
560 \ilink{Restore Chapter}{Windows} of this manual for problems
561 that you might encounter doing a restore.
563 section{Windows Backup Problems}
564 \index[general]{Problems!Windows Backup}
565 \index[general]{Windows Backup Problems}
566 If during a Backup, you get the message:
567 {\bf ERR=Access is denied} and you are using the portable option,
568 you should try both adding both the non-portable (backup API) and
569 the Volume Shadow Copy options to your Director's conf file.
571 In the Options resource:
578 In the FileSet resource:
585 In general, specifying these two options should allow you to backup
586 any file on a Windows system. However, in some cases, if users
587 have allowed to have full control of their folders, even system programs
588 such a Bacula can be locked out. In this case, you must identify
589 which folders or files are creating the problem and do the following:
592 \item Grant ownership of the file/folder to the Administrators group,
593 with the option to replace the owner on all child objects.
594 \item Grant full control permissions to the Administrators group,
595 and change the user's group to only have Modify permission to
596 the file/folder and all child objects.
599 Thanks to Georger Araujo for the above information.
601 \section{Windows Ownership and Permissions Problems}
602 \index[general]{Problems!Windows Ownership and Permissions}
603 \index[general]{Windows Ownership and Permissions Problems}
605 If you restore files backed up from Windows to an alternate directory,
606 Bacula may need to create some higher level directories that were not saved
607 (or restored). In this case, the File daemon will create them under the SYSTEM
608 account because that is the account that Bacula runs under as a service. As of
609 version 1.32f-3, Bacula creates these files with full access permission.
610 However, there may be cases where you have problems accessing those files even
611 if you run as administrator. In principle, Microsoft supplies you with the way
612 to cease the ownership of those files and thus change the permissions.
613 However, a much better solution to working with and changing Win32 permissions
614 is the program {\bf SetACL}, which can be found at
615 \elink{http://setacl.sourceforge.net/}{http://setacl.sourceforge.net/}.
617 If you have not installed Bacula while running as Administrator
618 and if Bacula is not running as a Process with the userid (User Name) SYSTEM,
619 then it is very unlikely that it will have sufficient permission to
620 access all your files.
622 Some users have experienced problems restoring files that participate in
623 the Active Directory. They also report that changing the userid under which
624 Bacula (bacula-fd.exe) runs, from SYSTEM to a Domain Admin userid, resolves
628 \section{Manually resetting the Permissions}
629 \index[general]{Manually resetting the Permissions}
630 \index[general]{Permissions!Manually resetting the}
632 The following solution was provided by Dan Langille \lt{}dan at langille in
633 the dot org domain\gt{}. The steps are performed using Windows 2000 Server but
634 they should apply to most Win32 platforms. The procedure outlines how to deal
635 with a problem which arises when a restore creates a top-level new directory.
636 In this example, "top-level" means something like {\bf
637 c:\textbackslash{}src}, not {\bf c:\textbackslash{}tmp\textbackslash{}src}
638 where {\bf c:\textbackslash{}tmp} already exists. If a restore job specifies /
639 as the {\bf Where:} value, this problem will arise.
641 The problem appears as a directory which cannot be browsed with Windows
642 Explorer. The symptoms include the following message when you try to click on
645 \bsysimageN{access-is-denied}{Popup on permission issue}{fig:accessdenied}
647 If you encounter this message, the following steps will change the permissions
648 to allow full access.
651 \item right click on the top level directory (in this example, {\bf c:/src})
652 and select {\bf Properties}.
653 \item click on the Security tab.
654 \item If the following message appears, you can ignore it, and click on {\bf
657 \bsysimageH{view-only}{Message to ignore}{fig:messagetoignore}
659 You should see something like this:
661 \bsysimageH{properties-security}{Properties security}{fig:propertiessecurity}
662 \item click on Advanced
663 \item click on the Owner tab
664 \item Change the owner to something other than the current owner (which is
665 {\bf SYSTEM} in this example as shown below).
667 \bsysimageH{properties-security-advanced-owner}{Properties security advanced owner}{fig:propertiessecurityadvancedowner}
668 \item ensure the ``Replace owner on subcontainers and objects'' box is
671 \item When the message ``You do not have permission to read the contents of
672 directory c:\textbackslash{}src\textbackslash{}basis. Do you wish to replace
673 the directory permissions with permissions granting you Full Control?'', click
676 \bsysimageH{confirm}{Confirm granting permissions}{fig:confirmgrantingpermissions}
677 \item Click on OK to close the Properties tab
680 With the above procedure, you should now have full control over your restored
683 In addition to the above methods of changing permissions, there is a Microsoft
684 program named {\bf cacls} that can perform similar functions.
686 \section{Backing Up the WinNT/XP/2K System State}
687 \index[general]{State!Backing Up the WinNT/XP/2K System}
688 \index[general]{Backing Up the WinNT/XP/2K System State}
690 Note, most of this section applies to the older Windows OSes that
691 do not have VSS. On newer Windows OSes that have VSS, all files
692 including the System State will by default be properly backed
695 A suggestion by Damian Coutts using Microsoft's NTBackup utility in
696 conjunction with Bacula should permit a full restore of any damaged system
697 files on Win2K/XP. His suggestion is to do an NTBackup of the critical system
698 state prior to running a Bacula backup with the following command:
702 ntbackup backup systemstate /F c:\systemstate.bkf
706 The {\bf backup} is the command, the {\bf systemstate} says to backup only the
707 system state and not all the user files, and the {\bf /F
708 c:\textbackslash{}systemstate.bkf} specifies where to write the state file.
709 this file must then be saved and restored by Bacula.
711 To restore the system state, you first reload a base operating system if the
712 OS is damaged, otherwise, this is not necessary, then you would use Bacula to
713 restore all the damaged or lost user's files and to recover the {\bf
714 c:\textbackslash{}systemstate.bkf} file. Finally if there are any damaged or
715 missing system files or registry problems, you run {\bf NTBackup} and {\bf
716 catalogue} the system statefile, and then select it for restore. The
717 documentation says you can't run a command line restore of the systemstate.
719 To the best of my knowledge, this has not yet been tested. If you test it,
720 please report your results to the Bacula email list.
722 Note, Bacula uses VSS to backup and restore open files and
723 system files, but on older Windows machines such as WinNT and
724 Win2000, VSS is not implemented by Microsoft so that you must
725 use some special techniques to back them up as described
726 above. On new Windows machines, Bacula will backup and restore
727 all files including the system state providing you have
728 VSS enabled in your Bacula FileSet (default).
730 \section{Fixing the Windows Boot Record}
731 \index[general]{Fixing the Windows Boot Record}
732 \index[general]{Windows!Fixing the Boot Record}
734 An effective way to restore a Windows backup for
735 those who do not purchase the bare metal restore
736 capability is to install Windows on a different
737 hard drive and restore the backup. Then run the
753 \section{Considerations for Filename Specifications}
754 \index[general]{Windows!Considerations for Filename Specifications}
757 \ilink{Director's Configuration chapter}{win32} of this manual
758 for important considerations on how to specify Windows paths in Bacula FileSet
759 Include and Exclude directives.
761 \index[general]{Unicode}
762 Bacula versions prior to 1.37.28 do not support Windows Unicode filenames.
763 As of that version, both {\bf bconsole} and {\bf bwx-console} support Windows
764 Unicode filenames. There may still be some problems with multiple byte
765 characters (e.g. Chinese, ...) where it is a two byte character but the
766 displayed character is not two characters wide.
768 \index[general]{Win32 Path Length Restriction}
769 Path/filenames longer than 260 characters (up to 32,000) are supported
770 beginning with Bacula version 1.39.20. Older Bacula versions support
771 only 260 character path/filenames.
773 \section{Win32 Specific File daemon Command Line}
774 \index[general]{Client!Win32 Specific File daemon Command Line Options}
775 \index[general]{Win32 Specific File daemon Command Line Options}
777 These options are not normally seen or used by the user, and are documented
778 here only for information purposes. At the current time, to change the default
779 options, you must either manually run {\bf Bacula} or you must manually edit
780 the system registry and modify the appropriate entries.
782 In order to avoid option clashes between the options necessary for {\bf
783 Bacula} to run on Windows and the standard Bacula options, all Windows
784 specific options are signaled with a forward slash character (/), while as
785 usual, the standard Bacula options are signaled with a minus (-), or a minus
786 minus (\lstinline:--:). All the standard Bacula options can be used on the Windows
787 version. In addition, the following Windows only options are implemented:
793 Start Bacula as a service
797 Run the Bacula application
801 Install Bacula as a service in the system registry
805 Uninstall Bacula from the system registry
809 Show the Bacula about dialogue box
813 Show the Bacula status dialogue box
817 Show the Bacula events dialogue box (not yet implemented)
821 Stop any running {\bf Bacula}
825 Show the Bacula help dialogue box
828 It is important to note that under normal circumstances the user should never
829 need to use these options as they are normally handled by the system
830 automatically once Bacula is installed. However, you may note these options in
831 some of the .bat files that have been created for your use.
833 \section{Shutting down Windows Systems}
834 \index[general]{Shutting down Windows Systems}
835 \index[general]{Systems!Shutting down Windows}
837 Some users like to shutdown their Windows machines after a backup using a
838 Client Run After Job directive. If you want to do something similar, you might
839 take the shutdown program from the
840 \elink{apcupsd project}{http://www.apcupsd.com} or one from the
841 \elink{Sysinternals project}
842 {http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx}.