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
I've been using Runrestic for the incredibly long time of almost 72hrs now. (Quite liking it!) I do quite a lot of work without a connection, so restic + runrestic has been me slowly building up a time-machine like backup strategy. Time Machine backs up locally to a hidden partition, then copies over backups to the network storage when you're back within the network. With this background in mind, does it make sense to try to expand runrestic to have the concept of "backup" repos vs "copy-to" repos?prune and check would still need to be done against these copy-to repos, but backing up would always happen to a local destination first, with a second phase of copying out to these other repos if reachable, next.
The text was updated successfully, but these errors were encountered:
I've been using Runrestic for the incredibly long time of almost 72hrs now. (Quite liking it!) I do quite a lot of work without a connection, so restic + runrestic has been me slowly building up a time-machine like backup strategy. Time Machine backs up locally to a hidden partition, then copies over backups to the network storage when you're back within the network. With this background in mind, does it make sense to try to expand runrestic to have the concept of "backup" repos vs "copy-to" repos?
prune
andcheck
would still need to be done against these copy-to repos, but backing up would always happen to a local destination first, with a second phase of copying out to these other repos if reachable, next.The text was updated successfully, but these errors were encountered: