IT tutorials
 
Technology
 

Windows Server 2012 : Continuous availability (part 1) - Failover Clustering enhancements - CSV2 and scale-out file servers

10/7/2013 8:56:02 PM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

Guaranteeing continuous availability of applications and services is essential in today’s business world. If users can’t use the applications they need, the productivity of your business will be affected. And if customers can’t access the services your organization provides, you’ll lose their business. Although previous versions of Windows Server have included features like Failover Clustering and NLB that help you ensure the availability of business-critical applications and services, Windows Server 2012 adds a number of improvements that can greatly help ensure application uptime and minimize service disruptions.

Key availability improvements include enhancements to Failover Clustering such as greater scalability, simplified updating of cluster nodes, and improved support for guest clustering. The new SMB 3.0 Transparent Failover capability lets you perform maintenance on your cluster nodes without interrupting access to file shares on your cluster. Storage Migration now allows you to transfer the virtual disks and configuration of VMs to new locations while the VMs are still running. Windows NIC Teaming now provides an in-box solution for implementing fault tolerance for the network adapters of your servers. Improvements to Chkdsk greatly reduce potential downtime caused by file system corruption on mission-critical servers. Easy conversion between installation options provides increased flexibility for how you configure servers in your environment, whereas Features On Demand lets you install Server Core features from a remote repository instead of the local disk. And DHCP failover improves resiliency by allowing you to ensure continuous availability of Dynamic Host Configuration Protocol (DHCP) services to clients on your network.

In the following sections, we’ll dig deeper into each of these capabilities and features. And we’ll continue to benefit from the insights and tips from insiders working at Microsoft and from select experts who have worked with Windows Server 2012 during the early stages of the product release cycle.

Combining host and guest clustering for continuously available workloads

A major investment area in Windows Server 2012 is the notion of continuous availability. This refers to the combination of infrastructure capabilities that enable VMs and workloads to remain online despite failures in compute, network, or storage infrastructure. Designing infrastructure and workloads for continuous availability requires analyzing and providing resiliency for each layer of the supporting architecture. The physical compute, storage, and network architecture providing the private cloud fabric is the first area of interest. Next, guest clustering or clustering of the VMs providing the workload functionality is an additional layer of resiliency that can be used. Together, these technologies can be deployed to provide continuous availability during both planned and unplanned downtime of the host infrastructure or the guest infrastructure.

At the fabric level or physical infrastructure layer, a Windows Server 2012 infrastructure provides continuous availability technologies for compute, network, and storage. For storage, Windows Server 2012 introduces Storage Spaces, a new technology for providing highly available storage using commodity hardware. Using either Storage Spaces or SAN-based storage, Windows Server 2012 also introduces Scale-Out File Server Clusters. With Scale-Out File Server Clusters, two or more clustered file servers use Cluster Shared Volumes Version 2 (CSV2) to enable a single share to be scaled out across file servers, providing very high-speed access and high availability of the file share. This file share can be used as the storage location for VMs because Windows Server 2012 supports storing VMs on SMB 3 file shares. With the combination of Storage Spaces, Scale-Out File Clusters, and SMB 3 Multi-Channel access, any component of the Windows Server 2012 storage infrastructure could fail, but access to the file share or VM will be maintained. This combination provides continuous availability of the storage infrastructure.

For the network infrastructure, Windows Server 2012 introduces built-in network adapter teaming that supports load balancing and failover (LBFO) for servers with multiple network adapters. Regardless of brands or speeds of network adapters in your server, Windows Server 2012 can take those adapters and create a network adapter “team.” The team can then be assigned an IP address and will remain connected, provided that at least one or more of the network adapters has connectivity. When more than one network adapter is available in a team, traffic can be load-balanced across them for higher aggregate throughput. Use of NIC teaming at the host level, combined with redundancy of the switch/routing infrastructure, provides continuous availability of the network infrastructure.

For the compute infrastructure, Windows Server 2012 continues to use Windows Failover Clustering with Hyper-V host clusters. The scalability of Hyper-V hosts and clusters has been increased dramatically, up to 64 nodes per cluster. Host clusters enable the creation of highly available virtual machines (HAVMs). Hyper-V host clusters use the continuously available storage infrastructure to store the HAVMs. For planned downtime, HAVMs (as well as non-HA VMs) can be live-migrated to another host with no downtime for the VMs. For unplanned downtime, a VM is moved to or booted on another node in the cluster automatically. Clusters can be updated automatically using Cluster Aware Updating, which live-migrates all VMs off the node to be updated so that there is no downtime during host maintenance and updating. Together, these technologies enable continuous availability of the compute and virtualization infrastructure.

Although these technologies provide a robust physical infrastructure and virtualization platform, the key availability requirement is for the workloads being hosted. A VM may still be running, but its workload may have an error, stop running, or suffer from some other downtime-causing event. To enable continuous availability for workloads, Windows Server 2012, like Windows Server 2008 R2, also support guest clustering, or creating a failover cluster consisting of VMs. A common example is creating a guest cluster of SQL VMs so that the advanced error detection and failover of database instances between cluster nodes can be used even when the nodes are virtualized. Previously, the only shared storage supported for guest clusters was iSCSI. With Windows Server 2012, Fibre Channel shared storage for VMs are enabled by the introduction of the virtual Fibre Channel host bus adapter (HBA) for VMs. This feature enables Fibre Channel–based storage to be zoned and presented directly into VMs. The VMs can then use this as shared storage for guest failover clusters.

The combination of host and guest clustering can provide continuous availability of the workload despite the failure of any layer of the architecture. In the case of a SQL guest cluster, if there is a problem in SQL such as a service or other failure, the database instance can fail over to another node in the guest cluster. If one of the network connections of the underlying physical host is lost, NIC teaming enables the SQL VM to remain accessible. Anti-affinity rules can be configured such that the SQL guest cluster VMs will not all be running on the same physical node; therefore, if a physical node fails, the SQL databases will fail over to another SQL node in the guest cluster running on one of the other nodes in the host cluster. If one of the disks where the SQL VM or its data is being stored fails, Storage Spaces and the Scale-Out File Cluster maintain uninterrupted access to the data.

These examples show that with proper design, the combination of host and guest clustering in conjunction with other Windows Server 2012 features like NIC teaming, enables continuous availability of VMs and their workloads.

David Ziembicki

Senior Architect, U.S. Public Sector, Microsoft Services

1. Failover Clustering enhancements

Failover Clustering is a feature of Windows Server that provides high availability for server workloads. File servers, database servers, and application servers are often deployed in failover clusters so that when one node of the cluster fails, the other nodes can continue to provide services. Failover Clustering also helps ensure workloads can be scaled up and out to meet the demands of your business.

Although the Failover Clustering feature of previous versions of Windows Server provided a robust solution for implementing high-availability solutions, this feature has been significantly enhanced in Windows Server 2012 to provide even greater scalability, faster failover, more flexibility in how it can be implemented, and easier management. The sections that follow describe some the key improvements to Failover Clustering found in Windows Server 2012. Note that some other cluster-aware features, such as concurrent Live Migrations and Hyper-V Replica.

Increased scalability

Failover Clustering in Windows Server 2012 now provides significantly greater scalability compared to Windows Server 2008 R2 by enabling you to do the following:

  • Scale out your environment by creating clusters with up to a maximum of 64 nodes, compared to only 16 nodes in the previous version.

  • Scale up your infrastructure by running up to 4,000 VMs per cluster and up to 1,024 VMs per node.

These scalability enhancements make Windows Server 2012 the platform of choice for meeting the most demanding business needs for high availability.

CSV2 and scale-out file servers

Version 1 of Cluster Shared Volumes (CSV) was introduced in Windows Server 2008 R2 to allow multiple cluster nodes to access the same NTFS-formatted volume simultaneously. A number of improvements have been made to this feature in Windows Server 2012 to make it easier to configure and use a CSV and to provide increased security and performance.

For example, a CSV now appears as a single consistent file namespace called the CSV File System (CSVFS), although the underlying file system technology being used remains NTFS. CSVFS also allows direct I/O for file data access and supports sparse files, which enhances performance when creating and copying VMs. From the security standpoint, a significant enhancement is the ability to use BitLocker Drive Encryption to encrypt both traditional failover disks and CSVs. And it’s also easier now to back up and restore a CSV with in-box support for CSV backups provided by Windows Server Backup. Backups of CSV volumes no longer require redirected I/O in version 2. The volume snapshots can be taken on the host that currently owns the volume, unlike version 1, where they were taken on the node requesting the backup. Configuring a CSV can now be performed with a single right-click in the Storage pane of Failover Cluster Manager.

Scale-out file servers are built on top of the Failover Clustering feature of Windows Server 2012 and the SMB 3.0 protocol enhancements. Scale-out file servers allow you to scale the capacity of your file servers upward or downward dynamically as the needs of your business change. This means you can start with a low-cost solution such as a two-node file server, and then later add additional nodes (to a maximum of four) without affecting the operation of your file server.

Scale-out file servers can be configured by starting the High Availability Wizard from Failover Cluster Manager. Begin by selecting File Server from the list of cluster roles (formerly called clustered services and applications):

image with no caption

Then, on the next page of the wizard, select the File Server For Scale-Out Application Data option, as shown here, and continue through the wizard:

image with no caption

When the wizard executes, a series of steps is performed to create the scale-out file server. These steps are summarized in a report that the wizard generates:

image with no caption

Scale-out file servers have a few limitations that general-use file servers don’t have. Specifically, scale-out file servers don’t support:

  • File Server Resource Management (FSRM) features like Folder Quotas, File Screening, and File Classification

  • Distributed File Services Replication (DFS-R)

  • NFS

  • Data deduplication

 
Others
 
- Windows Phone 8 : Location APIs (part 3) - Emulating Location Information
- Windows Phone 8 : Location APIs (part 2) - Accessing Location Information
- Windows Phone 8 : Location APIs (part 1) - Location Permission
- SQL Server 2008 : Data compression (part 2) - Data compression considerations
- SQL Server 2008 : Data compression (part 1) - Row compression, Page compression
- SQL Server 2008 : BLOB storage with FileStream (part 2) - FileStream data
- SQL Server 2008 : BLOB storage with FileStream (part 1) - BLOBS in the database, BLOBS in the file system
- Windows Small Business Server 2011 : Managing Software Updates - Using SBS Software Updates (part 2) - Deploying Updates
- Windows Small Business Server 2011 : Managing Software Updates - Using SBS Software Updates (part 1) - Configuring Software Update Settings
- Windows Small Business Server 2011 : Managing Software Updates - The Patching Cycle
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us