Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
articles:proxmox_upgrade_reinstall_migration_guide [2025-01-03 05:22] – created Tony | articles:proxmox_upgrade_reinstall_migration_guide [2025-01-03 05:38] (current) – Tony | ||
---|---|---|---|
Line 41: | Line 41: | ||
- IF YOU WILL BE RE-USING SSD'S, MAKE SURE YOU DD A BACKUP OF THEM! | - IF YOU WILL BE RE-USING SSD'S, MAKE SURE YOU DD A BACKUP OF THEM! | ||
- This one saved me and allowed me to repeat this procedure twice. | - This one saved me and allowed me to repeat this procedure twice. | ||
- | - | + | - Grab the important config files you will need from the old host |
+ | - / | ||
+ | - Ignore the keys and stuff, it'll cause pain and misery | ||
+ | - / | ||
+ | - If you rely on wireguard and want to be lazy and re-use old keys (not best security practice) | ||
+ | - / | ||
+ | - If you have non-standard mounts (I had an older btrfs HDD not in an zpool or lvm) | ||
+ | - / | ||
+ | - If you have custom NFS exports to go from PVE over to VMs (LXCs just bind mount) | ||
+ | - / | ||
+ | - If you have custom networking or VLAN setups | ||
+ | - ~/ | ||
+ | - Any special configs you have. | ||
+ | - Swap out the SSDs for the new ones, prepare proxmox installation media | ||
+ | - Install Proxmox fresh on your two new SSDs! | ||
+ | - You should be able to boot into your new system | ||
+ | - Bring your system roughly in line with your old setup. For me, this included | ||
+ | - Re-setup network interfaces and bridges the way they were | ||
+ | - Restore my fstab, wireguard, exports | ||
+ | - Wireguard needs apt install wireguard wireguard-tools | ||
+ | - systemctl enable wg-quick@wg0.service --now (start your tunnel at boot) | ||
+ | - Re-import your storage devices (eg: my VM/LXC SSDs, data HDDs) | ||
+ | - Make sure they are all detected under disks! | ||
+ | - For my data HDD zpool, this was two steps | ||
+ | - zpool import tonydata | ||
+ | - causes it to show up in node -> disks | ||
+ | - add it in the proxmox UI | ||
+ | - datacenter -> storage -> add new -> zfs | ||
+ | - For my LVM SSDs, this was 1 step as they were already listed under disks | ||
+ | - add it in proxmox UI | ||
+ | - datacenter -> storage -> add new -> lvm thin | ||
+ | - For my old BTRFS HDD, this was 3 steps | ||
+ | - Restore my old fstab (verifying UUID stayed the same) | ||
+ | - mount -a | ||
+ | - datacenter -> storage -> add new -> btrfs | ||
+ | - Remember to choose the types of storage this is (backup and data, not disk images in my case) | ||
+ | - Export my NFS pools (this one I forgot to do until my VM was mad) | ||
+ | - apt install nfs-kernel-server | ||
+ | - restore / | ||
+ | - exportfs -av | ||
+ | - Note, if you miss the above, it's probably not that bad, you'll be warned if things fail to start, it's iterative. | ||
+ | - Restore / | ||
+ | - You should now see your left bar populate back up with all your past lxc and VMs | ||
+ | - Try starting them, maybe they work, maybe they error, if so look back to above. | ||
+ | |||
+ | |||
+ | That was it. Didn't end up using any of my backups from the backup server (surprisingly). Only used losetup on my dd to grab config files for networks and such retroactively to remember names and addresses. | ||
Line 57: | Line 103: | ||
* Restoring the backup will yield errors with file overwrites | * Restoring the backup will yield errors with file overwrites | ||
* Allowing overwrites will break your configs in two and fail on /etc/pve | * Allowing overwrites will break your configs in two and fail on /etc/pve | ||
- | * NOTE: proxmox-backup-client doesn' | + | * NOTE: proxmox-backup-client doesn' |
* PROXMOX BACKUP SERVER IS A RED HERRING!! | * PROXMOX BACKUP SERVER IS A RED HERRING!! | ||
* In fact, if you don't need to back up and restore VMs, and you've taken a DD of your old SSD, you don't need it. | * In fact, if you don't need to back up and restore VMs, and you've taken a DD of your old SSD, you don't need it. | ||
- | * If it very useful | + | * it is excellent software |
+ | * If it's not obvious, if you are using drive letters, like /dev/sda, sdb, YOU NEED TO STOP. | ||
+ | * Please just use UUIDs, or heck even labels. After you reinstall, things WILL be shifting!! | ||
+ | |||
+ | |||
+ | In fact, let me do a whole segment on this | ||
+ | |||
+ | ==== Proxmox backup server? ==== | ||
+ | |||
+ | There seems to be some confusion with how this works, as a backup server can be added in two ways. | ||
+ | |||
+ | - Datacenter -> Storage | ||
+ | - This can be used for backing up the LXC and VMs on your system. | ||
+ | - Note: VM and LXC items backed up this way will keep some config data without /etc/pve, specifically ram and cpu amounts | ||
+ | - This can not be used to backup PVE itself | ||
+ | - proxmox-backup-client | ||
+ | - This can be used to backup PVE. by default, backs up a partition of your choosing | ||
+ | - If you backup /, make sure you also include /etc/pve which is a fuse mount | ||
+ | - If you already DDed the drive, you can always losetup and mount the disk image instead of using pxar. | ||
+ | |||
+ | |||