From fe356c76876db38f9672281c72d298f8718cc15e Mon Sep 17 00:00:00 2001
From: Jelle van der Waa <jelle@archlinux.org>
Date: Wed, 17 Jun 2020 11:51:37 +0200
Subject: [PATCH] Add setting up borg backups on a new machine section

---
 README.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/README.md b/README.md
index d16b54219..7ec7dcdc3 100644
--- a/README.md
+++ b/README.md
@@ -283,6 +283,22 @@ Medium-fast-ish packet.net box with Debian on it. Is currently maintained manual
 
 ## Backup documentation
 
+Adding a new server to be backed up goes as following:
+
+* Make sure the new servers host key is synced to docs/ssh-known_hosts.txt if not run:
+  ansible-playbook playbooks/tasks/sync-ssh-hostkeys.yml
+
+* Add the server to [borg-clients] in hosts
+
+* Run the borg role on vostok to allow the new machine to create backups
+  ansibe-playbook playbooks/vostok.yml -t borg
+
+* Run the borg role for rsync.net to allow the new machine to create backups
+  ansibe-playbook playbooks/rsync.net.yml
+
+* Run the borg role on the new machine to initialize the repository
+  ansibe-playbook playbooks/$machine.yml -t borg
+
 Backups should be checked now and then. Some common tasks:
 
 ### Listing current backups per server
-- 
GitLab