diff options
| -rw-r--r-- | README.md | 44 |
1 files changed, 22 insertions, 22 deletions
@@ -18,10 +18,10 @@ itself: you should do that manually or use another puppet module such as ### Remote backups using Borg - # remote encrypted backup from localhost to $node_name using Borg - backup::borg { "$node_name": - port => "$port", - } + # remote encrypted backup from localhost to $node_name using Borg + backup::borg { "$node_name": + port => "$port", + } ### Local encrypted backups pushed to remotes @@ -33,16 +33,16 @@ it's more reliable and fast than to let duplicity do all the job. #### Example with [duplicity][] and [rsync][] - # local encrypted/signed backup - backup::duplicity { "localhost": - encryptkey => "$key_id", - password => "$key_password", - } + # local encrypted/signed backup + backup::duplicity { "localhost": + encryptkey => "$key_id", + password => "$key_password", + } - # remote backup of previously encrypted/signed backup sent to $node_name - backup::rsync { "$node_name": - port => "$port", - } + # remote backup of previously encrypted/signed backup sent to $node_name + backup::rsync { "$node_name": + port => "$port", + } * The first definition will keep local encrypted/signed backups using duplicity at `/var/backups/duplicity`. @@ -52,16 +52,16 @@ it's more reliable and fast than to let duplicity do all the job. #### Example with [duplicity][] and [rdiff-backup][] - # local encrypted/signed backup - backup::duplicity { "localhost": - encryptkey => "$key_id", - password => "$key_password", - } + # local encrypted/signed backup + backup::duplicity { "localhost": + encryptkey => "$key_id", + password => "$key_password", + } - # remote backup of previously encrypted/signed backup sent to $node_name - backup::rdiff { "$node_name": - port => "$port", - } + # remote backup of previously encrypted/signed backup sent to $node_name + backup::rdiff { "$node_name": + port => "$port", + } [duplicity]: https://duplicity.gitlab.io/ [rdiff-backup]: https://rdiff-backup.net/ |