X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fmanuals%2Fen%2Fmain%2Fnewfeatures.tex;h=803cf0944174e869c79d16e82b4142215e057308;hb=9db4f0e1919fe2f4045593b41778f4925ec7af11;hp=50d8f559e27237f3a0c37faabfed81e7656beefe;hpb=e5ee26f88665f73086bf2225da9dd60b27873230;p=bacula%2Fdocs diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex index 50d8f559..803cf094 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 @@ -52,28 +67,15 @@ a bconsole command {\bf status scheduled} produces: \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} @@ -139,13 +141,6 @@ The above command is now simplified to be: truncate storage=File pool=Default \end{verbatim} -\subsection{New Resume Command} -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. - \subsection{Migration/Copy/VirtualFull Performance Enhancements} The Bacula Storage daemon now permits multiple jobs to simultaneously read the same disk Volume, which gives substantial performance enhancements when @@ -358,7 +353,7 @@ RunAfterJob = "/bin/echo Pid=%P isCloned=%C" \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 @@ -410,6 +405,42 @@ command line. 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. @@ -426,7 +457,7 @@ especially useful for specifying more complicated Migration/Copy SQL 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 @@ -445,8 +476,8 @@ directive of a Schedule resource. This version of Bacula also permits 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 @@ -463,12 +494,35 @@ to select all the appropriate Jobs. \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}