Microsoft IT Camp Hands-On Lab

Transcription

1 Microsoft IT Camp Hands-On Lab Windows Server 2012: High Availability File Server Lab version: Last updated: 7/19/2012

2 CONTENTS OVERVIEW... 3 Objectives 3 Prerequisites 3 LAB DEPLOYMENT... 4 LAB... 6 MORE INFORMATION... 8 To give feedback please write to labs@holsystems.com Copyright 2011 by Microsoft Corporation. All rights reserved.

3 Overview In this lab, you will see how the new, continuously available file server in Windows Server 2012 allows user sessions to move from one file server node to another without any downtime. This lab environment already has an existing failover cluster configured. Note the failover cluster type of Continuous Availability is set for the share VMStore. Also, note that the cluster type is a Scale-Out File Server, which is a new cluster type. Objectives In this series of exercises, you will explore the following: Connecting to an existing failover cluster. Configuring real-time Network-Performance-Monitoring of cluster traffic. Moving file server traffic to a different cluster node, without interruption of network services. Prerequisites Knowledge of Hyper-V Familiarity with Windows PowerShell

4 Lab Deployment This lab requires that the following host computers and virtual machines be running. Host Computers: WS2012InfHost Host Name: WS2012InfHost Primary Roles: Hyper-V Server; contains all lab VMs (except Server3) Virtual Machines: DC AdminClient Server1 Virtual Machine Name: WS2012RCDemos-DC Primary Roles: Domain Controller and Enterprise Root CA for Contoso domain Additional Roles: DHCP, DNS Virtual Machine Name: WS2012RCDemos-AdminClient OS: Windows 8 Release Preview Primary Role: Remote Services Administration Tools (RSAT) Virtual Machine Name: WS2012RCDemos-Server1 Primary Roles: IIS, File and Storage Services Additional Roles: RSAT, Centralized SSL Certificate Support

5 Node1 Node2 Virtual Machine Name: WS2012RCDemos-Node1 Primary Role: Failover Clustering Virtual Machine Name: WS2012RCDemos-Node2 Primary Role: Failover Clustering

6 Lab Tasks in this lab module 1) Connect to an existing failover cluster 2) Configure real-time Network Performance Monitoring 3) Transfer file server traffic to a different cluster node, without interruption of network services. 1) Connect to an existing failover cluster 1. Log on to AdminClient as Contoso\Administrator using the password Passw0rd! 2. From the Taskbar, open Server Manager. 3. In Server Manager, click Tools, and then click Failover Cluster Manager. 4. On the Actions menu, click Connect to Cluster, type cluster.contoso.com and then click OK. 5. Expand Cluster.contoso.com, and then click Roles. 6. Click HAFileServer. Note the current owner of the Node. 7. On the Shares tab, note the available shares. 8. Close Failover Cluster Manager. 2) Configure real-time Network-Performance-Monitoring 1. In Server Manager, click All Servers. 2. Right-click Server1, and then click Remote Desktop Connection. 3. Log on to Server1 as Contoso\Administrator using the password Passw0rd! 4. Click OK to acknowledge the password notification. 5. From the Taskbar, open Windows Explorer and navigate to \\HAFileServer\VMStore. 6. On the desktop, double-click Network-Performance-Monitoring. 7. Click Allow Blocked Content, click the Play button, and then click Yes. 8. Switch to AdminClient.

7 9. Open Windows PowerShell, type the following command and then press ENTER. As an alternative to typing, you can run the Display SMB Witness Configuration portion of SMB-HA- File-Server.ps1, which is located in the PowerShell Scripts folder on the AdminClient desktop. If the script fails to run, type Set-ExecutionPolicy RemoteSigned and then re-run the script. Invoke-Command -Computer NODE1 -ScriptBlock{ Write-Host "SMB Witness Configuration" Get-SmbWitnessClient FL $Witness = Get-SmbWitnessClient Write-host ("Witness is on " + $Witness.WitnessNodeName) } IMPORTANT: Note the output line that reads "Witness is on NODEX". The witness node must be modified in the next command. 3) Move file server traffic to a different cluster node, without interruption of network services. 1. Switch to Server1. 2. Copy Install.wim from D:\Sources to \\HAFileServer\VMStore. 3. Observe the traffic in Network1Performance-Monitoring. 4. In Windows PowerShell, type the following command, and then press ENTER. As an alternative to typing, you can run the Move IO to the other node portion of SMB-HA-File-Server.ps1, which is located in the PowerShell Scripts folder on the AdminClient desktop. Invoke-Command -Computer NODE1 -ScriptBlock{ Write-Host "Moving SMB Traffic" Move-SmbWitnessClient -ClientName Server1 -DestinationNode Node1 } IMPORTANT: This command defaults to moving to NODE2. If the output of the previous command indicated that the witness node was on NODE2 already, change the script value - DestinationNode to NODE1. 5. When prompted, click Yes. Notice that the file server traffic is moved to the other node without any interruption in the copy operation.

8 More Information High-Performance, Continuously Available File Share Storage for Server Applications Technical Preview Windows Server Blogs Windows Server 2012 Home Page and Product Download Windows Server 2012 Virtual Labs