Replies: 3 comments
-
Thinking about this some more... it could get messy. Retentions uses 'after-backup', how would a copy be defined? 'after-retention' ??? I am thinking it would need to look like:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
One of my configs below:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I know this is definitely a missing feature, it's on my TODO list 😉 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am a bit lost here. I have a backup running in the 'default' profile that puts data in an onsite Restic repo (for speed). I then have a 'copy' block defined in the 'default' profile to send snapshots to an offsite repo (Borgbase). What is the best way to have the copy run after a backup as the backup command does not have a 'after-backup' like 'retention' does.
The only way I can see to do this is run 'copy' on a standalone schedule based on time alone.
Beta Was this translation helpful? Give feedback.
All reactions