From bcf91f1fc3538693c1a199837e25eb112e7adc09 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Mon, 5 May 2014 18:12:27 +0200 Subject: [PATCH] Add doc of status storage changes --- docs/manuals/en/console/bconsole.tex | 29 +++++++++++++++++++++++----- docs/manuals/en/main/newfeatures.tex | 15 ++++++++++++++ 2 files changed, 39 insertions(+), 5 deletions(-) diff --git a/docs/manuals/en/console/bconsole.tex b/docs/manuals/en/console/bconsole.tex index c07c88be..fd30c180 100644 --- a/docs/manuals/en/console/bconsole.tex +++ b/docs/manuals/en/console/bconsole.tex @@ -1197,7 +1197,8 @@ status [all | dir=\lt{}dir-name\gt{} | director [days=nnn] | problem by doing a {\bf status dir}, but you can most often get a much more specific indication of the problem by doing a {\bf status storage=xxx}. For example, on an idle test system, when - I do {\bf status storage=File}, I get: + we do {\bf status storage=File}, we get: + \footnotesize \begin{verbatim} status storage=File @@ -1237,11 +1238,11 @@ In Use Volume status: \end{verbatim} \normalsize -Now, what this tells me is that no jobs are running and that none of -the devices are in use. Now, if I {\bf unmount} the autochanger, which +Now, what this tells us is that no jobs are running and that none of +the devices are in use. Now, if we {\bf unmount} the autochanger, which will not be used in this example, and then start a Job that uses the -File device, the job will block. When I re-issue the status storage -command, I get for the Device status: +File device, the job will block. When we re-issue the status storage +command, we get for the Device status: \footnotesize \begin{verbatim} @@ -1268,6 +1269,24 @@ the user unmounted the device. The real problem for the Job I started using the "File" device is that the device is blocked waiting for media -- that is Bacula needs you to label a Volume. +\smallskip +If you enter {\bf status storage}, Bacula will prompt you with a +list of the storage resources. When you select one, the Storage daemon +will be requested to do a {\bf status}. However, note that the Storage +daemon will do a status of all the devices it has, and not just of the +one you requested. In the current version of Bacula, when you enter +the {\bf status storage} command, it prompts you only with a subset of +all the storage resources that the Director considers to be in different +Storage daemons. In other words, it attempts to remove duplicate +storage definitions. This can be a bit confusing at first, but can +vastly simplify the promt listing if you have defined a large number +of storage resources. + +If you prefer to see the full list of all storage resources, simply +add the keyword {\bf select} to the command such as: +{\bf status select storage} and you will get a prompt that includes +all storage resources even if they reference the same storage daemon. + \item [time] \index[general]{time} Prints the current time. diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex index 599b31eb..c9bae7fa 100644 --- a/docs/manuals/en/main/newfeatures.tex +++ b/docs/manuals/en/main/newfeatures.tex @@ -44,6 +44,21 @@ the Job or the Pool. In general, more information is displayed in the Job log on exactly which Next Pool specification is ultimately used. +\subsection{status storage} +The bconsole {\bf status storage} has been modified to attempt to eliminate +duplicate storage resources and only show one that references any given +storage daemon. This might be confusing at first, but tends to make a +much more compact list of storage resource from which to select if there +are multiple storage devices in the same storage daemon. + +If you want the old behavior (always display all storage resources) simply +add the keyword {\bf select} to the command -- i.e. use +{\bf status select storage}. + + + + + \subsection{status schedule} A new status command option called {\bf scheduled} has been implemented in bconsole. By default it will display 20 lines of the next scheduled -- 2.39.5