JumpStart: Server Virtualization with Windows Server Hyper-V and System Center

Module 5Virtual Machine Movement and Hyper-V Replica

Microsoft Virtual Academy120409A05: Virtual Machine Movement and Hyper-V ReplicaModule OverviewProviding High Availability and Redundancy for VirtualizationImplementing Virtual Machine MovementImplementing and Managing Hyper-V Replica220409A05: Virtual Machine Movement and Hyper-V ReplicaLesson 1: Providing High Availability and Redundancy for VirtualizationWhy Is High Availability Important?Redundancy in Windows Server 2012 R2 and Hyper-V320409A05: Virtual Machine Movement and Hyper-V ReplicaWhy Is High Availability Important?Server downtime is unavoidableServers are not always availableSoftware or hardware maintenance or upgrade Application and operating system updatesComponent failure, power outages, natural disastersCritical services must be constantly availableRunning in virtual machinesWhen fails or unavailableIt must be serviced elsewhereGoal of high availabilityMake services availableEven when failure occurs

AvailabilityDowntime (per year) 99% 3.7 days 99.9% 8.8 hours 99.99% 53 minutes 99.999% 5.3 minutes 420409A05: Virtual Machine Movement and Hyper-V ReplicaRedundancy in Windows Server 2012 R2 and Hyper-VDisaster recoveryHyper-V Replica for asynchronous replicationCSV integration with storage arrays for synchronous replicationApplication / Service failoverNon-cluster aware apps: Hyper-V app monitoringVirtual machine guest cluster: iSCSI, Fibre Channel, .vhdx sharingVirtual machine guest teaming of SR-IOV NICSI/O redundancyNLB and NIC TeamingStorage multi-path IOMultichannel SMBPhysical server failureLive migration for planned downtimeFailover clustering for unplanned downtimeHardware failureWindows hardware error architecture Reliability, availability, serviceability520409A05: Virtual Machine Movement and Hyper-V ReplicaLesson 2: Implementing Virtual Machine MovementVirtual Machine Moving OptionsHow Storage Migration WorksOverview of the Move WizardLive Migration of Non-clustered Virtual Machines620409A05: Virtual Machine Movement and Hyper-V ReplicaVirtual Machine Moving OptionsVirtual machine and storage migrationIncludes from Windows Server 2012 to Windows Server 2012 R2Quick migration requires failover clusteringLive migration requires only network connectivityImproved performance in Windows Server 2012 R2Hyper-V ReplicaAsynchronously replicate virtual machinesConfigure replication frequency and extended replicationExporting and Importing of a virtual machineExporting while virtual machine is runningCan import virtual machine without prior export720409A05: Virtual Machine Movement and Hyper-V ReplicaHow Storage Migration Works

Hyper-V serverVirtual machine

Virtual hard disk stack12345Read/Write to source virtual hard disk

Virtual hard disk is copied to destination

Writes are mirrored to source and destination virtual hard disks

After virtual hard disk is synchronized, virtual machine switches to copied virtual hard disk

Source virtual hard disk is deletedVirtual machine is running uninterrupted during the migration process

Virtual hard disk

Virtual hard diskCompares withStorage vMotion

820409A05: Virtual Machine Movement and Hyper-V ReplicaOverview of the Move WizardUsed for moving virtual machine or its storageWhile virtual machine is runningLive migration or storage migrationAlternatively, use Windows PowerShell cmdlets Move-VM or Move-VMStorageStorage migration is enabled by default (two at the same time)Live migration must be enabled before moving virtual machineAll virtual machine data can be moved to same locationOr you can specify location for each data itemOr you can move only virtual hard diskVirtual machine data itemsVirtual hard disks, current configuration, checkpoints, smart pagingYou can move only the virtual machine or also include data items920409A05: Virtual Machine Movement and Hyper-V ReplicaLive Migration of Non-clustered Virtual MachinesReferred as a shared nothing live migrationVirtual machine data can be local or on an SMB shareLocal: storage migration to move to target Hyper-V hostSMB: leave data on the SMB 3.0 shareIn both cases virtual machine is movedStorage migration and virtual machine moveStorage is migratedVirtual machine memory is movedSource storage is deletedLive migration speed is affected byVirtual machine memory size and modificationsBandwidth between source and destination Hyper-V hostsCompares withvMotion

1020409A05: Virtual Machine Movement and Hyper-V Replica(More notes on the next slide)Live Migration of Non-clustered Virtual MachinesVirtual machine memory is moved in iterationsSource is active and can be modifying memoryModified memory pages are sent after initial copyRepeats over newly modified pagesFinal copy iteration takes less than TCP timeoutNew MAC address is send to network switchesSource Hyper-V hostDestination Hyper-V hostConfigurationVirtual machine memoryConfigurationStateStateVirtual machine memory1120409A05: Virtual Machine Movement and Hyper-V ReplicaLesson 3: Implementing and Managing Hyper-V ReplicaPrerequisites for Hyper-V ReplicaOverview of Hyper-V ReplicaEnabling a Virtual Machine for ReplicationHyper-V Replication HealthTest Failover, Planned Failover, and FailoverHyper-V Replica Resynchronization1220409A05: Virtual Machine Movement and Hyper-V ReplicaPrerequisites for Hyper-V ReplicaWindows Server 2012 with Hyper-V roleHyper-V Replica is part of the Hyper-V roleAt least two servers, usually in different sitesSufficient storage to host virtual machinesLocal and replicated virtual machinesConnectivity between primary and replica sitesWindows firewall configured to allow replicationHyper-V Replica HTTP and Hyper-V Replica HTTPSX.509v3 certificate for mutual authenticationIf certificate authentication is usedOtherwise, Hyper-V hosts must be in the same AD DS forest

1320409A05: Virtual Machine Movement and Hyper-V ReplicaOverview of Hyper-V ReplicaHyper-V Replica has the following components:Replication engineManages replication configuration and handles initial replication, delta replication, failover, and test-failoverChange tracking moduleKeeps track of the write operations in the virtual machineNetwork moduleProvides a secure and efficient channel to transfer dataHyper-V Replica Broker server roleProvides seamless replication while a virtual machine is running on different failover cluster nodesManagement toolsHyper-V Manager, Windows PowerShell, Failover Cluster Manager1420409A05: Virtual Machine Movement and Hyper-V ReplicaOverview of Hyper-V Replica

Primary SiteSecondary Site

Initial ReplicaReplicated Changes

CSV onBlockStorageSMB ShareFile BasedStorage1520409A05: Virtual Machine Movement and Hyper-V ReplicaEnabling a Virtual Machine for ReplicationReplication is enabled per virtual machine Enable Replication WizardReplica serverConnection parametersChoose replication VHDsChose replication frequencyConfigure additional recovery pointsChoose initial replication methodFailover TCP/IP SettingsPreconfigure IP address for replica virtual machineRequires integration servicesShould be configured on both the primary and replica server

Primary 10.22.100.18Virtual machineReplica 192.168.15.101620409A05: Virtual Machine Movement and Hyper-V ReplicaHyper-V Replication HealthNormalLess than 20% replication cycles are missedLast synchronization point was less than an hour agoAverage latency is less than the configured limitWarningGreater than 20% of replication cycles have been missed More than hour since the last send replica Initial replication has not been completedFailover initiated, but not reverse replicationPrimary virtual machine replication is pausedCriticalReplica paused on the replica virtual machinePrimary server unable to send the replica data

1720409A05: Virtual Machine Movement and Hyper-V ReplicaTest Failover, Planned Failover, and FailoverTest failoverNon-disruptive testing, with zero downtimeNew virtual machine created in recovery siteFrom the replica checkpointTurned off and not connectedStop Test FailoverPlanned failoverInitiated at primary virtual machine which is turned offSends data that has not been replicatedFail over to replica serverStart the replica virtual machineReverse the replication after primary site is restored1820409A05: Virtual Machine Movement and Hyper-V ReplicaTest Failover, Planned Failover, and FailoverFailoverInitiated at replica virtual machinePrimary virtual machine has failed (turned off or unavailable)Data loss can occurReverse the replication after primary site is recoveredOther replication-related actionsPause Replication and Resume Replication View Replication HealthExtend ReplicationRemove Recovery PointsRemove Replication1920409A05: Virtual Machine Movement and Hyper-V ReplicaHyper-V Replica ResynchronizationWhen normal replication process is interruptedChange tracking issues on primary serverReplication issues with tracking logsProblems linking virtual hard disk with parentTime travel virtual machine restored from backupReverse replication after failover processProcessor, storage, and network intensiveConfigured on primary virtual machineManual, automatic, or during scheduled timeIf more than 6 hours, perform full initial replication2020409A05: Virtual Machine Movement and Hyper-V Replica