Debian Codegraph @

manuals/en/main/bsplugins.tex

raw
1 \subsection{Include All Windows Drives in FileSet}
2
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
5 installer.
6
7 \begin{bVerbatim}
8 FileSet {
9 Name = EverythingFS
10 ...
11 Include {
12 Plugin = "alldrives"
13 }
14 }
15 \end{bVerbatim}
16
17 You exclude some specific drives with the \texttt{exclude} option.
18
19 \begin{bVerbatim}
20 FileSet {
21 Name = EverythingFS
22 ...
23 Include {
24 Plugin = "alldrives: exclude=D,E"
25 }
26 }
27 \end{bVerbatim}
28
29 The alldrives Windows plugin only considers regular drives (i.e. \bdirectoryname{C:/},
30 \bdirectoryname{D:/}, \bdirectoryname{E:/}).
31 Mount points inside the directory tree will no be part of the snapshots
32 unless you set ``\bdirectivename{OneFS = no}'' in the \bresourcename{Options}
33 block of the FileSet, which will cause \bacula{} to snapshot everything.
34
35 \subsection{Microsoft \acs{VSS} Writer Plugin}
36 \index[general]{Microsoft \acs{VSS} Writer Plugin}
37 We provide a single plugin named \btool{vss-fd.dll} that
38 permits you to backup a number of different components
39 on Windows machines. This plugin is available from \bacula{} Systems
40 as an option.
41
42 Please \bfootref{mailto:[email protected]}{write to the Support Team} to find more information about our \acs{VSS} products.
43
44 \begin{bitemize}
45 \item System State writers
46 \begin{bitemize}
47 \item Registry
48 \item Event Logs
49 \item COM+ REGDB (COM Registration Database)
50 \item System (Systems files -- most of what is under c:/windows and more)
51 \item \ac{WMI}
52 \item \ac{NTDS} (Active Directory)
53 \item \ac{NTFRS} (SYSVOL etc replication -- Windows 2003 domains)
54 \item \ac{DFS} Replication (SYSVOLS etc replication -- Windows 2008 domains)
55 \item \ac{ASR} Writer
56 \end{bitemize}
57 This component is known to work.
58 \item \mssql{} databases (except those owned by Sharepoint if that plugin is
59 specified).\\
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
65 testing.
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
72 detail.
73 \end{bitemize}
74
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 \textbf{vss:} and be followed
78 with a keyword which indicates the writer, such as \textbf{/@SYSTEMSTATE/}
79 (see below).
80 To activate each component you use the following:
81
82 \begin{bitemize}
83 \item System State writers
84 \begin{bVerbatim}
85 Plugin = "vss:/@SYSTEMSTATE/"
86 \end{bVerbatim}
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 \acs{WMI}
90 are enabled.
91 \item \mssql{} databases (except those owned by Sharepoint if that plugin is
92 specified)
93 \begin{bVerbatim}
94 Plugin = "vss:/@MSSQL/"
95 \end{bVerbatim}
96 The Microsoft
97 literature says that the mssql writer is only good for snapshots
98 and it needs to be
99 enabled via a registry tweak or else the older MSDE writer will be
100 invoked instead.
101 \item Exchange (all exchange databases)
102 \begin{bVerbatim}
103 Plugin = "vss:/@EXCHANGE/"
104 \end{bVerbatim}
105 \end{bitemize}
106
107 The plugin directives must be specified exactly as shown above.
108 A Job may have one or more of the \textbf{vss} plugins components specified.
109
110
111 Also ensure that the \btool{vss-fd.dll} plugin is in the plugins directory
112 on the FD doing the backup, and that the plugin directory config line is
113 present in the FD's configuration file (\bfilename{bacula-fd.conf}).
114
115 \subsubsection{Backup}
116 If everything is set up correctly as above then the backup should
117 include the system state. The system state files backed up will appear
118 in a \btool{bconsole} or \bat{} restore like:
119
120 \begin{bVerbatim}
121 /@SYSTEMSTATE/
122 /@SYSTEMSTATE/ASR Writer/
123 /@SYSTEMSTATE/COM+ REGDB Writer/
124 \end{bVerbatim}
125 etc
126
127
128
129 Only a complete backup of the system state is supported at this time. That
130 is it is not currently possible to just back up the Registry or Active
131 Directory by itself. In almost all cases a complete backup is a good idea
132 anyway as most of the components are interconnected in some way. Also, if
133 an incremental or differential backup is specified on the backup Job then a
134 full backup of the system state will still be done. The size varies
135 according to your installation. We have seen up to 6GB
136 under Windows 2008, mostly because of the ``System'' writer, and
137 up to 20GB on Vista. The actual size depends on how many Windows
138 components are enabled.
139
140 The system state component automatically respects all the excludes present
141 in the FilesNotToBackup registry key, which includes things like \bdirectoryname{\%TEMP\%},
142 \bfilename{pagefile.sys}, \bfilename{hiberfil.sys}, etc. Each plugin may additionally specify
143 files to exclude, eg the \acs{VSS} Registry Writer will tell \bacula{} to not back
144 up the registry hives under \bdirectoryname{C:\textbackslash{}WINDOWS\textbackslash{}system32\textbackslash{}config} because they
145 are backed up as part of the system state.
146
147 \subsubsection{Restore}
148 In most cases a restore of the entire backed up system state is
149 recommended. Individual writers can be selected for restore, but currently
150 not individual components of those writers. To restore just the Registry,
151 you would need to mark \texttt{@SYSTEMSTATE} (only the directory, not the
152 subdirectories), and then do \textbf{mark Registry*} to mark the Registry writer
153 and everything under it.
154
155 Restoring anything less than a single component may not produce the
156 intended results and should only be done if a specific need arises and you
157 know what you are doing, and not without testing on a non-critical system
158 first.
159
160 To restore Active Directory, the system will need to be booted into
161 Directory Services Restore Mode, an option at Windows boot time.
162
163 Only a non-authoritative restore of \acs{NTFRS}/\acs{DFSR} is supported at this
164 time. There exists Windows literature to turn a \ac{DC}
165 restored in non-authoritative mode back into an authoritative Domain
166 Controller. If only one \ac{DC} exists it appears that Windows does an
167 authoritative restore anyway.
168
169 Most \acs{VSS} components will want to restore to files that are currently in
170 use. A reboot will be required to complete the restore (eg to bring the
171 restored registry online).
172
173 Starting another restore of \acs{VSS} data after the restore of the registry
174 without first rebooting will not produce the intended results as the
175 ``to be replaced next reboot'' file list will only be updated in the
176 ``to be replaced'' copy of the registry and so will not be actioned.
177
178 \subsubsection{Example}
179 Suppose you have the following backup FileSet:
180
181 \begin{bVerbatim}
182 @SYSTEMSTATE/
183 System Writer/
184 instance_{GUID}
185 System Files/
186 Registry Writer/
187 instance_{GUID}
188 Registry/
189 COM+ REGDB Writer/
190 instance_{GUID}
191 COM+ REGDB/
192 NTDS/
193 instance_{GUID}
194 ntds/
195 \end{bVerbatim}
196
197 If only the Registry needs to be restored, then you could use the
198 following commands in \btool{bconsole}:
199
200 \begin{bVerbatim}
201 markdir @SYSTEMSTATE
202 cd @SYSTEMSTATE
203 markdir "Registry Writer"
204 cd "Registry Writer"
205 mark instance*
206 mark "Registry"
207 \end{bVerbatim}
208
209 \subsubsection{Windows Plugins Items to Note}
210 \begin{bitemize}
211 \item Reboot Required after a Plugin Restore\\
212 In general after any \acs{VSS} plugin is used to restore a component, you will
213 need to reboot the system. This is required because in-use files cannot be
214 replaced during restore time, so they are noted in the registry and
215 replaced when the system reboots.
216 \item After a System State restore, a reboot will generally take
217 longer than normal because the pre-boot process must move the newly restored
218 files into their final place prior to actually booting the \acs{OS}.
219 \item One File from Each Drive needed by the Plugins must be backed up\\
220 At least one file from each drive that will be needed by the plugin must
221 have a regular file that is marked for backup. This is to ensure that the
222 main \bacula{} code does a snapshot of all the required drives. At a later
223 time, we will find a way to accomplish this automatically.
224 \item \bacula{} does not Automatically Backup Mounted Drives\\
225 Any drive that is mounted in the normal file structure using a mount point
226 or junction point will not be backed up by \bacula{}. If you want it backed
227 up, you must explicitly mention it in a \bacula{} ``\bdirectivename{File}'' directive in your
228 FileSet.
229 \item When doing a backup that is to be used as a Bare Metal Recovery, do
230 not use the \acs{VSS} plugin. The reason is that during a Bare Metal Recovery,
231 \acs{VSS} is not available nor are the writers from the various components that
232 are needed to do the restore. You might do full backup to be used with
233 a Bare Metal Recovery once a month or once a week, and all other days,
234 do a backup using the \acs{VSS} plugin, but under a different Job name. Then
235 to restore your system, use the last Full non-\acs{VSS} backup to restore your
236 system, and after rebooting do a restore with the \acs{VSS} plugin to get
237 everything fully up to date.
238 \end{bitemize}
239
240 This plugin is available as an option. Please contact \bacula{} Systems to
241 get access to the \acs{VSS} Plugin packages and the documentation.
242
243 \subsection{Support for NDMP Protocol}
244
245 The new \btool{ndmp} Plugin is able to backup a \acs{NAS} through \acs{NDMP} protocol
246 using \textbf{Filer to server} approach, where the Filer is backing up across
247 the \acs{LAN} to your \bacula{} server.
248
249 Accurate option should be turned on in the Job resource.
250 \begin{bVerbatim}
251 Job {
252 Accurate = yes
253 FileSet = NDMPFS
254 ...
255 }
256
257 FileSet {
258 Name = NDMPFS
259 ...
260 Include {
261 Plugin = "ndmp:host=nasbox user=root pass=root file=/vol/vol1"
262 }
263 }
264 \end{bVerbatim}
265
266 This plugin is available as an option. Please contact \bacula{} Systems to get
267 access to the \acs{NDMP} Plugin packages and the documentation.
268
269 \subsection{Incremental Accelerator Plugin for NetApp}
270
271 The Incremental Accelerator for NetApp Plugin is designed to simplify the
272 backup and restore procedure of your NetApp \acs{NAS} hosting a huge number of files.
273
274 \smallskip{} When using the NetApp \acs{HFC} Plugin, \bacula{} Enterprise will query the
275 NetApp device to get the list of all files modified since the last backup
276 instead of having to walk through the entire filesystem. Once \bacula{} have the
277 list of all files to back's up, it will use a standard network share (such as
278 \acs{NFS} or \acs{CIFS}) to access files.
279
280 \smallskip{}
281 This plugin is available as an option. Please contact \bacula{} Systems to get
282 access to the Incremental Accelerator Plugin for NetApp packages and the
283 documentation.
284
285
286 \subsection{PostgreSQL Plugin}
287
288 The \postgresql{} plugin is designed to simplify the backup and restore procedure
289 of your \postgresql{} cluster, the backup administrator doesn't need to learn about
290 internals of \postgresql{} backup techniques or write complex scripts. The plugin
291 will automatically take care for you to backup essential information such as
292 configuration, users definition or tablespaces. The \postgresql{} plugin supports
293 both dump and \ac{PITR} backup techniques.
294
295 \smallskip{}
296 This plugin is available as an option. Please contact \bacula{} Systems to get
297 access to the \postgresql{} Plugin packages and the documentation.
298
299
300 \subsection{VMWare vSphere VADP Plugin}
301
302 The \bacula{} Enterprise vSphere plugin provides virtual
303 machine bare metal recovery, while the backup at the guest level simplify data
304 protection of critical applications.
305
306 The plugin integrates the VMware's \ac{CBT} technology to
307 ensure only blocks that have changed since the initial Full, and/or the last
308 Incremental or Differential Backup are sent to the current Incremental or
309 Differential backup stream to give you more efficient backups and reduced
310 network load.
311
312 \smallskip{}
313 This plugin is available as an option. Please contact \bacula{} Systems to get
314 access to the vSphere Plugin packages and the documentation.
315
316 \subsection{Oracle RMAN Plugin}
317
318 The \bacula{} Enterprise Oracle Plugin is designed to simplify the backup and
319 restore procedure of your Oracle Database instance, the backup administrator
320 don't need to learn about internals of Oracle backup techniques or write
321 complex scripts. The \bacula{} Enterprise Oracle plugin supports both dump and
322 \ac{PITR} with \ac{RMAN} backup techniques.
323
324 \smallskip{}
325 This plugin is available as an option. Please contact \bacula{} Systems to get
326 access to the Oracle Plugin packages and the documentation.