From: Eric Bollengier Date: Sun, 31 Aug 2008 19:02:57 +0000 (+0000) Subject: ebl Adding new status slots command to newfeature chapter X-Git-Tag: Release-3.0.0~1038 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=5b9e31fa85a94342662ad8bd6037410a1311f9ba;p=bacula%2Fdocs ebl Adding new status slots command to newfeature chapter --- diff --git a/docs/manuals/en/concepts/autochangers.tex b/docs/manuals/en/concepts/autochangers.tex index 9c74a483..d3fa47e0 100644 --- a/docs/manuals/en/concepts/autochangers.tex +++ b/docs/manuals/en/concepts/autochangers.tex @@ -15,13 +15,12 @@ which is explained in more detail after this list: sent by Bacula. We furnish such a script that works with {\bf mtx} found in the {\bf depkgs} distribution. -\item That each Volume (tape) to be used must be defined in the Catalog and - have a Slot number assigned to it so that Bacula knows where the Volume is in - the autochanger. This is generally done with the {\bf label} command, - but can also done after the tape is labeled using the {\bf update slots} - command. See - below for more details. You must pre-label the tapes manually before - using them. +\item That each Volume (tape) to be used must be defined in the Catalog and + have a Slot number assigned to it so that Bacula knows where the Volume is + in the autochanger. This is generally done with the {\bf label} command, but + can also done after the tape is labeled using the {\bf update slots} + command. See below for more details. You must pre-label the tapes manually + before using them. \item Modifications to your Storage daemon's Device configuration resource to identify that the device is a changer, as well as a few other parameters. diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex index e954e91f..54884403 100644 --- a/docs/manuals/en/concepts/newfeatures.tex +++ b/docs/manuals/en/concepts/newfeatures.tex @@ -94,19 +94,42 @@ run job=MyBackup level=Incremental run job=MyBackup level=Incremental \end{verbatim} -So providing there were changes between each of those jobs, you would end up with -a Full backup, a Differential, which includes the first Incremental backup, then two -Incremental backups. All the above jobs would be written to the \bf{Default} pool. +So providing there were changes between each of those jobs, you would end up +with a Full backup, a Differential, which includes the first Incremental +backup, then two Incremental backups. All the above jobs would be written to +the \bf{Default} pool. -To consolidate those backups into a new Full backup, you would run the following: +To consolidate those backups into a new Full backup, you would run the +following: \begin{verbatim} run job=MyBackup level=VirtualFull \end{verbatim} -And it would produce a new Full backup without using the client, and the output would -be written to the \bf{Full} Pool which uses the Diskchanger Storage. +And it would produce a new Full backup without using the client, and the output +would be written to the \bf{Full} Pool which uses the Diskchanger Storage. +\section{Accurate Backup} +\index[general]{Accurate Backup} +\section{Using bconsole to display autochanger content} +\index[general]{StatusSlots} + +The {\bf status slots storage=xxx} command displays autochanger content. + +\footnotesize +\begin{verbatim} + Slot | Volume Name | Status | Media Type | Pool | Loaded | +------+-----------------+----------+-------------------+----------------+---------| + 1 | 00001 | Append | DiskChangerMedia | Default | 0 | + 2 | 00002 | Append | DiskChangerMedia | Default | 0 | + 3*| 00003 | Append | DiskChangerMedia | Scratch | 0 | + 4 | | | | | 0 | +\end{verbatim} +\normalsize + +If you see a {\bf *} near the slot number, you have to run {\bf update slots} +command to synchronize autochanger content with your catalog. +