Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.

Control time of cutover in migration

I'm testing platespin to see if it will work for a fairly important
migration job and am a bit confused about something.

I'm migrating from Citrix XenServer to Hyper-V 2012. I cannot get
platespin to understand Hyper-V 2012 so I have booted into the ISO and
sucessfully migrated a machine, however, the machine goes offline and
"reboots" on the destination end.

This is fine and I can live with this, however, there seems to be no way
to control WHEN that happens, i.e. it just happens when everything is
copied over. Since this is a very large VM (800-odd gig) and i only have
a 1GB link between the machines, this could end up being in the middle
of the day.

Is there a way to pre-stage everything, have the destination VM sitting
and waiting, then hit a button on demand (which will be done out of
hours) and have any changes that have been made since the initial copy
(and/or have the changes constantly replicating) copied over and then do
the shutdown source/boot up destination process?

Without this the whole process seems fairly useless.. I'm sure I'm
missing something but i cant seem to find what i want in the help


mattbsyd's Profile: https://forums.netiq.com/member.php?userid=5399
View this thread: https://forums.netiq.com/showthread.php?t=48127

1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Control time of cutover in migration

Hi Mattbsyd,

I would like to start by reminding you to check the documentation first
as it lists Hyper-V and Hyper-V R2 as supported targets but Hyper-V 2012
is not yet listed as it is not yet supported.

As for the versions of Hyper-V we do support already, we do not support
discovering them as virtual targets but require you to make the VM
yourself and boot it to ISO to fake a physical target which is what you
have already done.

As for the reboot, there are several possible reasons for this but I
would need more info to determine why. Firstly, WinPE itself has a
built in feature of the kernel which hard reboots the WinPE OS after a
certain amount of time to keep people from using it as a permanent OS.
So if using the default WinPE of ours (WinPE 1.5) then the ISO will
reboot itself every 24 hours of being online. If the target is
rebooting during the migration then this is usually the cause.

If the data has already been migrated over and the migration is
configuring the OS then the target VM should get rebooted automatically
several times by our product which leaves a Windows Service behind on
the target to handle the configuration automatically and it reboots at
least 3 times at the end of every migration in order to apply some
settings and depending on the OS changes you selected when setting up
the migration, the service may need to reboot ever more then 3 times.


icroitoru's Profile: https://forums.netiq.com/member.php?userid=2152
View this thread: https://forums.netiq.com/showthread.php?t=48127

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.