Move PVE from old to new hardware

[Nezdeshniy]

Hello everybody!

I have working stand alone proxmox server:

PVE Manager version pve-manager/2.2-32/3089a616
Kernel version Linux 2.6.32-16-pve #1 SMP Fri Nov 9 11:42:51 CET 2012
MB ASUS P8H67-M PRO
CPU i72600s(2.8Ghz)
RAM 32Gb
Adaptec 6405E RAID10(2Tb) for PVE + RAID 10(2Tb) for backup's
(UPTIME 196 days =()


Now i need change my MB and CPU to ASUS P8Z77 WS + i72600k(4.5Ghz)...i need high clock speed.

How i can do this ? I have only 45-90 min for work.
Should i update proxmox to 3.x first ? I realy nn new version...

I test in lab: i install pve 3.0 on 1st server and move raid to new one 2nd server with new mb and new NIC!!!
and the network has stopped working... so again now to move pve from one mb to anothe new mb
if mb are not the same and pve normal workind on both mb, and should i update pve kernel fist?

THX =)

P.S. i need decision in a week.

 

[kotakomputer]

It's depending on 3 factors: how many VM, how big you VM and your 45/90 minutes time limit!

In my experience, it wasn't easier to change H/W with same OS installed, you will experience to many errors/issues, so the best is install new Proxmox into new server, then backup and restore each VMs. But if your VM very2 big it may take very2 long time backup (if possible the best was Stopped VM during backup) so you may setup new VM and only backup data inside VM.

 

[udo]

Hello everybody!

I have working stand alone proxmox server:

PVE Manager version pve-manager/2.2-32/3089a616
Kernel version Linux 2.6.32-16-pve #1 SMP Fri Nov 9 11:42:51 CET 2012
MB ASUS P8H67-M PRO
CPU i72600s(2.8Ghz)
RAM 32Gb
Adaptec 6405E RAID10(2Tb) for PVE + RAID 10(2Tb) for backup's
(UPTIME 196 days =()


Now i need change my MB and CPU to ASUS P8Z77 WS + i72600k(4.5Ghz)...i need high clock speed.

How i can do this ? I have only 45-90 min for work.
Should i update proxmox to 3.x first ? I realy nn new version...

I test in lab: i install pve 3.0 on 1st server and move raid to new one 2nd server with new mb and new NIC!!!
and the network has stopped working...

Hi,
this depends due the new onboard NIC - the old one was eth0 and the new one is eth1 (or eth2...).
Simply edit /etc/udev/rules.d/70-persistent-net.rules (remove the old nic-entry and change the new one to eth0, or remove all entrys), reboot and your network is up again!

so again now to move pve from one mb to anothe new mb
if mb are not the same and pve normal workind on both mb, and should i update pve kernel fist?

THX =)

P.S. i need decision in a week.

an update is an good choice, but I assume it's will be hard to be finish in 90min with all steps (changing motherboards and so on).
Depends on you storage-system (lvm?) you can do something like this:

1. create an backup of all VMs to your backup-raid
2. connect single disks to your old MB
3. restart pve-host (to see the new disks) - perhaps not nessesary
4. copy boot-blk + /boot to the first single disk (with dd).
5. expand your vg (pve + ?) with partitions from the new disks
6. pvmove the raid-volumes (to the single disks) - take a time (but all VMs are online in this time)
7. vgreduce the raid-pv from the VGs, pvremove the raid-partitions
8. unmount your backup-fs and remove the entry from /etc/fstab

only during the reboot your VMs are up an running.
Now you should be able to shutdown the pve-host, use the old MB with the single disks (on another chassis) and start without the raid-controller. The old system should (if you have copy MBR and so on right - and use the right bios-settings about boot-disks) boot and you can build your new MB with the raid-controller (and the raid-disks) - if something go wrong, simply put the raid-controller back, boot and find the issue.

Now you have time enough to install the new system (new MB, old raidcontroller) - you only need of course an new IP for the host.
If the new system ist up and running, you can "migrate" VM for VM from the old host to the new one - mount the backup-storage from the new pve-host on the old host, shutdown a VM, backup and restore this VM on the new host.

Perhaps this fit your timetable?

Disadvantage of this solution:
1. You should have knowledge about linux (but the good thing is, that you will learn a lot).
2. During migration you have less speed (single disks instead of raid-10).
3. During migration your VMs are not protected for an hdd-failure (but for that you have the backup on the backup-raid)

Udo