Let’s imagine, you have a node with /dev/sda drive that consists of a boot partition, root partition and swap and /dev/sd[b-c] drives that compose the volume group with LVM images of your VPSes.
In this case, it is necessary:

• Copy the directory /home/kvm with VPSes configs to another server.
• Deactivate the volume group with LVM images:
vgchange -an design VGNAME
Replace VGNAME with the actual Volume Group name
• Export the volume group. This prevents it from being accessed on the “old” host system and prepares it to be removed.
vgexport VGNAME
• Reinstall the server
During reinstallation make sure the disks the volume group consists of are intact
• Install SolusVM KVM Slave node and setup network bridge:
https://docs.solusvm.com/v1/installation-and-configuration/installing-slave/installing-kvm-slave/Installation%2Bof%2BKVM%2BSlave.html

https://docs.solusvm.com/v1/installation-and-configuration/installing-slave/installing-kvm-slave/Bridge%2Bconfiguration%2Bfor%2BKVM%2BSlave.html

• Change the slave node ID/Password using the solution from this article:
https://support.solus.io/hc/en-us/articles/360029017492-Cannot-connect-to-slave-node-in-SolusVM-Connection-Failed-Debug-Data-ERROR-4

1. Login to SolusVM admin panel
2. Copy ID Key from SolusVM at List Nodes > Edit Node Password
   
   
3. Connect to the affected slave node via SSH
4. Create a backup of original /usr/local/solusvm/data/solusvm.conf file on the affected slave node:

   # cp -a /usr/local/solusvm/data/solusvm.conf{,.bkp}

5. Paste this ID Key to /usr/local/solusvm/data/solusvm.conf replacing the original one:

   # cat /usr/local/solusvm/data/solusvm.conf
   3BfBmcKgBcGiliVbY4LtY0udlmbxFD62SqOoCR61gMjeTqMxST:wXEonrxjek7fTbVTxOHVTPqY7wUjgZyLKRb37XkhhFNTaSybGP

6. Copy the PASSWORD (second part of /usr/local/solusvm/data/solusvm.conf file) and Paste PASSWORD to ID Password field at List Nodes > Edit Node Password:
   

• Restore the directory /home/kvm
• Import the volume groupIf importing on an LVM 2 system, run:

lvmdevices --adddev /dev/md124 before pvscan

vgimport VGNAME
If importing on an LVM 1 system, add the PVs that need to be imported:
vgimport VGNAME PVNAME1 PVNAME2
where PVNAME1 and PVNAME2 are the corresponding Physical volumes’ names
• Activate the volume group:
vgchange -ay VGNAME

Please see this for reference:
https://access.redhat.com/solutions/4123