docs: condense snap job overview table row

This commit is contained in:
Christian Schwarz 2019-03-17 21:29:09 +01:00
parent 158d1175e3
commit dd673bf923
2 changed files with 17 additions and 18 deletions

View File

@ -23,24 +23,22 @@ For communication, the active side connects to the passive side using a :ref:`tr
The following table shows how different job types can be combined to achieve both push and pull mode setups: The following table shows how different job types can be combined to achieve both push and pull mode setups:
+-----------------------+--------------+----------------------------------+-----------------------------------------------+ +-----------------------+--------------+----------------------------------+------------------------------------------------------------------------------------+
| Setup name | active side | passive side | use case | | Setup name | active side | passive side | use case |
+=======================+==============+==================================+===============================================+ +=======================+==============+==================================+====================================================================================+
| Push mode | ``push`` | ``sink`` | * Laptop backup | | Push mode | ``push`` | ``sink`` | * Laptop backup |
| | | | * NAS behind NAT to offsite | | | | | * NAS behind NAT to offsite |
+-----------------------+--------------+----------------------------------+-----------------------------------------------+ +-----------------------+--------------+----------------------------------+------------------------------------------------------------------------------------+
| Pull mode | ``pull`` | ``source`` | * Central backup-server for many nodes | | Pull mode | ``pull`` | ``source`` | * Central backup-server for many nodes |
| | | | * Remote server to NAS behind NAT | | | | | * Remote server to NAS behind NAT |
+-----------------------+--------------+----------------------------------+-----------------------------------------------+ +-----------------------+--------------+----------------------------------+------------------------------------------------------------------------------------+
| Local replication | | ``push`` + ``sink`` in one config | * Backup FreeBSD boot pool | | Local replication | | ``push`` + ``sink`` in one config | * Backup FreeBSD boot pool |
| | | with :ref:`local transport <transport-local>` | | | | | with :ref:`local transport <transport-local>` | |
+-----------------------+--------------+----------------------------------+-----------------------------------------------+ +-----------------------+--------------+----------------------------------+------------------------------------------------------------------------------------+
| SnapJob | ``snap`` | N/A | * Data requires versioning but no backups | | Snap & prune-only | ``snap`` | N/A | * | Snapshots & pruning but no replication |
| | | | * Combined with a ``push`` or ``pull`` job: | | | | | | required |
| | | | | | | | | * Workaround for :ref:`source-side pruning <prune-workaround-source-side-pruning>` |
| | | | * High frequency local snapshotting | +-----------------------+--------------+----------------------------------+------------------------------------------------------------------------------------+
| | | | * Low frequency replication |
+-----------------------+--------------+----------------------------------+-----------------------------------------------+
How the Active Side Works How the Active Side Works
~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~

View File

@ -158,6 +158,7 @@ Policy ``regex``
Like all other regular expression fields in prune policies, zrepl uses Go's `regexp.Regexp <https://golang.org/pkg/regexp/#Compile>`_ Perl-compatible regular expressions (`Syntax <https://golang.org/pkg/regexp/syntax>`_). Like all other regular expression fields in prune policies, zrepl uses Go's `regexp.Regexp <https://golang.org/pkg/regexp/#Compile>`_ Perl-compatible regular expressions (`Syntax <https://golang.org/pkg/regexp/syntax>`_).
The optional `negate` boolean field inverts the semantics: Use it if you want to keep all snapshots that *do not* match the given regex. The optional `negate` boolean field inverts the semantics: Use it if you want to keep all snapshots that *do not* match the given regex.
.. _prune-workaround-source-side-pruning:
Source-side snapshot pruning Source-side snapshot pruning
---------------------------- ----------------------------