Hi all,
I'm using Proxmox for six months now for my own VPS production and testing environment and enjoying it very much!
Since I had some old VPS's on HyperVM I recently decided to move those as well
All went fine (making ssh-key between old VPS server and new one) and then from the command line used the vzmigrate command.
The only problem is that the newly created VPS's are created in the large LV:
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
while to moved ones are now residing in the (much smaller) root LV:
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/180"
Since I moved one large VPS over, it's now bogging when making backup's since the partition is getting to small. I could perhaps fix this by resizing the LV, but moving those VPS's over to /var/lib/vz would be a better solution, since this was the intended location on Proxmox.
Anyone a suggestion how I should approach this without much downtime?
Cheers,
I'm using Proxmox for six months now for my own VPS production and testing environment and enjoying it very much!
Since I had some old VPS's on HyperVM I recently decided to move those as well
All went fine (making ssh-key between old VPS server and new one) and then from the command line used the vzmigrate command.
The only problem is that the newly created VPS's are created in the large LV:
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
while to moved ones are now residing in the (much smaller) root LV:
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/vz/private/180"
Since I moved one large VPS over, it's now bogging when making backup's since the partition is getting to small. I could perhaps fix this by resizing the LV, but moving those VPS's over to /var/lib/vz would be a better solution, since this was the intended location on Proxmox.
Anyone a suggestion how I should approach this without much downtime?
Cheers,