Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Implementing 3-2-1 backup strategy #97

Open
toskium opened this issue Mar 25, 2024 · 0 comments
Open

Feature Request: Implementing 3-2-1 backup strategy #97

toskium opened this issue Mar 25, 2024 · 0 comments

Comments

@toskium
Copy link

toskium commented Mar 25, 2024

My current understanding of restic-windows-backup is that it only allows for one restic repository to save backups to.
With the PR #96 one can add additional parameters to employ rclone but it does not allow for multiple repositories.

What I would like to do is the following:

  1. define local restic repository on a NAS
  2. define rclone remote on some cloud storage
  3. run restic-backup to store everything on the local restic repository
  4. run rclone after restic-backup has finished and sync all the new files to the defined rclone remote (possibly multiple rclone remotes)
  5. When doing restic-backup maintenance also do rclone remote maintenance to check if everything is in order.

Is this feature request in alignment with the project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant