Windows 2012 Storage & HYPER-V improvements
•
3 j'aime•1,796 vues
Windows 2012 offer many enhancement in File Servers, Clusters, Virtualization and Server Management. This presentation covers some of those enchantments.
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (13)
Similaire à Windows 2012 Storage & HYPER-V improvements
Similaire à Windows 2012 Storage & HYPER-V improvements (20)
Dernier
Dernier (20)
Windows 2012 Storage & HYPER-V improvements
- 2. Server Manager and PowerShell Highly Available Files and Services Storage Enhancements Network Enhancements Hyper-V Enhancements Storage and Networking Enhancements for Hyper-V Network Virtualization 2
- 3. STANDARDS-BASED MANAGEMENT MULTISERVER ECOSYSTEM AND MANAGEMENT EXTENSIBILITY Windows Management Framework Server Manager Cross platform provides a common platform for building enables a capabilities automation and integration incorporating PowerShell, WS- multiserver enable management automation Management and WMI experience that across the builds on the datacenter standardized ROBUST AUTOMATION approach to management and Standardized robust interfaces and Windows PowerShell 3.0 tools extend the automation provides more features to allow more activities capabilities interoperability to be automated across the server ecosystem with DevOps 3
- 4. MULTISERVER MANAGEMENT Windows Server 2008 FILE SERVICES R2 HYPER-V STORAGE Connect to server roles (such as File Services, Hyper-V, and Remote Desktop Services) on a per-server basis. Windows Server 1 Server 2 Server 3 Server 1 Server 3 Server 2012 Role 1 Server 2 Role 2 Manage a server role as Server 1 Role 3 it spans across servers, or look at a Role 1 Role 3 server and the server Role 2 roles on that server. Both options are 4 important.
- 6. ROBUST AUTOMATION Key features Broader coverage Greater resiliency • Rich management through more than 2400 • Robust session connectivity cmdlets • Disconnected sessions • Session configuration files • Job scheduling • Windows PowerShell Web Access More intuitive • Integrated Scripting Environment 3.0: Syntax simplification | IntelliSense | Reusable text in code examples Higher performance • Cmdlet discovery and module autoloading • On-the-fly compilation—up to six times • Updatable help faster • Script-sharing • Windows PowerShell Workflow 6
- 7. ROBUST AUTOMATION More intuitive Cmdlet Integrated Scripting Get-Command *-Net* Environment (ISE) 3.0 discovery Get-Help *-Net* Updatable Update-Help Help Save-Help Script-sharing IntelliSense 7
- 8. ROBUST AUTOMATION PowerShell 3.0 Modules Windows PowerShell 3.0 New Modules • Comprehensive server management with more than 2,400 cmdlets • Many new modules that allow the use of Windows PowerShell 3.0 to manage all aspects of the datacenter; for • Over 60 new modules to replace command line commands example, new modules for: • Networking, DNS, DHCP, BranchCache, DA, Server Roles, AD • Dynamic Host Configuration Deployment, Firewall, Teaming, PKI, Security, Remote Protocol (DHCP) server Desktop, VDI, RRAS, Group Policy, AppLocker, and many more • Domain Name System (DNS) server • No more knowing the module, modules load on the fly. • Others 9
- 9. STANDARDS- BASED MANAGEMENT • Primary, default server deployment option • Supports more roles and • Minimal User Experience Option services, including .Net • Server Core with GUI tools Framework 4.5 and SQL Server • Server Manager and cmd.exe 2012 launch by default when server is • Firewall-friendly remote booted management (WinRM) and • Allows other GUI tools to be Windows PowerShell are enabled loaded and installed by default • Enabled through Add Roles and • Adds the ability to easily move Features wizard, or with between Server Core and PowerShell MinShell 11
- 10. NETWORKING QOS DHCP FAILOVER IP ADDRESS MANAGEMENT Inbox feature for integrated management of IP addresses, domain Helps guarantee Automatically names and device identities predictable replicates and load network balances DHCP Tightly integrates with Microsoft DNS and DHCP servers performance and scopes Provides custom IP address space display, reporting, and fair sharing during management congestion Audits server configuration changes and tracks IP address use Helps enforce customer SLAs and NIC TEAMING maximum pricing HYPER-V NETWORK VIRTUALIZATION caps Supports Combine any two bandwidth floors adapters with one Isolation traffic without VLAN – Keep customers on the same server but and bandwidth caps PowerShell on different IP subnets command Cross Subnet Migration – Move a VM to a new subnet without changing the IP address in the VM 12
- 11. SIMPLIFIED MULTITENANT INFRASTRUCTURE Blue sees Orange sees SQL Server Web SQL Server Web 10.1.1.1 10.1.1.2 10.1.1.1 10.1.1.2 10.1.1.1 192.168.1.10 10.1.1.1 192.168.1.11 10.1.1.2 192.168.2.12 10.1.1.2 192.168.2.13 Server Virtualization Network Virtualization What’s really happening • Run multiple virtual 192.168.n.n • Run multiple virtual servers on a physical networks on a physical server PROVIDER ADDRESS SPACE (PA) network • Each virtual machine 192.168.1.10 192.168.1.11 192.168.2.12 192.168.2.13 • Each virtual network acts as though it is acts as though it is running as a physical running as physical server fabric 10.1.1.1 192.168.1.10 10.1.1.1 192.168.1.11 10.1.1.1 192.168.1.11 10.1.1.1 192.168.1.10 10.1.1.2 192.168.2.12 10.1.1.2 192.168.2.13 10.1.1.2 192.168.2.13 10.1.1.2 192.168.2.12 10.1.1.1 10.1.1.1 10.1.1.2 10.1.1.2 SQL Server SQL Server Web Web CUSTOMER ADDRESS SPACE 13
- 12. CONTINUOUS APPLICATION AVAILABILITY • Provides network fault tolerance and continuous availability when network adapters fail by teaming multiple network interfaces • Vendor agnostic and shipped inbox Virtual adapters • Provides local or remote management Team network adapter Team network adapter through Windows PowerShell or UI • Enables teams of up to 32 network adapters • Aggregates bandwidth from multiple network adapters • Includes multiple nodes: switch dependent and independent 14
- 13. HIGH- PERFORMANCE NETWORKING Without RDMA With RDMA • Higher performance through offloading of network I/O processing onto network adapter File Client File Server • Higher throughput with low latency and ability to take advantage of high-speed networks App Buffer (such as InfiniBand and iWARP) • Remote storage at the speed of direct storage SMB SMB Buffer Buffer • Transfer rate of around 50 Gbps on a single NIC port OS OS • Compatible with SMB Multichannel for load Buffer Buffer balancing and failover Driver Driver Buffer Buffer iWARP Adapter Buffer rNIC NIC rNIC NICAdapter Buffer InfiniBand 15
- 14. CLUSTER AWARE DEDUPLICATION SMB 3.0 UPDATING SMB 3.0 Direct – Supports RDMA adapters for higher speeds and lower Automatically Eliminates file latency moves file server duplication for up to SMB Multi-Channel – Leverages all network connections for higher speed roles to additional 95% spaces savings and greater through put nodes without on software and Continuously Available File Server – Failover without loss of connection service interruption. VHD library folders or interruption of data flow Orchestrates updates across all ONLINE BACKUP cluster nodes with STORAGE SPACES zero downtime. Backup directly to a Returns all roles to Windows Azure Thin Provisioning– Enables to present the storage you need, not what you preferred node on subscription have. Add later completion Clustering – Create storage spaces from JBOD disk systems and cluster them 16
- 15. ALWAYS ON, ALWAYS UP CHKDSK NTFS improvements • Seconds to fix corrupted data • Rapid recovery from file system corruption without affecting • availability time when used with CSV No offline • Rapid recovery from file system corruption without • Data scanning process separated from repair allocate-on-write • Disk corruption virtually eliminated through process affecting availability • Period checksumwith volume, offline repair • Online scanning validation of file system meta-data • Resilient against power outage corruption • Seamless data integrity protection • Periodic checksum validation of file system metadata 400 • Improved data integrity protection 300 • Greater compatibility with SATA standards 200 • Ideal for file server volumes 100 0 100 Million Files 200 Million Files 300 Million Files Windows Server 2008 R2 Windows Server 2012
- 16. ENTERPRISE-CLASS FEATURES ON LESS EXPENSIVE HARDWARE Windows Application Server or File Server • Virtualization of storage with Physical or Storage Pools and Storage Spaces virtualized deployments • Storage resilience and availability with commodity Integrated File Server Hyper-V SMB Multichannel hardware Administration Console with other • Resiliency and data Windows redundancy through Failover Clustering NTFS SMB Direct Server 2012 n-way mirroring (clustered or capabilities unclustered) or parity mode Cluster Shared NFS Windows Storage Mgmt. (unclustered) Volume • Utilization optimized through Windows thin and trim provisioning and Virtualized Storage Space Storage Space Storage Space enclosure awareness Storage • Integration with other Windows Server 2012 capabilities Storage Pool Storage Pool • Serial Attached SCSI (SAS) Physical and Serial AT Attachment Storage (SATA) interconnects 18 (Shared) SAS or SATA
- 17. ENTERPRISE-CLASS FEATURES ON LESS EXPENSIVE HARDWARE • Highly available, shared Microsoft data store for SQL Server Hyper-V Cluster SQL Server databases and Hyper-V workloads SMB • Increased flexibility, and Single Logical Server FooShare easier provisioning and File Server management Cluster • Ability to take advantage Single File System Namespace of existing network infrastructure Cluster Shared Volumes • No application downtime for planned maintenance Windows or unplanned failures with Virtualized RAID Storage Space RAID Storage Space Storage SpaceRAID failover clustering Storage Array Array Array • Highly available scale-out file server Storage Pool Storage Pool SAN • Built-in encryption Physical support Storage 19
- 19. VIRTUAL MACHINE ISOLATION AND SCALE AND PERFORMANCE MOBILITY CONTINUOUS SERVICES OPEN AND EXTENSIBLE MULTITENANCY Larger virtual Simultaneous live Clustering Open, extensible Network machines support migrations ease enhancements switch helps support Virtualization increased workloads management increase availability security and supports burdens management needs multitenancy and IP portability Hardware Shared-nothing live Dynamic Memory Increased support Resource Metering offloading offers migration enables increases capacity for Windows shows how many better performance live migration with no downtime PowerShell helps resources each tenant and scale between clusters increase automation is using 21
- 20. Run more Take advantage of demanding newer Bigger, faster virtual machines applications with hardware, while still better performance using existing Guest applications hardware to take advantage of maximum improved Non- advantage Uniform Memory Hardware Access (NUMA) offloading support 22
- 21. SCALE AND PERFORMANCE Maximum number Improvement Windows Server System Resource Windows 2008 R2 2012 factor Logical processors on hardware 64 320 5× Physical memory 1 terabyte 4 terabytes 4× Host Virtual processors per host 512 1,024 2× Virtual processors per virtual machine 4 64 16× Memory per virtual machine 64 GB 1 terabyte 16× Virtual Active virtual machines 384 1,024 2.7× machine Virtual disk size 2 terabytes 64 terabytes 32× Nodes 16 64 4× Cluster Virtual machines 1,000 8,000 8× 23
- 22. SCALE AND PERFORMANCE vNUMA node A vNUMA node B vNUMA node A vNUMA node B Non-Uniform Memory Access • Projects NUMA topology onto a virtual machine • Allows guest operating systems and applications to make intelligent NUMA NUMA node 1 NUMA node 2 NUMA node 3 NUMA node 4 decisions • Aligns guest NUMA nodes with host resources Guest NUMA topology by default matches host NUMA topology 24
- 24. Manage virtual machines independently Live migration Live migration of from underlying infrastructure within a cluster storage Shared-nothing live Hyper-V Handle changing needs on demand migration Replica 26
- 25. VIRTUAL MACHINE MOBILITY Live migration based on Modified pages transferred Memorymigration setup Storage handle moved Live server message block (SMB) share Improvements VM Modified memory pages Configuration data Memory content VM MEMORY • Faster and simultaneous migration • Live migration outside a clustered environment IP connection • Store virtual machines on a File Share SMB network storage 27
- 26. VIRTUAL MACHINE MOBILITY DiskReads are mirrored; outstanding Disk contentswrites go to to new writes and are copied new Live migration of storage Reads and writes go to the source VHD changes are replicated destination VHD Move virtual hard disks attached to a running virtual machine Computer Benefits running • Manage storage in a cloud environment Virtual machine Hyper-V with greater flexibility and control • Move storage with no downtime • Update physical storage available to a virtual machine (such as SMB-based Source device Target device storage) • Windows PowerShell cmdlets 28
- 27. VIRTUAL MACHINE MOBILITY Readswrites are mirrored; Disk and writes go to the Disk contents writes go toto new Reads and are copied the Shared-nothing live source VHD. Live Migration Live Migration Completes Live Migration Continues outstanding changes are destination VHD source VHD migration replicated Begins Source Live Migration Destination Hyper-V Configuration data Hyper-V MEMORY Modified memory pages Memory content Benefits Virtual machine Virtual machine • Increase flexibility of virtual machine IP connection placement • Increase administrator efficiency • Reduce downtime for migrations across cluster boundaries Source device Target device 29
- 29. VIRTUAL MACHINE MOBILITY New feature Primary site Replica site Replicate Hyper-V virtual machines from a Exchange virtual machine primary site to a replica site CRM virtual machine IIS virtual machine Exchange replica SQL virtual machine virtual SharePoint virtual machine machine Benefits CRM replica virtual • Affordable in-box business continuity and machine disaster recovery R2 • Failure recovery in minutes Replicate over R1 R3 P1 P2 WAN link • More secure replication across network • No need for storage arrays • No need for other software replication SMB file share SAN Hyper-V role and tools Hyper-V role and tools technologies Hyper-V Hyper-V PS Hyper-V Hyper-V PS • Automatic handling of live migration cmdlets integrated UI cmdlets integrated UI • Simpler configuration and management Send/receive replica traffic Hyper-V Management Module Hyper-V Management Module tracks and replicates changes for receives and applies the changes to each virtual machine the replica virtual machine 31
- 31. OPEN AND EXTENSIBLE Offloaded Data Transfer (ODX) Token-based data transfer between intelligent storage arrays Benefits • Rapid virtual machine provisioning and migration Token • Faster transfers on large files • Minimized latency Offload read Token Token Offload write • Maximized array throughput • Less CPU and network use Intelligent storage array • Performance not limited by network throughput or server use • Improved datacenter capacity and scale • Automation Actual data transfer Token-based copy operation 33
- 33. Extending the Hyper-V Extensible Switch For new capabilities Manageability • Windows PowerShell and scripting support Extensibility features Extension monitoring • Unified tracing and enhanced diagnostics Extension uniqueness Extensions that learn virtual machine life cycle Benefits Extensions that can veto state changes • Open platform to fuel plug-ins Multiple extensions on same switch • Free core services Integration with built-in features • Windows reliability/quality Ability to capture extensions • Unified management • Easier support • Live migration support 35
- 34. OPEN AND EXTENSIBLE Single Root I/O Virtualization Virtual machine (SR-IOV) Network stack • Increases network throughput Software NIC Virtual function (VF) • Reduces network latency • Reduces host CPU overhead for processing network traffic Benefits Hyper-V Extensible Switch • Maximizes use of host system processors and memory • Handles the most demanding workloads SR-IOV network adapter VF VF VF 36
- 35. 37
Notes de l'éditeur
- Windows Server 2012 Management has many new features and enhancements at its core. To show you some of these and their value to your organization lets walk through a number of themMultiserver ManagementIn Windows Server 2012, the capabilities of Server Manager have expanded considerably to facilitate multiserver tasks such as remote role and feature deployment to both physical and virtual servers, remote role and feature management, and custom server group creation. By using Server Manager,IT pros can now provision servers and offline virtual hard disks from their desktop without requiring either physical access to the system or Remote Desktop Protocol (RDP) connections to each server. Server Manager also helps administrators manage groups of servers collectively from within a single, integrated console, allowing them respond to business-critical problems with greater speed and agility. Server Manager can handle multiple servers in a server pool, and create server groups to organize them. The server grouping functionality resembles grouping functionality in Windows Server Update Services (WSUS), or the cloud service Windows Intune. Groups let you manage servers that are related by certain commonalities (such as location, function, Windows operating system release, or hardware type) as if they were a single unit.Role and feature deploymentWindows Server 2012 can deploy both roles and features in a single session using the unified Add Roles and Features Wizard. The Add Roles and Features Wizard in Windows Server 2012 performs validation passes on a server that you select for deployment as part of the installation process; you don’t need to pre-verify that a server in your Server Manager server pool is properly configured to support a role.Administrators can deploy roles and features to remote servers and offline virtual hard disks from Server Manager on their local server. In a single session in the Add Roles and Features Wizard, you can add your desired roles and features to an offline virtual hard disk, allowing for faster and simpler repetition and consistency of desired configurations.Integrated ConsoleWindows Server 2012 now has a fully integrated console that can Manage groups of servers collectively from within a single, integrated console, allowing you to respond to business-critical problems with greater speed and agilityGenerate status views for multiple servers after polling servers for operational statistics, including which roles and features are installed, events, service states, performance threshold alerts, and Best Practices Analyzer (BPA) scan resultsAccess to over 2,400 PowerShell 3.0 cmdletsWindows PowerShell 3.0 provides many improvements that help manage a multiserver network. These features as a whole improve manageability through improved coverage, automation, resiliency, and simplicity includingWorkflows that run long-running activities (in sequence or in parallel) to perform complex, larger management tasks, such as multi-machine application provisioning. Using Windows PowerShell Workflow, IT Pros can run tasks (workflows) that are repeatable, parallelizable, interruptible, and recoverable (suspendable/resumable).Robust Session Connectivity, which allows session to automatically recover from network failures and interruptions.Disconnected Sessions, which allows you to disconnect from an active session, shut down the computer, and reconnect from a different computer without interrupting the task.Scheduled jobs that run regularly or in response to an event to deliver standardized "lights-out" operations.Commands that can be executed with a delegated set of credentials so users with limited permissions can run critical jobs.Simplified language syntax that make commands and scripts look a lot less like code and a lot more like natural language.Improved cmdlet discovery and automatic module loading that make it easier to find and run any of the cmdlets installed on your computer.Updatable Help through the new Update-Help cmdlet, which simplifies access to the most recent Help documentation.Show-Command, a cmdlet and ISE Add-On that helps users find the right cmdlet, view its parameters in a dialog box, and run it.Disconnected SessionsWindows PowerShell 3.0 lets you disconnect from and then reconnect to any session without losing state. Disconnected Sessions allows you to create a session, start a command or job on a remote computer, disconnect from the session, shut down your computer, and then reconnect to the session from a different computer at a later time to check the job status or get the results. When administrators are disconnected from the session, persistent commands and jobs continue to run.Windows PowerShell WorkflowWindows PowerShell 3.0 goes beyond scripting and enables you to write workflows—long-running task sequences that are repeatable, parallelizable, interruptible, and restartable. Workflows are scripts written in the Windows PowerShell language, typically run from a client computer to gather data from or make changes to a few or hundreds of target computers. Workflows can be written in the Windows PowerShell language or in XAML and are executed by the Windows Workflow Foundation (WF) engine. Windows PowerShell Web AccessWindows PowerShell Web Access (PowWA) is a new feature enabled by Windows Server 2012 that lets you to manage Windows servers by using Windows PowerShell within a web browser. The target machines you want to manage can be running any version of Windows that is enabled for PowerShell remoting. Windows PowerShell ISAThe Windows PowerShell Integrated Scripting Environment (ISE) 3.0 includes many new features to ease beginning users into Windows PowerShell and provide advanced editing support for scripters. The following are some of the new features:Show-Command pane lets users find and run cmdlets in a dialog box.IntelliSense provides context-sensitive command completion for cmdlet and script names, parameter names and enumerated values, and property and method names.Code examples add reusable text to scripts and commands. The built-in code examples include templates for functions, parameters, and statements so that users don’t have to remember the syntax.Collapsible regions in scripts and XML files make navigation in long scripts easier.Script SharingWindows PowerShell 3.0 helps IT professionals by providing access to a community-generated library of Windows PowerShell code snippets, called Integrated Script Snippets, within Windows PowerShell ISE. To access Integrated Script Snippets, the user presses the keystroke (Ctrl-J). The user can then select from a list of script templates, select the appropriate template, and have partially completed script inserted into the editor. By default ISE ships with twelve script snippets to ease creating the commonly used programming syntax patterns.Syntax Simplification and IntelliSenseWindows PowerShell 3.0 includes simplified, consistent syntax across all cmdlets. The ForEach-Object and Where-Object cmdlets have been updated to support an intuitive command structure that more closely models natural language. Users are able to construct commands without script block, braces, the current object automatic variable ($_), or dot operators to get properties and methods. In short, the “punctuation” that plagued beginning users is no longer required.
- Deployment of both roles and features is combined into a single Add Roles and Features Wizard. While the process of installing roles is familiar, and consistent with the Add Roles Wizard in earlier Windows Server releases, there are changes. To support remote deployment and installations on offline virtual hard disks, some roles have moved some initial configuration (tasks formerly performed in the Add Roles Wizard during an installation) into post-installation configuration wizards. For some offline virtual hard disk deployments, installation tasks are scheduled to run the first time the machine is started.In Windows Server 2008 and Windows Server 2008 R2, you connect to a server to get to a server role, not the other way around.Note that Windows Server 2012 does not abandon the old management model; it simply expands upon it. Sometimes you need to manage a server and its roles. Sometimes you need to manage a role and its servers. A modern server operating system needs to provide this management flexibility.In Windows Server 2008 R2, roles and features are deployed by using the Add Roles Wizard or Add Features Wizard in Server Manager running on a local server. This requires either physical access to the server or Remote Desktop access by using RDP. Installing Remote Server Administration Tools lets you run Server Manager on a Windows-based client computer, but adding roles and features is disabled, because remote deployment isn’t supported.In Windows Server 2012 the deployment capabilities are extended to support robust remote deployment of roles and features. Using Server Manager in Windows Server 2012, IT pros can provision servers from their desktops without requiring either physical access to the systems or the need to enable RDP connection to each server. Windows Server 2012 with Server Manager can deploy both roles and features in a single session using the unified Add Roles and Features Wizard. The Add Roles and Features Wizard in Windows Server 2012 performs validation passes on a server you select for deployment as part of the installation process; there’s no need to pre-verify that a server in your Server Manager server pool is properly configured to support a role.When logged on to a remote virtual machine using the built-in Administrator account, administrators can deploy roles and features to offline virtual hard disks from Server Manager on their local server. In a single session in the Add Roles and Features Wizard, you can add your desired roles and features to an offline virtual hard disk, allowing for faster and simpler repetition and consistency of desired configurations.In Windows Server 2012 Server Manager is a multi-server management tool. Your servers appear all at once, and you can organize these servers into groups representing, for example, departments or locations or functions. Multiserver experienceManage groups of servers collectively from within a single, integrated consoleRespond to business-critical problems with greater speed and agilityGenerate status views for multiple servers after polling servers for operational statisticsIncludes installed roles and features, events, service states, performance threshold alerts, and Best Practices Analyzer (BPA) scan results
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Management and Automation”Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- More IntuitiveEnhanced ISE with IntellisenseSimplified language syntaxUpdatable help systemEasy command discovery and importBroader CoverageOver 2,400 cmdlets across WindowsSupport for thriving communityScript Explorer & Script LibraryGreater ResiliencyRobust session connectivityIntegrated workflowConnect/disconnect remote sessionsScheduled jobsPowerShell 3.0 is a better 2.0Many suggestions addressedOn-the-fly compilation allows scripts to run up to 6x fasterEnhanced interactive console experienceCore cmdlet and provider improvements
- Windows PowerShell 3.0 provides a comprehensive management platform for all aspects of the data center: servers, network, and storage. Windows PowerShell 3.0 includes 260 core cmdlets. Windows Server 2012 includes more than 2,400 total cmdlets in 239 available modules.New Windows PowerShell ISE Features. The Windows PowerShell Integrated Scripting Environment (ISE) 3.0 includes many new features to ease beginning users into Windows PowerShell and provide advanced editing support for scripters. Some of the new features are:Show-Command pane lets users find and run cmdlets in a dialog box. IntelliSense provides context-sensitive command completion for cmdlet and script names, parameter names and enumerated values, and property and method names. IntelliSense also supports paths, types, and variables.Code examples add reusable text to scripts and commands. The built-in code examples include templates for functions, parameters, and statements so users don’t have to remember the syntax.Syntax simplification: Windows PowerShell 3.0 includes simplified, consistent syntax across all cmdletsShow-Command pane for finding and running cmdlets in a dialog boxINTELISENSEWindows PowerShell ISE 3.0 includes many other new features to ease beginning users into Windows PowerShell and provide advanced editing support for scripters. Some of the new features are:Code examples add reusable text to scripts and commands. The built-in code examples include templates for functions, parameters, and statements so users don’t have to remember the syntax.Collapsible regions in scripts and XML files make navigation in long scripts easier.Context-sensitive command completion for cmdlet and script names, parameter names and enumerated values, and property and method namesSimplified scripting through Windows PowerShell ISE 3.0:Built-in code examples include templates for functions, parameters, and statementsUsers do not need to remember the syntaxCode examples add reusable text to scripts and commandsCMDLET DISCOVERYWindows PowerShell 3.0 helps IT pros by providing access to a community-generated library of Windows PowerShell code snippets, called Integrated Script Snippets, within Windows PowerShell ISE. To access Integrated Script Snippets, the user presses the keystroke (Ctrl+J). The user can then select from a list of script templates, select the appropriate template, and have partially completed script inserted into the editor.Windows Server 2012 includes more than 2,300 cmdlets, which you can learn and discover easily. Modules are easier than ever to find, explore, create, and use, and users no longer have to import modules manually to use cmdlets. Users can just run a cmdlet, and Windows PowerShell will import the module automatically. In addition, Get-Command has been updated to find all cmdlets installed on the system. For example, to find all networking cmdlets, you can run Get-Command *-Net*. Update-Help Install the latest Windows PowerShell Help files on the local computer. Save-Help Download the latest Windows PowerShell Help files into a network share.In Windows PowerShell 3.0, new Update-Help and Save-Help cmdlets download and install the newest Help files for each module. The cmdlets find the Help files on the Internet, determining whether they are newer than local files, unpack them, and install them in the correct location. The updated files are ready for immediate use in Get-Help—you don't need to restart Windows PowerShell. Help files for Windows PowerShell 3.0 are guaranteed to be up to date on first use because they do not ship in the box. Get-Help displays auto-generated Help for commands and then prompts you to use the Update-Help cmdlet to install or update the Help files for your modules.For some environments, such as large enterprises behind Internet firewalls, it is preferable to be able to update Help files from a local share instead of from the Internet. In these cases, you can use Save-Help -DestinationPath<share> to create a local share that stores the latest Windows PowerShell Help files. Users within the organization can then update their Help files by pointing to that share and running Update-Help –SourcePath<share>.Script Sharing:Windows PowerShell 3.0 helps IT pros by providing access to a community-generated library of Windows PowerShell code snippets, called Integrated Script Snippets, within Windows PowerShell ISE. To access Integrated Script Snippets, the user presses the keystroke (Ctrl+J). The user can then select from a list of script templates, select the appropriate template, and have partially completed script inserted into the editor.
- Session Configuration Files:Simplified process for defining a new session configuration. Administrator uses name-value pairs in a Windows PowerShell data file to specify the configuration in a declarative manner.Easier to understand how a session configuration is defined by inspecting the file.For most settings, it is simpler than writing a Windows PowerShell scriptWith the new release of Windows PowerShell, sessions aren't just persistent; they are resilient. Robust Session Connectivity allows sessions to remain in a connected state even when network connectivity is briefly disrupted.With Robust Session Connectivity, remote sessions can remain in a connected state for up to 4 minutes, even if the client computer crashes or becomes inaccessible, and tasks on the managed nodes continue to run on their own making the end to end system more reliable. If connectivity cannot be restored within 4 minutes, execution on the managed nodes is suspended with no loss of data and remote sessions automatically transition to a disconnected state, allowing them to be reconnected after network connectivity is restored. Corruption of application and system state from premature termination of running tasks due to unexpected client disconnection is virtually eliminatedThe Disconnected Sessions feature allows administrators to create a session, alter its state, disconnect from the session, and then reconnect to it from a different Windows PowerShell session. When administrators are disconnected from the session, persistent commands and jobs continue to run.The Disconnected Sessions feature works because Windows PowerShell sessions are stored on the remote (server-side) computer. This arrangement allows users to search and reconnect to sessions at a later time. Users can disconnect from and then reconnect to any session without losing state, whether they disconnect unintentionally through a network failure, or intentionally, by shutting down their computer and reconnecting from a different computer hours later.
- Windows PowerShell 3.0 provides a comprehensive management platform for all aspects of the data center: servers, network, and storage. Windows PowerShell 3.0 includes 260 core cmdlets. Windows Server 2012 includes more than 2,400 total cmdlets in 239 available modules.Workflows are scripts written in the Windows PowerShell language, typically run from a client computer to gather data from or make changes to a few or hundreds of target computers. Workflows can be written in the Windows PowerShell language or in XAML and are executed by the Windows Workflow Foundation (WF) engine. When you create a session, the session configuration defines the environment for the session. Windows PowerShell includes a specially designed session configuration or "endpoint" that’s designed to optimize Workflows. This endpoint provides the benefit of a shared hosting for Workflow execution, which in turn gives you implicit disconnect/reconnect functionality.When you add a Workflow to a Windows PowerShell session, either by typing it at the command line, including it in a script, or using the Import-Module command to import a XAML-based Workflow, it becomes a command in the session, just like a cmdlet. The component commands inside the Workflow are called activities. Each activity inherits the properties of the Workflow, including the powerful Workflow common parameters.Commands and scripts in the Workflow that restart a computer (Restart-Computer) can wait for the computer to resume, or wait for Windows PowerShell, the network, or a particular service on the restarted computer to be available. In addition, a Suspend-Resume feature enables you to stop a running workflow job and restart it later.Benefits:Simplifies administration of multiple servers, even in multiple sitesMakes cmdlets easier to learn and scripts easier to writeOffers path toward full automationEnables greater productivity
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Management and Automation”Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- While Microsoft remains committed to GUIs, the primary place GUIs should exist is on the administrator’s desktop – not on the Server.Server resources are much more expensive than client resources and running GUIs on servers requires additional software components. Every component increases the security and serviceability exposure of that server so you should only install those components that are necessary to that server workload. Fewer things running on the server means fewer patches and more resources available to the server workload.Windows Server 2012 has made several investments to help administrators succeed in choosing Server Core as the primary deployment option for Windows Server. The traditional “Server with a GUI” is still provided as a full option if required.The number of server roles that run on Server Core has increased with support for .Net Framework 4.5 included. SQL Sever 2012 now installs, eliminating the most common reason administrators cited for not being able to run in the Server Core configuration. Firewall-friendly remote management (WinRM) and Windows PowerShell are now enabled and installed by default on all servers, removing any configuration needed before being able to manage the server remotely. Windows PowerShell’s 2400+ cmdlets provide the command line coverage necessary for most admin scenarios. Microsoft has alsoreleased an updated version of the Remote Server Administrative Tools providing a rich GUI experience to manage all Servers, including Server Core, from a Windows Client.Perhaps most significantly Windows Server 2012 has added the ability to move between Server Core, Full GUI and Minimal Server Interface (MinShell) without the need to reinstall the server! This means administrators can safely start with their server deployed in the Server Core configuration and if they find they need the GUI they can add it, and also remove it as needed using the SCONFIG CLI tool, Windows PowerShell or the Add/Remove Roles and Features Wizard. Minimal Server Interface (MinShell), provides many of the benefits of Server Core while still having the safety-factor of being able to run GUIs should the administrator need to log into the Server directly.The Minimal Server Interface enables most local GUI management tasks without requiring the full GUI Shell or Internet Explorer to be installed. Technically, the Minimal Server Interface is a full Windows Server install excluding Internet Explorer, Windows shell components such as the desktop, Windows Explorer, Metro-style application support, multimedia support, and the Desktop Experience. It provides many of the benefits of Server Core (reduced footprint, attack service and serviceability) for those applications that can be made to work without IE or the Shell. We refactored all of the GUI management tools and frameworks (such as MMC.exe) into separate installable packages, and removed extra fonts and graphical resources.Minimal Server Interface can be enabled Add Roles and Features wizard, or with PowerShell.Windows Server 2012 empowers administrators to deploy servers with “just enough” of content and capabilities to fulfill their server’s desired function. By increasing deployment agility and refactoring monolithic components – such as the Windows Foundation – into smaller, installable packages, we’re putting more power in the hands of system administrators than ever before.
- Windows Server 2012 Networking has many new features and enhancements at its core. To show you some of these and their value to your organization lets walk through a number of themNIC TeamingNIC teaming allows you to grow bandwidth while also protecting the services hosted on the server from network or hardware outages. Aside from being vendor-neutral, the other advantage of using Windows Server 2012 to team network adapters is that it’s done through the operating system, therefore requires no installing and configuring special drivers and can support multiple teams that are all managed through the same management interface.Network VirtualizationNetwork Virtualization extends the concept of server virtualization to permit multiple virtual networks, potentially with overlapping IP addresses, to be deployed on the same physical network. With Hyper‑V Network Virtualization, you can set policies that isolate traffic in your dedicated virtual network independently of the physical infrastructure for fully secure and isolated multi-tenancy. Network Virtualization also provides IP Portability, and the ability for you to move Virtual Machines across physical subnets without changing your address space. You VM’s can keep there IP address whether moving across servers, racks, buildings, geographies or even to the cloud – no more need to reconfigure complex VLANs or adjust your address space to suite the destination environment.DHCP server failoverWindows Server 2012 scans, isolates, and responds to unexpected server problems by supporting the Dynamic Host Configuration Protocol (DHCP) failover protocol as described in the Internet Engineering Task Force (IETF) Internet Draft. Through this protocol, the DHCP Server Failover feature enables two DHCPv4 servers to synchronize lease information almost instantly and to provide high availability of DHCP service. If one of the servers becomes unavailable, the other server assumes responsibility for servicing clients for the same subnet.SR-IOVWindows Server 2012 adds the ability to assign SR-IOV functionality from physical devices directly to virtual machines. This gives VMs the ability to bypass the software-based Hyper-V Virtual Switch, and directly address the NIC. As a result, CPU overhead and latency is reduced, with a corresponding rise in throughput. SR-IOV works in conjunction with system chipset support for virtualization technologies that provide remapping of interrupts and Direct Memory Access (DMA) and lets SR-IOV-capable devices be assigned directly to a virtual machine. Hyper‑V in Windows Server 2012 enables support for SR‑IOV–capable network devices and lets an SR‑IOV virtual function of a physical network adapter be assigned directly to a virtual machine. Resource MeteringWindows Server 2012 Hyper‑V introduces Resource Metering, a technology that helps you track historical data of the use of virtual machines. With Resource Metering, you can gain insight into the resource use of specific servers. You can use this data to perform capacity planning, to monitor consumption by different business units or customers, or to capture data needed to help redistribute the costs of running a workload. You could also use the information that this feature provides to help build a billing solution, so that customers of your hosting Dynamic Virtual Machine QueueVirtual machine queue (VMQ) is a feature available to computers that have VMQ-capable network hardware. VMQ uses hardware packet filtering to deliver packet data from an external virtual machine network directly to virtual machines, which reduces the overhead of routing packets and copying them from the management operating system to the virtual machine. With VMQ, a dedicated queue is established on the physical network adapter for each virtual network adapter that has requested a queue. As packets arrive for a virtual network adapter, the physical network adapter places them in that network adapter’s queue. When packets are indicated up, all the packet data in the queue is delivered directly to the virtual network adapter. Packets arriving for virtual network adapters that don’t have a dedicated queue, as well as all multicast and broadcast packets, are delivered to the virtual network in the default queue. The virtual network handles routing of these packets to the appropriate virtual network adapters as it normally would.IP Address Management (IPAM)IPAM in Windows Server 2012 is a new built-in framework for discovering, monitoring, auditing, and managing the IP address space used on a corporate network. IPAM provides for administration and monitoring of servers running Dynamic Host Configuration Protocol (DHCP) and Domain Name Service (DNS). IPAM includes components for:Automatic IP address infrastructure discovery: IPAM discovers domain controllers, DHCP servers, and DNS servers in the domains you choose. You can enable or disable management of these servers by IPAM.Custom IP address space display, reporting, and management: The display of IP addresses is highly customizable and detailed tracking and utilization data is available. IPv4 and IPv6 address space is organized into IP address blocks, IP address ranges, and individual IP addresses. IP addresses are assigned built-in or user-defined fields that can be used to further organize IP address space into hierarchical, logical groups.Audit of server configuration changes and tracking of IP address usage: Operational events are displayed for the IPAM server and managed DHCP servers. IPAM also enables IP address tracking using DHCP lease events and user logon events collected from Network Policy Server (NPS), domain controllers, and DHCP servers. Tracking is available by IP address, client ID, host name, or user name.Monitoring and management of DHCP and DNS services: IPAM enables automated service availability monitoring for Microsoft DHCP and DNS servers across the forest. DNS zone health is displayed, and detailed DHCP server and scope management is available using the IPAM console.Quality of Service (QoS)QoS is a set of technologies for managing network traffic in a cost effective manner, to enhance user experiences in enterprise environments, as also in home and small offices. QoS technologies allow you to measure bandwidth, detect changing network conditions (such as congestion or availability of bandwidth), and prioritize or throttle traffic. For example, you can use QoS to prioritize traffic for latency-sensitive applications (such as voice or video), and to control the impact of latency-insensitive traffic (such as bulk data transfers). For network administrators, QoS in Windows Server2012 is designed to help manage network traffic on the physical network and on the virtual network. Policy-based QoS is designed to manage traffic on the physical network. And a new functionality in QoS, referred to in this document as Hyper-V QoS, is designed to manage traffic on the virtual network. BranchCacheBranchCache is a wide area network (WAN) bandwidth optimization technology.To optimize WAN bandwidth when users access content on remote servers, BranchCache copies content from your main office or hosted cloud content servers and caches the content at branch office locations, allowing client computers at branch offices to access the content locally rather than over the WAN.At branch offices, content is stored either on servers that are configured to host the cache or, when no server is available in the branch office, on client computers that are running Windows 8 or Windows 7. After a client computer requests and receives content from the main office and the content is cached at the branch office, other computers at the same branch office can obtain the content locally rather than downloading the content from the content server over the WAN link. When subsequent requests for the same content are made by client computers, the clients download content information from the server instead of the actual content. Content information consists of hashes that are calculated using chunks of the original content, and are extremely small compared to the content in the original data. Client computers then use the content information to locate the content from a cache in the branch office, whether the cache is located on a client computer or on a server. Client computers and servers also use content information to secure cached content so that it cannot be accessed by unauthorized users.BranchCache increases end user productivity by improving content query response times for clients and servers in branch offices, and can also help improve network performance by reducing traffic over WAN links.SMB Direct and MultichannelSMB Multichannel enables aggregation of network bandwidth and network fault tolerance if multiple paths are available between the SMB 3.0 client and the SMB 3.0 server. This enables server applications to take full advantage of all available network bandwidth and be resilient to a network failure.SMB Direct supports the use of network adapters that have RDMA capability and can function at full speed with very low latency, while using very little CPU. For workloads such as Hyper-V or Microsoft SQL Server, this enables a remote file server to resemble local storage.
- Note to presenter: 7 clicks in build.Hyper-V Network Virtualization extends the concept of server virtualization to allow multiple virtual networks, potentially with overlapping IP addresses, to be deployed on the same physical network. With Hyper-V Network Virtualization, you can set policies that isolate traffic in your dedicated virtual network, independent of the physical infrastructure. This diagram illustrates how you can use Hyper-V Network Virtualization to isolate network traffic belonging to two different customers. In the figure, Blue and Red virtual machines are hosted on a single physical network, or even on the same physical server. However, because they belong to separate virtual networks, the Blue Network and the Red Network, the virtual machines can’t communicate with each other even if the customers assign them IP addresses from the same address space. Highlights:Location-independent addressing by virtualizing the IP address.Creation of virtual layer-2/layer-3 topologies over any physical network that supports bidirectional IP connectivity.A physical network that can be a hierarchical three-tier network, a full bi-section bandwidth Clos network, or a large layer-2 network.Virtual networks that can span multiple physical subnets and multiple sites.
- Note to presenter: 3 clicks to complete build.Windows Server 2012 helps you provide fault tolerance on your network adapters without having to buy additional hardware and software. Windows Server 2012 includes NIC Teaming as a new feature, which allows multiple network interfaces to work together as a team, preventing connectivity loss if one network adapter fails. It allows a server to tolerate network adapter and port failure up to the first switch segment. NIC Teaming also allows you to aggregate bandwidth from multiple network adapters, for example, so four 1‑gigabyte (GB) network adapters can provide an aggregate of 4 GB/second of throughput.The advantages of a Windows teaming solution are that it works with all network adapter vendors, spares you from most potential problems that proprietary solutions cause, provides a common set of management tools for all adapter types, and is fully supported by Microsoft.Teaming network adapters involves the following:NIC Teaming configurations. Two or more physical network adapters connect to the NIC Teaming solution’s multiplexing unit and present one or more “virtual adapters” (team network adapters) to the operating system. Algorithms for traffic distribution. Several different algorithms distribute inbound and outbound traffic between the network adapters. Team network adapters exist in third-party NIC Teaming solutions to divide traffic by virtual local area network (VLAN) so that applications can connect to different VLANs simultaneously. Like other commercial implementations of NIC Teaming, Windows Server 2012 has this capability.
- Note to presenter: 3 clicks to build.SMB Direct is a new class of SMB file storage connectivity that allows RDMA-compliant network adapters to offload the network I/O processing from the CPU onto the NIC. Essentially, RDMA bypasses the network stack, allowing the adapter to approach full performance capacity, which is especially useful when accessing storage over a network since it offers a more direct path to the storage itself. SMB Direct can work with SMB Multichannel (something we talk about on the next slide) to deliver high-performance storage network capability with failover resiliency. However, because RDMA bypasses the network stack, it does not work with Windows Server 2012 NIC Teaming. Still, when dealing with storage network, MPIO and SMB MultiChannel are preferred over NIC Teaming anyway so this shouldn’t be a concern.Also worth a mention, RDMA compatibility is currently limited to InfiniBand, iWARP, and RoCE (RDMA over Converged Ethernet) as of this publication.
- Windows Server 2012 has many new features and enhancements related to storage and supporting application storage. To show you some of these and their value to your organization lets walk through a number of themStorage SpacesStorage Spaces enables you to deliver a new category of highly capable storage solutions to ITat a dramatically lower price point. Storage Spaces is flexible, allowing you to leverage SAS, Shared SAS, or SATA interconnects to build virtualized storage pools from which you can build various volumes to provide for your storage requirements. Storage Spaces volumes can be configured with RAID0, RAID1, or RAID5 equivalent striping to offer varied levels of performance and data protection as needed.File system improvementsWindows Server 2012 includes new file system enhancements including the introduction of the new Resilient File System (ReFS) storage standard, and delivers the ability to deploy 64 TB volumes through improved NTFS and ReFS availability features. Specifically, Windows Server 2012 takes a new approach to correctly identify and eliminate transient error conditions while keeping the file system accessible. This new approach prioritizes file system availability even when corruption is present, and delivers on a new model for managing file system corruption.ReFS is an update to the NTFS standard, and adds support for SCSI storage devices. ReFS also includes improved support for SATA storage standards, which means that ReFS offers more performance and features that work with SATA than NTFS currently provides. Among the benefits of ReFS with SATA is better resilience against corruption caused by unexpected power loss conditions, and better utilization of read and write drive caching. Further enhancements include:Improved self-healing. ReFS and NTFS instantaneously self-heal more issues online without requiring Chkdsk to run. This reduces Chkdsk execution frequency.Online analysis. The time needed to scan and analyze the volume is a background task performed while the volume remains online. Corruption correction. Upon completion of an online scan, a determination is made whether the volume must be taken offline to complete the repair. Chkdsk directly fixes the previously identified corruption, and the offline time is reduced to seconds. Consequently, volume unavailability is no longer proportional to the number of files on the volume, but rather to the number of corruptions on the volume.Thin Provisioning“Get thin” and “stay thin” through new native support for thin provisioning and trim, which is the ability to provision storage as needed and to reclaim storage that is no longer needed. Instead of removing redundant data on the volume, thin provisioning gains efficiencies by enabling you to allocate just enough storage at the moment of storage allocation, and then increase capacity as your business needs grow over timeCluster Shared VolumeNot just for Microsoft Hyper-V any longer, this popular shared file storage solution gives administrators the flexibility to house storage and applications in a consolidated cluster while taking advantage of many other new Windows Server 2012 features. With CSVs, all cluster hosts have simultaneous access to a single shared volume through a shared namespaces to share configurations across all cluster nodes, including the ability to build continuously available cluster-wide file systems. Application storage can be served from the same share as data, eliminating the need to deploy two clusters, an application and separate storage cluster, to support true high availability application scenarios.SMB 3.0 for workloadsWindows Server 2012 now offers support for application-based file shares. This application support for SQL and Hyper-V allows you to leverage the high-performance and high availability features now available with Windows Server 2012 for your SQL databases or your Hyper-V guests. For example, by leveraging SMB Direct and SMB Multichannel on a file server hosting the VHDX drives for your Hyper-V cluster, you can see storage performance on your Hyper-V guests that approaches that of a built-in server storage. No only that, but those Hyper-V guests enjoy the resiliency of a failover network to help avoid any outages.Offloaded Data TransferOffloaded Data Transfers (ODX) in Windows Server 2012 enables you to accomplish more with your existing hardware infrastructure by letting you quickly move large files and virtual machines directly between storage arrays, which reduces host CPU and network resource consumption. ODX enables rapid provisioning and migration of virtual machines and provides significantly faster transfers of large files such as database or video files. By offloading the file transfer to the storage array, ODX minimizes latencies, maximizes the use of array throughput, and reduces host resource usage such as CPU and network consumption. File transfers are automatically and transparently offloaded when you move or copy files, regardless of whether you perform drag-and-drop through Windows Explorer or use command-line file copy commands. No administrator setup or intervention is needed.Transparent FailoverA new runtime infrastructure for failover clustering allows Windows Server 2012 to perform failover operations on clustered storage so quickly that most applications and services relying on that high-availability experience no downtime at all. If anything, business critical applications like SQL and Hyper-V may see a small I/O hiccup during a failover, but that delay occurs so quickly that everything is transparent to server applications and no errors are generated. Transparent failover takes effect during planned and unplanned outages alike, so transparent failover keeps your applications and services running through hardware failures, software failures, rebalancing operations, and even during cluster updates or other maintenance, freeing administrators from constraining downtime windows and keeping users productive 24/7, 365 days a year.NFS SupportFile-based storage has become a practical alternative to more expensive SAN storage because file-based storage is straightforward to provision and file-based storage has gained viability as an alternative to more expensive SAN storage because it is simple to provision and manage. An example of this trend is the recent popularity of deploying and running VMware ESX/ESXi virtual machines from file-based storage accessed over the NFS protocol. To help you take advantage of this, Windows Server 2012 includes an updated Server for NFS that supports NFS version 4.1 and can leverage many other performance, reliability, and availability enhancements available throughout the Windows storage stack.iSCSI TargetTake advantage of low-cost servers providing block storage. One use case for iSCSI Target is the diskless Internet SCSI (iSCSI) boot services, which provide storage provisioning capabilities that are traditionally reserved only for high-end storage devices now fully integrated into Windows Server 2012. In this release, the iSCSI Target has been continuously improving the performance and scalability; ultimately, the iSCSI Target feature built into Windows Server 2012 lets you create a SAN storage device on any hardware and gives you the power to store operating system images in a centralized location to improve efficiency, manageability, availability, and security.Storage ManagementAlong with the growing and costly demand for storage, storage infrastructure complexity brings additional costs that need to be addressed. To help improve storage management efficiency and offset that cost, Windows Server 2012 will come with a set of storage management APIs and provider interfaces that will enable administrators to centrally manage disparate storage resources and solutions, like SANs and storage arrays, from a centralized “single pane of glass” interface. Manageable resources can include SANs that are SMI-S complaint, storage devices with proprietary hardware that has compatible third-party storage management providers, or storage devices that are already being allocated through the use of Storage Spaces. This storage management capability will allow administrators to configure and manage all of the storage devices throughout their organization or management sphere through an easy-to-use management interface that they are already familiar with, the Server Manager. By using Server Manager, administrators can populate server groups with file servers or storage clusters that leverage Storage Spaces, or reach out to populate manageable devices that have SMI-S agents enabled.
- Windows Server 2012 introduces a newly engineered file system called Resilient File System (ReFS) that is built on the foundations of NTFS to maintain compatibility with that highly popular file system while also architected to support a new generation of storage technologies and scenarios. ReFS was designed with three key goals in mind: • Maintain compatibility with the NTFS features that are widely adopted and successful while replacing features that provide limited value. • Maintain the highest levels of system availability and reliability possible under the assumption that underlying storage may be inherently unreliable. • Provide a full end-to-end resilient architecture when used in conjunction with Storage Spaces so that these two features magnify the capabilities and reliability of the other when used together. Uses “Copy on Write” method to update files and saves file to new location every time it is updated there-by avoiding corruptions caused during disk power outage.Checksums on all metadata in ReFS are performed at the tree level and these checksums are stored independently from the tree page itself. This enables the detection of all forms of disk corruption, including degradation of data on media. Along with Storage Spaces, ReFS forms the storage foundation on Windows for the next decade and beyond with features that enabled significant storage stability, flexibility, scalability, and availability,
- We have had virtualization at Hyper-V layer over the last couple of releases of Windows server. With Windows Server 2012, we give you the ability to virtualize your storage solution. Storage spaces gives you the ability to consolidate all your SAS and SATA connected disks – no matter whether they are SSDs or traditional HDDs and consolidate them together as storage Pools. Once you have the storage pools created, you can cave our virtual disks or Storage Spaces that can be exposed out as volume shares to your VMs or applications. Storage Spaces is compatible with other Windows Server 2012 storage features, like SMB Direct and SMB Failover Clustering, so you can use simple inexpensive storage devices to create powerful and resilient storage infrastructures on a limited budget. Storage Spaces is also flexible, allowing you to leverage SAS, Shared SAS, or SATA interconnects to build virtualized storage pools from which you can build various volumes to provide for your storage requirements. Storage Spaces volumes can be configured with RAID0, RAID1, or RAID5 equivalent striping to offer varied levels of performance and data protection as needed.Storage Spaces enable you to deliver a new category of highly capable storage solutions to all Windows customer segments at a dramatically lower price point. At the same time, you can maximize your operations by leveraging commodity storage to supply high-performance and feature-rich storage to servers, clusters, and applications alike.
- Windows Server 2012 now offers support for application-based file shares. This application support for SQL and Hyper-V allows you to leverage the high-performance and high availability features now available with Windows Server 2012 for your SQL databases or your Hyper-V guests. Enables virtual machines and virtual machine storage to reside on SMB network shares, giving you the power to design new flexible storage solutions for your virtual or cloud infrastructure. For example, by leveraging SMB Direct and SMB Multichannel on a file server hosting the VHDX drives for your Hyper-V cluster, you can see storage performance on your Hyper-V guests that approaches that of a built-in server storage. No only that, but those Hyper-V guests enjoy the resiliency of a failover network to help avoid any outages.With other features, like Cluster-Aware Updating, you can deploy updates to file clusters hosting your applications without any downtime and minimal administrative overhead. SMB support for applications also gives you additional flexibility for storage design in addition to the standard storage options like iSCSI, SANs, or direct-attached storage.To help deliver storage for clusters that can grow to such a massive scale, you can also leverage the scalability offered by SMB clusters. File server clusters offer high-availability features that can also support your high-density workloads like SQL and Hyper-V. Storage clusters offer the convenience of single file system namespaces along with transparent failover and cluster-aware update automation to ensure that you file shares are always accessible.Also, did I happen to mention that SMB clusters support active/active clustering access?So no matter what your underlying storage subsystem is, SMB provides an easy and highly available repository for your SQL databases and Hyper-V VMs.
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Storage”Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- There are many new features within Windows Server 2012 Hyper‑V to support those needs and challenges of an organization or a customer. These are just a few of the more important ones. Virtual machines running on Windows Server 2012 Hyper‑V are much larger than what they were with Windows Server 2008 R2 or even SP1. So we have given them the larger virtual machines and we’ve been able to increase performance through hardware offloading to allow better performance and more scale within that physical host.Things like multiple simultaneous live migrations which allows you to quickly move virtual machines around between hosts whether they are on the same cluster or using technologies like shared nothing live migration to move virtual machinesacross multiple different clusters.The many different VM availability options that give you lots of flexibility and the ability to meet the availability demands that your organizations require. You need these machines to be more available and thus, under VM availability, we have added many clustering enhancements to increase that availability of keeping the virtual machine up and running as well as being able to do things to the virtual machine without taking it down, thereby, increasing the availability Things like dynamic memory enhancements where we can increase the memory capacity to a virtual machine without any downtime to the VM. We don’t do this all by ourselves; we have support from our customers and our partners to create extensions to their Hyper-V infrastructure. With an open and extensible virtual switch we allow different third-party vendors to create plugins that will handle specific tasks within this switch to help support security and management needs. This will also help organizations who want to customize aspects of running their infrastructure by giving them the ability to automate tasks through our enhanced support of Windows PowerShell.You need to be able to handle multitenant environments and in those multitenant environments, we use capabilities like network virtualization and resource metering to better support these multitenant environments and report back on the quantity of resources your virtual machines are using.
- NOTE: This slide is animated and has 3 clicks[Click]The first scenario we are going to talk about is how you can achieve greater densities and run more demanding workloads through the Scale and Performance improvements of Windows Server 2012 Hyper-V. Within your organization, as you virtualize more of your infrastructure you need to have a platform, a hypervisor, that can support your most demanding workloads.[Click]Also, as you adopt newer hardware, you will need to be able to utilize the advancements within the hardware to the fullest, without losing the capability of the existing investments in infrastructure you already have.[Click]We do this through new features and updates delivered with Windows Server 2012 Hyper-V like:Bigger, faster virtual machinesHardware offloadingNon-Uniform Memory Access (NUMA) support
- Before Windows Server 2012Hyper‑V in Windows Server 2008 R2 supported configuring virtual machines with a maximum of four virtual processors and up to 64 GB of memory. However, IT organizations increasingly want to use virtualization when they deploy mission‑critical, tier-1 business applications. Large, demanding workloads such as online transaction processing (OLTP) databases and online transaction analysis (OLTA) solutions typically run on systems with 16 or more processors and demand large amounts of memory. For this class of workloads, more virtual processors and larger amounts of virtual machine memory are a core requirement.Hyper-V in Windows Server 2012Hyper‑V in Windows Server 2012greatly expands support for host processors and memory. New features include support for up to 64 processors and 1 TB of memory for Hyper‑V guests, a new VHDX virtual hard disk format with larger disk capacity of up to 64 TB (see the section, “New virtual hard disk format“), and additional resiliency. These features help ensure that your virtualization infrastructure can support the configuration of large, high-performance virtual machines to support workloads that might need to scale up significantly.
- Windows Server 2012 Hyper‑V supports NUMA in a virtual machine. What is NUMA?NUMA, or Non-Uniform Memory Access, refers to a computer architecture in multiprocessor systems in which the time required for a processor to access memory depends on the memory’s location relative to the processor. With NUMA, a processor can access local memory (memory attached directly to the processor) faster than it can access remote memory (memory that is local to another processor in the system). Modern operating systems and high-performance applications such as SQL Server have developed optimizations to recognize the system’s NUMA topology and consider NUMA when they schedule threads or allocate memory to increase performance.Guest NUMAProjecting a virtual NUMA topology onto a virtual machine provides optimal performance and workload scalability in large virtual machine configurations. It does this by allowing the guest operating system and applications such as SQL Server to take advantage of their inherent NUMA performance optimizations (for example, making intelligent NUMA decisions about thread and memory allocation). The default virtual NUMA topology projected into a virtual machine running Hyper‑V is optimized to match the host’s NUMA topology, as shown in the figure.
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Server Virtualization Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- NOTE: This slide is animated and has 3 clicksIn this scenario we will discuss how you can achieve Increased business flexibility with virtual machine mobility.[Click]What we are going to talk about here are the different ways of moving a virtual machine around between different servers, the things that we have done with Windows Server 2012 Hyper‑V that allow us to gain a benefit for our customers of being able to manage the virtual machines independently of thier underlying and physical infrastructure.[Click]Also, you need to be able to handle the changes in demand as they occur. You have a need to rebalance where the virtual machines are located either via through the servers the VMs reside on, or the storage resources used by the virtual machine.[Click]Within Windows Server 2012 we provide these values through:Live Migration within a clusterLive Migration of storageShared nothing live migrationHyper-V Replica
- NOTE: This slide is animated and has 5 clicksTo maintain optimal use of physical resources and to add new virtual machines easily, you must be able to move virtual machines whenever necessary – without disrupting your business. Windows Server 2008 R2 introduced live migration, which made it possible to move a running virtual machine from one physical computer to another with no downtime and no service interruption. However, this assumed that the virtual hard disk for the virtual machine remained consistent on a shared storage device such as a Fibre Channel or iSCSI SAN. In Windows Server 2012, live migrations are no longer limited to a cluster and virtual machines can be migrated across cluster boundaries, including to any Hyper-V host server in your environment. Hyper-V builds on this feature, adding support for simultaneous live migrations, enabling you to move several virtual machines at the same time. When combined with features such as Network Virtualization, this feature even allows virtual machines to be moved between local and cloud hosts with ease.In this example, we are going to show how live migration works when connected to an SMB File Share. With Windows Server 2012 and SMB3, you can store your virtual machine hard disk files and configuration files on an SMB share and live migrate the VM to another host whether that host is part of a cluster or not.[Click]Live migration setup: During the live migration setup stage, the source host creates a TCP connection with the destination host. This connection transfers the virtual machine configuration data to the destination host. A skeleton virtual machine is set up on the destination host, and memory is allocated to the destination virtual machine.[Click]Memory page transfer: In the second stage of a SMB-based live migration, the memory that is assigned to the migrating virtual machine is copied over the network from the source host to the destination host. This memory is referred to as the “working set” of the migrating virtual machine. A page of memory is 4 KB.During this phase of the migration, the migrating virtual machine continues to run. Hyper-V iterates the memory copy process several times, with each iteration requiring a smaller number of modified pages to be copied. After the working set is copied to the destination host, the next stage of the live migration begins.[Click]Memory page copy process: This stage is a memory copy process that duplicates the remaining modified memory pages for “Test VM” to the destination host. The source host transfers the CPU and device state of the virtual machine to the destination host.During this stage, the available network bandwidth between the source and destination hosts is critical to the speed of the live migration. Use of a 1‑gigabit Ethernet (GbE) or faster connection is important. The faster the source host transfers the modified pages from the migrating virtual machine’s working set, the more quickly live migration is completed.The number of pages transferred in this stage is determined by how actively the virtual machine accesses and modifies the memory pages. The more modified pages, the longer it takes to transfer all pages to the destination host.[Click]Moving the storage handle from source to destination: During this stage of a live migration, control of the storage that is associated with “Test VM”, such as any virtual hard disk files or physical storage attached through a virtual Fibre Channel adapter, is transferred to the destination host. (Virtual Fibre Channel is also a new feature of Hyper-V. For more information, see “Virtual Fibre Channel in Hyper-V”). The following figure shows this stage.[Click]Bringing the virtual machine online on the destination server: In this stage of a live migration, the destination server has the up-to-date working set for the virtual machine and access to any storage that the VM uses. At this time, the VM resumes operation.Network cleanup: In the final stage of a live migration, the migrated virtual machine runs on the destination server. At this time, a message is sent to the network switch, which causes the switch to obtain the new MAC addresses of the migrated virtual machine so that network traffic to and from the VM can use the correct switch port.The live migration process completes in less time than the TCP time-out interval for the virtual machine that is being migrated. TCP time-out intervals vary based on network topology and other factors.
- NOTE: This slide is animated and has 3 clicksNot only can we live migrate a virtual machine between two physical hosts, Hyper‑V in Windows Server 2012 introduces live storage migration, which lets you move virtual hard disks that are attached to a running virtual machine without downtime. Through this feature, you can transfer virtual hard disks, with no downtime, to a new location for upgrading or migrating storage, performing backend storage maintenance, or redistributing your storage load. You can perform this operation by using a new wizard in Hyper‑V Manager or the new Hyper‑V cmdlets for Windows PowerShell. Live storage migration is available for both storage area network (SAN)-based and file-based storage.When you move a running virtual machine’s virtual hard disks, Hyper‑V performs the following steps to move storage:Throughout most of the move operation, disk reads and writes go to the source virtual hard disk.[Click]After live storage migration is initiated, a new virtual hard disk is created on the target storage device. While reads and writes occur on the source virtual hard disk, the disk contents are copied to the new destination virtual hard disk.[Click]After the initial disk copy is complete, disk writes are mirrored to both the source and destination virtual hard disks while outstanding disk changes are replicated.[Click]After the source and destination virtual hard disks are synchronized, the virtual machine switches over to using the destination virtual hard disk.The source virtual hard disk is deleted.Just as virtual machines might need to be dynamically moved in a cloud data center, allocated storage for running virtual hard disks might sometimes need to be moved for storage load distribution, storage device servicing, or other reasons.[Additional information]Updating the physical storage that is available to Hyper‑V is the most common reason for moving a virtual machine’s storage. You also may want to move virtual machine storage between physical storage devices, at runtime, to take advantage of new, lower-cost storage that is supported in this version of Hyper‑V, such as SMB-based storage, or to respond to reduced performance that can result from bottlenecks in the storage throughput. Windows Server 2012 provides the flexibility to move virtual hard disks both on shared storage subsystems and on non-shared storage as long as a Windows Server 2012 SMB3 network shared folder is visible to both Hyper‑V hosts.You can add physical storage to either a stand-alone system or to a Hyper‑V cluster and then move the virtual machine’s virtual hard disks to the new physical storage while the virtual machines continue to run.Storage migration, combined with live migration, also lets you move a virtual machine between hosts on different servers that are not using the same storage. For example, if two Hyper‑V servers are each configured to use different storage devices and a virtual machine must be migrated between these two servers, you can use storage migration to a shared folder on a file server that is accessible to both servers and then migrate the virtual machine between the servers (because they both have access to that share). Following the live migration, you can use another storage migration to move the virtual hard disk to the storage that is allocated for the target server.You can easily perform the live storage migration using a wizard in Hyper‑V Manager or Hyper‑V cmdlets for Windows PowerShell.BenefitsHyper‑V in Windows Server 2012 lets you manage the storage of your cloud environment with greater flexibility and control while you avoid disruption of user productivity. Storage migration with Hyper‑V in Windows Server 2012 gives you the flexibility to perform maintenance on storage subsystems, upgrade storage appliance firmware and software, and balance loads as capacity is used without shutting down virtual machines.Requirements for live storage migrationWindows Server 2012.The Hyper‑V role.Virtual machines configured to use virtual hard disks for storage.
- NOTE: This slide is animated and has 4 clicksWith Windows Server 2012 Hyper-V, you can also perform a “Shared Nothing” Live Migration where you can move a virtual machine, live, from one physical system to another even if they don’t have connectivity to the same shared storage. This is useful, for example, in a branch office where you may be storing the virtual machines on local disk, and you want to move a VM from one node to another. This is also especially useful when you have two independent clusters and you want to move a virtual machine, live, between them, without having to expose their shared storage to one another. You can also use “Shared Nothing” Live Migration to migrate a virtual machine from one datacenter to another provided your bandwidth is large enough to transfer all of the data between the datacenters.As you can see in the animation, when you perform a live migration of a virtual machine between two computers that do not share an infrastructure, Hyper-V first performs a partial migration of the virtual machine’s storage by creating a virtual machine on the remote system and creating the virtual hard disk on the target storage device.[Click]While reads and writes occur on the source virtual hard disk, the disk contents are copied over the network to the new destination virtual hard disk.This copy is performed by transferring the contents of the VHD between the two servers over the IP connection between the Hyper-V hosts.[Click]After the initial disk copy is complete, disk writes are mirrored to both the source and destination virtual hard disks while outstanding disk changes are replicated.This copy is performed by transferring the contents of the VHD between the two servers over the IP connection between the Hyper-V hosts.[Click]After the source and destination virtual hard disks are synchronized, the virtual machine live migration process is initiated, following the same process that was used for live migration with shared storage.After the virtual machine’s storage is migrated, the virtual machine migrates while it continues to run and provide network services. [Click]After the live migration is complete and the virtual machine is successfully running on the destination server, the files on the source server are deleted.
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Server Virtualization Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- Current situationBusiness continuity is the ability to quickly recover business functions from a downtime event with minimal or no data loss. There are number of reasons why businesses experience outage including power failure, IT hardware failure, network outage, human errors, IT software failures, and natural disasters. Depending on the type of outage, customers need a high availability solution that simply restores the service. However, some outages that impact the entire data center such as natural disaster or an extended power outage require a disaster recovery solution that restores data at a remote site in addition to bringing up the services and connectivity. Organizations need an affordable and reliable business continuity solution that helps them recover from a failure.Before Windows Server 2012Beginning with Windows Server 2008 R2, Hyper‑V and Failover Clustering can be used together to make a virtual machine highly available and minimize disruptions. Administrators can seamlessly migrate their virtual machines to a different host in the cluster in the event of outage or to load balance their virtual machines without impacting virtualized applications. While this can protect virtualized workloads from a local host failure or scheduled maintenance of a host in a cluster, this does not protect businesses from outage of an entire data center. While Failover Clustering can be used with hardware-based SAN replication across data centers, these are typically expensive. Hyper‑V Replica fills an important gap in the Windows Server Hyper‑V offering by providing an affordable in-box disaster recovery solution. Windows Server 2012 Hyper‑V ReplicaWindows Server 2012 introduces Hyper‑V Replica, a built-in feature that provides asynchronous replication of virtual machines for the purposes of business continuity and disaster recovery. In the event of failures (such as power failure, fire, or natural disaster) at the primary site, the administrator can manually fail over the production virtual machines to the Hyper‑V server at the recovery site. During failover, the virtual machines are brought back to a consistent point in time, and within minutes they can be accessed by the rest of the network with minimal impact to the business. Once the primary site comes back, the administrators can manually revert the virtual machines to the Hyper‑V server at the primary site.Hyper‑V Replica is a new feature in Windows Server 2012. It lets you replicate your Hyper‑V virtual machines over a network link from one Hyper‑V host at a primary site to another Hyper‑V host at a Replica site without reliance on storage arrays or other software replication technologies. Benefits of Hyper‑V ReplicaHyper‑V Replica fills an important gap in the Windows Server Hyper‑V offering by providing an affordable in-box business continuity and disaster recovery solution. Failure recovery in minutes. In the event of an unplanned shutdown, Hyper‑V Replica can restore your system in just minutes.More secure replication across the network. Hyper‑V Replica tracks the write operations on the primary virtual machine and replicates these changes to the Replica server efficiently over a WAN. The network connection between the two servers uses the HTTP or HTTPS protocol and supports both integrated and certificate-based authentication. Connections configured to use integrated authentication are not encrypted; for an encrypted connection, you should choose certificate-based authentication. Hyper‑V Replica is closely integrated with Windows failover clustering and provides easier replication across different migration scenarios in the primary and Replica servers.Hyper‑V Replica doesn’t rely on storage arrays.Hyper‑V Replica doesn’t rely on other software replication technologies.Hyper‑V Replica automatically handles live migration.Configuration and management are simpler with Hyper‑V Replica:Integrated user interface (UI) with Hyper‑V Manager. Failover Cluster Manager snap-in for Microsoft Management Console (MMC).Extensible WMI interface.Windows PowerShell command-line interface scripting capability.RequirementsTo use Hyper‑V Replica, you need two physical computers configured with:Windows Server 2012.Hyper‑V server role.Hardware that supports the Hyper‑V role.Sufficient storage to host the files that virtualized workloads use. Additional storage on the Replica server based on the replication configuration settings may be necessary.Sufficient network bandwidth among the locations that host the primary and Replica servers and sites.Firewall rules to permit replication between the primary and Replica servers and sites.Failover Clustering feature, if you want to use Hyper‑V Replica on a clustered virtual machine.
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Server Virtualization Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- Crucial maintenance tasks for virtual hard disks, such as merge, move, and compact, depend on copying large amounts of data. SAN vendors are working to provide near-instantaneous copy operations of large amounts of data. This storage lets the system above the disks specify the move of a specific data set from one location to another, a hardware feature known as a copy offload. In Windows Server 2012, Hyper‑V takes advantage of the new SAN copy offload innovations to copy large amounts of data from one location to another.Whenever possible, the speed of your virtualization platform should rival that of physical hardware. Offloaded Data Transfer (ODX) support is a feature of the storage stack of Hyper‑V in Windows Server 2012. ODX, when used with offload-capable SAN storage hardware, lets a storage device perform a file copy operation without the main processor of the Hyper‑V host actually reading the content from one storage place and writing it to another.Technical descriptionThe storage stack of Hyper‑V in Windows Server 2012 supports ODX operations so that these operations can be passed from the guest operating system to the host hardware, letting the workload use ODX–enabled storage as if it were running in a non-virtualized environment. The Hyper‑V storage stack also issues copy offload operations in VHD and VHDX maintenance operations such as merging disks and storage migration meta-operations in which large amounts of data are moved from one virtual hard disk to another virtual hard disk or to another location.ODX uses a token-based mechanism for reading and writing data within or between intelligent storage arrays. Instead of routing the data through the host, a small token is copied between the source and destination. The token simply serves as a point-in-time representation of the data. As an example, when you copy a file or migrate a virtual machine between storage locations (either within or between storage arrays), a token that represents the virtual machine file is copied, which removes the need to copy the underlying data through the servers. In a token-based copy operation, the steps are as follows (see the following figure):A user initiates a file copy or move in Windows Explorer, a command-line interface, or a virtual machine migration.Windows Server automatically translates this transfer request into an ODX (if supported by the storage array) and receives a token representation of the data.The token is copied between the source and destination systems.The token is delivered to the storage array.The storage array performs the copy internally and returns progress status.ODX is especially significant in the cloud space when you must provision new virtual machines from virtual machine template libraries or when virtual hard disk operations are triggered and require large blocks of data to be copied, as in virtual hard disk merges, storage migration, and live migration. These copy operations are then handled by the storage device that must be able to perform offloads (such as an offload-capable iSCSI, Fibre Channel SAN, or a file server based in Windows Server 2012) and frees up the Hyper‑V host processors to carry more virtual machine workloads.BenefitsODX frees up the main processor to handle virtual machine workloads and lets you achieve native-like performance when your virtual machines read from and write to storage.Feature-level benefits of ODX are:Greatly reduced time to copy large amounts of data.Copy operations that don’t use processor time.Virtualized workload that operates as efficiently as it would in a non-virtualized environment.You can more rapidly perform crucial maintenance tasks for virtual hard drives (such as merge, move, and compact) that depend on copying large amounts of data without using processor time. Enabling ODX support in the Hyper‑V storage stack makes it possible to complete these operations in a fraction of the time it would have taken without the support.RequirementODX support in Hyper‑V requires the following:ODX-capable hardware to host the virtual hard disk files, connected to the virtual machine as virtual SCSI devices or directly attached (sometimes referred to as pass-through disks).This optimization is also supported for natively attached, VHDX-based virtual disks.VHD- or VHDX-based virtual disks attached to virtual IDE do not support this optimization because integrated development environment (IDE) devices lack ODX support.
- Populate the demo title depending upon which demo you plan to deliver. If you don’t plan to deliver demos, please hide this slide. Click through demos are located at “\\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Click Thru Demos\\Server Virtualization Demo environment build instructions are located here: \\\\scdemostore01\\demostore\\Windows Server 2012\\WS 2012 Demo Series\\Demo Builds
- Before Windows Server 2012Many enterprises need the ability to extend virtual switch features with their own plug-ins to suit their virtual environment. If you’re in charge of making IT purchasing decisions at your company, you want to know that the virtualization platform you choose won’t lock you in to a small set of compatible features, devices, or technologies.With Windows Server 2012The Hyper‑V Extensible Switch in Windows Server 2012 is a layer-2 virtual network switch that provides programmatically managed and extensible capabilities to connect virtual machines to the physical network. The Hyper‑V Extensible Switch is an open platform that lets multiple vendors provide extensions that are written to standard Windows API frameworks. The reliability of extensions is strengthened through the Windows standard framework and reduction of required third-party code for functions and is backed by the Windows Hardware Quality Labs (WHQL) certification program. You can manage the Hyper‑V Extensible Switch and its extensions by using Windows PowerShell, programmatically with WMI or the Hyper‑V Manager user interface.Extensibility of the Hyper‑V Extensible Switch Windows Server 2012 extends the virtual switch to provide new capabilities.The Hyper‑V Extensible Switch architecture in Windows Server 2012 is an open framework that allows third parties to add new functionality such as monitoring, forwarding, and filtering to the virtual switch. Two platformsExtensions are implemented using the following drivers: Network Device Interface Specification (NDIS) filter drivers are used to monitor or modify network packets in Windows. NDIS filters were introduced with the NDIS 6.0 specification.Windows Filtering Platform (WFP) callout drivers introduced in Windows Vista and Windows Server 2008, let independent software vendors (ISVs) create drivers to filter and modify TCP/IP packets, monitor or authorize connections, filter IP security (IPsec)-protected traffic, and filter remote procedure calls (RPCs). Filtering and modifying TCP/IP packets provides unprecedented access to the TCP/IP packet processing path. In this path, you can examine or modify outgoing and incoming packets before additional processing occurs. By accessing the TCP/IP processing path at different layers, you can more easily create firewalls, antivirus software, diagnostic software, and other types of applications and services. For more information, see the Windows Filtering Platform.Extensions may extend or replace these aspects of the switching process:Ingress filteringDestination lookup and forwardingEgress filteringOnly one instance of the forwarding extension may be used per switch instance, and it overrides the default switching of the Hyper‑V Extensible Switch.Some other features of Hyper‑V Extensible Switch extensibility are:Extension monitoring. In addition, by monitoring extensions you can gather statistical data by monitoring traffic at different layers of the Hyper‑V Extensible Switch. Multiple monitoring and filtering extensions can be supported at the ingress and egress portions of the Hyper‑V Extensible Switch.Extension uniqueness. Extension state/configuration is unique to each instance of an Extensible Switch on a machine.Extensions that learn virtual machine life cycle. Virtual machine activity cycle is similar to that of physical servers, having peak times during various parts of the day or night based on their core workloads. Extensions can learn the flow of network traffic based on the workload cycle of your virtual machines and optimize your virtual network for greater performance.Extensions that can veto state changes. Extensions can implement monitoring, security, and other features to further improve the performance, management, and diagnostic enhancements of the Hyper‑V Extensible Switch. Extensions can help ensure the security and reliability of your system by identifying harmful state changes, and stopping them from being implemented.Multiple extensions on same switch. Multiple extensions can coexist on the same Hyper‑V Extensible Switch.
- The figure shows the architecture of SR-IOV support in Hyper‑V.Support for SR-IOV networking devices Single Root I/O Virtualization (SR-IOV) works in conjunction with system chipset support for virtualization technologies that provide remapping of interrupts and Direct Memory Access, and allows SR-IOV-capable devices to be assigned directly to a virtual machine. Hyper‑V in Windows Server 2012 enables support for SR‑IOV-capable network devices and allows an SR‑IOV virtual function of a physical network adapter to be assigned directly to a virtual machine. This increases network throughput and reduces network latency while also reducing the host CPU overhead required for processing network traffic. BenefitsThese new Hyper‑V features let enterprises take full advantage of the largest available host systems to deploy mission-critical, tier-1 business applications with large, demanding workloads.You can configure your systems to maximize the use of host system processors and memory to effectively handle the most demanding workloads.RequirementsTo take advantage of the new Hyper‑V features for host scale and scale-up workload support, you need the following:One or more Windows Server 2012 installations with the Hyper‑V role installed. Hyper‑V requires a server that provides processor support for hardware virtualization.The number of virtual processors that may be configured in a virtual machine depends on the number of processors on the physical machine. You must have at least as many logical processors in the virtualization host as the number of virtual processors required in the virtual machine. For example, to configure a virtual machine with the maximum of 32 virtual processors, you must be running Hyper‑V in Windows Server 2012 on a virtualization host that has 32 or more logical processors.SR-IOV networking requires the following:A host system that supports SR-IOV (such as Intel VT-d2), including chipset support for interrupt and DMA remapping and proper firmware support to enable and describe the platform’s SR-IOV capabilities to the operating system.An SR-IOV–capable network adapter and driver in both the management operating system (which runs the Hyper‑V role) and each virtual machine where a virtual function is assigned.