-
\subsection{Include All Windows Drives in FileSet}
The \texttt{alldrives} Windows Plugin allows you to include all local drives
with a simple directive. This plugin is available in the Windows 64 and 32 bit
installer.
-\begin{verbatim}
+\begin{lstlisting}
FileSet {
Name = EverythingFS
...
Plugin = "alldrives"
}
}
-\end{verbatim}
+\end{lstlisting}
You exclude some specific drives with the \texttt{exclude} option.
-\begin{verbatim}
+\begin{lstlisting}
FileSet {
Name = EverythingFS
...
Plugin = "alldrives: exclude=D,E"
}
}
-\end{verbatim}
+\end{lstlisting}
\subsection{Microsoft VSS Writer Plugin}
Only the System State component is currently supported. The Sharepoint,
MSSQL, and Exchange components are available only for testing.
-\begin{itemize}
+\begin{bsysitemize}
\item System State writers
- \begin{itemize}
+ \begin{bsysitemize}
\item Registry
\item Event Logs
\item COM+ REGDB (COM Registration Database)
\item NTFRS (SYSVOL etc replication -- Windows 2003 domains)
\item DFS Replication (SYSVOLS etc replication -- Windows 2008 domains)
\item ASR Writer
- \end{itemize}
+ \end{bsysitemize}
This component is known to work.
\item Sharepoint writers \\
This component has not yet been tested. It is included so that you
use it in production without careful testing. \\ Bacula Systems has a
White Paper that describes backup and restore of MS Exchange 2010 in
detail.
-\end{itemize}
+\end{bsysitemize}
Each of the above specified Microsoft components can be backed up
by specifying a different plugin option within the Bacula FileSet.
(see below).
To activate each component you use the following:
-\begin{itemize}
+\begin{bsysitemize}
\item System State writers
- \begin{verbatim}
+ \begin{lstlisting}
Plugin = "vss:/@SYSTEMSTATE/"
- \end{verbatim}
+ \end{lstlisting}
Note, exactly which subcomponents will be backed up depends on
which ones you have enabled within Windows. For example, on a standard
default Vista system only ASR Writer, COM+ REGDB, System State, and WMI
are enabled.
\item Sharepoint writers
- \begin{verbatim}
+ \begin{lstlisting}
Plugin = "vss:/@SHAREPOINT/"
- \end{verbatim}
+ \end{lstlisting}
\item MSSQL databases (except those owned by Sharepoint if that plugin is
specified)
- \begin{verbatim}
+ \begin{lstlisting}
Plugin = "vss:/@MSSQL/"
- \end{verbatim}
+ \end{lstlisting}
To use the sharepoint writer you'll need to enable the mssql writer
which is not enabled by default (a Microsoft restriction). The Microsoft
literature says that the mssql writer is only good for snapshots
enabled via a registry tweak or else the older MSDE writer will be
invoked instead.
\item Exchange (all exchange databases)
- \begin{verbatim}
+ \begin{lstlisting}
Plugin = "vss:/@EXCHANGE/"
- \end{verbatim}
-\end{itemize}
+ \end{lstlisting}
+\end{bsysitemize}
The plugin directives must be specified exactly as shown above.
A Job may have one or more of the {\bf vss} plugins components specified.
include the system state. The system state files backed up will appear
in a {\bf bconsole} or {\bf bat} restore like:
-\begin{verbatim}
+\begin{lstlisting}
/@SYSTEMSTATE/
/@SYSTEMSTATE/ASR Writer/
/@SYSTEMSTATE/COM+ REGDB Writer/
etc
-\end{verbatim}
+\end{lstlisting}
Only a complete backup of the system state is supported at this time. That
is it is not currently possible to just back up the Registry or Active
in the FilesNotToBackup registry key, which includes things like \%TEMP\%,
pagefile.sys, hiberfil.sys, etc. Each plugin may additionally specify
files to exclude, eg the VSS Registry Writer will tell Bacula to not back
-up the registry hives under \verb+C:\WINDOWS\system32\config+ because they
+up the registry hives under \lstinline+C:\WINDOWS\system32\config+ because they
are backed up as part of the system state.
\subsubsection{Restore}
\subsubsection{Example}
Suppose you have the following backup FileSet:
-\begin{verbatim}
+\begin{lstlisting}
@SYSTEMSTATE/
System Writer/
instance_{GUID}
NTDS/
instance_{GUID}
ntds/
-\end{verbatim}
+\end{lstlisting}
If only the Registry needs to be restored, then you could use the
following commands in {\bf bconsole}:
-\begin{verbatim}
+\begin{lstlisting}
markdir @SYSTEMSTATE
cd @SYSTEMSTATE
markdir "Registry Writer"
cd "Registry Writer"
mark instance*
mark "Registry"
-\end{verbatim}
+\end{lstlisting}
\subsubsection{Windows Plugins Items to Note}
-\begin{itemize}
+\begin{bsysitemize}
\item Reboot Required after a Plugin Restore\\
In general after any VSS plugin is used to restore a component, you will
need to reboot the system. This is required because in-use files cannot be
to restore your system, use the last Full non-VSS backup to restore your
system, and after rebooting do a restore with the VSS plugin to get
everything fully up to date.
-\end{itemize}
+\end{bsysitemize}
This plugin is available as an option. Please
contact Bacula Systems to get access to the VSS Plugin packages and the
the LAN to your Bacula server.
Accurate option should be turned on in the Job resource.
-\begin{verbatim}
+\begin{lstlisting}
Job {
Accurate = yes
FileSet = NDMPFS
Plugin = "ndmp:host=nasbox user=root pass=root file=/vol/vol1"
}
}
-\end{verbatim}
+\end{lstlisting}
This plugin is available as an option. Please
contact Bacula Systems to get access to the NDMP Plugin packages and the
projects / bacula / docs / blobdiff