google-drive-ocamlfuse VS borgmatic

I fixed the problem, it was due to the incorrect setup of the google drive. I followed this guide to set everything up from scratch and create the folder directly in Linux instead of constantly accessing the apparently "encrypted" cloud. If anyone ever runs into the same problem, I really hope this thread is helpful :D

You might be able to use something like https://github.com/astrada/google-drive-ocamlfuse

Its a little hacky, but google drive with mounted ocaml-fuse kinda does-ish this... though git/GitHub does the trick, too.

There are fuse drivers like https://github.com/astrada/google-drive-ocamlfuse but I pretty darned sure it's using exactly the same transport protocol as Google's own app.

you might be able to load a drive with locally with google-drive-ocamlfuse but you wouldn't get access to google drives proprietary files (google doc, sheet, slide, etc)

There's always the excellent unofficial google-drive-ocamlfuse which uses FUSE to mount Google drive to a local directory.

https://github.com/astrada/google-drive-ocamlfuse

Agree with previous comment, dejadup is a good option for local backups, but there isnt a really good backup cloud tool in linux enviroment: https://github.com/vitalif/grive2, https://github.com/astrada/google-drive-ocamlfuse, etc.

- for important files, a separate box where I have borgmatic [1] in deduplication mode installed; this is updated once in a while

Just curious: Do you have any reason to believe that such a data corruption bug is likely in ZFS? It seems like saying that ext4 could have a bug and you should also store stuff on NTFS, just in case (which I think does not make sense..).

[1]: https://github.com/borgmatic-collective/borgmatic

Not really dumb. I do use them too but with Borgbackup on the top (since they support it natively).

I found Borgmatic ( https://torsion.org/borgmatic/ ) to be the best way to run my backups. It takes care of everything from pruning to verifying the checksum etc... and it integrates with some monitoring (like cronitor).

So Borgmatic + rsync.net is the best combo

For backups I use Borg myself. If you need a GUI, you can use Vorta or Pika. With borgmatic, there is also a wrapper that extends the range of functions of Borg.

Furthermore, Borgmatic is a wrapper for Borg that extends or improves the range of functions.

For those of you not familiar, borgmatic is a very convenient tool which runs as a wrapper around borg.

I recommend Borg and Borgmatic. Automated, easy to setup, capable of notifying you if anything happens, deduplication and compression makes backups smaller, etc.

To add to this, Borg backup can be a little daunting to configure. There is a wrapper script called Borgmatic that distills it down to a single yaml config file. There are also some cloud hosts like BorgBase and rsync.net with native Borg support.