1 \subsection{Include All Windows Drives in FileSet}
3 The \texttt{alldrives} Windows Plugin allows you to include all local drives
4 with a simple directive. This plugin is available in the Windows 64 and 32 bit
17 You exclude some specific drives with the \texttt{exclude} option.
24 Plugin = "alldrives: exclude=D,E"
30 \subsection{Microsoft VSS Writer Plugin}
31 \index[general]{Microsoft VSS Writer Plugin}
32 We provide a single plugin named {\bf vss-fd.dll} that
33 permits you to backup a number of different components
34 on Windows machines. This plugin is available from Bacula Systems
37 Only the System State component is currently supported. The Sharepoint,
38 MSSQL, and Exchange components are available only for testing.
41 \item System State writers
45 \item COM+ REGDB (COM Registration Database)
46 \item System (Systems files -- most of what is under c:/windows and more)
47 \item WMI (Windows Management and Instrumentation)
48 \item NTDS (Active Directory)
49 \item NTFRS (SYSVOL etc replication -- Windows 2003 domains)
50 \item DFS Replication (SYSVOLS etc replication -- Windows 2008 domains)
53 This component is known to work.
54 \item Sharepoint writers \\
55 This component has not yet been tested. It is included so that you
56 may test it, but please do not use it in production without careful
58 \item MSSQL databases (except those owned by Sharepoint if that plugin is
60 This component has been tested, but only works for Full backups. Please
61 do not attempt to use it for incremental backups. The Windows writer
62 performs block level delta for Incremental backups, which are only
63 supported by Bacula version 4.2.0, not yet released. If you use
64 this component, please do not use it in production without careful
66 \item Exchange (all exchange databases) \\
67 We have tested this component and found it to work, but only for Full
68 backups. Please do not attempt to use it for incremental or differential
69 backups. We are including this component for you to test. Please do not
70 use it in production without careful testing. \\ Bacula Systems has a
71 White Paper that describes backup and restore of MS Exchange 2010 in
75 Each of the above specified Microsoft components can be backed up
76 by specifying a different plugin option within the Bacula FileSet.
77 All specifications must start with {\bf vss:} and be followed
78 with a keyword which indicates the writer, such as {\bf /@SYSTEMSTATE/}
80 To activate each component you use the following:
83 \item System State writers
85 Plugin = "vss:/@SYSTEMSTATE/"
87 Note, exactly which subcomponents will be backed up depends on
88 which ones you have enabled within Windows. For example, on a standard
89 default Vista system only ASR Writer, COM+ REGDB, System State, and WMI
91 \item Sharepoint writers
93 Plugin = "vss:/@SHAREPOINT/"
95 \item MSSQL databases (except those owned by Sharepoint if that plugin is
98 Plugin = "vss:/@MSSQL/"
100 To use the sharepoint writer you'll need to enable the mssql writer
101 which is not enabled by default (a Microsoft restriction). The Microsoft
102 literature says that the mssql writer is only good for snapshots
104 enabled via a registry tweak or else the older MSDE writer will be
106 \item Exchange (all exchange databases)
108 Plugin = "vss:/@EXCHANGE/"
112 The plugin directives must be specified exactly as shown above.
113 A Job may have one or more of the {\bf vss} plugins components specified.
116 Also ensure that the vss-fd.dll plugin is in the plugins directory
117 on the FD doing the backup, and that the plugin directory config line is
118 present in the FD's configuration file (bacula-fd.conf).
120 \subsubsection{Backup}
121 If everything is set up correctly as above then the backup should
122 include the system state. The system state files backed up will appear
123 in a {\bf bconsole} or {\bf bat} restore like:
127 /@SYSTEMSTATE/ASR Writer/
128 /@SYSTEMSTATE/COM+ REGDB Writer/
132 Only a complete backup of the system state is supported at this time. That
133 is it is not currently possible to just back up the Registry or Active
134 Directory by itself. In almost all cases a complete backup is a good idea
135 anyway as most of the components are interconnected in some way. Also, if
136 an incremental or differential backup is specified on the backup Job then a
137 full backup of the system state will still be done. The size varies
138 according to your installation. We have seen up to 6GB
139 under Windows 2008, mostly because of the "System" writer, and
140 up to 20GB on Vista. The actual size depends on how many Windows
141 components are enabled.
143 The system state component automatically respects all the excludes present
144 in the FilesNotToBackup registry key, which includes things like \%TEMP\%,
145 pagefile.sys, hiberfil.sys, etc. Each plugin may additionally specify
146 files to exclude, eg the VSS Registry Writer will tell Bacula to not back
147 up the registry hives under \lstinline+C:\WINDOWS\system32\config+ because they
148 are backed up as part of the system state.
150 \subsubsection{Restore}
151 In most cases a restore of the entire backed up system state is
152 recommended. Individual writers can be selected for restore, but currently
153 not individual components of those writers. To restore just the Registry,
154 you would need to mark @SYSTEMSTATE (only the directory, not the
155 subdirectories), and then do {\bf mark Registry*} to mark the Registry writer
156 and everything under it.
158 Restoring anything less than a single component may not produce the
159 intended results and should only be done if a specific need arises and you
160 know what you are doing, and not without testing on a non-critical system
163 To restore Active Directory, the system will need to be booted into
164 Directory Services Restore Mode, an option at Windows boot time.
166 Only a non-authoritative restore of NTFRS/DFSR is supported at this
167 time. There exists Windows literature to turn a Domain Controller
168 restored in non-authoritative mode back into an authoritative Domain
169 Controller. If only one DC exists it appears that Windows does an
170 authoritative restore anyway.
172 Most VSS components will want to restore to files that are currently in
173 use. A reboot will be required to complete the restore (eg to bring the
174 restored registry online).
176 Starting another restore of VSS data after the restore of the registry
177 without first rebooting will not produce the intended results as the 'to be
178 replaced next reboot' file list will only be updated in the 'to be
179 replaced' copy of the registry and so will not be actioned.
181 \subsubsection{Example}
182 Suppose you have the following backup FileSet:
200 If only the Registry needs to be restored, then you could use the
201 following commands in {\bf bconsole}:
206 markdir "Registry Writer"
212 \subsubsection{Windows Plugins Items to Note}
214 \item Reboot Required after a Plugin Restore\\
215 In general after any VSS plugin is used to restore a component, you will
216 need to reboot the system. This is required because in-use files cannot be
217 replaced during restore time, so they are noted in the registry and
218 replaced when the system reboots.
219 \item After a System State restore, a reboot will generally take
220 longer than normal because the pre-boot process must move the newly restored
221 files into their final place prior to actually booting the OS.
222 \item One File from Each Drive needed by the Plugins must be backed up\\
223 At least one file from each drive that will be needed by the plugin must
224 have a regular file that is marked for backup. This is to ensure that the
225 main Bacula code does a snapshot of all the required drives. At a later
226 time, we will find a way to accomplish this automatically.
227 \item Bacula does not Automatically Backup Mounted Drives\\
228 Any drive that is mounted in the normal file structure using a mount point
229 or junction point will not be backed up by Bacula. If you want it backed
230 up, you must explicitly mention it in a Bacula "File" directive in your
232 \item When doing a backup that is to be used as a Bare Metal Recovery, do
233 not use the VSS plugin. The reason is that during a Bare Metal Recovery,
234 VSS is not available nor are the writers from the various components that
235 are needed to do the restore. You might do full backup to be used with
236 a Bare Metal Recovery once a month or once a week, and all other days,
237 do a backup using the VSS plugin, but under a different Job name. Then
238 to restore your system, use the last Full non-VSS backup to restore your
239 system, and after rebooting do a restore with the VSS plugin to get
240 everything fully up to date.
243 This plugin is available as an option. Please
244 contact Bacula Systems to get access to the VSS Plugin packages and the
247 \subsection{Support for NDMP Protocol}
249 The new \texttt{ndmp} Plugin is able to backup a NAS through NDMP protocol
250 using \textbf{Filer to server} approach, where the Filer is backing up across
251 the LAN to your Bacula server.
253 Accurate option should be turned on in the Job resource.
265 Plugin = "ndmp:host=nasbox user=root pass=root file=/vol/vol1"
270 This plugin is available as an option. Please
271 contact Bacula Systems to get access to the NDMP Plugin packages and the
274 \subsection{Incremental Accelerator Plugin for NetApp}
276 The Incremental Accelerator for NetApp Plugin is designed to simplify the
277 backup and restore procedure of your NetApp NAS hosting a huge number of files.
279 \smallskip{} When using the NetApp HFC Plugin, Bacula Enterprise will query the
280 NetApp device to get the list of all files modified since the last backup
281 instead of having to walk through the entire filesystem. Once Bacula have the
282 list of all files to back's up, it will use a standard network share (such as
283 NFS or CIFS) to access files.
286 This plugin is available as an option. Please contact Bacula Systems to get
287 access to the Incremental Accelerator Plugin for NetApp packages and the
291 \subsection{PostgreSQL Plugin}
293 The PostgreSQL plugin is designed to simplify the backup and restore procedure
294 of your PostgreSQL cluster, the backup administrator doesn't need to learn about
295 internals of Postgres backup techniques or write complex scripts. The plugin
296 will automatically take care for you to backup essential information such as
297 configuration, users definition or tablespaces. The PostgreSQL plugin supports
298 both dump and Point In Time Recovery (PITR) backup techniques.
301 This plugin is available as an option. Please contact Bacula Systems to get
302 access to the PostgreSQL Plugin packages and the documentation.
305 \subsection{VMWare vSphere VADP Plugin}
307 The Bacula Enterprise vSphere plugin provides virtual
308 machine bare metal recovery, while the backup at the guest level simplify data
309 protection of critical applications.
311 The plugin integrates the VMware's Changed Block Tracking (CBT) technology to
312 ensure only blocks that have changed since the initial Full, and/or the last
313 Incremental or Differential Backup are sent to the current Incremental or
314 Differential backup stream to give you more efficient backups and reduced
318 This plugin is available as an option. Please contact Bacula Systems to get
319 access to the vSphere Plugin packages and the documentation.
321 \subsection{Oracle RMAN Plugin}
323 The Bacula Enterprise Oracle Plugin is designed to simplify the backup and
324 restore procedure of your Oracle Database instance, the backup administrator
325 don't need to learn about internals of Oracle backup techniques or write
326 complex scripts. The Bacula Enterprise Oracle plugin supports both dump and
327 Point In Time Recovery (PITR) with RMAN backup techniques.
330 This plugin is available as an option. Please contact Bacula Systems to get
331 access to the Oracle Plugin packages and the documentation.