My dear lemmings,

I discovered Clonezilla a while ago and it still is my main tool to backup and restore the partitions I care about on my computers.

I cannot help but wonder if there are now better, more efficient alternatives or is it still a solid choice? There’s nothing wrong with it, I’m just curious about others’ practices and habits — and if there was newer tools or solutions available.

Thank you for your feedback, and keep your drives safe!

  • Toribor@corndog.social
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    9 months ago

    Generally I just don’t take clones of disk partitions anymore. They tend to take up too much disk space to keep more than one or two backups and typically require the disk to be unmounted which means it’s a mostly manual process. That all but guarantees that any backup I take will be out of date when I need it most.

    Instead I’ve found it better to take regular automated file level backups and automate the way I configure my environment so that I can quickly restore and rebuild if something goes wrong.

    If I just want to be able to quickly revert a drive to a previous state or have easy point-in-time restore I manage the disk with ZFS. ZFS has a snapshotting feature which is great for this sort of thing and you can even restore snapshots to another zfs pool the same way you might restore a partition to another disk but without all the hassle of resizing things.

  • MangoPenguin@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    9 months ago

    It’s difficult to use with some odd defaults as I remember, and you have to boot into it which is annoying.

    Rescuezilla seems like a good open source option, but you do still have to boot into it.

    My go-to is the free Veeam Endpoint, as it just installs on the system and does full system images without needing to reboot. I’m not sure if there is a good easy to use open source equivalent to it, so far I have not found one.

    • Godort@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      I also use Veeam at home for this. It’s not FOSS, but it is still free, and works really well.

      • Nix@merv.news
        link
        fedilink
        English
        arrow-up
        3
        ·
        9 months ago

        I hate that it requires a phone to download unless you already have a download link

      • Nix@merv.news
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 months ago

        I hate that it requires a phone to download unless you already have a download link

  • loie@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    9 months ago

    Second for Rescuezilla, it’s a Clonezilla front end with sane defaults you’d probably pick anyways.

  • MangoKangaroo@beehaw.org
    link
    fedilink
    arrow-up
    8
    ·
    9 months ago

    I still use Clonezilla to back up devices before performing reinstalls/major updates (when Timeshift isn’t practical). No issues so far backing up and restoring both Windows and Linux partitions/drives.

    • strax@kbin.social
      link
      fedilink
      arrow-up
      4
      ·
      9 months ago

      yeah, partclone is the tool that clonezilla uses under the hood. i find that using partclone directly is easier.

  • PenguinCoder@beehaw.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 months ago

    Clonezilla has its place, but not as a main backup and restoration tool. I personally don’t see it as a backup tool, especially that it operates at partition level for such. What you want is you base install system and file level backups for your data (/home/) etc. For the file level backups, use something like restic. Backup what you need to go from a fresh install to a system with your data back on it. Packages can be reinstalled.

    Restic is my primary backup for all my devices. If I need something more than fresh iso -> my data system, I use packer.

    • yo_scottie_oh@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      I noticed for file level backups you mentioned something other than rsync. Any particular reason why you landed on restic instead?

  • BCsven@lemmy.ca
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    Clonezilla or dd. if you are on GNOME you can use gnome disks and it has a create diak image, restore disk image option, if you want an img file

  • Terces@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    Clonezilla is the tool I use after all else has failed. I agree that it is difficult to use, but it can do things others can’t. I saved quite a few of my drives with this thing. So while I try to avoid having to use it, it still belongs in my toolkit.

  • utopiah@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    Others have mentioned rsync and I’d like to suggest on top of rdiff-backup but it’s indeed for files, not partitions or disks. That being said IMHO if you are not managing data-centers and thus swapping entire physical disks by the bucket, you probably don’t want to actually care for disks themselves.

    If you genuinely have to frequently change not just data but entire systems, maybe looking at nix or cloud-init could help.

  • makeasnek@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    3
    ·
    edit-2
    9 months ago

    The fact that Linux lacks a decent system-level backup tool with a GUI is kind of a mind boggler for me. The best one I’ve found which gets close to this is timeshift. File-level backups can’t restore your whole system state and users shouldn’t be expected to remember or manually export their package lists and god knows what else. I have subsisted on file-only backups but it’s really not great as a solution. Disks fail, and when they do, you inevitably have to reinstall the entire OS. It’s a mess. RAID1 could theoretically prevent this, but no distro makes it easy to boot from a RAID1 setup.

    Backing up the entire filesystem is not a technically complex thing, there are plenty of command-line tools to do this and some filesystems even support this concept via snapshots etc. But this has yet to be put into a useful practice for end users.

  • BaldProphet@kbin.social
    link
    fedilink
    arrow-up
    5
    arrow-down
    6
    ·
    edit-2
    9 months ago

    I have never gotten Clonezilla to work. I don’t want to call it obsolete, but… it certainly isn’t intuitive, and in 2024 I expect even open source software as widely known as Clonezilla to have a straightforward interface.

    For simple data backups, I use Kopia.

    EDIT: Apparently there’s a GUI for Clonezilla called Rescuezilla. I’ll have to give it a try sometime.

    • KnightontheSun@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      9 months ago

      Somewhat curious how CZ has never worked for you. I’ve used it for years and any failures it has had were fixed with tweaking some of the options. I love the tool myself, but I have also never heard of Rescuezilla so thanks for that. I think I’ll give that a go next time.

      • BaldProphet@kbin.social
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        9 months ago

        It’s been a while since I tried it, so I don’t recall exactly what didn’t work the last time. I think it may have been driver related.

        I’m definitely going to give it another go one of these days.

    • rtxn@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      It’s definitely a beast at the best of times, but the scriptability is great.

      Just a few weeks ago I used it to deploy a custom Win10 image to several hundred computers in a very heterogenous environment in lite-server mode (basically PXE with extra steps). It took three of us sysadmins several days to figure out why it wasn’t working, several more to write a script that could handle every scenario. Some computers had SATA SSDs, some NVMe, some both, some SSD+HDD, the block device names (sda, sdb…) were never consistent, and some reported its HDDs to sysfs as SSDs. I ended up dissecting the ISO and came up with a solution that only required a single Enter key to start and did everything else automatically.