22
Advice/poll on switching away from Ubuntu for my VM host. (lemmy.procrastinati.org)
submitted 1 year ago by SeeJayEmm@lemmy.procrastinati.org to c/selfhosted@lemmy.world
30 comments fedilink hide all child comments

First off, I know ultimately I'm the only person who can decide if it's worth it. But I was hoping for some input from your collective experience.

I have a server I built currently running Ubuntu 22.04. I'm using KVM/qemu to host VMs and have recently started exploring the exciting world of Docker, with a VM dedicated to Portainer. I manage the VMs with a mix of virt-manager via xRDP, cli tools, and (if I'm feeling extra lazy) Cockpit. Disks are spindles currently in software Raid 10 (md), and I use LVM to assign volumes to the KVM VMs. Backups are via a script I wrote to snapshot the LVM volume and back it up to B2 via restic.

It all works. Rather smoothly except when it doesn't 😀.

I've been planning an HD upgrade and was considering using that as an excuse to start over. My thoughts are to either install Debian and continue with my status quo, or to give Proxmox a try. I've been reading alot of positive comments about it here and I have longed for one unified web interface to manage my VMs.

My main concerns are:

  1. Backups. I want to be able to backup to B2 but from what I've read I don't see a way to do that. I don't mean backup to a local repository and then sync that to B2. I'm talking direct to B2.
  2. Performance. People rave about ZFS, but I have no experience. Will I get at least equivalent performance out of ZFS and how much RAM will that cost me? Do I even need ZFS or can I just continue to store VMs the way I do today?

Having never used Proxmox to compare I'm really on the fence about this one. I'd appreciate any input. Thanks.

you are viewing a single comment's thread
view the rest of the comments
[-] SeeJayEmm@lemmy.procrastinati.org 1 points 1 year ago

Proxmox wont make backups to B2 easier, but since it is basically a web interface and API for Debian and KVM/QEMU you might be able to use your current backup strategy with very little modification.

I found this which leads me to believe I may be able to pipe zfs send to restic to replicate my current disk backup strategy. Presumably I could fire up a VM and build a zfs storage pool in it to test that theory out.

As for ZFS, you can expect to use about a GB of RAM for each TB in a ZFS pool. I (only) run 2x 4TB drives in ZFS mirror and it results in about 4-5 GB of RAM overhead.

So if I were to put 4x4TB in a RAID10 equivalent pool I'd be looking at ~ 8GB not 16, whew.

For a homelab it’s a bit much, the learning experience is the biggest part. It’s an entire rabbit hole.

The rabbit hole is where all the fun is. Templating was something I never really got around to in my current setup. I do have an ansible playbook and set of roles that will take a brand new Ubuntu VM and configure it just how I like it.

Thanks for all the info. I'll be sure to check out your repo.

[-] modesto_hagney@lemmy.world 2 points 1 year ago

My zfs cache for 6x 4tb drives in raidz2 is about 10gb of ram.

[-] SeeJayEmm@lemmy.procrastinati.org 1 points 1 year ago

I found this which leads me to believe I may be able to pipe zfs send to restic to replicate my current disk backup strategy. Presumably I could fire up a VM and build a zfs storage pool in it to test that theory out.

Replying to myself but I think this is a square peg, round hole, situation.

If I'm starting over with proxmox I likely need to rethink my entire backup strategy.

this post was submitted on 17 Jul 2023
22 points (92.3% liked)

Selfhosted

39677 readers
319 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz