schmurian

3 backups:

• phone data is synced to a nvme drive (1) which holds all the data of my homelab
• This nvme is backed up to a nvme (2) drive on the same device via backrest
• The nvme is also synced via Diplicati to a cloud storage provider (3)

2 locations: home and cloud

1... what was 1 again?

I agree with this comment. As mentioned as answer in the post, to have a backup of these things is a big reason why I chose to selfhost. I had to switch devices (and operating systems) too many times. Moving data around everytime would be a hassle. To have all the important stuff not only stored but also organized and easy to access is very convenient and makes me stop worrying to accidentially lose my phone for example.

I just recently switched over to rpi-clone after doing backups of the booted SD with SD Card Copier, the GUI app on Raspberry OS.

The original version from billw2 didn't work with modern OS versions. After doing some lookups in the issues and online, the users pointed to geerlingguy's version, which seems to be maintained.

I'm not using rpi-clone-setup but rpi-clone sdX and after trying it for the first time, it worked. I swapped out the SD with the copy and the raspberry booted (it didn't boot with billw2's version).

Next step is to create a script for regular backups.

To your questions:

• Tried it, it works for my use-case
• rpi-clone asks for confirmation, which I need to address when trying to do backups automatically
• Have tried others but needed a working copy on a new SD card, so this is the solution I'm going with
• If you want a file you probably want to use dd. I'm aware of the space issue. I quickly looked up other tools: partclone and fsarchiver seem to address the free space issue, but I never tried them so I cannot speak to that.

Unexpected Keyboard

I think buying a Pixel phone second hand solves this issue and reduces a little e-waste at the same time.

What are you using to download them as Markdown?

The movie wasn't living up to the book though...