I am running a Pi 4 with the Raspberry Pi 64-bit Bookworm GUI OS image in a Generac generator using Genmon from github to graphically monitor the generator status. The Pi is headless and I manage it through terminal sessions and with RealVNC. I'm new to Linux and the Pi; as I work through this I have discovered that on occasion I have had to go to a backup SD card because of an app destroying what I've done so far, finger-checks, or simply not following app install directions carefully. I have several 64GB micro-SD cards and take full clone backups often along the way, documenting the point when each clone was made.
To date, to clone the OS I have taken the running OS out of the generator Pi, booted it in a second Pi 4 in the house, and used the GUI SD Card Copier utility to make the clone. This is simple, quick, and painless and beats other backup methods I have found so far. But to make the clone using the second Pi I have to shut down the generator Pi and would rather not to that. I haven't yet used dd to clone directly via the terminal, and just got RealVNC running on the Genmon Pi so haven't used the GUI utility there.
I have read that dd will not always produce a reliable clone, as doing this from a running OS may introduce inconsistencies, with code on the SD card changing while the system is running. But I also have read that the Debian Pi OS is written in such a fashion that very little change is made on the SD card while running in order to prolong the life of the SD card.
My questions are:
- Is this unreliable SD clone concern real when using dd in my environment?
- If producing a reliable SD clone is a concern, does this concern exist also for the GUI SD Card Copier, or have the developers put code into that utility to ensure that the clone is an exact copy at some point-in-time, much like backup applications on some other platforms? I am only interested in producing SD clones, not images that need to be restored.
- Any suggestions about what apps might be available to ensure this?
Many thanks!