2019-08-30 20:43:52 +02:00
|
|
|
# evobackup-client
|
|
|
|
|
|
2019-09-03 15:50:13 +02:00
|
|
|
Allows the configuration of backups to one or more remote filesystems.
|
2019-08-30 20:43:52 +02:00
|
|
|
|
2019-09-03 15:50:13 +02:00
|
|
|
The backup hosts in use need to be defined in evobackup-client__hosts
|
2019-08-30 20:43:52 +02:00
|
|
|
and the bkctld jail ssh port has to be defined in
|
2019-09-03 15:50:13 +02:00
|
|
|
evobackup-client__ssh_port before running it.
|
2019-08-30 20:43:52 +02:00
|
|
|
|
|
|
|
|
The default zzz_evobackup.sh configures a system backup, but the
|
|
|
|
|
template can be overriden to configure a full backup instead. If
|
|
|
|
|
you change the variables in defaults/main.yml you can easily run
|
2019-09-03 15:50:13 +02:00
|
|
|
this again and configure backups to a second set of hosts.
|
2019-08-30 20:43:52 +02:00
|
|
|
|
2019-09-03 15:50:13 +02:00
|
|
|
Do not forget to set the evobackup-client__mail variable to an
|
2019-08-30 20:43:52 +02:00
|
|
|
email adress you control.
|
|
|
|
|
|
|
|
|
|
You can add this example to an installation playbook to create the
|
|
|
|
|
ssh key without running the rest of the role.
|
|
|
|
|
|
|
|
|
|
~~~
|
|
|
|
|
post_tasks:
|
|
|
|
|
- include_role:
|
|
|
|
|
name: evobackup-client tasks_from: ssh_key.yml
|
|
|
|
|
~~~
|
