1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
---
title: Borg ansible role
date: 2021-05-02
description: The ansible role I wrote to manage my borg backups
tags:
- ansible
- backups
---
## Introduction
I have been managing my personal infrastructure with ansible for a few years and used borg to backup my servers for many more.
My ansible git repository is not published for privacy and confidentiality reasons but this week-end I decided to finally take the time to cleanup the code and publish this role. Thanks to `git filter-branch --subdirectory-filter roles/borg --prune-empty -- --all` I managed to extract the folder of my ansible repository and turn it into a submodule.
I wanted a role to easily manage my backups and did not find an existing one that satisfied me. A mandatory feature for me was the ability to configure a client in only one place without having to configure a server : the server configuration will be derived from the clients that need to use it as a backup target. Another mandatory feature is the validation of host_vars which virtually no role in the wild ever does... So I wrote [mine](https://git.adyxax.org/adyxax/borg-ansible-role).
This way configuring backups for a host named `yen.adyxax.org` is as simple as having the following `host_vars` :
```yaml
julien@yen:~/git/adyxax/ansible$ cat host_vars/yen.adyxax.org
---
borg_server: cobsd-jde.nexen.net
borg_jobs:
- { name: etc, path: "/etc", exclude: [ "/etc/firmware" ] }
- name: gitea
path: "/tmp/gitea.zip"
pre_command: "echo '/usr/local/sbin/gitea -C /etc/gitea -c /etc/gitea/app.ini dump -f /tmp/gitea.zip' | su -l _gitea"
post_command: "rm -f /tmp/gitea.zip"
- { name: nethack, path: "/opt/nethack" }
- { name: var_imap, path: "/var/imap" }
- { name: var_spool_imap, path: "/var/spool/imap" }
...
```
Which can be used in a simple playbook like :
```yaml
julien@yen:~/git/adyxax/ansible$ cat setup.yml
---
- name: Gather facts
hosts: all
tags: always
tasks:
- name: Gather facts
setup:
- name: Enforce every configurations
hosts: all
roles:
- { role: borg, tags: [ 'borg' ] }
...
```
## Configuration
First of all you only need to configure hosts that are backup clients. There are several `host_vars` you can define to this effect :
- `borg_server`: a string that contains a hostname.
- `borg_jobs`: a list of dict, one item per job with the following keys:
- `name`: the name of the borg job, an alphanumeric string.
- `path`: an optional path containing the files to backup.
- `command_to_pipe`: an optional command to pipe the backup data from.
- `pre_command`: an optional command to run before a job.
- `post_command`: an optional command to run after a job.
- `exclude`: an optional list of paths containing locations to exclude.
- `borg_prune_arguments`: a string passed to the `borg prune` command, defaults to `'--keep-within 30d'` for a 30 days backups retention.
To be valid a borg job entry needs to have a name and exactly one of `path` or `command_to_pipe` key.
## Jobs examples
Here are some job examples :
- backup a simple path, exclude a subdirectory :
```yaml
- { name: etc, path: "/etc", exclude: [ "/etc/firmware" ] }
```
- backup from a command output, this is what I use in conjunction with another of my yet unreleased roles :
```yaml
- name: mysqldump
command_to_pipe: >
/usr/bin/mysqldump -h {{ mysql_server }}
-u {{ ansible_hostname }}
-p {{ ansible_local.mysql_client.password }}
--single-transaction
--add-drop-database
-B {{ ansible_hostname }}
```
- backup job with pre and post commands, what I use for my gitea server on OpenBSD :
```yaml
- name: gitea
path: "/tmp/gitea.zip"
pre_command: "echo '/usr/local/sbin/gitea -C /etc/gitea -c /etc/gitea/app.ini dump -f /tmp/gitea.zip' | su -l _gitea"
post_command: "rm -f /tmp/gitea.zip"
```
## What the role does
### On the servers
On servers, the role creates a `borg` user with `/srv/borg` as a home directory where backups will be stored. For each client, a line in the borg user's `authorized_keys` file is generated to enforce and limit access to only one clients' repository.
### On the clients
On clients, the role creates a borg ssh key for the root user and generates a backup script in `/usr/local/bin/adyxax_backup.sh`. The role also adds a cron job that will run the backup script each nigh. Lastly it makes sure the client's borg repository is properly initialised on the server.
### Action plugins
There is an action plugin that validates host_vars types and values for each borg role variable, and another that parses the borg_server entries from all host_vars and set a borg fact for both machines to be backed up and for machines that are specified as backup targets (so that they do not require any manual configuration or variables). This action plugin also enforces the job rules to make sure those are valid and without ambiguities.
### Ansible fact
There is a fact script deployed on each server. It is used to retrieve the ssh public key of clients or the repository status of servers and used in tasks.
## Usefull command:
Manually schedule a backup run :
```sh
ansible all -i hosts -m shell -a "/usr/local/bin/adyxax_backup.sh"
```
|
