evolix/ansible-roles
22
2
Fork 2
Code Issues 61 Pull requests 18 Releases 34 Wiki Activity

Added evobackup-client role #83

Manually merged
Ghost merged 17 commits from evobackup-client into unstable 2020-02-06 22:31:45 +01:00
Conversation 5 Commits 17 Files changed 11 +1 -1
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 11e006201a - Show all commits

2
evobackup-client/templates/zzz_evobackup.default.sh.j2
View file

@ -341,7 +341,7 @@ if [ "${SYNC_TASKS}" = "1" ]; then
/etc \
/root \
/var \
/home/backup \
/home \
jlecour commented 2019-09-02 08:52:53 +02:00
Outdated
Review
Copy link

Why /home/backup and not /home like it is in the official script https://gitea.evolix.org/evolix/evobackup/src/branch/master/zzz_evobackup#L344 ?

Why /home/backup and not /home like it is in the official script https://gitea.evolix.org/evolix/evobackup/src/branch/master/zzz_evobackup#L344 ?
Ghost commented 2019-09-03 15:19:58 +02:00
Outdated
Review
Copy link

The way I've been using it mostly is for system backups not full backups, hence the '/home/backup'. If you're doing a complete backup, it's almost always going to be more custom, so I feel like the more common use case is more useful. But I dont have strong opinions about this.

The way I've been using it mostly is for system backups not full backups, hence the '/home/backup'. If you're doing a complete backup, it's almost always going to be more custom, so I feel like the more common use case is more useful. But I dont have strong opinions about this.
Ghost commented 2019-09-03 17:19:16 +02:00
Outdated
Review
Copy link

This would be the main outstanding question. I feel like /home/backup is a better default, but I can change it. What do you think ?

This would be the main outstanding question. I feel like /home/backup is a better default, but I can change it. What do you think ?
jlecour commented 2019-09-05 05:55:36 +02:00
Outdated
Review
Copy link

This reveals a blindspot in our setup.

When we do a "system only" backup, we definitely want to keep the files with the list of packages, mtr output… They currently go to /home/backup by default.

But when we also backup the whole server to another backup server and there are databases dumps in /home/backup then thos files are also added to the "system-only" backup, which is not good.

Maybe we should put lightweight important files to backup to /root/backup and large data dumps to /home/backup. Then we would always add /root/backup to the rsync command, and only add /home to full backups.

This reveals a blindspot in our setup. When we do a "system only" backup, we definitely want to keep the files with the list of packages, mtr output… They currently go to `/home/backup` by default. But when we also backup the whole server to another backup server and there are databases dumps in `/home/backup` then thos files are also added to the "system-only" backup, which is not good. Maybe we should put lightweight important files to backup to `/root/backup` and large data dumps to `/home/backup`. Then we would always add `/root/backup` to the `rsync` command, and only add `/home` to full backups.
Ghost commented 2019-09-05 14:46:57 +02:00
Outdated
Review
Copy link

That makes sense. We could then add a boolean switch to enable "full" backups from ansible.

Could this cause any problems with the typical free space on /root ?

That makes sense. We could then add a boolean switch to enable "full" backups from ansible. Could this cause any problems with the typical free space on /root ?
/srv \
-e "${RSH_COMMAND}" \
"root@${SSH_SERVER}:/var/backup/" \