Migrate Virtual Machines From Server 2012 to Server 2012 R2 Clustered

Steps to migrate virtual machines from Server 2012 non-clustered to Server 2012 R2 clustered.

Prepare the migration

  1. At the source server, check the VM settings and the current network Virtual Switch name.

    A matching Virtual Switch name must exist on the destination server or you will get a nonsensical error message about not being able to connect to the destination server.
  2. As a temporary fix where the names do not match... 
    If both systems are production systems and you don't want to interfere with operations. Go to the destination server and create a new Virtual Switch and assign this to the internal network.

    This will be sufficient to get the migration working but you will need to swap the adaptor on completion.
  3. At the destination server, create the virtual machine folder in the final location on the clustered CSV volume that the machine will finish up in (only the root folder is needed).

Do the move

  1. At the source server commence a 'Move'.

    For the destination server, use any one of the physical hosts that are in the destination cluster.

    Select the clustered volume location you set up earlier, as the destination folder.
  2. Once the move is complete, (swap the network adaptor if you used a temporary internal network).
  3. Confirm network connectivity.

Import to the Cluster

  1. Now open Cluster Manager, and Select 'Configure Role' from the right-hand navigation.
  2. Click Next and select 'Virtual Machine'. From this screen you will be able to locate the machine you moved onto one of the hosts. Select the machine and complete the wizard to make it highly-available (clustered).
  3. Now complete your tidy up tasks - Virtual machine Additions, Guest Services for the new copy and paste between host and guest.

Please add feedback about your experiences.

Mark

Location: New Zealand

Comments

Post a Comment

Popular posts from this blog

Server Manager Refresh completed with one or more warning

The system cannot access one or more event logs because of insufficient rights The Problem: Configuration refresh message. The system cannot access one or more event logs because of insufficient rights, file corruption, or other reasons. For more information, see the Operation channel in the ServerManager-ManagementProvider error log on the target server. Problem occurred on Server 2012 servers that have been upgraded to Server 2012R2 servers. Servers are also clustered. The Solution: Following the event logs leads to a few registry keys. You can eliminate the messages by: 1. Export the following registry keys (for safety) 2. Delete the following keys: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DxpTaskRingtone/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-Roaming/Analytic HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-IME-SCDICCOMPILER/Analytic HKLM\SOFTWARE\Mic
Read more

Shrewsoft VPN client - can't open Access Manager

Shrewsoft VPN client - can't open Access Manager Problem Access Manager is not visible Occurred after adjusting using dual monitors. Reinstall does not fix the issue. The Fix Use regedit to rename or delete the following key: HKEY_CURRENT_USER\Software\ShrewSoft\vpn\user Had a look around the Shrewsoft support site - nothing useful in there to fix this problem.
Read more

Hyper-V could not replicate changes for virtual machine as replication is suspended on the Replica server

Image
EVENT ID 32088 for all VMs After running out of disk space on the Replica host server, all VMs stopped replicating.  Replication cannot simply be started by right clicking on the source VM and selecting Resume Replication. No console error message just the event log event 32088.  I considered removing replication and re-replicating but this seemed an awful lot of work for simple problem. Tried stopping the Hyper-V service on the replica host and restarting, but this also did not work. THE FIX 1. Go to the destination replica server, right click each VM and select Resume Replication.  2. Now you can go to the source server, right click each VM and select Resume Replication. For some strange reason this works. Just trying one end or the other will fail without a console error message (but shows in the event log).
Read more