On Fri, 07 Sep 2018 13:00:17 +1000 "Michael D. Setzer II"
A number of good replies already, but just to add a note:
I've been the maintainer of the g4l disk imaging project since 2004, and it
basically uses dd for most operations.
I'm replying, not only OT to the ML but OT to this thread, because I've
just experimented g4l for backing up several windows systems (for Linux
boxes I run my own rsync-based scripts) and wanted to share that. The
process was pretty simple: shutting them down, booting from the USB storage
where g4l resides (either legacy or UEFI mode), configured the process
to send to a FTP server over the LAN. The process is reliable and
pretty fast, approx 2h for each 500GB disk (RAW copy mode), I though
it would be longer. The only thing I added is generating a .md5 file on
storage, in case, that should be done by g4l IMO.
My former experience were using a similar approach but with clonezilla
(in that time, no FTP sending but local storage or at least I couldn't
find it, and a slower process, less simple at least, partition by
partition and a user interface that is prone to user error), which led
me to back my Windows systems up way less often.
IOW, Michael, thanks for providing g4l!