A little bit about myself. I’m @jdanton on Twitter---how many of you are on Twitter? It’s a really great resource for the SQL Community—we have a lot of interaction and discussion there, and additionally there is a great hashtag called SQLHelp. Where you can get questions answered by experts. My blog is at joedantoni.wordpress.com—I have posts on a lot of the topics we will talk about today, and have instructions on setting up an AlwaysOn environment there. Lastly you can reach me by email at firstname.lastname@example.org. I have a blog post with my slides and additional resources from today’s presentation up at this bit.ly URL.Lastly, stop me at anytime if you have questions for me, I’ll do my best to answer, or direct you to an answer.
1. Windows Server 2012Failover ClusteringNew FeaturesJoe D’AntoniPhiladelphia SQL Server Users Group13 February 2013
2. @jdanton Joedantoni.wordpress.comAbout Me email@example.com
3. Easier ManagementOverview ofChanges Increase Scailability—Hyper V Greater Flexibility
4. WindowsServer 2012
5. Cluster Virtual NameInstanceNameFailover SQL InstanceClusterInstances Node A Node B Windows Failover Cluster
6. ScalabilityLimits 16 Nodes 64 Nodes Windows Server 2008R2 Windows Server 2012
7. Search, filtering, and custom views. Administrators can manage and navigate large numbers of clustered virtual machines or other clustered roles. Multiselect. Administrators can select a specific collection of virtual machines and then perform any needed operation (such asFailover live migration, save, shutdown, or start).ClusterManagement Simplified live migration and quick migration of virtual machines and virtual machine storage. Live migration and quick(Hyper-V) migration are easier to perform. Support for Hyper-V Replica. Hyper-V Replica provides point-in- time replication of virtual machines between storage systems, clusters, and data centers for disaster recovery.
8. 4000 Hyper V VMs per clusterServer Server Manager will show all nodes, including the name of theManager cluster and any VMs in the cluster
9. All Nodes can be seen from Server Manager This can be doneServer either remotely orManager locally on the cluster
10. When creating a new cluster, the cluster object will be created in the Organizational Unit (OU) where the node(s) resides This action will use the account of logged on user—not a system accountNew AD If needed this can be specified at cluster creationIntegrationFeatures
11. Automated repair of cluster virtual computer objects (VCOs) if they are deleted accidentally Cluster access only to Read-only domain controllersAD New Ability of the cluster to start with no AD DSFeatures dependencies Failover clusters do not support group Managed Service Accounts However services running on a cluster (e.g. SQL Server) do
13. Windows Cluster Q Node 1 Node 2Quorum Node Majority Mode Node and Disk Majority In Node/Disk Majority Mode Cluster sustain node failure
14. Dynamic quorum model is now the default when creating cluster Nodes and also be manually removed from voting (for example—a SQL Availability Group node used exclusively for reporting)QuorumManagement
15. Washington Philadelphia Node1 Node2 Node3 Node4Dynamic Node 4 is now not aQuorum voting member of the cluster Quorum File Share
16. Storage Tests will run significantly faster Tests are now integrated with WMICluster New Checks are Included for Cluster Shared Volumes (CSV) forValidation Hyper-V and its VMs Tests check to see if networking is optimal so live migrations can function as expected
17. Node A goes down while being updated, service move to Node B Cluster Aware UpdatingCluster Aware Node B then goes down for update, and isUpdating Cluster Node A Cluster Node B restarted Quorum Disk Windows Cluster Node B doesn’t begin its updates until Node A has come back up
18. Cluster-Aware Updating (CAU) is an automated feature that allows you to update clustered servers with little or no loss in availability during the update process. During an Updating Run, CAU transparently performs the following tasks: Puts each node of the cluster into node maintenance mode Moves the clustered roles off the node Installs the updates and any dependent updatesCluster Aware Performs a restart if necessaryUpdating Brings the node out of maintenance mode Restores the clustered roles on the node Moves to update the next node
19. For services like SQL Server—there is a minimal amount of downtime With Hyper-V Virtuals Machines, no downtime is needed This can also be used to apply SQL Service Packs and CumulativeCluster Aware UpdatesUpdating Different CAU run profiles can be applied to different sets of Failover Clusters Can be run on Server Core Operated remotely
20. By using the updated Migrate a Cluster Wizard in Windows Server 2012, administrators can migrate the configuration settings for clustered roles (formerly called clustered services and applications) from clusters that are running Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008. Migration enhancements in Windows Server 2012 include:ClusterUpgrade and Export and reimport Hyper-V virtual machines.Migration Migrate to CSV disks. Map storage and virtual networks. Reuse existing storage.
21. The task scheduler in a cluster is now cluster aware Tasks can be run in three ways: Cluster-wide. The task is scheduled on all cluster nodes.Task SchedulerIntegration Any node. The task is scheduled on a single, random node. Resource specific. The task is scheduled only on a node that owns a specified cluster resource.
22. Cluster.exe commands are marked as deprecated—still inPowerShell Windows, but will be going away All cluster functions can be managed through PowerShell cmdletsSupport
23. Majority of changes are designed for increase flexibility for Hyper- V virtual environments Cluster Aware Updating is the feature we will use most frequentlySummary Flexible quorum allows for easier cluster repair in an emergency