Hi everyone!

I now have 4 computers running Linux, each with an almost perfectly set up distro (which took days to perfect) and would want to create backups so that I can move and restore these between all of my computers.

Here is a list of my computers:

Surface Go 1 128gb SSD 8gb of Ram running Fedora Silverblue

MacBook Pro 2012 (upgraded with 512gb SSD and 16gb of Ram) running Pop!_OS

NUC7i3DNB 128gb SSD 8gb of Ram running LibreELEC

Steam Deck LCD 256 SSD 16gb of Ram running Steam OS

I was planning on using Clonezilla to create backups of these, store them somewhere (kDrive and external hard drive) and be able to restore these between each of these (and my future) computers if needed.

I’ve succesfully used Clonezilla in the past, but I’ve also encountered a dead end issue when trying to restore my Surface Go 1 backup on an old Acer (probably 5737Z) I had lying around. I don’t remember what the problem was, but something related to UEFI and EFI legacy stuff I think…

So, as all these computers are quite different and not all of them so Linux friendly, I wanted to know if you think I’ll encounter issues when trying to move installs between them or not.

In order to save space, I’d probably shrink every partition so that it’s the same size as the data it contains and then extend it again once restored on another computer.

Thanks in advance for your help!

Edit: Thanks for your help. In the end, I think I’ll keep building installation tutorials for myselt to be able to reproduce my distros and might one day try NixOs on one of my computers

  • fozid@lem.radiantfig.fyiEnglish
    14·
    2 days ago

    For me that would be a waste of time. Just because my setup seems perfect today, tomorrow I might decide to make changes to accommodate a new task. My pc’s are living breathing machines that are always a day or 2 away from a slight tweak.

    When I move to a new machine, I rarely want to replicate another machine I have as then I would have 2 machines setup for the same tasks. Each machine serves a different purpose so needs a different setup.

    If I am replacing a machine, then I would transfer the physical disk itself. Only use clonezilla type tools for replacing a disk, as in replacing the sata SSD holding root with a new fast nvme.

    It’s easy to transfer config files from one machine to another if you want to replicate some specific setups.

    • unfortunate_ferret@piefed.caEnglish
      2·
      2 days ago

      What do you do when you need to restore from failure, for one of those specific tasks? Just build from scratch every time?

      • fozid@lem.radiantfig.fyiEnglish
        22·
        2 days ago

        What sort of failure? A harddrive failure? I have never had a disk completely fail where every bit of data is unreadable.

          • fozid@lem.radiantfig.fyiEnglish
            11·
            23 hours ago

            good response 👍 bad questioning though 👎 i have a nas, with a raid1 array split out with lvm for separate partitions and users on my server, holding 2x2tb ssd’s. This backs up every night to 2x8tb HDD’s. I have a script that i invoke on my machines manually, that runs rsync on important data, and a backup to the nas raid1 array, overwriting the previous invocation. the HDD’s hold out of sync versions running back to 2 months, which i can dip into any time to recover something. so if something does fail, i wont lose anything. I dont hold offsite backups, so if a nuke lands on my house, i will lose everything. Im comfortable with that level of risk, but i know some people arent. however the op wasnt specifically asking about data backup, they were asking about replication, and how to preserve the initial install and setup to be able to revert and replicate. there are better ways to achieve this than just cloning the disk. Build your own actual distro is the best solution and burn it to a usb as a live disk that is easily installed. or just save a list of packages and configs. cloning a disk is a huge amount of out of date data.