Home > Hyper-V, Hyper-V R2, Microsoft, Virtualization, Windows 2008 R2 > NetApp: Install Order for Hyper-V Clusters

NetApp: Install Order for Hyper-V Clusters

A very useful blog from NetApp team

Source: http://blogs.netapp.com/msenviro/2011/02/install-order-for-hyper-v-clusters.html

 

One of the most complex things that we support in the Microsoft universe is a Hyper-V cluster environment.  With the additon of Clustered Shared Volumes (CSV’s) there are quite a few moving parts and getting them all installed in the correct order can be a challenge.

One of our Professional Services architects, Chris Collins, has put together a nice cheat-sheet for ensuring that everything is installed and deployed in the correct order.  We’ll be putting together a more detailed TR on this, but I thought this little checklist would help out anyone who’s deploying Hyper-V clusters.  Thanks Chris!!

Installation Process for Hyper V

1. Install NetApp storage system

a. Create Aggregates to support infrastructure

b. Create volumes to support CSV infrastructure (turn on Thin Provisioning)

2. Server OS Prep

a. Install Windows OS

i. Hyper V – Role

ii. Failover cluster feature

iii. .NET 3.5 feature

iv. MPIO Feature

v. All Patches

b. Install Microsoft Hot Fixes

NOTE:  You can get a full list of Hyper-V related hotfixes from MSFT here.  Note that the V2 hotfixes below are normally the Windows 2008 R2 version of the hotfix.  See technet.microsoft.com for more information on each hotfix listed below.

i. KB975921

ii. KB974909

iii. KB975354

iv. KB975354 V2

v. KB979743 V2

vi. KB979743 V2

vii. KB974909 V2

c. Install NetApp Software

i. NetApp Windows Host Utility Kit 5.3

ii. NetApp MPIO 3.4

iii. Snap Drive 6.3 P2

3. Setup Server Network

a. Network 1 – Server Management (ILO) (Optional)

b. Network 2 – Client Access (VM BRIDGE)

c. Network 3 – Live migration Network (Optional)

d. Network 4 – Heartbeat network

e. Network 5 – ISCSI Network (As needed)

f. HBA – FCP connections as needed (AS needed)

4. Setup Snap Drive for Windows

a. Setup transport Protocol defaults

b. Setup individual Filers

c. Setup Disks preferred filer system

5. Setup Cluster

a. Create windows cluster

b. Enable clustered shared Volumes

c. Use snap Drive to set up LUN to be used for Quorum drive

d. Use Cluster Manger to setup failover cluster settings for Quorum system

6. Create Clustered shared volumes (CSV)

a. Use Snap Drive for windows to crate clustered shared volume

b. Open system manager and convert LUNS to thin provisioned LUNS

7. Snap Manger for Hyper V (SMHV)

a. Use Snap Drive to Create a single clustered drive that will be used for the Snap info Directory

b. Install Snap Manager for Hyper V on every node in the clusters

c. Add cluster to the SMHV management console

d. Create a base data set

e. Create a backup policy

8. Create VM’s

a. Create VM’s as needed

9. Open SMHV to add virtual machines to appropriate Data sets.

Advertisements
  1. March 20, 2011 at 1:24 pm

    Hi Mohamed

    It seems there is a bug when Snap Drive is installed on Server Core. It takes between 5 to 7 minutes longer to boot the server. NetApp is working on it, but in the meantime consider a coffee break when you reboot a host 😉

    Cheers
    Michel

  1. March 4, 2011 at 9:15 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: