@cryptgoat Unless you want to be writing your own backup scripts, you should probably compare the higher-level backup software that wraps each of #Restic and #BorgBackup. For instance: #autorestic and #borgmatic.
I am looking for a parallelized pipeline system in #Python. Basically a build system lile #SCons but without the files as intermediary step, all in memory. So for example I'd like to read some data files, extract metadata from them, then save that metadata (with :gitannex: #gitAnnex). Along the way there might be other branches of logic that could need parallelization.
Ideally with progress visualisation.
Is there something like this in #Python or do I have to roll my own?
@folkerschamel@birnim But total progress bars and ETA estimations are sometimes actively decided against. I think #borgBackup doesn't do it. Neither does :gitannex: #gitAnnex, though I don't know for what specific reasons.
Every time I've set up my Mac to back up to a network drive, it refuses to actually run a backup hourly, instead reading "Next backup: When triggered manually". This phrase nets zero Google search results.
How the heck do I actually force it to run hourly?
@searls for me Time Machine has always been very bad at backing up to network targets. Frequently got stuck, aborted or wanted to start over with a full backup every week. I now use #Vorta (#borgbackup frontend) and it's much faster and more robust. You don't get 1-click restore and some built-in apps are tricky to handle (i.e. better sync Keychain to iCloud etc.), but it's a trade-off worth making imho.