Oh yes, I tried testing my Clonezilla restore on an older laptop, but after logging in, the keyboard and trackpad stopped working. I wondered if that was a hardware incompatibility problem, since the keyboard and trackpad worked fine at the greeter screen. 🤷
jbrains
Indeed, I have a lot of redundancy for critical documents, including a restic backup to Blackblaze and many many git repositories. What I don't have is the "Get back to work quickly when the internal drive dies" that SuperDuper gave me on my Mac. That's the missing piece I'd like.
And, as you noticed, since I was struggling with testing the Clonezilla backup, I couldn't possibly trust it. Now, at least, I have a plan.
And yes, I have onsite backups, offsite backups, and a succession plan.
That depends on whom you ask. 🤷 And how eager are you to live in a remote community?
The word they meant to use is "carelessly". We would also have accepted "inattentively".
Thank you. Of the folks who have engaged me over the past few years trying to find an adequate backup system, you're the first to tell me that I'm indeed not missing anything and that this cannot be made to work the way I'm expecting. I find that comforting.
Now I have a way to move forward: to back up a 1 TB drive, I can partition a 2 TB drive in half, back up to an image on one, restore that image to the other, chroot, and check that that worked.
Wasteful, but workable.
Thank you.
Shithole country.
KDE FTW.
People like work. People rarely get to work at job. Result? People hate job.
Gib better job!
Threaten the guillotines more aggressively. That's what worked previously.
First, thanks. And no, I haven't tried their support yet, because the situation hadn't become urgent enough yet.
I can restore an image, but that doesn't let me test, unless I restore to yet another external drive with enough space, then chroot to it, I guess. I didn't have another 1 TB drive at hand to try.
I didn't try to boot to the clone, because I read a warning about booting with two different connected drives having the same UUID. I wouldn't use my daily drive laptop to try that out in case something serious went wrong. All I found online were vague warnings and I wasn't prepared to ignore them. Also, I know software, and I could imagine some potentially serious errors due to optimistic assumptions in software about the uniqueness of drive UUIDs.
I can't disable my laptop's internal drive through BIOS and I'm not prepared to open the machine to physically disconnect the drive.
That's where I am now. It looks like the best option to test would be to backup to an image on USB drive A, then restore to USB drive B, then boot to a live installation and chroot. I mean... OK, but that's not what I hoped for from a so-called bootable backup.
Am I missing something obvious? Am I making a clearly invalid assumption?
So that's what they look like inside!