The third form deletes the specified Job record from the catalog database.
The last form deletes JobId records for JobIds n,m,o,p, q,r, and t. Where each
one of the n,m,... is, of course, a number.
-\label{estimate}
+\label{estimate}
\item [estimate]
- \index[console]{estimate }
- Using this command, you can get an idea how many files will be backed up, or
-if you are unsure about your Include statements in your FileSet, you can test
-them without doing an actual backup. The default is to assume a Full backup.
-However, you can override this by specifying a {\bf level=Incremental} or
-{\bf level=Differential} on the command line. A Job name must be specified
-or you will be prompted for one, and optionally a Client and FileSet may be
-specified on the command line. It then contacts the client which computes
-the number of files and bytes that would be backed up. Please note that this
-is an estimate calculated from the number of blocks in the file rather than
-by reading the actual bytes. As such, the estimated backup size will
-generally be larger than an actual backup.
-
-Optionally you may specify the keyword {\bf listing} in which case, all the
-files to be backed up will be listed. Note, it could take quite some time to
-display them if the backup is large. The full form is:
+ \index[console]{estimate}
+ Using this command, you can get an idea how many files will be backed
+ up, or if you are unsure about your Include statements in your FileSet,
+ you can test them without doing an actual backup. The default is to
+ assume a Full backup. However, you can override this by specifying a
+ {\bf level=Incremental} or {\bf level=Differential} on the command line.
+ A Job name must be specified or you will be prompted for one, and
+ optionally a Client and FileSet may be specified on the command line.
+ It then contacts the client which computes the number of files and bytes
+ that would be backed up. Please note that this is an estimate
+ calculated from the number of blocks in the file rather than by reading
+ the actual bytes. As such, the estimated backup size will generally be
+ larger than an actual backup.
+
+ Optionally you may specify the keyword {\bf listing} in which case, all the
+ files to be backed up will be listed. Note, it could take quite some time to
+ display them if the backup is large. The full form is:
estimate job=\lt{}job-name\gt{} listing client=\lt{}client-name\gt{}
fileset=\lt{}fileset-name\gt{} level=\lt{}level-name\gt{}
@output /tmp/listing
estimate job=NightlySave listing level=Incremental
@output
-
\end{verbatim}
\normalsize
/tmp/listing}.
\item [help]
- \index[console]{help }
+ \index[console]{help}
This command displays the list of commands available.
\item [label]
- \index[console]{label }
+ \index[console]{label}
+ \index[console]{relabel}
+ \index[general]{label}
+ \index[general]{relabel}
This command is used to label physical volumes. The full form of this command
-is:
+ is:
label storage=\lt{}storage-name\gt{} volume=\lt{}volume-name\gt{}
slot=\lt{}slot\gt{}
\footnotesize
\begin{verbatim}
-
update storage=xxx pool=yyy slots=1-5,10 barcodes
\end{verbatim}
\normalsize
\item [list]
\index[console]{list }
The list command lists the requested contents of the Catalog. The various
-fields of each record are listed on a single line. The various forms
-of the list command are:
+ fields of each record are listed on a single line. The various forms
+ of the list command are:
\footnotesize
\begin{verbatim}
list jobs
list volumes job=\lt{}job-name\gt{}
- list volume=\lt{}volume-name\gt{} list nextvolume job=\lt{}job-name\gt{}
+ list volume=\lt{}volume-name\gt{}
+
+ list nextvolume job=\lt{}job-name\gt{}
list nextvol job=\lt{}job-name\gt{}
+
\end{verbatim}
\normalsize
-What most of the above commands do should be more or less obvious. In general
-if you do not specify all the command line arguments, the command will prompt
-you for what is needed.
-
-The {\bf list nextvol} command will print the Volume name to be used by the
-specified job. You should be aware that exactly what Volume will be used
-depends on a lot of factors including the time and what a prior job will do.
-It may fill a tape that is not full when you issue this command. As a
-consequence, this command will give you a good estimate of what Volume will
-be used but not a definitive answer. In addition, this command may have
-certain side effect because it runs through the same algorithm as a job,
-which means it may automatically purge or recycle a Volume.
-
-If you wish to add specialized commands that list the contents of the
-catalog, you can do so by adding them to the {\bf query.sql} file. However,
-this takes some knowledge of programming SQL. Please see the {\bf query}
-command below for additional information. See below for listing the full
-contents of a catalog record with the {\bf llist} command.
-
-As an example, the command {\bf list pools} might produce the following
-output:
+
+ What most of the above commands do should be more or less obvious. In
+ general if you do not specify all the command line arguments, the
+ command will prompt you for what is needed.
+
+ The {\bf list nextvol} command will print the Volume name to be used by
+ the specified job. You should be aware that exactly what Volume will be
+ used depends on a lot of factors including the time and what a prior job
+ will do. It may fill a tape that is not full when you issue this
+ command. As a consequence, this command will give you a good estimate
+ of what Volume will be used but not a definitive answer. In addition,
+ this command may have certain side effect because it runs through the
+ same algorithm as a job, which means it may automatically purge or
+ recycle a Volume.
+
+ If you wish to add specialized commands that list the contents of the
+ catalog, you can do so by adding them to the {\bf query.sql} file.
+ However, this takes some knowledge of programming SQL. Please see the
+ {\bf query} command below for additional information. See below for
+ listing the full contents of a catalog record with the {\bf llist}
+ command.
+
+ As an example, the command {\bf list pools} might produce the following
+ output:
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-As mentioned above, the {\bf list} command lists what is in the database.
-Some things are put into the database immediately when Bacula starts up, but
-in general, most things are put in only when they are first used, which is
-the case for a Client as with Job records, etc.
+ As mentioned above, the {\bf list} command lists what is in the
+ database. Some things are put into the database immediately when Bacula
+ starts up, but in general, most things are put in only when they are
+ first used, which is the case for a Client as with Job records, etc.
-Bacula should create a client record in the database the first time you run a
-job for that client. Doing a {\bf status} will not cause a database record to
-be created. The client database record will be created whether or not the job
-fails, but it must at least start. When the Client is actually contacted,
-additional info from the client will be added to the client record (a "uname
--a" output).
+ Bacula should create a client record in the database the first time you
+ run a job for that client. Doing a {\bf status} will not cause a
+ database record to be created. The client database record will be
+ created whether or not the job fails, but it must at least start. When
+ the Client is actually contacted, additional info from the client will
+ be added to the client record (a "uname -a" output).
-If you want to see what Client resources you have available in your conf
-file, you use the Console command {\bf show clients}.
+ If you want to see what Client resources you have available in your conf
+ file, you use the Console command {\bf show clients}.
\item [llist]
- \index[console]{llist }
- The llist or "long list" command takes all the same arguments that the list
-command described above does. The difference is that the llist command list
-the full contents of each database record selected. It does so by listing the
-various fields of the record vertically, with one field per line. It is
-possible to produce a very large number of output lines with this command.
+ \index[console]{llist}
+ The llist or "long list" command takes all the same arguments that the
+ list command described above does. The difference is that the llist
+ command list the full contents of each database record selected. It
+ does so by listing the various fields of the record vertically, with one
+ field per line. It is possible to produce a very large number of output
+ lines with this command.
-If instead of the {\bf list pools} as in the example above, you enter {\bf
-llist pools} you might get the following output:
+ If instead of the {\bf list pools} as in the example above, you enter
+ {\bf llist pools} you might get the following output:
\footnotesize
\begin{verbatim}
\normalsize
\item [messages]
- \index[console]{messages }
+ \index[console]{messages}
This command causes any pending console messages to be immediately displayed.
\item [mount]
- \index[console]{mount }
- The mount command is used to get Bacula to read a volume on a physical
-device. It is a way to tell Bacula that you have mounted a tape and that
-Bacula should examine the tape. This command is used only after there was no
-Volume in a drive and Bacula requests you to mount a new Volume or when you
-have specifically unmounted a Volume with the {\bf unmount} console command,
-which causes Bacula to close the drive. If you have an autoloader, the mount
-command will not cause Bacula to operate the autoloader. The various forms of
-the mount command are:
+ \index[console]{mount}
+ The mount command is used to get Bacula to read a volume on a physical
+ device. It is a way to tell Bacula that you have mounted a tape and
+ that Bacula should examine the tape. This command is used only after
+ there was no Volume in a drive and Bacula requests you to mount a new
+ Volume or when you have specifically unmounted a Volume with the {\bf
+ unmount} console command, which causes Bacula to close the drive. If
+ you have an autoloader, the mount command will not cause Bacula to
+ operate the autoloader. The various forms of the mount command are:
mount storage=\lt{}storage-name\gt{}
mount [ jobid=\lt{}id\gt{} | job=\lt{}job-name\gt{} ]
-If you have specified {\bf Automatic Mount = yes} in the Storage daemon's
-Device resource, under most circumstances, Bacula will automatically access
-the Volume unless you have explicitly {\bf unmount}ed it in the Console
-program.
+ If you have specified {\bf Automatic Mount = yes} in the Storage daemon's
+ Device resource, under most circumstances, Bacula will automatically access
+ the Volume unless you have explicitly {\bf unmount}ed it in the Console
+ program.
\item[python]
\index[console]{python}
python restart
- This causes the Python interpreter in the Director to be
- reinitialized. This can be helpful for testing because once
- the Director starts and the Python interpreter is initialized,
- there is no other way to make it accept any changes to the
- startup script {\bf DirStartUp.py}. For more details on
- Python scripting, please see the \ilink{Python Scripting}{_ChapterStart60}
- chapter of this manual.
+ This causes the Python interpreter in the Director to be reinitialized.
+ This can be helpful for testing because once the Director starts and the
+ Python interpreter is initialized, there is no other way to make it
+ accept any changes to the startup script {\bf DirStartUp.py}. For more
+ details on Python scripting, please see the \ilink{Python
+ Scripting}{_ChapterStart60} chapter of this manual.
\label{ManualPruning}
\item [prune]
\index[console]{prune }
- The Prune command allows you to safely remove expired database records from
-Jobs and Volumes. This command works only on the Catalog database and does
-not affect data written to Volumes. In all cases, the Prune command applies
-a retention period to the specified records. You can Prune expired File
-entries from Job records; you can Prune expired Job records from the
-database, and you can Prune both expired Job and File records from specified
-Volumes.
+ The Prune command allows you to safely remove expired database records
+ from Jobs and Volumes. This command works only on the Catalog database
+ and does not affect data written to Volumes. In all cases, the Prune
+ command applies a retention period to the specified records. You can
+ Prune expired File entries from Job records; you can Prune expired Job
+ records from the database, and you can Prune both expired Job and File
+ records from specified Volumes.
prune files|jobs|volume client=\lt{}client-name\gt{}
volume=\lt{}volume-name\gt{}
-For a Volume to be pruned, the {\bf VolStatus} must be Full, Used, or Append,
-otherwise the pruning will not take place.
+ For a Volume to be pruned, the {\bf VolStatus} must be Full, Used, or
+ Append, otherwise the pruning will not take place.
\item [purge]
\index[console]{purge }
- The Purge command will delete associated Catalog database records from Jobs
-and Volumes without considering the retention period. {\bf Purge} works only
-on the Catalog database and does not affect data written to Volumes. This
-command can be dangerous because you can delete catalog records associated
-with current backups of files, and we recommend that you do not use it
-unless you know what you are doing. The permitted forms of {\bf purge} are:
+ The Purge command will delete associated Catalog database records from
+ Jobs and Volumes without considering the retention period. {\bf Purge}
+ works only on the Catalog database and does not affect data written to
+ Volumes. This command can be dangerous because you can delete catalog
+ records associated with current backups of files, and we recommend that
+ you do not use it unless you know what you are doing. The permitted
+ forms of {\bf purge} are:
purge files jobid=\lt{}jobid\gt{}|job=\lt{}job-name\gt{}|client=\lt{}client-name\gt{}
The actual data written to the Volume will be unaffected by this command.
\item [relabel]
- \index[console]{relabel }
- This command is used to label physical volumes. The full form of this command
-is:
+ \index[console]{relabel}
+ \index[general]{relabel}
+ This command is used to label physical volumes. The full form of this
+ command is:
relabel storage=\lt{}storage-name\gt{} oldvolume=\lt{}old-volume-name\gt{}
volume=\lt{}newvolume-name\gt{}
-If you leave out any part, you will be prompted for it. In order for the
-Volume (old-volume-name) to be relabeled, it must be in the catalog, and the
-volume status must be marked {\bf Purged} or {\bf Recycle}. This happens
-automatically as a result of applying retention periods, or you may
-explicitly purge the volume using the {\bf purge} command.
+ If you leave out any part, you will be prompted for it. In order for
+ the Volume (old-volume-name) to be relabeled, it must be in the catalog,
+ and the volume status must be marked {\bf Purged} or {\bf Recycle}.
+ This happens automatically as a result of applying retention periods, or
+ you may explicitly purge the volume using the {\bf purge} command.
-Once the volume is physically relabeled, the old data previously written
-on the Volume is lost and cannot be recovered.
+ Once the volume is physically relabeled, the old data previously written
+ on the Volume is lost and cannot be recovered.
\item [release]
\index[console]{release }
- This command is used to cause the Storage daemon to rewind (release) the
-current tape in the drive, and to re-read the Volume label the next time the
-tape is used.
+ This command is used to cause the Storage daemon to rewind (release) the
+ current tape in the drive, and to re-read the Volume label the next time
+ the tape is used.
release storage=\lt{}storage-name\gt{}
-After a release command, the device is still kept open by Bacula (unless
-Always Open is set to No in the Storage Daemon's configuration) so it cannot
-be used by another program. However, with some tape drives, the operator can
-remove the current tape and to insert a different one, and when the next Job
-starts, Bacula will know to re-read the tape label to find out what tape is
-mounted. If you want to be able to use the drive with another program (e.g.
-{\bf mt}), you must use the {\bf unmount} command to cause Bacula to
-completely release (close) the device.
+ After a release command, the device is still kept open by Bacula (unless
+ Always Open is set to No in the Storage Daemon's configuration) so it
+ cannot be used by another program. However, with some tape drives, the
+ operator can remove the current tape and to insert a different one, and
+ when the next Job starts, Bacula will know to re-read the tape label to
+ find out what tape is mounted. If you want to be able to use the drive
+ with another program (e.g. {\bf mt}), you must use the {\bf unmount}
+ command to cause Bacula to completely release (close) the device.
\item [reload]
\index[console]{reload}
command. Once at least one old set of config values has been
released it will again accept new reload commands.
-While it is possible to reload the Director's configuration on the fly,
-even while jobs are executing, this is a complex operation and not
-without side effects. Accordingly, if you have to reload the Director's
-configuration while Bacula is running, it is advisable to restart the
-Director at the next convenient opportunity.
+ While it is possible to reload the Director's configuration on the fly,
+ even while jobs are executing, this is a complex operation and not
+ without side effects. Accordingly, if you have to reload the Director's
+ configuration while Bacula is running, it is advisable to restart the
+ Director at the next convenient opportunity.
\item [restore]
\index[console]{restore }
- The restore command allows you to select one or more Jobs (JobIds) to be
-restored using various methods. Once the JobIds are selected, the File
-records for those Jobs are placed in an internal Bacula directory tree, and
-the restore enters a file selection mode that allows you to interactively
-walk up and down the file tree selecting individual files to be restored.
-This mode is somewhat similar to the standard Unix {\bf restore} program's
-interactive file selection mode.
+ The restore command allows you to select one or more Jobs (JobIds) to be
+ restored using various methods. Once the JobIds are selected, the File
+ records for those Jobs are placed in an internal Bacula directory tree,
+ and the restore enters a file selection mode that allows you to
+ interactively walk up and down the file tree selecting individual files
+ to be restored. This mode is somewhat similar to the standard Unix {\bf
+ restore} program's interactive file selection mode.
restore storage=\lt{}storage-name\gt{} client=\lt{}client-name\gt{}
-where=\lt{}path\gt{} pool=\lt{}pool-name\gt{} fileset=\lt{}fileset-name\gt{}
-select current all done
+ where=\lt{}path\gt{} pool=\lt{}pool-name\gt{} fileset=\lt{}fileset-name\gt{}
+ select current all done
-Where {\bf current}, if specified, tells the restore command to automatically
-select a restore to the most current backup. If not specified, you will be
-prompted. The {\bf all} specification tells the restore command to restore
-all files. If it is not specified, you will be prompted for the files to
-restore. For details of the {\bf restore} command, please see the
-\ilink{Restore Chapter}{_ChapterStart13} of this manual.
+ Where {\bf current}, if specified, tells the restore command to
+ automatically select a restore to the most current backup. If not
+ specified, you will be prompted. The {\bf all} specification tells the
+ restore command to restore all files. If it is not specified, you will
+ be prompted for the files to restore. For details of the {\bf restore}
+ command, please see the \ilink{Restore Chapter}{_ChapterStart13} of this
+ manual.
\item [run]
\index[console]{run }
This command allows you to schedule jobs to be run immediately. The full form
-of the command is:
+ of the command is:
run job=\lt{}job-name\gt{} client=\lt{}client-name\gt{}
-fileset=\lt{}FileSet-name\gt{} level=\lt{}level-keyword\gt{}
-storage=\lt{}storage-name\gt{} where=\lt{}directory-prefix\gt{}
-when=\lt{}universal-time-specification\gt{} yes
+ fileset=\lt{}FileSet-name\gt{} level=\lt{}level-keyword\gt{}
+ storage=\lt{}storage-name\gt{} where=\lt{}directory-prefix\gt{}
+ when=\lt{}universal-time-specification\gt{} yes
-Any information that is needed but not specified will be listed for
-selection, and before starting the job, you will be prompted to accept,
-reject, or modify the parameters of the job to be run, unless you have
-specified {\bf yes}, in which case the job will be immediately sent to the
-scheduler.
+ Any information that is needed but not specified will be listed for
+ selection, and before starting the job, you will be prompted to accept,
+ reject, or modify the parameters of the job to be run, unless you have
+ specified {\bf yes}, in which case the job will be immediately sent to
+ the scheduler.
-On my system, when I enter a run command, I get the following prompt:
+ On my system, when I enter a run command, I get the following prompt:
\footnotesize
\begin{verbatim}
desired start time in YYYY-MM-DD HH:MM:SS format.
\item [setdebug]
- \index[dir]{setdebug }
+ \index[dir]{setdebug}
This command is used to set the debug level in each daemon. The form of this
-command is:
+ command is:
setdebug level=nn [trace=0/1 client=\lt{}client-name\gt{} | dir | director |
-storage=\lt{}storage-name\gt{} | all]
+ storage=\lt{}storage-name\gt{} | all]
-If trace=1 is set, then the tracing will be enabled, and the daemon where the
-setdebug applies will be placed in trace mode, and all debug output will go
-to the file {\bf bacula.trace} in the current directory of the daemon.
-Normally, tracing is used only for Win32 clients where the debug output
-cannot be written to a terminal or redirected to a file. When tracing, each
-debug output message is appended to the trace file. You must explicitly
-delete the file when you are done.
+ If trace=1 is set, then the tracing will be enabled, and the daemon
+ where the setdebug applies will be placed in trace mode, and all debug
+ output will go to the file {\bf bacula.trace} in the current directory
+ of the daemon. Normally, tracing is used only for Win32 clients where
+ the debug output cannot be written to a terminal or redirected to a
+ file. When tracing, each debug output message is appended to the trace
+ file. You must explicitly delete the file when you are done.
\item [show]
\index[console]{show }
- The show command will list the Director's resource records as defined in the
-Director's configuration file (normally {\bf bacula-dir.conf}). This command
-is used mainly for debugging purposes by developers. The following keywords
-are accepted on the show command line: directors, clients, counters, jobs,
-storages, catalogs, schedules, filesets, groups, pools, messages, all, help.
-Please don't confuse this command with the {\bf list}, which displays the
-contents of the catalog.
+ The show command will list the Director's resource records as defined in
+ the Director's configuration file (normally {\bf bacula-dir.conf}).
+ This command is used mainly for debugging purposes by developers. The
+ following keywords are accepted on the show command line: directors,
+ clients, counters, jobs, storages, catalogs, schedules, filesets,
+ groups, pools, messages, all, help. Please don't confuse this command
+ with the {\bf list}, which displays the contents of the catalog.
\item [sqlquery]
\index[dir]{sqlquery }
- The sqlquery command puts the Console program into SQL query mode where each
-line you enter is concatenated to the previous line until a semicolon (;) is
-seen. The semicolon terminates the command, which is then passed directly to
-the SQL database engine. When the output from the SQL engine is displayed,
-the formation of a new SQL command begins. To terminate SQL query mode and
-return to the Console command prompt, you enter a period (.) in column 1.
-
-Using this command, you can query the SQL catalog database directly. Note you
-should really know what you are doing otherwise you could damage the catalog
-database. See the {\bf query} command below for simpler and safer way of
-entering SQL queries.
-
-Depending on what database engine you are using (MySQL, PostgreSQL or SQLite), you will
-have somewhat different SQL commands available. For more detailed
-information, please refer to the MySQL, PostgreSQL or SQLite documentation.
+ The sqlquery command puts the Console program into SQL query mode where
+ each line you enter is concatenated to the previous line until a
+ semicolon (;) is seen. The semicolon terminates the command, which is
+ then passed directly to the SQL database engine. When the output from
+ the SQL engine is displayed, the formation of a new SQL command begins.
+ To terminate SQL query mode and return to the Console command prompt,
+ you enter a period (.) in column 1.
+
+ Using this command, you can query the SQL catalog database directly.
+ Note you should really know what you are doing otherwise you could
+ damage the catalog database. See the {\bf query} command below for
+ simpler and safer way of entering SQL queries.
+
+ Depending on what database engine you are using (MySQL, PostgreSQL or
+ SQLite), you will have somewhat different SQL commands available. For
+ more detailed information, please refer to the MySQL, PostgreSQL or
+ SQLite documentation.
\item [status]
\index[dir]{status }
- This command will display the status of the next jobs that are scheduled
-during the next twenty-four hours as well as the status of currently running
-jobs. The full form of this command is:
+ This command will display the status of the next jobs that are scheduled
+ during the next twenty-four hours as well as the status of currently
+ running jobs. The full form of this command is:
status [all | dir=\lt{}dir-name\gt{} | director |
-client=\lt{}client-name\gt{} | storage=\lt{}storage-name\gt{}]
+ client=\lt{}client-name\gt{} | storage=\lt{}storage-name\gt{}]
-If you do a {\bf status dir}, the console will list any currently running
-jobs, a summary of all jobs scheduled to be run in the next 24 hours, and a
-listing of the last 10 terminated jobs with their statuses. The scheduled
-jobs summary will include the Volume name to be used. You should be aware of
-two things: 1. to obtain the volume name, the code goes through the same code
-that will be used when the job runs, which means that it may prune or recycle
-a Volume; 2. The Volume listed is only a best guess. The Volume actually
-used may be different because of the time difference (more durations may
-expire when the job runs) and another job could completely fill the Volume
-requiring a new one.
+ If you do a {\bf status dir}, the console will list any currently
+ running jobs, a summary of all jobs scheduled to be run in the next 24
+ hours, and a listing of the last 10 terminated jobs with their statuses.
+ The scheduled jobs summary will include the Volume name to be used. You
+ should be aware of two things: 1. to obtain the volume name, the code
+ goes through the same code that will be used when the job runs, which
+ means that it may prune or recycle a Volume; 2. The Volume listed is
+ only a best guess. The Volume actually used may be different because of
+ the time difference (more durations may expire when the job runs) and
+ another job could completely fill the Volume requiring a new one.
-In the Running Jobs listing, you may find the following types of information:
+ In the Running Jobs listing, you may find the following types of
+ information:
\footnotesize
\end{verbatim}
\normalsize
-Looking at the above listing from bottom to top, obviously JobId 5343 (Rufus)
-is running. JobId 5348 (Minou) is waiting for JobId 5343 to finish because it
-is using the Storage resource, hence the "waiting on max Storage jobs".
-JobId 5349 has a lower priority than all the other jobs so it is waiting for
-higher priority jobs to finish, and finally, JobId 2508 (MatouVerify) is
-waiting because only one job can run at a time, hence it is simply "waiting
-execution"
+ Looking at the above listing from bottom to top, obviously JobId 5343
+ (Rufus) is running. JobId 5348 (Minou) is waiting for JobId 5343 to
+ finish because it is using the Storage resource, hence the "waiting on
+ max Storage jobs". JobId 5349 has a lower priority than all the other
+ jobs so it is waiting for higher priority jobs to finish, and finally,
+ JobId 2508 (MatouVerify) is waiting because only one job can run at a
+ time, hence it is simply "waiting execution"
\item [unmount]
\index[console]{unmount }
\footnotesize
\begin{verbatim}
-.die cause the Director to segment fault (for debugging)
-.jobs list all job names
-.filesets list all fileset names
-.clients list all client names
-.msgs return any queued messages
-.quit quit
-.exit quit
+.backups job=xxx list backups for specified job
+.defaults client=xxx fileset=yyy list defaults for specified client
+.die cause the Director to segment fault (for debugging)
+.dir when in tree mode prints the equivalent to the dir command,
+ but with fields separated by commas rather than spaces.
+.jobs list all job names
+.levels list all levels
+.filesets list all fileset names
+.clients list all client names
+.pools list all pool names
+.types list job types
+.msgs return any queued messages
+.messages get quick messages
+.help help command output
+.quit quit
+.status get status output
+.exit quit
\end{verbatim}
\normalsize
projects / bacula / docs / blobdiff