six demon bag
Wind, fire, all that kind of thing!
If you have a live migration fail with an error like this:
Live migration of 'Virtual Machine VM01' failed.
Virtual machine migration operation for 'scvmm_instance' failed at migration source 'Hypervisor01'. (Virtual machine ID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'Hypervisor02': The specified target is unknown or unreachable (0x80090303).
The Virtual Machine Management Service failed to authenticate the connection for a Virtual Machine migration at the source host: The specified target is unknown or unreachable (0x80090303).
check that both hypervisors have the required SPNs registered.
Posted 17:22 [permalink]
Share migration is a common (if not integral) part of a file server migration. If you just move the shares from one host to another host the process is pretty straightforward as described in MSKB article 125996:
[HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares]on the old file server to a file:
reg export HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares shares.reg
Copy the file to the new file server and import it:
reg import shares.reg
net stop server && net start server
Posted 21:09 [permalink]
I've been working on a project where I needed to migrate (clone actually, in order to maintain a fallback scenario) virtual machines from external (standalone) Hyper-V hosts to a Hyper-V cluster. The external hypervisors were not members of the same domain as the cluster nodes. The networks were separated by a firewall. A trust relationship between the domains was not desired.
System Center Virtual Machine Manager 2012 (SCVMM) supports this scenario, but there are several steps that must be performed to prepare for the migration.
Posted 20:03 [permalink]