[SOLVED] Latest ProxMox & previous version VM's?

[GazdaJezda]

Hi!

I have a problem with server's NVME boot disc. It will die soon, so if I install a latest version of ProxMox (8.2) on a new disc on that server, will there be any problems importing my current VM's (from currently running latest PVE 6.4) into it? A new install because it seems that disk cloning was not successfull and now this seems the only option for me to build my PVE box back.

At the moment I have a (power down) server with:

• damaged NVME disc with PVE 6.4.xx (latest / final 6.4 patches) and 8% of available spare sectors.
• 4 discs with ZFS pool (raidz1 pool, 1 disc redundancy) - contains my VM's
• external disc (USB connected), containing weekly VM's backup (latest 12 weeks)
• backup of PVE system folders: /etc, /var - if others are needed, I can probably still manage to copy it.

Question:
If I put new NVME disc into server and install PVE 8.2 on it, will I be able to add my current VM's (from PVE 6.4) into it and start it?

I find this thread:

• https://forum.proxmox.com/threads/add-ssd-zfs-pool-with-vms-to-new-proxmox-server.116569/

but I do not know if it's still usable for my case? If answer is no, I can still install PVE 7.x (instead of 8.2). I would like to get my VM's up & running asap. Thanks for any useful answer, really.

Regards.

 

[Kingneutron]

https://github.com/kneutron/ansitest/tree/master/proxmox

Setup and run the bkpcrit script, should save your VM configs. Run it frequently after you're back online.

I would start with Proxmox 7 and hopefully everything should restore. Once you get everything up and running, do a bare-metal backup and then try the upgrade to 8. I'm not sure about a 2-major-versions direct backwards compatibility.

https://www.youtube.com/watch?v=g9J-mmoCLTs

 

[Eric Faden]

@Kingneutron Is there instructions somewhere for installing your scripts?

 

[Kingneutron]

Go to the base URL, click the green Code button and download the .zip

https://github.com/kneutron/ansitest/tree/master

mkdir -pv /root/bin/boojum

put the BKPDEST.mrg in that directory, the rest can run from /root/bin if you want. Install midnight commander if you want an easy way to copy/move things around (it's also the safest way to recursively delete directories)

If /root/bin is not already in your PATH ( echo $PATH # to check ) you will need to add something like this to /root/.bashrc

export PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/local/games:/usr/games:/root/bin:/root/bin/boojum:/usr/X11R6/bin:/usr/NX/bin:

and then source ~/.bashrc # for it to take effect in the current shell

For good measure, chmod -R 750 /root/bin # make scripts executable

Then you want to edit /root/bin/boojum/BKPDEST.mrg and define the target for your backups. This will probably also need to be a mountpoint defined in /etc/fstab, unless you're using sshfs. The BKPDEST will attempt to mount it if it isn't already active.

This target mountpoint CANNOT be root on the same system (or preferably, not even a separate partition on the same root disk) - needs to be separate media or NAS. (If your root disk dies, you still want access to the backup.)