<p>The job level is one of "I" for incremental or "F" for full or "D" for differential.
-<p>A purged value of 1 means that the files for that job have been purged and you
-are not be able to browse for the files backed up with that jobid.
+<p>A purged value of yes means that the files for that job have been purged from the
+catalog's file table. Purged jobs are not be able to have their files browsed when
+restoring from a job with that jobid.
<p>This interface uses a splitter to divide the display of the table and the controls
used to modify the selection criterion. There are 7 drop down boxes that can be used
<p>Pushing the Graph button opens up a new JobPlot interface. All of the
drop downs and limiting controls in the JobPlot window default to the current
-settings of the controls in the JobList interface.
+settings of the controls in the JobList interface. If the graph button is not there,
+bat was not compiled with qwt libraries.
<p>There are many options in the context sensitive popup that appear when the user
right clicks on an item in the job table.
user to inform the bacula server details of the host and path to restore to, the
replacement rules, when to restore and what priority to give the restore job.
-<h2>A Version Browser Limitation</h2>
-
-There is an important limitation of the version browser. If a fileset
-specifically points to a file instead of a directory that contains files, it
-will not be seen in the version browser. This is due to the way that the
-version browser searches for directories first, then for files contained in
-those directories. A common example is with the catalog job.
-It by default points directly to one file created in a databse dump.
-
<h2>The Version Browser Restore Interface</h2>
<p>This restore interface is <b>NOT</b> intended to perform major restores of directory
Restore. These indicate to the user the time it may take to complete any tasks
that could take a long time period.
+<h2>A Version Browser Limitation</h2>
+
+There is an important limitation of the version browser. If a fileset
+specifically points to a file instead of a directory that contains files, it
+will not be seen in the version browser. This is due to the way that the
+version browser searches for directories first, then for files contained in
+those directories. A common example is with the catalog job.
+It by default points directly to one file created in a databse dump.
+
<h2>Version Browser Performance</h2>
<p>If you have used the version browser with a large database, you may have