Failover Clustering and Network Load Balancing Team Blog
Hi Cluster Fans,
It has been a while since our last post and that is because we have been so busy unleashing Clustering in Windows Server 2008 R2 (“R2”) to the world. At several recent conferences, including TechEd EMEA and WinHec, we publically announced our R2 plans and features for Failover Clustering and Network Load Balancing. Over the next few months we will be discussing each of these new features on this blog, so check back regularly to learn all about clustering in R2.
· Cluster Shared Volumes (CSV) – A distributed access file system optimized for Hyper-V allowing virtual machines and their disk resources to reside be on any cluster node
· Live Migration – Move virtual machines between different physical machines while keeping them running and maintaining client connections
· PowerShell Support – The scripting language of the future which will gradually replace cluster.exe
· DFS-Replication support – Configure members servers in your replication group to be highly available for uniterrupted and failure resilient replication services
· Remote Desktop / Terminal Services support – Make the Connection Broker highly available ensuring that clients are reconnected to their same session or virtual machine within a server farm
· Network Prioritization – Plan your internal cluster network for efficiency, giving the fastest network the highest priority for internal traffic (heartbeat, CSV & Live Migration traffic)
· Read-Only APIs – This security enhancement allows admins to query the state of the cluster, but not perform any actions, making it ideal for first-level triage who "can look, but not touch"
· ETW logging channels – New Crimson channel makes cluster-wide events easier to manage
· Performance Monitor – Clustering counters allow the user to monitor the cluster and tweak it for optimal performance
· Enhanced Validation – Improvements to the functional test tool with additional tests which execute on production cluster nodes to ensure they are running optimally, with best practices deployed
· Migration – The clustering upgrade path now supports more workloads and configurations and offers detailed information about what will be migrated and any additional steps required by the user
· Extended Affinity – Ensures clients are reconnected to the same node to retain cached information if they are disconnected
· PowerShell Support – The new NLB scripting language which will gradually replace nlb.exe and wlbs.exe
We’ve also made additional improvements to virtually every workload, adding greater resiliency, functionality, and parity with standalone servers.
Thanks,Symon PerrimanProgram ManagerClustering & HA
I understand that Microsoft re-designed the "Challenge/Defense" protocol that was based on SCSI bus reset's, however I am unable to find any documentation on how it is currenty done. Can you please Blog on this or publish links to the appropriate documentation. Thanks.
The challenge/defense protocol is based on a SCSI SPC-3 specification called “persistent reservations” (PRs) and is used in Windows Server 2008 and R2.
The following webcast covers this process, I believe it is towards the end of this video: Webcast: TechNet Webcast: Failover Clustering and Quorum in Windows Server 2008 Enterprise Storage: http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032364842&EventCategory=5&culture=en-US&CountryCode=US
Clustering & HA
Hi Cluster Fans, Amongst the long list of features that is being added in Windows Server R2, Clustering
PingBack from http://unemploymentofficeresource.info/story.php?id=3750