This command does exactly the same thing as a
{\bf restart} command but for some users the
name may be more logical since in general the
-{\bf restart} command is used to resume running
-a Job that was incompleted.
+{\bf restart} command is used to rerun running
+a Job that had been canceled or had failed.
\subsection{Migration/Copy/VirtualFull Performance Enhancements}
The Bacula Storage daemon now permits multiple jobs to simultaneously read
\end{verbatim}
\subsection{Read Only Storage Devices}
-This version of Bacula permits defining a Storage deamon device
+This version of Bacula permits defining a Storage daemon device
to be read-only. That is if the {\bf ReadOnly} directive is specified and
enabled, the drive can only be used for read operations.
The the {\bf ReadOnly} directive can be defined in any bacula-sd.conf
accurate
\end{verbatim}
-On or more of these command keywords can be placed in qoutes and separated
+On or more of these command keywords can be placed in quotes and separated
by spaces on the Disable Command directive line. Note: the commands must
be written exactly as they appear above.
statements and in creating long restricted console ACL lists.
\subsection{Maximum Spawned Jobs}
-The Job resource now permits specifing a number of {\bf Maximum Spawn
+The Job resource now permits specifying a number of {\bf Maximum Spawn
Jobs}. The default is 300. This directive can be useful if you have
big hardware and you do a lot of Migration/Copy jobs which start
at the same time. In prior versions of Bacula, Migration/Copy
specifying the 6th week of a month with the keyword {\bf sixth} or
{\bf 6th}.
-\subsection{Secheduling the Last Day of a Month}
-This version of Bacula now premits specifying the {\bf lastday}
+\subsection{Scheduling the Last Day of a Month}
+This version of Bacula now permits specifying the {\bf lastday}
keyword in the {\bf run} directive of a Schedule resource.
If {\bf lastday} is specified, it will apply only to those months
specified on the {\bf run} directive. Note: by default all months
\subsection{bconsole Performance Improvements}
In previous versions of Bacula certain bconsole commands could wait a long
-time due to catalog lock contention. This was especially noticable
+time due to catalog lock contention. This was especially noticeable
when a large number of jobs were running and putting their attributes
into the catalog. This version uses a separate catalog connection that
should significantly enhance performance.