After a little searching through the forums for the best automated solution for remote backups. I found the generous work of Guillaume, who was inspired by @MWDelaney ’s brilliant work on Trellis-Backup.
roots:master ← jillro:stouts.backup
opened 12:44PM - 31 Aug 16 UTC
This is a proposition for a backup feature inspired by @MWDelaney work.
The ro… le uses [Souts.backup](https://github.com/Stouts/Stouts.backup) to create two duply backup profiles for each `wordpress_sites` which has `backup: {enabled: true}`.
The configuration for each `wordpress_sites` is the following :
``` yaml
backup:
enabled: true # creates a backup profile if true (default: false)
auto: true # set up a cron job for backup each night if true (default: false)
target: scp://user@example.com/website_name # any valid duplicity location
```
The parameter `auto` allows to create backup profile without installing the cron job. This is usefull if you want to use the backup profile only to restore backups made from another server, by running `sudo duply website_name_database restore` and `sudo duply website_name_uploads restore` . This can be an interesting solution to synchronize database and uploads between production and staging for example.
https://discourse.roots.io/t/trellis-backup-an-ansible-role-for-local-backups/6497
I’ve had no success with GTPR as of yet, but am determined to make it work with AWS S3 as my remote location.
I thought it was worth starting a thread to see how everybody else is doing such a crucial task - surely we all have some good ideas to share
1 Like
