Windows Server 2016 Cloud building brick Ljubo Brodarić Siemens CVC.
-
Upload
olivia-murphy -
Category
Documents
-
view
217 -
download
0
Transcript of Windows Server 2016 Cloud building brick Ljubo Brodarić Siemens CVC.
Windows Server 2016Cloud building brickLjubo BrodarićSiemens CVC
Agenda
• Cluster Operating System Rolling Upgrade
• Cloud Witness
• Cluster Compute Resiliency
• Workgroup and Multi-domain clusters
• Storage Replica
• Storage Spaces Direct (S2D)
Cluster OS Rolling Upgrade (1)• Adding node with next version of OS into existing
cluster
• Most wanted and criticized feature‐ Migration upgrade only option until now
‐ Hyper-V platform suffered most
• No need to stop the cluster
• No need for new hardware or cluster
Cluster OS Rolling Upgrade (2)• Node has to be reinstalled (in-place upgrade not
supported or recommended)
• Simple roll-back in case of any problems‐ ClusterFunctionalLevel
• Upgrade of all nodes should be done in reasonable time
• Microsoft support 4 weeks after upgrade starts
• Hyper-V, SOFS and all other clusters
• Windows Server 2012 R2 only
Cluster OS Rolling Upgrade (3)
Tranzicijska stanja prilikom nadogradnje klastera
DemoCluster Operating System Rolling Upgrade
Cloud Witness (1)
• Additional vote in cluster for achieving quorum
‐ Necessary for split-brain scenario
• Azure blob storagea used‐ Third location problem removed
• Very important for streched clusters
‐ File Share Witness used so far
Cloud Witness (2)
• Azure Storage Account required‐ One for many clusters
‐ Geo-redundancy must be disabled
• Azure VM not needed for File Share Witnessa
• Cheap‐ Small amount of data
‐ Incremental Sequence Number stored only
• Internet access required
Cloud Witness (3)
• Since Windows Server 2012 R2 witness should be allways configured
‐ Dynamic Witness
• All clusters without shared storage‐ SQL Always On, Exchange DAG, virtual clusters
hosted in Azureu or private cloud
DemoCloud Witness
Cluster Compute Resiliency (1)• Resiliency to transient failures
• Network is the most common reason
• Cluster should react ASAP, but…
• Two types of resiliency‐ Node Isolation
‐ Node Quarantine
Cluster Compute Resiliency (2)
Node Isolation
• VMs or any other resources continue to run even when a node falls out of cluster membership
• Cluster waits 4 minutes before roles drain
Cluster
?
?
?Network
CommunicationFailure
Cluster Compute Resiliency (3)
Node Quarantine
• Unhealthy nodes are quarantined and are no longer allowed to join the cluster
‐ Prevents flapping nodes from negatively effecting the cluster
‐ If node ungracefully leaves the cluster three times within an hour
‐ Roles gracefully drained
• QuarantineDuration: 2 hours
• QuarantineState: Node read only
QuarantinedCluster
Workgroup and Multi-domain clusters (1)• Single-domain Clusters: Clusters with all nodes
joined to the same domain
• Multi-domain Clusters: Clusters with nodes which are members of different domains
• Workgroup Clusters: Clusters with nodes which are member servers / workgroup (not domain joined)
Workgroup and Multi-domain clusters (2)• Consistent local administrator accounts on all
nodes of the cluster must exist
• DNS suffix must be configured for all nodes
• Witness must be Cloud Witness or Disk Witness
• Power Shell management only
http://blogs.msdn.com/b/clustering/archive/2015/08/17/10635825.aspx
Workgroup and Multi-domain clusters (3)
Technical Preview 3 Workload Support
Cluster workload Status More Information
SQL Server Supported We recommend that you use SQL Server Authentication.
File Server Supported, but not recommended
Kerberos (which is not available) authentication is the preferred authentication protocol for Server Message Block (SMB) traffic.
Hyper-V Supported, but not recommended
Live migration is not supported. Quick migration is supported.
DemoWorkgroup Cluster
Storage Replica (1)
• Ent to End Microsoft Disaster Recovery solution
• Block-level, volume-based Synchronous & Asynchronous SMB3 transport
• Any Windows volume, Any fixed disk storage, Any storage fabric
• Hardware agnostic: Storage Spaces, SAN (FC or iSCSI), DAS...
• Management: Power Shell, Failover Cluster Manager
Storage Replica (2)
Data
2
Application
Source
1
Log
5
t 2
Data
Destination
Log
t 3
4
1
Data
4
Application
Source
1
Log
3
t 2
Data
Destination
Log
t 5
6
1
Synchronous replica
Asynchronous replica
Storage Spaces Direct - S2D• Storage Spaces Direct is an evolution of Storage
Spaces
• Storage Spaces Direct leverages SMB3 for all intra-node (aka east-west) communication
‐ SMB Direct and SMB Multichannel
Storage Spaces Direct - S2D
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.