Ansible Role: serdigital64.backup.bkp_restic

Purpose

Manage provisioning of the Restic tool.

Supported features in the current version:

  • Deploy application. Packages are defined in the variable bkp_restic_profiles.

The bkp_restic Ansible-Role is part of the A:Platform64 project and is available in the backup Ansible-Collection.

Usage

The following example is an Ansible Playbook that includes all the supported features:

use this link if viewing the doc on github

---
- name: "Backup / Restic / Usage example"
  hosts: "localhost"
  gather_facts: true

  tasks:
    - name: "Example: Install Restic"
      vars:
        bkp_restic:
          resolve_prereq: true
          deploy: true
      ansible.builtin.include_role:
        name: "serdigital64.backup.bkp_restic"
...

The playbook can be run by executing:

# Set ANSIBLE_COLLECTIONS_PATHS to the default location. Change as needed.
ANSIBLE_COLLECTIONS_PATHS="${HOME}/.ansible/collections"
ansible-playbook "${ANSIBLE_COLLECTIONS_PATHS}/ansible_collections/serdigital64/backup/playbooks/bkp_restic.yml"

Role Parameters

Actions

  • Use action-parameters to control what tasks are enabled for the role to execute.
  • Parameters should be declared as task level vars as they are intented to be dynamic.
bkp_restic:
  resolve_prereq:
  deploy:
Parameter Required? Type Default Purpose / Value
bkp_restic.resolve_prereq no boolean false Enable automatic resolution of prequisites
bkp_restic.deploy no boolean false Enable installation of application packages

End State

  • Use end-state parameters to define the target state after role execution.
  • Parameters should be declared in host_vars or group_vars as they are intended to be permanent.
bkp_restic_application:
  name:
  type:
  version:
  installed:
Parameter Required? Type Default Purpose / Value
bkp_restic_application no dictionary Set application package end state
bkp_restic_application.name no string "restic" Select application package name
bkp_restic_application.type no string "binary" Select application package type
bkp_restic_application.installed no boolean true Set application package end state
bkp_restic_application.version no string "v0_12" Select application package version

Deployment

OS Compatibility

  • CentOS8
  • RedHat8
  • AlmaLinux8
  • OracleLinux8
  • Ubuntu20
  • Ubuntu21
  • Fedora33
  • Fedora35
  • Debian10
  • Debian11

Dependencies

  • Ansible Collections:
    • serdigital64.backup
      • bkp_archive
    • serdigital64.system
      • sys_package
      • sys_repository

Prerequisites

The Ansible engine must be already installed and configured for privileged access and remote execution.

In addition the following prerequisites can be automatically solved when running the playbook by setting the role action: resolve_prereq: true

  • Package manager for the target application is installed and enabled.

Installation Procedure

Manually install Ansible Collections from the Ansible Galaxy repository:

ansible-galaxy collection install --upgrade serdigital64.backup

Automatic installation is also available by deploying A:Platform64

Contributing

Help on implementing new features and maintaining the code base is welcomed.

Please see the guidelines for further details.

Author

License

GPL-3.0-or-later