dattobd VS PrawnOS

https://github.com/datto/dattobd is still a thing, apparently. Needs its own kernel module, so have fun with that.

There's https://github.com/datto/dattobd Never used it though.

(Or if you're really crazy, and want image based incremental backups then this exists https://github.com/datto/dattobd).

The dattobd [1] block device driver fills this gap. It basically implements VSS like behavior on Linux. It is used in the Datto Linux backup agent in combination with the backup appliance [2], but it can be used stand alone as well (see readme).

Disclaimer: I'm a software engineer for Datto.

[1] https://github.com/datto/dattobd

It connects but fails to back up a remote Linux server. Then I read from somewhere saying it works only in LAN. I ends up using https://github.com/datto/dattobd and rsync.

In my last job I worked on writing backup agents in C++ for multiple platforms using userspace API's. There was a team that exclusively worked on the Linux driver that our agent used, the driver is open source too - https://github.com/datto/dattobd

The OP's computer is one of those Rockchip ARM models. It is much more difficult to get an alternate OS on it compared to Intel models. Maybe this one: https://github.com/SolidHal/PrawnOS

> I'd hardly argue that the RK3399 SoC is more "open" than any of the broadcom SoCs.

What? The gru-kevin chromebook (RK3399) can be booted without using a single binary blob, absolutely everything (even the arm trusted firmware) built from source. I use mine that way.

I've never seen a laptop with a "broadcom SoC" that could make that claim.

https://github.com/SolidHal/PrawnOS

chromebooks fork linux almost as badly as androids. instead of mainline + some patches/modules you get a custom kernel made for the hardware in question, usually with lots of proprietary drivers that make it hard for users to update. this is worse for ARM chromebooks than x86 chromebooks, but often has the same result on both: instead of downloading your favorite distro's ISO and installing it, you need to find something like PrawnOS that supports your specific model. in many cases you can't dualboot either because google's gimped UEFI/uboot/whatever implementation only boots chromeOS, and once you replace it with a custom firmware chromeOS becomes unbootable

You might want to look for an installation guide for your specific model. For example I used this one to install PrawnOS on my Acer C201P

the mainstream name is core/libreboot like used here but there's various other custom firmware too