Migrating to new server, best way to do it?

[benpoepen]

I'm hitting hardware limits on my current proxmox server and plans to migrate it to a new server with new hardware. Since we're at it, I thought I might as well install the newest version.

so my idea is to install newest proxmox on new server, then move over the vm's.

but since my VM's together is about 1.7TB, a backup and restore backing up will take a long time. (yes, i have no backups yet)
I was thinking, backup to a external ssd (1TB) and restore from there to new server
is it possible to just pop out the nvme ssd containing the VM's disk and connect it to new server and expect it to work? (other option: clone the nvme instead of moving it)

 

[Dunuin]

is it possible to just pop out the nvme ssd containing the VM's disk and connect it to new server and expect it to work? (other option: clone the nvme instead of moving it)

Not with just the NVMe alone. You also need a lot of config files like the ones in "/etc/pve/firewall", "/etc/pve/lxc", "/etc/pve/qemu-server" and so on from your old root filesystem. And you still want backups in case you screw something up (and disks will fail sooner or later...you should always have backups of everything...even when using raid).

 

[spirit]

for proxmox itself,

if you reinstall with same hostname, you just need to copy /var/lib/pve-cluster/config.db to get the full /etc/pve configuration. (you just need to stop pve-cluster.service before copy)

 

[sansans]

Used the above reference and used something like the steps listed below. Premise in a cluster setting, moved from bigger hard disk (4TB) to smaller NVME drive (1TB).

1. Install proxmox with the same hostname and IP on new machine new drive
2. Stop systemctl stop both corosync and pve-cluster
# systemctl stop corosync
# systemctl stop pve-cluster
3. Copy /etc/corosync from to new
4. Copy /var/lib/pve-cluster/config.db to new
5. Start corosync and pve-cluster
6. Update certs and try restart.
# pvecm updatecerts -F
# systemctl restart pvedaemon pveproxy

Of course do check other stuff like debian repo , time sync (chrony) are all good as well.

 

[jaxjexjox]

Used the above reference and used something like the steps listed below. Premise in a cluster setting, moved from bigger hard disk (4TB) to smaller NVME drive (1TB).

1. Install proxmox with the same hostname and IP on new machine new drive
2. Stop systemctl stop both corosync and pve-cluster
# systemctl stop corosync
# systemctl stop pve-cluster
3. Copy /etc/corosync from to new
4. Copy /var/lib/pve-cluster/config.db to new
5. Start corosync and pve-cluster
6. Update certs and try restart.
# pvecm updatecerts -F
# systemctl restart pvedaemon pveproxy

Of course do check other stuff like debian repo , time sync (chrony) are all good as well.

Hello,

Please don't take this the wrong way, at all.
This solution feels like the 'homelab' solution for someone at home to do this, fiddling with files on the system and what have you.

I am curious what the solution might be for 'big business' or at least more professionally?
I guess what I'm asking, is there some kind of official migrate tool, from one host to another?

I was going to join my new server to my old one in a cluster, from there I wasn't really sure what to do, but I am curious if there's a 'less fiddly' solution than the one you've provided.

Again, no offense intended, looks helpful and if that's the only way, so be it!

Thank you.
(just to be clear, I am indeed a homelab person myself)