this post was submitted on 16 Dec 2025
60 points (94.1% liked)

Selfhosted

60664 readers
654 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I am working on setting up a home server but I want it to be reproducible if I need to make large changes, switch out hardware, or restore from a failure. What do you use to handle this?

you are viewing a single comment's thread
view the rest of the comments
[–] irmadlad@lemmy.world 1 points 7 months ago (1 children)

I use snapshots, once a month an image is made of the entire drive, and I have Duplicati that backs up to cloud. Whatever choice you make tho, remember 3,2,1, and backups are useless unless tested on a regular basis. The test portion always gives me anxiety.

[–] MonkeMischief@lemmy.today 10 points 7 months ago (1 children)

I'd really like to know if there's any practical guide on testing backups without requiring like, a crapton of backup-testing-only drives or something to keep from overwriting your current data.

Like I totally understand it in principle just not how it's done. Especially on humble "I just wanna back up my stuff not replicate enterprise infrastructure" setups.

[–] irmadlad@lemmy.world 2 points 7 months ago* (last edited 7 months ago)

You can use qemu utilities to convert your Linux disk image to VDI which you can then import into VM Workstation or Virtualbox:

qemu-img convert -f qcow2 -O vdi your-image.qcow2 your-image.vdi

One thing you might run into is that Ubuntu server images often use VirtIO drivers, So you may have to make adjustments for that. Or you may run into the need for other drivers that VM Workstation or VirtualBox don't provide.

https://documentation.ubuntu.com/server/how-to/virtualisation/qemu/#qemu

https://systemadministration.net/converting-virtual-disk-images-qemu-img/

ETA: There is also StarWind V2V Converter