Selfhosted

60320 readers

478 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Suggestions for migrating from Windows Server to Proxmox (startrek.website)

submitted 2 months ago* (last edited 2 months ago) by USSEthernet@startrek.website to c/selfhosted@lemmy.world

11 comments fedilink hide all child comments

I was wondering if I could get some suggestions from the community about the best way to go about migrating from Windows Server on my homelab host to Proxmox.

Background: Currently running Server 2022 Datacenter on my host because that's what I was familiar with. Using Hyper-V to manage multiple VMs like HomeAssistant and TrueNAS among other things. I have multiple container apps running within TrueNAS. There's an HBA passed through Hyper-V to the TrueNAS VM that has all of my HDDs connected to it. I'm just looking to migrate away from anything Microsoft/Windows.

Way Forward: The only procedure that I could come up with in my head was moving everything off of the NAS to my personal PC if I have the space, or maybe multiple PCs in the house. Back up all of my configs. Install Proxmox on the host, build out the VMs again, then restore the configs and just hope everything works the same. Or, just backup my configs build the new VMs on proxmox, restore and hope the new TrueNAS VM sees the data on the HDDs? I don't know if that would work.

If someone has a better idea, I'd like to hear it. Is there any way to dual boot Proxmox on the host maybe and slowly migrate things 1 by 1? Can you convert the VMs from Hyper-V before I install Proxmox?

Thanks everyone!

you are viewing a single comment's thread
view the rest of the comments

[–] USSEthernet@startrek.website 1 points 2 months ago (1 children)

You should be able to migrate most or all of your existing Hyper-V VMs to Proxmox, which would be relatively straight forward. My recommendation would be backing up everything to your TrueNAS (that has the dedicated HBA) then you can wipe your Windows boot drive and install Proxmox. Then you could start by migrating your TrueNAS VM over and passing it's HBA back to it.

Yeah I thought about this being the easiest way to do it. I just wasn't sure if TrueNAS would come back up and just recognize the disks and start working. I have backups of everything and I've tested restoral. I would prefer to not have to go the backup restoral route as it's more a scorched earth option. My other VMs I'm not really concerned about, it was mainly the NAS.

I don't really have any experience with PVE, but I want to learn. I've been learning about docker containers more recently, I like learning new tech so I'm all for it. My main PC has been running Linux for about 6 months now and I'm just trying to get away from Microsoft in general. Thanks for the info.

[–] kieron115@startrek.website 2 points 2 months ago* (last edited 2 months ago)

I haven't used TrueNAS but from what I'm reading it has an option to import existing pools. If you have spare SSD I would yank your windows drive out of the system and try installing Proxmox on the spare drive first. There's a truenas installation script on that community page I linked in my other post, it says to follow this discussion after it runs. That might be a good starting point.