Skip to content

Commit

Permalink
code blocks
Browse files Browse the repository at this point in the history
  • Loading branch information
pstorz committed Nov 27, 2018
1 parent 9111ae3 commit 41cd557
Show file tree
Hide file tree
Showing 40 changed files with 878 additions and 534 deletions.
11 changes: 11 additions & 0 deletions docs/manuals/en/new_main_reference/replace.sh
Expand Up @@ -92,7 +92,18 @@ sed -i -E 's|:raw-latex:`\\sinceVersion\{(.*)\}\{(.*)\}\{(.*)\}`|\3|g' *.rst
# file
sed -i -E 's|:raw-latex:`\\file\{(.*)\}`|:file:`\1`|g' *.rst

sed -i -E 's#^::$##g' *.rst

#code blocks
# {commands}{get the process ID of a running Bareos daemon}
# <command> </command><parameter>ps fax | grep bareos-dir</parameter>
# 2103 ? S 0:00 /usr/sbin/bareos-dir

#.. code-block:: c
# :caption: get the process ID of a running Bareos daemon


sed -i -E 's#\{commands\}\{(.*)\}#\n.. code-block:: sh\n :caption: \1\n#g' *.rst


#
Expand Down
26 changes: 13 additions & 13 deletions docs/manuals/en/new_main_reference/source/always-incremental.rst
Expand Up @@ -116,7 +116,7 @@ Always Incremental Backup Job
To configure a job to use Always Incremental Backup Scheme, following
configuration is required:

::


{bareosConfigResource}{bareos-dir}{job}{example}
Job {
Expand Down Expand Up @@ -151,7 +151,7 @@ configuration is required:
Consolidate Job
~~~~~~~~~~~~~~~

::


{bareosConfigResource}{bareos-dir}{job}{Consolidate}
Job {
Expand Down Expand Up @@ -199,7 +199,7 @@ For the Always Incremental Backup Scheme at least two storages are
needed. See :ref:`section-MultipleStorageDevices` how to
setup multiple storages.

::


{bareosConfigResource}{bareos-dir}{pool}{AI-Incremental}
Pool {
Expand All @@ -215,7 +215,7 @@ setup multiple storages.
Next Pool = AI-Consolidated # consolidated jobs go to this pool
}

::


{bareosConfigResource}{bareos-dir}{pool}{AI-Consolidated}
Pool {
Expand All @@ -231,7 +231,7 @@ setup multiple storages.
Next Pool = AI-Longterm # copy jobs write to this pool
}

::


{bareosConfigResource}{bareos-dir}{pool}{AI-Longterm}
Pool {
Expand All @@ -257,7 +257,7 @@ configured for always incremental Backup. The Backup itself is scheduled
every night to run as incremental backup, while the consolidation is
scheduled to run every day.

::


{bareosConfigResource}{bareos-dir}{job}{BackupClient1}
Job {
Expand All @@ -274,7 +274,7 @@ scheduled to run every day.
Full Backup Pool = AI-Consolidated
}

::


{bareosConfigResource}{bareos-dir}{job}{Consolidate}
Job {
Expand Down Expand Up @@ -447,7 +447,7 @@ was introduced.
needs to be configured in the
:raw-latex:`\resourceDirectiveValue{Dir}{Job}{Type}{Consolidate}` job:

::


{bareosConfigResource}{bareos-dir}{job}{Consolidate}
Job {
Expand Down Expand Up @@ -520,7 +520,7 @@ As all full backups go into the :raw-latex:`\pool{AI-Consolidated}`, we
just copy all uncopied backups in the
:raw-latex:`\pool{AI-Consolidated}` to a longterm pool:

::


{bareosConfigResource}{bareos-dir}{job}{CopyLongtermFull}
Job {
Expand All @@ -547,7 +547,7 @@ Virtual Full Jobs
The alternative to Copy Jobs is creating a virtual Full Backup Job when
the data should be stored in a long-term pool.

::


{bareosConfigResource}{bareos-dir}{job}{VirtualLongtermFull}
Job {
Expand Down Expand Up @@ -624,7 +624,7 @@ incremental backup of the remote client.
Run the first backup but make sure that you choose the remote storage to
be used.

::


{bconsole}{run}
*run job=BackupClient-remote level=Full storage=File-remote
Expand All @@ -643,7 +643,7 @@ daemon.
List volumes shows that the volumes used still belong to the remote
storage:

::


{bconsole}{list volumes}
*<input>list volumes</input>
Expand All @@ -658,7 +658,7 @@ storage:
Use :raw-latex:`\bcommand{update}{volume}` to set the right storage and
check with list volumes that it worked:

::


{bconsole}{update volume}
*<input>update volume=Full-0001 storage=File</input>
Expand Down

0 comments on commit 41cd557

Please sign in to comment.