You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the feature
db-backup creates files on different repositories in order to get them saved by the respective backup tools.
It would be fine to have RESTIC cli as one of the possible targets.
Benftits of feature
This would decouple database backups from the OS backup strategy completely and procure isolated backup for the db container(s).
The text was updated successfully, but these errors were encountered:
As Restic accepts database dumps through stdin, this would be ideal, yes.
A workaround I tried is (a) rebuild Docker container and adding restic and (b) installing restic on the Docker host and pointing a volume to it : "/usr/bin/restic:/usr/bin/restic:ro".
In both cases it would only work with first copying the backups to a folder on the local filesystem, and then having Restic back up the files in that folder using a db-backup post-script. But it does work.
Description of the feature
db-backup creates files on different repositories in order to get them saved by the respective backup tools.
It would be fine to have RESTIC cli as one of the possible targets.
Benftits of feature
This would decouple database backups from the OS backup strategy completely and procure isolated backup for the db container(s).
The text was updated successfully, but these errors were encountered: