X-Git-Url: https://arthur.barton.de/gitweb/?p=backup-script.git;a=blobdiff_plain;f=README.md;h=4f6ec5246c0bfe62c8affe7bdc9f3a78c717759f;hp=47ec27a91819dc27d1d52b6355126ed3deb3e16d;hb=HEAD;hpb=d90bbdfe4940046d36d79b0beec55c9750c9bd85 diff --git a/README.md b/README.md index 47ec27a..4f6ec52 100644 --- a/README.md +++ b/README.md @@ -3,9 +3,8 @@ A script for backing up data using `ssh`(1), `rsync`(1), and `scp`(1). Can handle backup generations on *btrfs* and *ZFS*. -Copyright (c)2008-2016 Alexander Barton () -Homepage: https://github.com/alexbarton/backup-script - +Copyright (c)2008-2020 Alexander Barton () +Homepage: ## Installation @@ -70,7 +69,6 @@ Options: When no *job* is given, all defined jobs are checked. - ## Configuration All default configuration variables are read from the first file found of this @@ -98,7 +96,6 @@ For example: - `/etc/backups-script.d/host01.example.net`: configuration for host 1 - `/etc/backups-script.d/clientXY.example.com`: configuration for host 2 - ### Global Settings The following global configuration options exist: @@ -111,7 +108,6 @@ In Addition, all job configuration options (see below) that have a "default_XXX" variant can be used and define default values for all jobs that don't overwrite them individually. - ## Configuration Variables ### system @@ -208,11 +204,11 @@ inside of the target directory. Supported file systems are: - * *btrfs*: - All generations are btrfs subvolumes and named after the date and time. - * *ZFS*: - All generations are ZFS file systems. Latest generation is named `current`, - elders are links to the ZFS snapshot directories. +- *btrfs*: + All generations are btrfs subvolumes and named after the date and time. +- *ZFS*: + All generations are ZFS file systems. Latest generation is named `current`, + elders are links to the ZFS snapshot directories. The latest snapshot is always reachable using a symlink named `latest` inside the system directory. @@ -250,11 +246,10 @@ The following job configurations variables used by the outdated backup-pull(1) script in job definition files are automatically mapped to the new backup-script variables: -* `host` -> `system` -* `source` -> `source_root` -* `pre_exec` -> `job_pre_exec` -* `post_exec` -> `job_post_exec` - +- `host` -> `system` +- `source` -> `source_root` +- `pre_exec` -> `job_pre_exec` +- `post_exec` -> `job_post_exec` ## Exit codes