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