During Windows Server 2012 Roadshow event at Singapore and Malaysia, i have presented on how to configure Hyper-V High Availability and Hyper-V Replica.
4. ...
Scale up
“Windows Server 2012” supports an
industry best 8,000 VMs per cluster
and can now massively scale out to
64 nodes in a cluster ...
Scale out
Robust management tools
5. HOST CLUSTERING AND GUEST CLUSTERING
Host Clustering Guest Clustering
• Cluster service runs inside (physical) • Cluster service runs inside a VM
host and manages VMs • Apps and services inside the VM are
• VMs move between cluster nodes managed by the cluster
• Apps move between clustered VMs
Cluster
Cluster
SAN iSCSI
6. Mixing Physical and Virtual
Scenarios
- Spare node is a VM in a Private Cloud
- Shared host running multiple spare iSCSI
nodes as VMs
- Test environment with limited
hardware
11. Step 1: Hardware Planning
Plan 1: Plan 2 Plan 3: Plan 4: Plan 5:
Server Processor Memory Network Storage
Interface Card
Root Reserve
Certified Hardware DEP
Hardware Assisted Virtualization 1 Management iSCSI
64 Bit 1 Live Migration FC SAN
Processor compatibility Mode 1 Private/CSV SMB 3.0
1 Backup Storage Space
N X Guest Networking
N X Storage
13. Step 2:- Validate Hardware
Significantly faster
storage validation
times
Granular control to run
Validate against
specific LUNs
New tests
Verify CSV requirements
Hyper-V specific tests
23. CLUSTER LIVE MIGRATIONS
Live Migration Queuing
Concurrent Live Migrations
Cluster VM Mobility Enhancements Concurrent Live Migrations:
Multiple simultaneous LMs for a
given source or target
Cluster VM Mobility Enhancements: Live Migration Queuing:
Node Drain, failback, Cluster aware In-box tools queue & manage large
updating… numbers of VMs
30. Overview of Steps
Step 1: Step 2: Step 3: Step 4: Step 5:
Prepare to Enable Test the Perform Respond to an
Deploy Hyper- Replication Replication Planned Unplanned
V Replica Deployment Failover Failover
32. Step 1:- Prepare to Deploy Hyper-V
Replica
Behind the firewall?
Stand Alone or Cluster Hyper-V
Security of replication data
Which VHD to be replicated?
How many recovery point?
Decide Initial replication method?
Bandwidth for replication
52. Join us ! Q&A
Malaysia Virtualization User Group
(MVUG)
https://www.facebook.com/groups/mvuggroup/ or go to
Facebook, search “MVUG”
Windows Server 2012 Hyper-V
Resources:-
Configure Hyper-V High Availability-
Resources http://technet.microsoft.com/en-us/library/hh831579.aspx
Configure Hyper-V Replica - http://technet.microsoft.com/en-
us/library/jj134207.aspx
53. Home PC Backup Software
Giveaway
Email to ms4u@outlook.com with the subject
“1st Windows Server 2012 Malaysia Roadshow
Giveaway”
What Host Clustering Deliver ?Avoids a single point of failure when consolidatingSurvive Host CrashesVMs restarted on another nodeRestart VM CrashesVM OS restarted on same nodeRecover VM HangsVM OS restarted on same nodeZero Downtime Maintenance & PatchingLive migrate VMs to other hostsMobility & Load DistributionLive migrate VMs to different servers to load balanceWhat Guest Clustering Deliver?Application Health MonitoringApp or service within VM crashes or hangs and moves to another VMApplication MobilityApps or services moves to another VM for maintenance or patching of guest OS
SCSI: If you are using iSCSI, each clustered server should have one or more network adapters or HBAs that are dedicated to the cluster storage. The network you use for iSCSI should not be used for network communication. In all clustered servers, the network adapters you use to connect to the iSCSI storage target should be identical, and we recommend that you use Gigabit Ethernet or higherFor iSCSI, network adapter teaming (also called load balancing and failover, or LBFO) is not supported. You can consider using MPIO software instead.To use the native disk support included in Failover Clustering, use basic diskWe recommend that you format the partitions with NTFS. If you use Cluster Shared Volumes (CSVs), the partition for each of those must be NTFSConsider using Storage Spaces: If you plan to deploy serial attached SCSI (SAS) clustered storage configured using Storage Spaces in Windows Server 2012, the following are requirements: A clustered storage pool made up of at least three SAS-connected physical disk drives, each with at least 4 GB capacity. The physical disks used for a clustered storage pool must be dedicated to that pool. Startup disks should not be added.Fixed provisioning of the storage pool.Either simple or mirror storage spaces. Parity spaces are not supported.
Non-disruptive testing of workload – zero downtimeTest any recovery pointPre-configure isolated network
At this time, CSVs do not support the Microsoft SQL Server clustered workload.Improvement:-CHKDSKInteroperate with AV and backupBitLocker-encrypted volumesStorage Spaces
Storage and disks must meet the following requirements:NTFS format A disk or storage space for a CSV must be a basic disk that is partitioned with NTFS. A CSV has the following additional requirements:You cannot use a disk for a CSV that is formatted with FAT, FAT32, or Resilient File System (ReFS).If you want to use a storage space for a CSV, you can configure a simple space or a mirror space. CSVs do not support parity spaces.A CSV cannot be used as a quorum witness disk. After you add a disk as a CSV, it is designated in the CSVFS format (for CSV File System). This allows the cluster and other software to differentiate the CSV storage from other NTFS storage. Generally, CSVFS supports the same functionality as NTFS. However, certain features are not supported. For example, you cannot enable data deduplication or compression on a CSV.
For an equivalent clustered virtual machine, you should organize the volumes and files in a similar way:System files, including a page file, in a VHD file on one CSVData files in a VHD file on another CSIf the cluster nodes are connected to networks that should not be used by the cluster, you should disable them. For example, we recommend that you disable iSCSI networks for cluster use to prevent CSV traffic on those networks. To disable a network, in Failover Cluster Manager, click Networks, click the network, click the Properties action, and then select Do not allow cluster network communication on this network.
Non-disruptive testing of workload – zero downtimeTest any recovery pointPre-configure isolated network
Shutdown primary VMSend last logFailover Replica VMReverse replicate