From c0f4afa79d12060f285070e9092bcba82bc15263 Mon Sep 17 00:00:00 2001 From: yova Date: Thu, 3 Mar 2022 15:45:37 +0100 Subject: [PATCH] typos --- content/blog/ovh-pca-backupninja-duplicity.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/blog/ovh-pca-backupninja-duplicity.md b/content/blog/ovh-pca-backupninja-duplicity.md index 2bee1b1..5d63190 100644 --- a/content/blog/ovh-pca-backupninja-duplicity.md +++ b/content/blog/ovh-pca-backupninja-duplicity.md @@ -4,11 +4,11 @@ description: Accessing the OVH Public cloud archive with the automated backup to date: 2022-03-03 --- -## motivation +## Motivation OVH provides a cheap way for longterm storing backup data, the Public Cloud Archive (PCA). As this is for write-once data (cold data store), it needs to be used together with a little bit more expensive hot data store for meta data when used for sequential backups. The backup solution [duplicity](https://duplicity.gitlab.io/duplicity-web/) is capable of using such multi backends. [backupninja](https://0xacab.org/liberate/backupninja) provides a nice solution for a standardized configuration of duplicity and running it automatically. ## Prerequisites -### On system +### On system to backup - Enable email sending for backup status mails by [installing a mta](/msmtp-on-debian/). - Install system dependencies - `apt install librsync-dev gpg backupninja`