Just when you thought… (Part 2)

Just when you thought… (Part 2)

  • Comments 1
  • Likes

In Part 1, I covered configuring the Hyper-V Failover Cluster and the Scale-Out File Server solution. In Part two, I will cover:

  • Creating the file shares in the Scale-Out File Server
  • Creating a virtual machine to use the SMB3.0 shares in the Scale-Out File Server
  • Verifying we can Live Migrate the virtual machines in the Hyper-V Failover Cluster

Creating the File Share

Execute the following steps to create a file share in the Scale-Out File Server

  1. In Failover Cluster Manager, right-click on the Scale-Out File Server role in the center pane and choose Add File Share. This starts the New Share Wizard
  2. In the Select Profile screen, choose SMB Share - Applications and click Next
  3. For the Share Location, choose one of the CSV Volumes and click Next
  4. Provide a Share Name, verify the path information and click Next
  5. In the Other Settings screen, Enable Continuous Availability is checked by default. Click Next
    Note: Some selections are greyed-out. This is because they are not supported for this share profile in a Failover Cluster
  6. In the Permissions screen, click Customize Permissions. In the Advanced Security Settings screen, note the default NTFS and Share permissions and then proceed to add the Hyper-V Failover Cluster Nodes Computer Accounts to the NTFS permissions for the share and ensure they have Full Control. If the permissions listing does not include the cluster administrator(s), add it and give the account (or Security Group) Full Control. Click Apply when finished

Complete configuring the file shares.

clip_image002

As a test, connect to each of the shares from the Hyper-V Failover Cluster and verify you can write to each location before proceeding to the next step.

Creating a Virtual Machine to use an SMB 3.0 Share

Execute the following steps to create a new virtual machine

  1. On one of the nodes in the Hyper-V Cluster, open Failover Cluster Manager
  2. In the left-hand pane, click on Roles and then in the right-hand Actions pane click on Virtual Machines and choose New Virtual Machine
  3. Choose one of the cluster nodes to be the target for the virtual machine and click OK
  4. This starts the New Virtual Machine Wizard. Review the Before You Begin screen and click Next
  5. In the Specify Name and Location screen, provide a name for the virtual machine and enter an UNC path to a share on the Scale-Out File Server and then click Next

    clip_image004
  6. Configure memory settings and click Next
  7. Configure network settings and click Next
  8. In the Connect Virtual Hard Disk screen, make a selection and click Next
  9. Review the Summary screen and click Finish
  10. Verify the process completes successfully and click Finish

Testing Live Migration

Once all the virtual machines are created, you may want to test Live Migration. Depending on how many simultaneous live migrations you want to support, you may have to modify the Live Migration settings on each of the Hyper-V Failover Cluster nodes. The default is to allow two simultaneous live migrations. Here is a little PowerShell script you can run to take care of the settings for all the nodes in the cluster -

$Cred = Get-Credential

Invoke-Command -Computername Fabrikam-N21,Fabrikam-N22,Fabrikam-N23 -Credential $Cred -scriptblock {Set-VMHost -MaximumVirtualMachineMigrations 6}

In my cluster, I have all the virtual machines running on the same node -

clip_image006

I will use a new feature in Windows Server 2012 Failover Clusters, multi-select, and select all of the virtual machines and live migrate them to another node in the cluster -

clip_image008

Since there are only four virtual machines and the maximum number of live migrations is equal to six, all will migrate.

clip_image010

If I were to rerun my script and make a change back to two, then two migrations will be queued until at least one of the in progress migrations completes.

clip_image012

You can use the Get-SmbSession PowerShell cmdlet on any node in the Scale-Out File Server to determine the number of sessions. For illustration purposes, I have all virtual machines running on the same Hyper-V Failover Cluster node (Fabrikam-N21) and the CSV volumes are running on the same node in the Scale-Out File Server (Fabrikam-N1) -

clip_image014

Distributing the virtual machines across the multi-node Hyper-V Failover Cluster (Fabrilam-N21, Fabrikam-N22, and Fabrikam-N23) is reflected on the Scale-Out File Server -
image

Finally, I re-distribute the CSV volumes across the Scale-Out File Server nodes as shown here -

clip_image018

This is reflected in the Get-SmbSession PowerShell cmdlet output -

clip_image020

Thanks, and come back again soon.

Chuck Timon
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support
High Availability\Virtualization Team

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hello Chuck ,

    If I am not wrong In the given scenario we are using SMB 3.0 Scale out file shares configured in a 2 node different cluster (on CSV volumes ) & our virtual machines configured on 3 node hyper v cluster are using these file shares to access their VHD's & Configuration file .

    Now if somehow this 2 node cluster goes down due to some reason for instance CNO goes down  , that will impact the virtual machines because we can take CSV volumes out of the cluster as an individual disks but the UNC paths will be not accessible , Do we have any workaround in that scenario ?

    In 2008 R2 cluster there was a way to bring VM's up if we take them out of the cluster along with the disk & do manual mapping of the VHD & configuration file but I am not sure how this can be achieved here ?

    Piyush Kumar