\begin{verbatim}
Scheduled Jobs:
-Level Type Pri Scheduled Job Name Schedule
+Level Type Pri Scheduled Job Name Schedule
======================================================================
-Differential Backup 10 Sun 30-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Mon 24-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Tue 25-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Wed 26-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Thu 27-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Fri 28-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Sat 29-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Mon 31-Mar 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Tue 01-Apr 23:05 BackupClient1 WeeklyCycle
-Incremental Backup 10 Wed 02-Apr 23:05 BackupClient1 WeeklyCycle
-Full Backup 11 Mon 24-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Tue 25-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Wed 26-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Thu 27-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Fri 28-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Sat 29-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Sun 30-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Mon 31-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Tue 01-Apr 23:10 BackupCatalog WeeklyCycleAfterBackup
-Full Backup 11 Wed 02-Apr 23:10 BackupCatalog WeeklyCycleAfterBackup
+Differential Backup 10 Sun 30-Mar 23:05 BackupClient1 WeeklyCycle
+Incremental Backup 10 Mon 24-Mar 23:05 BackupClient1 WeeklyCycle
+Incremental Backup 10 Tue 25-Mar 23:05 BackupClient1 WeeklyCycle
+...
+Full Backup 11 Mon 24-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
+Full Backup 11 Wed 26-Mar 23:10 BackupCatalog WeeklyCycleAfterBackup
+...
====
\end{verbatim}
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
This feature was developed by Josip Almasi, and enhanced to be runtime
dynamic by Kern Sibbald.
+\subsection{DisableCommand Directive}
+There is a new Directive named {\bf Disable Command} that
+can be put in the File daemon Client or Director resource.
+If it is in the Client, it applies globally, otherwise the
+directive applies only to the Director in which it is found.
+The Disable Command adds security to your File daemon by
+disabling certain commands. The commands that can be
+disabled are:
+
+\begin{verbatim}
+backup
+cancel
+setdebug=
+setbandwidth=
+estimate
+fileset
+JobId=
+level =
+restore
+endrestore
+session
+status
+.status
+storage
+verify
+RunBeforeNow
+RunBeforeJob
+RunAfterJob
+Run
+accurate
+\end{verbatim}
+
+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.
+
\subsection{Multiple Console Directors}
Support for multiple bconsole and bat Directors in the bconsole.conf and
bat.conf files has been implemented and/or improved.
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.
-
+\subsection{New .bvfs\_decode\_lstat Command}
+There is a new bconsole command, which is
+{\bf .bvfs\_decode\_lstat} it requires one argument, which
+is {\bf lstat="lstat value to decode"}. An example command
+in bconsole and the output might be:
+
+\small
+\begin{verbatim}
+.bvfs_decode_lstat lstat="A A EHt B A A A JP BAA B BTL/A7 BTL/A7 BTL/A7 A A C"
+
+st_nlink=1
+st_mode=16877
+st_uid=0
+st_gid=0
+st_size=591
+st_blocks=1
+st_ino=0
+st_ctime=1395650619
+st_mtime=1395650619
+st_mtime=1395650619
+st_dev=0
+LinkFI=0
+\end{verbatim}
+\normalsize
\subsection*{New Debug Options}
projects / bacula / docs / blobdiff