ansible/ansible_role_restic
1
0
Fork 0
mirror of https://github.com/roles-ansible/ansible_role_restic.git synced 2024-12-11 23:41:32 +01:00
Code Releases Activity
ansible_role_restic/templates/restic.service.j2

25 lines
615 B
Text
Raw Normal View History

implement systemd timer
2021-04-29 14:58:12 +02:00
[Unit]
Description=Backup {{ item.name }} using restic
[v2] feat: lvm: Add lvm-based backup functionality This commit implements the needs of #75[^1]: it allows for the creation of atomic backups when the backup target is a file/dir whose fs rests on LVM. This ensures the snapshot will be atomic. By using a mount namespace, the LVM snapshot can be done in the same directory -- so existing LVM-based applications of ansible_role_restic can be migrated to this implementation without any discontinuity in what appears to be backed up. This combination of LVM's snapshotting layer and mount namespaces comes with some caveats: - you cannot backup / due to namespace issues - subdirs with a separate fs won't be correctly detected - not all filesystems are happy about LVM snapshots -- btrfs, e.g. - LVM snapshots come with a performance penalty when active - fstrim and LVM snapshots don't like each other whatsoever [^1]: https://github.com/roles-ansible/ansible_role_restic/issues/75 -- Changes in v2: - Use `findmnt -v` to find snapshot when cleaning up - Check for _snap before `lvremove -y` Signed-off-by: Martin Kennedy <hurricos@gmail.com>
2022-08-28 01:17:41 +02:00
{% if item.lvm is defined %}
Conflicts=fstrim.service
After=fstrim.timer
{% endif %}
implement systemd timer
2021-04-29 14:58:12 +02:00
[Service]
Type=oneshot
quote BACKUP_SOURCES, add service_options
2024-01-27 23:49:08 +01:00
{% if item.service_options is defined %}
{% for key, value in item.service_options.items() %}
{{key}}={{value}}
{% endfor %}
{% endif %}
[v2] feat: lvm: Add lvm-based backup functionality This commit implements the needs of #75[^1]: it allows for the creation of atomic backups when the backup target is a file/dir whose fs rests on LVM. This ensures the snapshot will be atomic. By using a mount namespace, the LVM snapshot can be done in the same directory -- so existing LVM-based applications of ansible_role_restic can be migrated to this implementation without any discontinuity in what appears to be backed up. This combination of LVM's snapshotting layer and mount namespaces comes with some caveats: - you cannot backup / due to namespace issues - subdirs with a separate fs won't be correctly detected - not all filesystems are happy about LVM snapshots -- btrfs, e.g. - LVM snapshots come with a performance penalty when active - fstrim and LVM snapshots don't like each other whatsoever [^1]: https://github.com/roles-ansible/ansible_role_restic/issues/75 -- Changes in v2: - Use `findmnt -v` to find snapshot when cleaning up - Check for _snap before `lvremove -y` Signed-off-by: Martin Kennedy <hurricos@gmail.com>
2022-08-28 01:17:41 +02:00
{% if item.lvm is defined %}
PrivateMounts=on
{% endif %}
template change and README clarification
2024-01-04 18:52:05 +01:00
{% if item.niceness is defined %}
ExecStart=/usr/bin/nice -n {{ item.niceness }} {{ restic_script_dir }}/backup-{{ item.name }}.sh
{% else %}
ExecStart={{ restic_script_dir }}/backup-{{ item.name }}.sh
{% endif %}
disable timeout mechanism
2021-12-07 17:47:51 +01:00
TimeoutStartSec=0
implement systemd timer
2021-04-29 14:58:12 +02:00
Environment="CRON=true"
Copy permalink