Update documentation about configuring multiple consistency checks or multiple databases (#559).

NEWS

@@ -1,3 +1,6 @@
+1.6.6.dev0
+ * #559: Update documentation about configuring multiple consistency checks or multiple databases.
+
 1.6.5
  * #553: Fix logging to include the full traceback when Borg experiences an internal error, not just
    the first few lines.

docs/how-to/backup-your-databases.md

@@ -52,6 +52,8 @@ hooks:
     postgresql_databases:
         - name: users
           hostname: database1.example.org
+        - name: orders
+          hostname: database2.example.org
           port: 5433
           username: postgres
           password: trustsome1
@@ -59,14 +61,14 @@ hooks:
           options: "--role=someone"
     mysql_databases:
         - name: posts
-          hostname: database2.example.org
+          hostname: database3.example.org
           port: 3307
           username: root
           password: trustsome1
           options: "--skip-comments"
     mongodb_databases:
         - name: messages
-          hostname: database3.example.org
+          hostname: database4.example.org
           port: 27018
           username: dbuser
           password: trustsome1

docs/how-to/deal-with-very-large-backups.md

@@ -83,12 +83,15 @@ consistency:
     checks:
         - name: repository
           frequency: 2 weeks
+        - name: archives
+          frequency: 1 month
 ```
 
-This tells borgmatic to run this consistency check at most once every two
+This tells borgmatic to run the `repository` consistency check at most once
-weeks for a given repository. The `frequency` value is a number followed by a
+every two weeks for a given repository and the `archives` check at most once a
-unit of time, e.g. "3 days", "1 week", "2 months", etc. The `frequency`
+month. The `frequency` value is a number followed by a unit of time, e.g. "3
-defaults to "always", which means run this check every time checks run.
+days", "1 week", "2 months", etc. The `frequency` defaults to `always`, which
+means run this check every time checks run.
 
 Unlike a real scheduler like cron, borgmatic only makes a best effort to run
 checks on the configured frequency. It compares that frequency with how long

setup.py

@@ -1,6 +1,6 @@
 from setuptools import find_packages, setup
 
-VERSION = '1.6.5'
+VERSION = '1.6.6.dev0'
 
 
 setup(