I have old server with usual disks and new server with two ssd which are
smaller size. I have /vz on one disk and /vz2 on another.
I want to live migrate CTs from the old server to specified partition on
the new server but I can't find how to do it. Does anybody know?
--
Best Regards,
Nick
On 9/11/2014 7:00 PM, Nick Knutov wrote:
I have old server with usual disks and new server with two ssd which are
smaller size. I have /vz on one disk and /vz2 on another.
I want to live migrate CTs from the old server to specified partition on
the new server but I can't find how to do it. Does
I'm not good enough with such openvz internals and was hoped there is
ready solution. I found https://openvz.org/Vzmigrate_filesystem_aware
but it is for older version of vzmigrate.
Yes, I tried symlink and
1) /vz2 - /vz2 as symlink on /vz and back
and I have changed private/root paths in CT
Like I said though, use a symlink per VE, not the entire vz2/vz
directory. Then you won't have to change anything in the config. Just
create a symlink for the virtual servers you want on the second SSD
prior to migrating.
mkdir /vz2/private/VEID
ln -s /vz2/private/VEID /vz/private/VEID
I did exactly so.
Migration to symlink is working. And CT is running ok after. But
private/root paths are rewritten after migration to /vz + for simfs with
billions small files running CT from symlink can be slower.
Migration from symlink is also working. With the same issues plus source
folder
Shouldn't be millions of small files with ploop. Should just be the
one: root.hdd. Where it is mounted shouldn't matter (VE_ROOT).
On 9/11/2014 9:57 PM, Nick Knutov wrote:
I did exactly so.
Migration to symlink is working. And CT is running ok after. But
private/root paths are rewritten
There are cases when simfs is better solution. We have such cases. Any
way, the other problems remain.
12.09.2014 8:56, Devon B. пишет:
Shouldn't be millions of small files with ploop. Should just be the
one: root.hdd. Where it is mounted shouldn't matter (VE_ROOT).
On 9/11/2014 9:57 PM,
