| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Allow removing configuration for repositories.
|
| | |
|
| | |
|
| |
|
|
| |
Adds option to choose a non-default borg backup user on the server.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Add borg_storage_quota variable to limit repository storage on the
borg server via --storage-quota option in authorized_keys.
When not using borg_ssh_key_per_repo, all repos for a host must share
the same quota setting (similar to --append-only). Per-repo SSH keys
enable independent quotas per repository.
|
| |
|
|
|
|
|
|
|
| |
Add borg_ssh_key_per_repo option to generate unique SSH keypairs per
(server, repo) combination. When enabled, each repository gets its own
authorized_keys entry, enabling:
- Independent --append-only settings per repository
- Per-repo storage quotas
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This brings support for multiple backups pointing to the same borg
server, different repositories, from the same client. We support this by
parsing the SSH authorized key file first and appending allowed
repositories to allow independent definitions of the borg targets.
So that the decryption_keys do not clash we include the repository name
as well as the host in the key. This will lead to new keys being created
for existing hosts in the new format.
Old Format: {{ combine({inventory_hostname: borg_keys.stdout}) }}
New Format: {{ combine({(inventory_hostname ~ '_' ~ borg_repo_name): borg_keys.stdout}) }}
If upgrading from an older version that used just the hostname as the
key, your existing `decryption_keys.yml` can be manually removed once
the new format is also added.
|
| |
|
|
|
|
|
|
| |
- Add test systems for client/server setup
- Add tests for systemd service and timer files
- Add tests for SSH connectivity
- Add tests for security configurations
- Add tests for multi-instance backup scenarios
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Systemd gives us the ability to monitor backup job status using existing
monitoring solutions (node exporter) and allows us greater control over
the scheduling of the backup jobs.
This introduces a breaking change that requires users to manually remove
the old repositories from the clients and redeploying them with the
role. You will have to remove the Cron job that was created by the
Ansible script, everything else will be overwritten with a run from the
newer version.
- name: Remove backup cron jobs
ansible.builtin.cron:
name: BORG (Application level backups)
state: absent
become: true
- name: Remove env for backup cron job
ansible.builtin.cron:
name: BORG_PASSPHRASE
env: true
state: absent
become: true
Performing manual migrations on the Borg server is not required.
We now additionally support multiple Borg repositories per client host
using the `borg_backup_argument` variable.
Signed-off-by: Colin Wilk <colin.wilk@tum.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix linting errors that came up with the new rules
Main changes:
* Enforce YAML document start headers
* Enforce spacing with commas, colons and hyphens
* Enforce indentation
* Enforce use of quotes only then required
* Enforce use of single quotes over double quotes
* Enforce use of true/false over yes/no and derivatives
* [..] Other minor rules that were already followed
Signed-off-by: Colin Wilk <colin.wilk@tum.de>
|
|
|
Signed-off-by: Colin Wilk <colin.wilk@tum.de>
|
