| 
High Availability (HA)
- continually available apps, services or systems
- often quantified in related SLA
- uptime: 99.9% = 8.76h/yr OR 99.999% = 5.25m/yr
- HA methods: - Redudancy (duplication) OR Failover/failback
- 2 main options - Failover Clustering (FC) OR Network Load Balancing (NLB)
Multi-Site Clustering in Windows Server 2012
- FC (Failover Clustering) extended across a WAN link
- Requires storage replication (sync or async)
- When site fails, the multi-site cluster (semi-manually) fails over to the other site
- Inter-Site heartbeat is crucial (1/sec instead of 1/250ms)
- Infrastructure services must be present in all sites - AD DS, DNS, DHCP
Highly Available Hyper-V
- CSVs allow for quick failover/failback
- Node drain (Live migrate all VMs on host); can be used with Cluster Aware Updating (CAU)
- Windows Server 2012 allows live migrations even without failover clustering
- VM Monitoring; integration with Task Scheduler
- VDI can be deployed using RDS - Windows Server 2012 Remote Desktop Services (RDS)
- vMotion in Hyper-V - Hyper-V Live Migration vs. Quick Migration
- Cluster Aware Updating - Advanced Options and Updating Run Profiles for CAU
- Hyper-V Virtual Machine Connection - just like RDP but no need to type VM name/IP, just pick
SCVMM - System Center Virtual Machine Manager 2012
- P2V requirements: +512MB RAM, volumes max 2TB, ACPI BIOS, MBR, no perimeter network
- V2V are possible with SCVMM + Acronis True Image Echo
- Create and manage private clouds from Hyper-V, VMware and XenServer hosts
- Automate workflow across multiple Hyper-V servers
- Management layer that integrates seamlesly with: Failover clustering, Hypr-V and IP address virtualisation
Hyper-V and PowerShell - Hyper-V Cmdlets in Windows PowerShell
Resources
- Failover Clustering Hardware Requirements and Storage Options - Server 2012
- Heartbeat messages operate UDP on port 3343 - Windows Server 2008 Failover Clusters: Networking
- Network Load Balancing - Server 2012
- What's New in Failover Clustering (2008 vs 2012)
- Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
- New 2012 Feature - Scale-Out File Server for Application Data Overview
- CSVs - Cluster Shared Volumes - Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster
» allows more than 1 node to access shared storage
uses VHD image files; local mounts at c:\ClusterStorage\Volume1, etc.
» used for Hyper-V & Scale-Out File Server
- Failover Clusters Cmdlets in Windows PowerShell
- Events and Errors Message Center
- continually available apps, services or systems
- often quantified in related SLA
- uptime: 99.9% = 8.76h/yr OR 99.999% = 5.25m/yr
- HA methods: - Redudancy (duplication) OR Failover/failback
- 2 main options - Failover Clustering (FC) OR Network Load Balancing (NLB)
Multi-Site Clustering in Windows Server 2012
- FC (Failover Clustering) extended across a WAN link
- Requires storage replication (sync or async)
- When site fails, the multi-site cluster (semi-manually) fails over to the other site
- Inter-Site heartbeat is crucial (1/sec instead of 1/250ms)
- Infrastructure services must be present in all sites - AD DS, DNS, DHCP
Highly Available Hyper-V
- CSVs allow for quick failover/failback
- Node drain (Live migrate all VMs on host); can be used with Cluster Aware Updating (CAU)
- Windows Server 2012 allows live migrations even without failover clustering
- VM Monitoring; integration with Task Scheduler
- VDI can be deployed using RDS - Windows Server 2012 Remote Desktop Services (RDS)
- vMotion in Hyper-V - Hyper-V Live Migration vs. Quick Migration
- Cluster Aware Updating - Advanced Options and Updating Run Profiles for CAU
- Hyper-V Virtual Machine Connection - just like RDP but no need to type VM name/IP, just pick
SCVMM - System Center Virtual Machine Manager 2012
- P2V requirements: +512MB RAM, volumes max 2TB, ACPI BIOS, MBR, no perimeter network
- V2V are possible with SCVMM + Acronis True Image Echo
- Create and manage private clouds from Hyper-V, VMware and XenServer hosts
- Automate workflow across multiple Hyper-V servers
- Management layer that integrates seamlesly with: Failover clustering, Hypr-V and IP address virtualisation
Hyper-V and PowerShell - Hyper-V Cmdlets in Windows PowerShell
Resources
- Failover Clustering Hardware Requirements and Storage Options - Server 2012
- Heartbeat messages operate UDP on port 3343 - Windows Server 2008 Failover Clusters: Networking
- Network Load Balancing - Server 2012
- What's New in Failover Clustering (2008 vs 2012)
- Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
- New 2012 Feature - Scale-Out File Server for Application Data Overview
- CSVs - Cluster Shared Volumes - Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster
» allows more than 1 node to access shared storage
uses VHD image files; local mounts at c:\ClusterStorage\Volume1, etc.
» used for Hyper-V & Scale-Out File Server
- Failover Clusters Cmdlets in Windows PowerShell
- Events and Errors Message Center