Installation and Configuration Guide for Microsoft ... · PDF file1 Installation and...

Installation and Configuration Guide for Microsoft SharePoint Server 2013

Microsoft SharePoint solution based on Lenovo System x3550 M5 servers

Designed for medium to large sized organizations

Virtualized implementation of the presentation and business layers

Scalable, clustered, and flexible design that is highly available

Roland Mueller

Last update: 30 September 2015

http://lenovopress.com/updatecheck/TIPS1320/61b841675663df973b2befff55cab790

ii Installation and Configuration Guide for Microsoft SharePoint Server 2013

Table of Contents

1 Introduction ................................................................................................ 1

2 Installation and configuration................................................................... 2

3 Server installation ...................................................................................... 3

3.1.1 Hardware configuration ........................................................................................................... 4 3.1.2 Windows OS installation and configuration .............................................................................. 4

4 Networking .................................................................................................. 5

4.1 Using ISCLI to configure the G8124E network switches .......................................... 7

4.2 Configuring the ISL and VLAG peer relationship...................................................... 7 4.2.1 Configure vLAG peer health checks ........................................................................................ 8 4.2.2 Enable tagging on host ports ................................................................................................... 9 4.2.3 Configure the VLANs .............................................................................................................. 9 4.2.4 Configure LACP teams and enable vLAG on the host connections ........................................ 10

4.3 Creating the NIC team and network adapters ........................................................ 12 4.3.1 Creating the NIC team and network adapter for the Hyper-V cluster servers .......................... 12 4.3.2 Creating the NIC team and network adapter for the SQL Server AlwaysOn cluster servers .... 15

5 Storage networking.................................................................................. 17

5.1 Storage zoning ....................................................................................................... 17

5.2 Configuring the host bus adapters ......................................................................... 19

5.3 Enabling multipathing ............................................................................................. 20

5.4 Host definition on the Storwize V3700 ................................................................... 21

6 Storage partitioning ................................................................................. 24

6.1 Create storage pool ............................................................................................... 24

6.2 Create logical volumes ........................................................................................... 25

7 Creating Windows clusters ..................................................................... 28

7.1 Create the WSFC cluster ....................................................................................... 28

7.2 Adding the cluster shared volumes ........................................................................ 30

7.3 Configuring the cluster network .............................................................................. 33

iii Installation and Configuration Guide for Microsoft SharePoint Server 2013

8 Microsoft Hyper-V configuration ............................................................ 35

9 Creating a highly available VM for SharePoint Server 2013 ............... 36

9.1 Creation of SharePoint VMs................................................................................... 36

9.2 Changing the VM save state on shut down for migration ....................................... 37

9.3 VM preferred owners ............................................................................................. 38

9.4 VM network configuration....................................................................................... 39

9.5 Adding an additional drive for the SharePoint install files....................................... 40

10 Installing and configuring SQL Server 2012 SP2 ................................. 42

10.1 Install SQL Server 2012 SP2 ................................................................................. 42

10.2 Configuring max degree of parallelism ................................................................... 45

10.3 Assign permissions ................................................................................................ 46

10.4 Allowing access through the Windows firewall ....................................................... 47

10.5 Limiting memory usage .......................................................................................... 48

10.6 Compress backups ................................................................................................ 48

10.7 Configuring SQL Server AlwaysOn availability groups ........................................... 49

11 Installing and configuring SharePoint 2013 .......................................... 54

11.1 Installing software prerequisites ............................................................................. 54

11.2 Installing SharePoint .............................................................................................. 55

11.3 SharePoint 2013 products configuration wizard ..................................................... 57

11.4 SharePoint service deployment ............................................................................. 58 11.4.1 Distributed cache service ...................................................................................................... 59

11.5 Adding SharePoint databases to the AlwaysOn availability group ......................... 59

References ...................................................................................................... 64

1 Installation and Configuration Guide for Microsoft SharePoint Server 2013

1 Introduction This document provides information on how to implement the solution as described in the “Reference Architecture: Microsoft SharePoint Server 2013” which can be found at the following website: lenovopress.com/tips1319-microsoft-sharepoint-server-2013-ra

Whereas the reference architecture provides the planning, design considerations, and best practices for creating a Microsoft SharePoint Server 2013 architecture, this document provides the steps necessary to configure and install the solution using Lenovo products.

The intended audience of this document is IT professionals, technical architects, and consultants to assist in planning, designing, and implementing the solution as described in the reference architecture.


2 Installation and configuration Using a set of test-proven planning and deployment techniques can contribute significantly to the successful deployment and operation of a virtualized SharePoint Server 2013 environment that uses Windows Server Failover Clustering (WSFC) and Microsoft Hyper-V. Proper planning includes sizing resource requirements for servers (CPU and memory), storage (capacity and IOPS), and networking (bandwidth and VLAN assignment) to support the infrastructure. The sizing information, combined with industry-standard best practices, can be used to achieve optimal performance and growth headroom necessary for the life of the solution.

Configuration best practices and implementation guidelines, which aid in planning and configuration of the solution, are described in the following topics:

• 3 Server installation • 4 Networking • 5 Storage networking • 6 Storage partitioning • 7 Creating Windows clusters • 8 Microsoft Hyper-V configuration • 9 Creating a highly available VM for SharePoint Server 2013 • 10 Installing and configuring SQL Server 2012 SP2 • 11 Installing and configuring SharePoint 2013


3 Server installation Dual-socket Lenovo System x3550 M5 servers with the following configuration:

• 128 GB RAM • Two Intel Xeon E5-2660 v3 (Haswell) 2.1 GHz 12-core processors • One dual-port Emulex VFA5 2x10 GbE SFP+ PCIe Adapter for System x • One Emulex 8 Gb FC Dual-port HBA for System x

Setup of the servers involves the installation and configuration of the following items:

• Windows Server 2012 R2 Datacenter edition (on the two servers that comprise the Hyper-V cluster) • Windows Server 2012 R2 Standard edition (on the two servers that comprise the SQL Server cluster) • networking • storage

Windows Server 2012 R2 Datacenter edition allows unlimited Windows virtual machine (VM) rights on the host server and is the preferred version for building private cloud configurations. Windows Server 2012 R2 Standard edition supports clustering as well, but provides licensing rights only for up to two Windows VMs and is intended for physical servers that are hosting few or no VMs.


3.1.1 Hardware configuration Before installing the Windows Server operating system, verify the following on each of the servers:

• Confirm that the Emulex network adapter and HBA are installed • Validate that firmware levels are consistent across all servers • Verify that the two local disks are configured as a RAID-1 array for the operating system

3.1.2 Windows OS installation and configuration Install Windows Server 2012 R2 Datacenter edition on the Hyper-V servers and Standard edition on the SQL Server systems, then perform the following on each of the servers:

• Set the server name • Run Windows Update to ensure that any new patches are installed. All the servers in a Windows

Server failover cluster (WSFC) should have the same software updates (patches) and service packs. • Download and install the latest chipset driver • Download and install the latest network adapter and HBA drivers from the Lenovo Support portal:

support.lenovo.com/us/en/products • Install the Emulex OneCommand Manager utility to provide additional insight to the converged

infrastructure. A link to this tool is listed below: emulex.com/downloads/emulex/drivers/windows/windows-server-2012-r2/management/

• Install the Hyper-V role on the two Hyper-V servers. Because the servers that comprise the Hyper-V cluster use a virtual switch, this step is a pre-requisite for configuring networking.

• Install.Net Framework version 3.5.1 on the two SQL Server systems. • Install the Failover Clustering feature on all servers • After network configuration is complete, join the servers to the domain

http://www.emulex.com/downloads/emulex/drivers/windows/windows-server-2012-r2/management/


4 Networking This section describes the networking topology, Virtual LAN (VLAN) definitions, and includes instructions to correctly configure the network environment, as shown in Figure 1 below.

Figure 1. Network configuration

VLANs are used to provide logical isolation between the various data traffic.

All data traffic is over a single NIC team that is built using the Emulex VFA5 2x10 GbE SFP+ PCIe Adapter installed in each of the servers. The NIC team is created using the Windows Server 2012 R2 in-box NIC teaming feature, which provides fault tolerance and load balancing for the networks. The VLANs described in this section share the bandwidth of the single NIC team. Therefore, Quality of Service (QoS) will be applied from Windows to ensure each VLAN has available bandwidth.

The suggested VLANs are listed in Table 1.


Table 1. VLAN Definitions

VLAN ID Name Description

VLAN 70 Management Network A network used for host management, storage

management, and out-of-band communication to IMM

devices.

VLAN 61 Cluster Private Network A network reserved for cluster private (heartbeat)

communication between the clustered SQL Servers. There

should be no IP routing or default gateways for cluster

private networks.

VLAN 60 Cluster Private Network A network reserved for cluster private (heartbeat and

cluster shared volume) communication between the

clustered Hyper-V host servers. There should be no IP

routing or default gateways for cluster private networks.

VLAN 50 Live Migration Network A network to support Live Migration for the Hyper-V cluster.

There should be no routing on the live migration VLAN.

VLAN 40 Cluster Public (Corporate

Network)

A network reserved for connecting to the domain controller

and to the corporate network.

VLAN 100 vLAG (Virtual Link

Aggregation Group)

A dedicated VLAN to support communication between

Server 1 and the switch ports that are configured as

vLAG/LACP (Link Aggregation Control Protocol) teams.

VLAN 200 vLAG A dedicated VLAN to support communication between


vLAG/LACP teams.



vLAG/LACP teams.



vLAG/LACP teams.

VLAN 4094 Inter-Switch Link (ISL) A dedicated VLAN to support the ISL trunk group between

the two switches. The spanning tree protocol should be

disabled on the trunk group VLAN.


4.1 Using ISCLI to configure the G8124E network switches Below are some examples of the ISCLI commands to setup and configure the G8124E network switches. The commands below are for use with switches running Networking OS 7.2.2.0 software. If your switch has a different version, please refer to the applicable Application Guide for the appropriate commands. To download the G8124E Application Guide, visit the following website: ibm.com/support/docview.wss?uid=isg3T7000538

Changes to the running configuration on the switch must be made from Global Configuration Mode. Global Configuration Mode is accessed from Privileged EXEC mode, which in turn is accessed from User Exec Mode.

1. After entering the appropriate password to enter User Exec Mode, run the following command to access Privileged EXEC Mode:

Router> enable

2. To access Global Configuration Mode from Privileged EXEC Mode, enter the following command:

Router# configure terminal

The G8124E switch can accept abbreviated commands. For example, conf t can be used instead of configure terminal.

The commands shown in the remainder of this section are run in Global Configuration Mode.

4.2 Configuring the ISL and VLAG peer relationship This section covers the creation of an inter-switch link (ISL) between the two network switches that allows traffic to flow between the two switches as if they were one logical entity. A vLAG is then enabled to utilize the full bandwidth of the two ports being used in the ISL.

The commands in this section should be run in the order shown.

1. If Spanning-Tree Protocol (STP) is desired on the switch, use PVRST or MSTP mode only. To configure STP to run in PVRST mode run the following command on each switch before continuing:

Router(config)# spanning-tree mode pvrst

2. Enable vLAG globally by running the following command on each switch before continuing:

Router(config)# vlag enable

3. Place the ISL into a dedicated VLAN (VLAN 4094 is recommended) by running the following commands on each switch before continuing:

Router(config)# vlan 4094

The output of the previous command will be similar to the output shown below:

Router(config)# vlan 4094 was assigned to STG 126

Take note of the number immediately following STG as it will be used in a later command (in the example this is the number 126).

http://www-01.ibm.com/support/docview.wss?uid=isg3T7000538


Run the remaining commands to enable the VLAN. In this example, ports 23 and 24 are used for the ISL connection between the two switches:

Router(config-vlan)# enable

Router(config-vlan)# member 23-24

Router(config-vlan)# exit

4. Configure the ISL ports on each switch and place them into a port trunk group by running the following commands on each switch before continuing:

Router(config)# interface port 23-24

Router(config-if)# tagging

Router(config-if)# lacp mode active

Router(config-if)# lacp key 200

Router(config-if)# exit

5. Configure the vLAG Tier ID. This is used to identify the vLAG switch in a multitier environment:

Router(config)# vlag tier-id 10

6. If STP used on the switch, turn STP tree off for the ISL by running the following commands on each switch before continuing. Use the spanning tree number that was assigned to VLAN 4094 in step 3, above:

Router(config)# spanning-tree stp 126 vlan 4094

Router(config)# no spanning-tree stp 126 enable

Although STP is disabled on the ISL, Spanning Tree should be enabled on all switches on other networks according to your organizations requirements.

7. Define the vLAG peer relationship by running the following commands on each switch before continuing:

Router(config)# vlag isl vlan 4094

Router(config)# vlag isl adminkey 200

Router(config)# exit

8. Save the configuration changes by running the following command on each switch:

Router# write

4.2.1 Configure vLAG peer health checks Lenovo recommends configuring the G8214E to check the health status of its vLAG peer. Although the operational status of the vLAG peer is generally determined via the ISL connection, configuring a network health check provides an alternative means to check peer status in case the ISL links fail. Use an independent link (such as the 1 Gb management port) between the vLAG peer switches for the health check (e.g. the 1 Gb MGT port).

Comments are provided in italic blue. Comments are for informational purposes only and are not to be typed in the command line. Run the following commands from the ISCLI on each switch:


Router(config)# interface ip 128

Router(config-if-ip)# ip address 10.10.10.1 255.255.255.0

Use 10.10.10.2 on the second G8124E switch

Router(config-if-ip)# enable

Router(config-if-ip)# exit

After the previous set of commands has been run from each of the network switches, run the following command from the ISCLI on each of the switches to its vLAG peer.

Router(config)# vlag hlthchk peer-ip 10.10.10.2

Use 10.10.10.1 on the second G8124E switch

4.2.2 Enable tagging on host ports Before creating VLANs, tagging should be enabled on the host ports (ports 10, 11, 12, and 13 in our example environment) on each switch.

The commands in this section should be run in the order shown and after the commands in previous sections have been run.

Run the following commands from the ISCLI on each switch:

Router(config)# interface port 10-13

Router(config-if)# tagging


4.2.3 Configure the VLANs Define and assign the VLANs before the vLAGs are formed on the host ports.

1. Run the following commands from the ISCLI on each of the switches to configure the VLANs. (Each VLAN includes the ports 23 and 24 used in the ISL.)



Router(config-vlan)# member 10-13,23-24



















2. To verify that the VLANs have been configured correctly, run the following command:

Router(config)# show vlan

Figure 2 shows the example output from this command.

Figure 2. Results from the “show vlan” command

3. Save the configuration changes by running the following command on each switch:

Router(config)# write

4.2.4 Configure LACP teams and enable vLAG on the host connections This section describes the steps required to create an LACP team using the two 10 GbE connections from each host server to each of the switches. After the LACP team has been created, vLAG is enabled on the team to provide active-active usage of the connections.

The commands in this section should be run in the order shown and after the commands in previous sections have been run. Comments are provided in italic blue are for informational purposes only and are not typed in the command line.

1. Configure the LACP team for server 1. Run the following commands on both switches before continuing.

Router(config)# vlan 100 Create VLAN 100 for vLAG communication


Router(config-vlan)# member 23-24,10 Adds the ISL and host ports to the VLAN



Router(config)# interface port 10 Select the host port server 1

Router(config-if)# lacp mode active Activates LACP for the host port

Router(config-if)# lacp key 1000 Assigns a unique admin key for the LACP team


2. Enable vLAG for the LACP team on each switch. This allows the LACP teams to be formed across the two G8124 switches. Run the following command on both switches before continuing.

Router(config)# vlag adminkey 1000 enable






Router(config)# interface port 11 Select the host port for server 2




4. Enable vLAG for the LACP team on each switch. This allows LACP teams to be formed across the two G8124 switches. Run the following command on both switches before continuing.











6. Enable vLAG for the LACP team on each switch. This allows LACP teams to be formed across the two G8124E switches. Run the following command on both switches before continuing.












8. Enable vLAG for the LACP team on each switch. This allows LACP teams to be formed across the two G8124E switches. Run the following command on both switches before continuing.


9. Write the running configuration to the startup configuration by running the following command:

Router(config)# write

The LACP teams have been created and vLAG has been enabled. However, the vLAGs will show as “not formed” in the ISCLI of each of the switches until the NIC teaming has been configured on each of the servers from within Windows Server 2012 R2.

4.3 Creating the NIC team and network adapters Lenovo recommends renaming the network interface ports in Windows to better document the network topology. In the example shown in Figure 3 the ports are renamed to identify the ports as 10 Gb Ethernet (10 GbE), assign each port with an identifier (PT1 =Port 1), and document the switch and port to which it is connected (SW1-10 = Switch 1-Port 10).

Figure 3. Renamed 10 GbE network ports in Windows Server 2012 R2

After the network adapter ports have been renamed, the NIC team, virtual switch, and virtual network adapters can be created using Windows PowerShell commands.

The networking commands will vary depending on whether the server will be part of the Hyper-V cluster or the SQL Server AlwaysOn cluster.

4.3.1 Creating the NIC team and network adapter for the Hyper-V cluster servers As a prerequisite, the Hyper-V role must be installed on each of the servers that will be part of the Hyper-V cluster. Run the following commands from each of the servers that will be part of the Hyper-V cluster:

1. Run the following command from PowerShell to form a NIC team named “ClusterTeam” using the two 10 GbE network ports:

PS> New-NetLbfoTeam -name "ClusterTeam" -TeamMembers "10gbE-PT1-SW1-10",

"10gbE-PT2-SW2-10" -TeamingMode LACP


When running this command on the second Hyper-V server, the adapter names used in the command should be changed to match the name of the adapter ports in the server. For example, this guide uses “10gbE-PT1-SW1-11” and “10gbE-PT2-SW2-11” as the adapter port names on the second Hyper-V server.

2. Run the following command to create a virtual switch, named “ClusterSwitch”, which uses the newly formed NIC team:

PS> New-VMSwitch -Name "ClusterSwitch" -NetAdapterName "ClusterTeam"

-MinimumBandwidthMode Weight -AllowManagementOS $true

3. To fulfill the networking requirements, four virtual network adapters must be created. Run the following command to create the virtual network adapters (“ClusterPublicAdapter”, “ClusterPrivateAdapter”, “ManagementAdapter”, and “LiveMigrationAdapter”):

PS> Add-VMNetworkAdapter -ManagementOS -Name "ClusterPublicAdapter" -SwitchName

"ClusterSwitch"

PS> Add-VMNetworkAdapter -ManagementOS -Name "ClusterPrivateAdapter" -SwitchName

"ClusterSwitch"

PS> Add-VMNetworkAdapter -ManagementOS -Name "ManagementAdapter" -SwitchName

"ClusterSwitch"

PS> Add-VMNetworkAdapter -ManagementOS -Name "LiveMigrationAdapter" -SwitchName

"ClusterSwitch"

4. Because the various virtual network adapters will communicate over a single 10 GbE pipe, quality of service (QoS) must be configured to ensure each network has available bandwidth. The commands below will guarantee that the “ClusterPublicAdapter” virtual network adapter and the “ClusterPrivateAdapter” virtual network adapter each have a minimum bandwidth of 10% of the total bandwidth available. The “LiveMigrationAdapter” virtual network adapter may require more bandwidth to migrate VMs; therefore it is assigned a minimum bandwidth of 20%.

PS> Set-VMNetworkAdapter -ManagementOS -Name "ClusterPublicAdapter"

-MinimumBandwidthWeight 5

PS> Set-VMNetworkAdapter -ManagementOS -Name "ClusterPrivateAdapter"


PS> Set-VMNetworkAdapter -ManagementOS -Name "ManagementAdapter"


PS> Set-VMNetworkAdapter -ManagementOS -Name "LiveMigrationAdapter"


5. To logically isolate the various networks, run the following commands to assign VLANs to the virtual network adapters:


PS> Set-VMNetworkAdapterVLAN -ManagementOS -VMNetworkAdapterName

"ClusterPublicAdapter" -Access -VlanId 40


"ClusterPrivateAdapter" -Access -VlanId 60


"ManagementAdapter" -Access -VlanId 70


"LiveMigrationAdapter" -Access -VlanId 50

6. When configuring the IP addresses on the virtual network adapters, it is important for the ClusterPublicAdapter’s IP address to be on the same subnet as the domain controllers and DNS servers in your environment. In most cases this network adapter should be set to obtain an IP address through DHCP. However, for this guide a static IP address is assigned. Also, to prevent a warning during cluster validation, you should configure a gateway IP address on the ClusterPublicAdapter.

To configure the network IP address on the virtual network adapters, run the following commands:

When running these commands on the second server, increment the last octet by 1. For example, rather than 192.168.70.10, use 192.168.70.11 on the second host server.

PS> New-NetIPAddress -InterfaceAlias "vEthernet (ClusterPublicAdapter)"

-IPAddress 192.168.40.10 -PrefixLength 24

PS> New-NetIPAddress -InterfaceAlias "vEthernet (ClusterPrivateAdapter)"


PS> New-NetIPAddress -InterfaceAlias "vEthernet (ManagementAdapter)" -IPAddress

192.168.70.10 -PrefixLength 24

PS> New-NetIPAddress -InterfaceAlias "vEthernet (LiveMigrationAdapter)"


7. Finally, if the DNS is not being set by the DHCP server, set the DNS server on the “ClusterPublicAdapter” by running the following command:

PS> Set-DnsClientServerAddress -Interfacealias "vEthernet

(ClusterPublicAdapter)" -ServerAddress <IP Address of your DNS server>

The DNS server should be on the same subnet as the “ClusterPublicAdapter” virtual network adapter.

8. Cluster nodes are multi-homed systems. Network priority affects DNS Client for outbound network connectivity. Network adapters used for client communication should be at the top in the binding order. Non-routed networks can be placed at lower priority. Windows Server 2012 R2, automatically places the Cluster Network Driver (NETFT.SYS) adapter at the bottom of the binding order list.

Set the network binding order so the cluster public network (ClusterPublicAdapter - VLAN 40) is at the top. This can be accomplished from the Network Connections window in the server’s operating system. Click Alt to make the command ribbon visible and click Advanced. Click Advanced Settings to open the Advanced Settings window. The available connections are listed under Connections as shown in Figure 4. Use the arrows to move ClusterPublicAdapter to the top of the list. Click OK. Do this on each server.


Figure 4. Changing the network binding order

Before continuing, test the network implementation thoroughly to ensure communication is not lost despite the loss of a network switch or connection.

4.3.2 Creating the NIC team and network adapter for the SQL Server AlwaysOn

cluster servers Run the following commands from each of the servers that will be part of the SQL Server AlwaysOn cluster:

1. Run the following command from PowerShell to form a NIC team named “ClusterTeam” using the two 10 GbE network ports:

PS> New-NetLbfoTeam -name "ClusterTeam" -TeamMembers "10gbE-PT1-SW1-12",

"10gbE-PT2-SW2-12" -TeamingMode LACP

When running this command on the second SQL Server, the adapter names used in the command must be changed to match the name of the adapter ports in the server. For example, this guide uses “10gbE-PT1-SW1-13” and “10gbE-PT2-SW2-13” as the adapter port names on the second SQL Server.

2. To fulfill the networking requirements three virtual network adapters must be created. Run the following command to create the virtual network adapters (“ClusterPublicAdapter”, “ClusterPrivateAdapter”, and “ManagementAdapter”):


PS> Add-NetLbfoTeamNIC –Team “ClusterTeam” –Name “ClusterPublicAdapter” –VlanID

40

PS> Add-NetLbfoTeamNIC –Team “ClusterTeam” –Name “ClusterPrivateAdapter” –VlanID

61

PS> Add-NetLbfoTeamNIC –Team “ClusterTeam”-Name “ManagementAdapter” –VlanID 70

3. When configuring the IP addresses on the virtual network adapters, it is important for the ClusterPublicAdapter’s IP address to be on the same subnet as the domain controllers and DNS servers in your environment. In most cases this network adapter should be set to obtain an IP address through DHCP. However, for this guide a static IP address is assigned. Also, to prevent a warning during cluster validation, you should configure a gateway IP address on the ClusterPublicAdapter.

To configure the network IP address on the virtual network adapters, run the following commands:

PS> New-NetIPAddress -InterfaceAlias "ClusterPublicAdapter" -IPAddress


PS> New-NetIPAddress -InterfaceAlias "ClusterPrivateAdapter" -IPAddress


PS> New-NetIPAddress -InterfaceAlias "ManagementAdapter" -IPAddress


When running these commands on the second server, increment the last octet by 1, as described in section Creating the NIC team and network adapter for the Hyper-V cluster servers.

4. Finally, if the DNS is not being set by the DHCP server, set the DNS server on the “ClusterPublicAdapter” by running the following command:

PS> Set-DnsClientServerAddress -Interfacealias "ClusterPublicAdapter"

–ServerAddress <IP Address of your DNS server>

The DNS server should be on the same subnet as the “ClusterPublicAdapter” virtual network adapter.

5. As described in section Creating the NIC team and network adapter for the Hyper-V cluster servers, set the network binding order so the cluster public network (ClusterPublicAdapter - VLAN 40) is at the top.

Before continuing, test the network implementation thoroughly to ensure correct failover when a network switch is down or a connection is broken.


5 Storage networking This section describes the storage networking topology and includes instructions to correctly configure the storage environment.

The IBM Subsystem Device Driver Specific Module (SDDDSM) multipath driver in conjunction with the Windows Server 2012 R2 Multipath I/O (MPIO) feature is used to provide fault tolerance and path management between the servers and the storage (see section Enabling multipathing). In the event one or more hardware component fails, causing a path to fail, multipathing logic chooses an alternate path for I/O so applications can still access their data. Multi-path driver details and installation are covered in more depth in section, “Enabling multipathing”.

At the logical layer, zoning is used to provide isolation between the various data traffic. Figure 5 shows the fiber connections and zoning configuration between the servers, the switches, and the Storwize V3700.

Figure 5. SAN configuration

5.1 Storage zoning When creating a WSFC cluster to host virtual machines (VMs), Lenovo recommends using WWN-based zoning (software zoning) rather than port-based zoning (hardware zoning) on the fiber switches. In port-based zoning, a port is placed into a zone and anything connecting to that port is included in the zone (or zones). In WWN-based zoning, zones are defined using the WWNs of the connected interfaces. WWN-based zoning allows for a virtual SAN to be defined at the virtualization layer which uses the same physical HBA ports the host uses while maintaining isolation between the host and VM’s data traffic.

Lenovo recommends using single-initiator zoning for path isolation. In single-initiator zoning, zones are created based on a single initiator. This means that each zone contains a single HBA port WWN, or initiator. Multiple storage array WWNs can be added to the zone without violating the single initiator rule as storage arrays are the targets.

Zoning can be configured from the switch’s command-line interface or from the management web interface. This guide focuses on the command-line interface.


Table 2 lists the port definitions with connected devices, as well as the WWNs and aliases that are defined on each of the Brocade 6505 Switches. The WWNs in Table 2 are unique to the test environment and the WWNs for your environment will be different from those shown here.

Table 2. Port definitions on the Brocade 6505 Switches

Brocade 6505 Switch 1

Port Connected To Physical WWN Alias Zones

0 HBA Port-1 of Server 1 10:00:00:00:C9:7D:2B:46 S1PORT1 ZONE1 1 HBA Port-1 of Server 2 10:00:00:00:C9:95:2B:28 S2PORT1 ZONE2 2 HBA Port-1 of Server 3 10:00:00:00:C9:71:C0:96 S3PORT1 ZONE3 3 HBA Port-1 of Server 4 10:00:00:00:C9:82:B2:16 S4PORT1 ZONE4 4 V3700 Node-1 Port-1 50:05:07:68:03:04:12:04 N1PORT1 ZONE1, ZONE2, ZONE3, ZONE4 5 V3700 Node-2 Port-1 50:05:07:68:03:04:12:05 N2PORT1 ZONE1, ZONE2, ZONE3, ZONE4

Brocade 6505 Switch 2

Port Connected To Physical WWN Alias Zones

0 HBA Port-2 of Server 1 10:00:00:00:C9:7D:2B:47 S1PORT2 ZONE1 1 HBA Port-2 of Server 2 10:00:00:00:C9:95:2B:29 S2PORT2 ZONE2 2 HBA Port-2 of Server 3 10:00:00:00:C9:71:C0:97 S3PORT2 ZONE3 3 HBA Port-2 of Server 4 10:00:00:00:C9:82:B2:17 S4PORT2 ZONE4 4 V3700 Node-1 Port-2 50:05:07:68:03:08:12:04 N1PORT2 ZONE1, ZONE2, ZONE3, ZONE4 5 V3700 Node-2 Port-2 50:05:07:68:03:08:12:05 N2PORT2 ZONE1, ZONE2, ZONE3, ZONE4

To create the necessary zoning, Lenovo recommends following the steps below:

1. Create aliases for the HBA ports and the V3700 ports using their WWN identifiers.

2. Create zones using the aliases created in step 1. Each zone should consist of a single initiator (HBA port), and two V3700 ports, as shown in Table 2 above.

3. Create the zone configuration and add the zones created in step 2.

4. Save the zone configuration.

5. Enable the zone configuration.

To define the zones on the switches, perform the following steps:

1. Using SSH (Secure Shell), log in to the CLI of the first switch using the management IP address of the switch.

2. Run the following commands on SAN Switch 1 to create the zone configuration.

Switch:admin> alicreate "S1PORT1", "WWN of Server-1's Port-1"




Switch:admin> alicreate "N1PORT1", "WWN of Node-1's Port-1"



Switch:admin> zonecreate "ZONE1", "S1PORT1; N1PORT1; N2PORT1"




Switch:admin> cfgcreate "SHAREPOINT","ZONE1; ZONE2; ZONE3; ZONE4"

Switch:admin> cfgsave

Switch:admin> cfgenable "SHAREPOINT"

3. Repeat this process on SAN Switch 2 to complete the zoning.











Switch:admin> cfgcreate "SHAREPOINT","ZONE1; ZONE2; ZONE3; ZONE4"

Switch:admin> cfgsave

Switch:admin> cfgenable "SHAREPOINT"

5.2 Configuring the host bus adapters After you install the HBA and install the driver in Windows Server, you must configure the HBA. Lenovo recommends using the latest supported driver for the HBA when connecting to the Storwize V3700.

To check your driver version, open Microsoft Windows Device Manager and expand the Storage Controllers section.

Figure 6 shows the current driver using Microsoft Windows Device Manager.

Figure 6. Storport driver for the Emulex 8 Gb FC HBA as shown in Windows Device Manager

For the Emulex HBA StorPort driver, accept the default settings and set topology to 1 (1=F_Port Fabric) using the Emulex utility OneCommand Manager (default is 2). Reset the port using OneCommand Manager after making the change (the option to reset the port is located under Port in the main menu).

Figure 7 shows the location of the topology setting in OneCommand Manager.


Figure 7. Changing the topology of the HBA ports using OneCommand Manager

Modify the topology setting to “1” for each of the HBA ports on each of the servers before continuing.

5.3 Enabling multipathing The IBM Subsystem Device Driver Device-Specific Module (SDDDSM) is a multipath driver that is required when multiple connections to storage are present. When you use SDDDSM for multipathing with the Storwize V3700, it is important to use the latest HBA driver provided by IBM.

For this document, we used SDDDSM version 2.4.4.0 for Windows Server 2012 R2.

SDDDSM works in conjunction with the Microsoft Multipath I/O (MPIO) feature to support dynamic multipathing. Dynamic multipathing automatically configures and updates available paths to a storage volume. SDDDSM uses a load-balancing policy to equalize the load across all preferred paths. No user intervention is required, other than the typical new device discovery on a Windows Server operating system. SDDDSM is dependent on the Microsoft MPIO feature and will install it along with SDDDSM if not already installed.

You can download SDDDSM from: ibm.com/support/docview.wss?uid=ssg1S4000350

To install SDDDSM, download SDDDSM from the IBM website (using the link above) and extract the zip file onto each of the x3550 M5 servers. Run the setup.exe file to install SDDDSM. After the installation completes, reboot the server.

http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000350


Figure 8 shows SDDDSM during the install process.

Figure 8. SDDDSM install progress

5.4 Host definition on the Storwize V3700 Before performing the storage partitioning, define the hosts on the Storwize V3700. To do so, first obtain the WWNs of the HBA ports installed in each of the servers by opening Emulex OneCommand Manager to view the WWNs, as shown in Figure 9.

Figure 9. Finding WWPNs using OneCommand Manager

After you have listed the HBA port WWNs, open the Storwize V3700 web interface and authenticate. The web interface is shown in Figure 10.


Figure 10. Storwize V3700 Web UI

To define the hosts follow the steps below:

1. Open the Hosts window by clicking the icon illustrated by a disk-group attached to a server (highlighted in Figure 11) and then click Hosts.

Figure 11. Host menu option on the Storwize V3700

2. Click New Host and then click Fiber Channel Host on the Create Host window.

3. Type a name for the host, then select one of the WWNs from the dropdown list and click the Add Port to List button. Select the second WWN associated to the server and click the Add Port to List button.


Figure 12. Entering the WWNs of the HBAs installed in the servers

4. Click the Create Host button to create the host.

5. Repeat the process for the HBA ports on the remaining servers.


6 Storage partitioning This section provides details on storage partitioning using the Storwize V3700 management interface.

First a storage pool is created. Then the storage pool is split into three logical drives; two 5 GB logical drives for the cluster quorum drive and a larger drive for the cluster-shared volume (CSV), which houses the Hyper-V VHDX files for the VM system files.

6.1 Create storage pool To create a storage pool, follow the steps below:

1. Open the Internal Storage window by clicking the graphic shown in Figure 13 and then clicking Internal Storage from the pop-up menu.

Figure 13. Internal Storage menu option

2. On the Internal Storage window, click the Configure Storage button to open the Configure Internal Storage dialogue box.

3. On the Configure Internal Storage dialogue box select the radio button labeled Select a different configuration. Next, select the appropriate drive class from the from the Drive Class drop-down (the drive class will vary depending on the type of drives you have installed). In this example, 900 GB small form factor (SFF) 10k SAS drives are used for the cluster volumes. Next, select the type of RAID to use for the MDisk; in this case it is RAID-10 for the cluster pool. (The SharePoint data will reside on a different pool.) Next, select optimize for performance. Finally, enter the number of drives you want defined as MDisks. Figure 14 shows that 6 disks have been selected to create the MDisk.


Figure 14. Configuring internal storage

4. Click Next after you have configured the internal storage.

5. On the next page of the dialogue box, select the radio button labeled “Create one more new pools”. Finally, type a name for the new storage pool and click Finish.

6.2 Create logical volumes The next step is to define logical volumes from the storage pool that you just created and map the volumes to the hosts that were defined in a previous section. To define the logical volumes and map them to the hosts, follow the steps below:

1. Open the Volumes by Pool window by clicking the graphic shown in Figure 15 and then clicking Volumes by Pool.


Figure 15. Volumes by Pool menu option

2. On the Volumes by Pool window, click the Create Volume button.

3. When the Create Volume window opens, click the volume type you would like to use. Click Generic to continue.

4. One you click Generic, the window expands with a list of available Storage Pools. Click the Storage Pool you created earlier.

5. Enter the size of the size of the logical volume (in GB) and then type a name. Click the Create and Map to Host button. The example shown in Figure 16 is one of the 5 GB cluster quorum logical drives.

Figure 16. Defining the size and name of a logical volume


6. After the task completes, click the Continue button.

7. On the next window, select a host from the drop-down to open the Modify Host Mappings window.

8. Click the Apply button to apply the current mapping, then using the Host drop-down select the second server, as shown in Figure 17.

Figure 17. Modify Host Mappings window

9. Click the Apply button again, to apply the same mapping to the second host. At this point a warning dialogue will appear informing you a logical volume has been mapped to multiple hosts. Click Map All Volumes to continue.

10. Repeat the process to create a second 5 GB volume and assign it to the servers that will comprise the SQL Server cluster.

Next, follow the steps outlined above to create a volume to house the VHDX files for the VMs. This guide uses 4 VMs. Each VM will be assigned a 127 GB VHDx file for the VM’s system files. Therefore, a 508 GB volume is required to house the four 127 GB VHDx files. However, extra space should be allowed for additional VMs that might be needed in the future. Therefore, create a single volume using the storage pool’s remaining capacity (2 TB) and map it to the two servers that will comprise the Hyper-V cluster.

Microsoft recommends the following minimum free space on CSV volumes containing Hyper-V VM VHD and VHDX files:

• 15% free space if the partition size is less than 1 TB • 10% free space if the partition size is between 1 TB and 5 TB • 5% free space if the partition size is greater than 5 TB


7 Creating Windows clusters This section describes how to configure the Windows servers for clustering and connect them to the shared storage volumes used for the cluster shared volume (CSV) and for the cluster quorum.

The logical volumes created in the previous section should now be visible to the servers. Before continuing, verify that the logical volumes are visible in the Disks section of Windows Disk Manager on all the servers, as shown in Figure 18. The servers in the SQL Server cluster will not have the CSV volume because they are not hosting VMs. It may be necessary to perform a disk rescan to refresh the list.

Figure 18. Windows Disk Manager showing the new logical volumes on a Hyper-V cluster server

At this stage only one server at a time can have a disk online, until they have been added to CSV using the Failover Cluster Manager.

Verify that the servers can bring the drives online from a single server, then bring the drives online and initialize the drives as GPT (GUID Partition Table) disk. Create a new Windows volume on each of the drives, using the entire available capacity. It is not necessary to assign drive letters because the volumes will be used for specific clustering roles such as CSV and cluster quorum. Format the new volumes using NTFS. Volumes used for VHD/VHDx files, including CSV’s, should use an allocation size of 64K.

7.1 Create the WSFC cluster To create the WSFC cluster on Windows Server follow the steps outlined below:

1. If the Failover Clustering feature has not been installed on the servers, install the feature using Windows Server Manager.

2. After the Failover Clustering feature is installed, open the Failover Cluster Manager.

3. Validate the server configuration by running the Validate a Configuration Wizard from the Failover Cluster Manager. Because the cluster has not yet been formed, add both servers to the validation, as shown in Figure 19. The cluster validation wizard checks for available cluster-compatible servers, and validates storage and networking. To ensure a successful test, verify that the intended cluster storage is online to only one of the cluster nodes.


It is important to temporarily disable the default IBM USB Remote NDIS Network Device on all cluster nodes, because it causes the validation to issue a warning during network detection, due to all nodes sharing the same IP address.

Figure 19. Validate a Configuration Wizard

4. Address any issues flagged during the validation before continuing.

5. After the validation passes, leave the checkbox labeled Create the cluster now using the validated nodes… checked and click the Finish button to open the Create Cluster Wizard.

6. In the Create Cluster Wizard type a name for the cluster, then uncheck all networks except for the public one (192.168.40.0/24). Type an IP address to be used as the administrative access point for the cluster, as shown in Figure 20. Click Next to continue.


Figure 20. Defining the administrative access point for the cluster

7. On the Confirmation page, uncheck the checkbox labeled Add all eligible storage to the cluster and click Next.

8. After the cluster has formed, click the Finish button to exit the wizard and return to the Failover Cluster Manager.

9. Repeat this process using the two servers that comprise the SQL Server cluster.

7.2 Adding the cluster shared volumes After the clusters have been created, the storage volumes need to be assigned as disks under Windows. Follow the steps below on each of the clusters to assign the disks:

1. Using Failover Cluster Manager, select the cluster from the navigation pane and expand the Storage section. Click Add Disk in the Actions pane, as shown in Figure 21.

Figure 21. Adding a disk to the cluster


2. Confirm that both the cluster quorum volume and the VHDx volumes are checked and then click OK to continue.

When creating the SQL Server cluster, the only disk available is the quorum disk.

3. Lenovo recommends renaming the disks within the Failover Cluster Manager for better documentation. After the disks have been added, you can right-click a disk and click Properties. Type a new name for the disk and click the OK button. The names used in this guide are Quorum and CSV_VHDx.

4. Right-click the disk named CSV_VHDx (the 2.00 TB disk), and click Add to Cluster Shared Volumes from the right-click menu. The Assigned To column will update from Assigned Storage to Cluster Shared Volume.

This step is not required when creating the SQL Server cluster.

Next the quorum disk needs to be assigned. To manually assign the quorum disk follow the steps below:

1. With the cluster selected, on the Actions pane click More Actions (shown in Figure 22), and then click Configure Cluster Quorum Settings. The Configure Cluster Quorum Wizard appears. Click Next.

Figure 22. Failover Cluster Manager - More Actions menu option

2. On the Select Quorum Configuration Options page, select the radio button labeled Select the quorum witness. Click Next.

3. On the Select Quorum Witness page, select the radio button labeled Configure a disk witness. Click Next.

4. On the Configure Storage Witness page, check the drive you would like to use for the cluster quorum, as shown in Figure 23. Click Next.


Figure 23. Select a disk to use as the quorum

5. Click Next on the Confirmation page. After it completes click Finish to close the wizard.

6. Verify that the disk has successfully been added as a cluster quorum disk witness by navigating to Disks and checking the Assigned To column. The cluster quorum disk should be assigned to Disk Witness in Quorum.

After you have assigned the cluster shared volume and the cluster quorum disk, the storage section should look similar to that shown in Figure 24.

As mentioned earlier, the storage section will not include the CSV on the SQL Server cluster, because the SQL Server cluster does not host VMs.

Figure 24. The Storage section of Failover Cluster Manager


7.3 Configuring the cluster network Lenovo recommends renaming the cluster networks for better documentation. The networks should also be configured to limit the scope of network traffic to its intended use. To change the name and scope of the network follow the steps below:

1. Expand the Networks section in the Navigation pane and right-click each of the listed networks. Click Properties from the right-click menu.

2. Rename the network using Table 1 to determine the name and scope of the network. The Live Migration network and the Cluster Private network should be Cluster Only. The Management network and the Public network should include the clients. If a network requires client access, check the box labeled Allow clients to connect through this network, as shown in Figure 25.

Figure 25. Network properties

3. After you have renamed the network and correctly configured the scope, click OK.

Figure 26 shows the renamed networks.


Figure 26. Renamed networks on the Hyper-V cluster

When creating the Hyper-V cluster only, the last step is to configure Live Migration:

1. Next, click Live Migration Settings in the Actions pane to open the Live Migration Settings window.

2. Uncheck all networks except the 192.168.50.0 network (named Live Migration Network). Click OK.

The Live Migration network is not present when creating the SQL Server cluster.


8 Microsoft Hyper-V configuration This section covers the Hyper-V configuration for the Hyper-V cluster servers.

Using Hyper-V Manager, set the default paths for VM creation to use the CSV. The CSV disks are identified by a path name and each path appears to be on the system drive of the host server as a numbered volume under the \ClusterStorage folder. This path is the same when viewed from any node in the cluster. For example, the CSV created earlier will appear to each node in the cluster as C:\ClusterStorage\Volume1.

To configure Hyper-V to use the CSV follow the steps outlined below:

1. Using Hyper-V Manager, select the Hyper-V server and click Hyper-V Settings… from the Actions pane.

2. In the Server section, select the first option, Virtual Hard Disks. Type a new path for the VHDX files that points to the CSV.

3. Repeat the process to change the path for the VM configuration settings by selecting VMs and typing a new path that points to the CSV.

4. Repeat this process on the remaining cluster nodes.

At this point the Hyper-V cluster is operational and ready to host active roles.


9 Creating a highly available VM for SharePoint Server 2013

After the Hyper-V cluster is up and running, the SharePoint virtual infrastructure can be created. The first step is to build the VMs that will provide the virtual infrastructure for the SharePoint environment.

For this guide, four VMs are required: two VMs for the presentation layer’s web servers and two VMs for business layer’s application servers. The VMs have the following configuration:

• 24 GB memory • 4 virtual processors • 1 SCSI controller with two VHDX files

o 127 GB VHDX for the system files and operating system o 80 GB VHDX for the SharePoint installation

• 2 network adapters o Network adapter 1 = Public network 192.168.40.x o Network adapter 2 = Management network 192.168.70.x

9.1 Creation of SharePoint VMs Follow the steps below to create the highly available VMs:

1. In Failover Cluster Manager, with the cluster selected, click Roles in the Navigation pane.

2. In the Actions pane, click Virtual Machines…, and then click New Virtual Machine. The New Virtual Machine Wizard appears. Select one of the cluster nodes and click OK.

It is important to spread the VMs among the cluster nodes. Don’t place all the VMs on the same node.

3. Click Next to bypass the Before You Begin page.

4. On the Specify Name and Location page, type a name for the VM. Verify that the location to store the VM files is the path to the cluster shared volume. Click Next.

5. On the Specify Generation page, select Generation 2. Click Next.

6. On the Assign Memory page, specify the amount of memory required for the operating system that will run on this VM. Click Next.

Do not select dynamic memory as it is not supported by SharePoint Server 2013.

7. On the Configure Networking page, connect the network adapter to the virtual switch that is associated with the physical network adapter (ClusterSwitch in this guide). Click Next.

8. On the Connect Virtual Hard Disk page, select Create a virtual hard disk. If you want to change the name, type a new a name for the virtual hard disk. The default location of the VM files is located on the CSV and was configured in section Microsoft Hyper-V configuration. Click Next.

9. On the Installation Options page, click Install an operating system from a bootable image file. Navigate to the location of your installation media and select the appropriate file. Click Open to select the file, and then click Finish.


10. After the Windows installation completes, install.NET Framework version 3.5 on all the VMs.

After the VM is created, the High Availability Wizard in Failover Cluster Manager automatically configures the VM for high availability.

Before the VM is powered on, assign the correct number of virtual processors using the following steps:

1. In Failover Cluster Manager, select the cluster and click Roles in the Navigation pane.

2. In the Details pane, right-click the VM that was just created and click Settings.

3. Under the Hardware section of the Settings window, click Processor.

In the Details pane of the Settings window, use the drop-down labeled Number of virtual processors to assign the correct number of processors.

4. Click OK.

The VM configuration is now complete. Repeat the configuration process on the remaining VMs.

9.2 Changing the VM save state on shut down for migration For each VM you can configure automatic stop and start behavior if a physical computer shuts down. The options for stop are as follows:

• Save State. The current state of the VM is saved. When the VM is started, Hyper-V restores the VM to the saved state.

• Turn Off. This is the equivalent of pulling the power plug on a server. • Shut Down the Guest OS. This is the equivalent of shutting down a computer by using the Windows

Shut down option.

VMs that start from a saved state will be out of sync with the other servers in the SharePoint cluster. Therefore, Microsoft recommends that you configure the SharePoint VMs to use shutdown as the migration method (rather than save state), because it minimizes that chances that the VM can be corrupted. When a shutdown happens, all timer jobs that are running can finish, and there will be no synchronization issues when the VM restarts.

Therefore, all failover activity occurring at the hypervisor level must result in a cold boot when the VM is activated on the target node. All planned migrations must result in either a shutdown and cold boot, or an online migration that makes use of a technology such as Hyper-V Live Migration.

The opposite of an automatic stop is an automatic start. Hyper-V provides the following startup options when the physical server restarts:

• Do nothing. You have to start the VM manually regardless of its state when the physical server shut down.

• Automatically start if the VM was running when the service stopped. • Always start this VM automatically. Hyper-V starts the VM regardless of its state when the physical

server shut down.

Microsoft recommends you select either of the first two options. Both options are acceptable. In addition to the previous start options, you can configure a startup time delay for a VM. Microsoft recommends you do this to


reduce resource contention on a virtualization host. However, if your start option is to do nothing, this is not an issue.

To configure the VMs to shut down rather than save state upon a migration, follow the steps below:

1. In Failover Cluster Manager, select the cluster. Click Roles in the Navigation pane.

2. In the Details pane, right-click the VM that was just created in section Creation of SharePoint VMs. Click Settings.

3. In the Navigation pane, scroll down to the Management section. Click Automatic Stop Action.

4. In the Details pane, select the radio button to shut down the guest operating system. Click OK.

The automatic startup sequence for the VMs should be configured such that the application servers start first, followed by the web servers. To configure the VMs to start automatically, follow the steps below:

1. In Failover Cluster Manager, select the cluster. Click Roles in the Navigation pane.

2. In the Details pane, right-click the VM that was just created and click Settings.

3. In the Navigation pane, scroll down to the Management section. Click Automatic Start Action.

4. In the Details pane, select the radio button to automatically start if it was running when the service stopped.

5. Under the section labeled Automatic Start Delay enter the startup delay in seconds to stagger the start of the VMs. For this example the application VMs have a 0 second start delay and the web server VMs have a 60 second start delay. Click OK.

9.3 VM preferred owners To help prevent situations where all VMs migrate to a single cluster node when others are available, a highly-available VM can be configured with degrees of affinity for available nodes in the cluster. This affinity is called preferred owners. For example, a VM that is hosted on node-1 of the cluster and has preferred owners configured as node-1, node 2, and node-3 in descending priority order would failover to node-2 if node-1 were to fail. If node-2 failed, or was offline, the VM would failover to node-3.

The VMs are configured as shown below in Table 3.

Table 3. VM cluster node preferred ownership

VMs Hyper-V Cluster Node1 Hyper-V Cluster Node 2

SharePoint_Web1 1st Priority 2nd Priority

SharePoint_Web2 2nd Priority 1st Priority

SharePoint_App1 1st Priority 2nd Priority

SharePoint_App2 2nd Priority 1st Priority

To configure preferred ownership follow the steps below:

1. In Failover Cluster Manager, select the cluster and click Roles in the Navigation pane.

2. In the Details pane, double-click the VM you wish to configure to open its Properties window.


3. In the Properties window, click the checkbox next to the Hyper-V host servers and use the arrow keys to change the priority with the highest priority on top, as shown in Figure 27. Click OK.

Figure 27. Changing host server preferred ownership

4. Repeat this process to configure the preferred owner of the remaining virtual machines.

9.4 VM network configuration The VMs are each assigned two virtual network adapters. The first network adapter is on the public network (VLAN 40) so it can join the domain. The second network adapter is on the management network (VLAN 70) so the VM can communicate with the management infrastructure in place at the corporation.

To add and assign the VM’s network adapters, follow the steps below:

1. After a VM has been created, from within Failover Cluster Manager, click Roles from the navigation pane.

2. Right-click the VM and click Settings.

3. Click Add Hardware from the Hardware section.

If you added a virtual switch during the creation of the VM, there will be an existing network adapter under the Hardware section. Therefore, only one additional adapter should be created. The existing adapter will need a VLAN assigned.

4. Select Network Adapter from the Hardware section and click Add, as shown in Figure 28.


Figure 28. Adding a virtual network adapter

5. On the next page select ClusterSwitch (or the name you defined for the virtual switch) from the drop-down labeled Virtual switch. Check the checkbox labeled Enable virtual LAN identification and type 40 as the VLAN identifier (or 70 as the VLAN identifier if you are creating the adapter for the management network). Click OK.

6. Repeat this process until each VM has two network adapters: one on VLAN 40 and one on VLAN 70.

After the network adapters have been added and assigned to VLANs, start the VMs and assign IP addresses from within Windows Server and join the VMs to the domain.

9.5 Adding an additional drive for the SharePoint install files As a best practice, Lenovo recommends installing SharePoint on a drive other than the VM’s system drive. For the purposes of this guide, a second 80 GB drive is created and assigned to each VM for the SharePoint installation.

To add a second VHDX file to the VMs, follow the steps below:

1. From within Failover Cluster Manager, click Roles from the navigation pane.

2. Right-click one of the VMs in the detail pane, and click Settings in the right-click menu.

3. Click SCSI Controller in the Hardware section. In the details pane select Hard Drive and click the Add button, as shown in Figure 29.


Figure 29. Adding a hard drive to an existing VM

4. In the Hard Drive section, ensure that Virtual hard disk is selected and click the New button to open the New Virtual Hard Disk Wizard.

5. Click Next to bypass the Before you begin page.

6. Select the Fixed size radio button and click Next.

7. On the Name and Location page, type a meaningful name for the virtual hard drive and verify that the location is correct. Click Next to continue.

8. On the Configure Disk page, verify that the Create a new blank hard disk radio button is selected and enter a size for the virtual hard drive. Lenovo recommends 80 GB for the SharePoint drive. Click Finish to create the drive.

9. Repeat this process for the remaining SharePoint VMs.


10 Installing and configuring SQL Server 2012 SP2

After the SQL Server cluster is up and running, the SharePoint virtual infrastructure can be created. The first step is to build the VMs that will provide the virtual infrastructure for the SharePoint environment.

At this point the WSFC cluster for SQL Server 2012 SP2 should be up and running. The next step is to install SQL Server 2012 SP2 on each of the cluster nodes. However, before SQL Server can be installed, a number of logical drives must be created on the storage and assigned to the servers in the SQL Server cluster.

• 4-Disk, RAID-10 array for TempDB • 2-Disk, RAID-1 array for TempDB’s log files • 8-Disk, RAID-10 array for default Backup location • 4-Disk, RAID-10 array for User Databases

After SQL Server is installed on both the cluster nodes, then it must be configured for SharePoint and as an AlwaysOn Availability Group.

10.1 Install SQL Server 2012 SP2 Follow the steps below to install SQL Server 2012 SP2:

1. The first step of the SQL Server install is to click New SQL Server stand-alone installation… as shown in Figure 30.

Figure 30. Selecting the correct SQL Server installation type

2. The installation will run a number of system verification checks. After that completes, click OK to continue.

3. On the Product Key page, enter the product key for your organization. Click Next.

4. On the License Terms page, click the checkbox to accept the terms. Click Next.

5. On the Product Updates page install available updates or click Next to continue.

6. After another round of system verification checks, click Next to continue.

7. On the Setup Role page, leave the default selected (SQL Server Feature Installation). Click Next to continue.


8. On the Feature Selection page, the only required feature for SharePoint is Database Engine Services. However, for AlwaysOn Availability Groups, the SQL Server Replication service should be selected as well. Management tools and full-text search are also quite useful options. If a service is required at a later date, run the installation again and add the required service. Select the services, as shown in Figure 31. Click Next to continue.

Figure 31. SQL Server feature selection

9. After another round of system verification checks, click Next to continue.

10. On the Instance Configuration page, select either the default instance or a named instance to install. If you are planning to install a single instance, use the default instance. However, if the SQL Server is used for anything other than SharePoint, or if you plan to install multiple instances, use a named instance for SharePoint. Next, type a location for the instance root directory. In this case, the default instance is used as is the default instance root directory, as shown in Figure 32. Click Next to continue.


Figure 32. SQL Server instance configuration

11. The installation will check to verify that the directory specified as the instance root directory has enough disk space. Click Next to continue.

12. On the Server Configuration page, select an AD user for the SQL Server Agent and the SQL Server Database Engine. Type the password for the AD user in the space provided, as shown in Figure 33. The AD user does not require elevated privileges. In this version of SharePoint, a specific collation is not required so leave the default. Click Next to continue.

Figure 33. SQL Server server configuration

13. On the Database Engine Configuration page, leave Windows authentication as the default. However, to provide a back door into SQL Server, click the Add Current User button to add the current user as a SQL Server administrator. This account needs to be secure; therefore, the domain administrator account is used.


14. Next click the Data Directories tab, as shown in Figure 34. This step is the most complicated part of a SQL Server install. There are many methods for designing the database, log, and backup locations. Some methods increase performance, some reduce management overhead, and some maximize isolation. One assured best practice is to move Temp DB off the system drive and locate it on separate disks. In any case, it is important that the same method is used for both nodes of the SQL Server cluster, because they must be configured identically.

Assign a User database directory, Temp DB directory, Temp DB log directory, and a Backup directory. These paths should point to the drives you created on the SAN, as shown in Figure 34. Click Next to continue.

Figure 34. SQL Server database engine configuration

15. Click Next to bypass the Error Reporting page.

16. Click Next to bypass the Installation Configuration Rules page.

17. On the Ready to Install page, note the path at the bottom. It points to a file called ConfigurationFile.ini, which contains all the selections made during the install process. Click Install to begin the installation.

18. After the installation completes, repeat the process on the other cluster node.

10.2 Configuring max degree of parallelism New in SharePoint 2013 is a requirement that the maximum degree of parallelism (MAXDOP) must be set to 1. In previous versions, having MAXDOP set to 1 was a recommendation, not a requirement.

To change the MAXDOP to 1, follow the steps below:

1. Open SQL Server Management Studio (SSMS) and right-click the instance name. Click Properties from the right-click menu.

2. Under Select a Page, click Advanced. In the details pane, scroll down and change Max Degree of Parallelism to 1, as shown in Figure 35. Click OK.


Figure 35. Setting MAXDOP to 1

3. Repeat this process on the second SQL Server.

10.3 Assign permissions The account used to install SharePoint needs certain permissions on the SQL Servers to create the databases and manage security settings. To assign these permissions follow the steps below:

1. Open SQL Server Management Studio (SSMS. In the Object Explorer pane, under the instance you are using for SharePoint, expand Security, and then right-click Logins. Click New Login… from the right-click menu.

2. On the New Login page, under General, enter the name of the AD account that will be used to install SharePoint, as shown in Figure 36.


Figure 36. Creating a new login for SQL Server

3. Next, click Server Roles in the Select a page pane, and click the checkboxes for dbcreator and securityadmin privileges, as shown in Figure 37. Click OK to continue.

Figure 37. Assign the login account SQL Server privileges


10.4 Allowing access through the Windows firewall To allow SharePoint to contact the SQL Servers, the correct ports must be opened in the firewall. If not using the Windows Firewall, please reference the product documentation.

The SQL Server default instance running over TCP uses port 1433. To open port 1433 through the Windows Firewall for a SQL Server default instance, run the following command from PowerShell on each of the SQL Servers.

PS> netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action

= allow localport = 1433 remoteip = localsubnet profile = DOMAIN

By default, named instances (including SQL Server Express) use dynamic ports. This means that every time the Database Engine starts, it identifies an available port and uses that port number. If the named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433. If other instances of the Database Engine are installed, it will probably use a different TCP port. Because the port selected might change every time the Database Engine is started, it is difficult to configure the firewall to enable access to the


correct port number. Therefore, if a firewall is used, Lenovo recommends reconfiguring the Database Engine to use the same port number every time. This is called a fixed port or a static port. For more information, visit the following website: msdn.microsoft.com/en-us/library/ms177440.aspx.

10.5 Limiting memory usage To prevent SQL Server from using all the available memory and potentially locking up the server, limit the amount of memory to 90% of the available memory.

To limit the amount of memory SQL Server can use, follow the steps below:


2. Under Select a Page, click Memory. In the details pane, under Maximum server memory (in MB) enter a value which is approximately 90% of the server’s total available memory, as shown below in Figure 38.

Figure 38. Limiting the amount of memory used by SQL Server


10.6 Compress backups Because compressed data files are smaller, they require less I/O bandwidth to back up than uncompressed files do, which generally increases backup speed.

To enable backup compression, follow the steps below:


2. Under Select a Page, click Database Settings. In the details pane, check the checkbox labeled “Compress Backup” and click OK.


https://msdn.microsoft.com/en-us/library/ms177440.aspx


10.7 Configuring SQL Server AlwaysOn availability groups AlwaysOn Availability Groups must be enabled on all instances that host replica copies of the SharePoint databases.

To enable AlwaysOn Availability Groups follow the steps below:

1. Open SQL Server Configuration Manager and click SQL Server Services in the navigation pane. From the details pane, right-click your server’s instance name to open the properties dialogue box, as shown in Figure 39.

Figure 39. Access the instance properties in SQL Server Configuration Manager

2. In the Properties dialog box, click the AlwaysOn High Availability tab. Click the checkbox labeled Enable AlwaysOn Availability Groups, as shown in Figure 40. This will prompt you to restart the SQL Server service. Click OK.

Figure 40. Enabling AlwaysOn Availability Groups

3. Restart the SQL Server service by right-clicking your instance name and clicking Restart from the right-click menu.

4. After the service restart completes, repeat this process for the second SQL Server.


Before creating the Availability Group for a SharePoint 2013 farm, a temporary database must be created. After the SharePoint farm has been created, this temporary database can be removed from the Availability Group and deleted.

Create a temporary database and perform a full backup (database must be in full recovery mode). After the temporary database has been created and a full backup has run, follow the steps below to enable the Availability Group. (See section Adding SharePoint databases to the AlwaysOn availability group for steps to enable full recovery and run backups.)

1. Open SQL Server Management Studio and expand AlwaysOn High Availability in the navigation pane. Right-click Availability Groups and click New Availability Group Wizard from the right-click menu.

2. Click Next to bypass the Introduction page.

3. On the Specify Name page, type a name for the Availability Group. Click Next to continue.

4. On the Select Databases page, click the checkbox for the temporary databases you created and click Next to continue. See Figure 41.

Figure 41. Selecting the temporary database for Availability Group activation

5. In the Specify Replicas page, under the Replicas tab, click the Add Replicas button and connect to the other SQL Server instance. Next, check the checkboxes for Automatic Failover and Synchronous Commit. Leave Readable Secondary set to No, as shown in Figure 42.


Figure 42. Adding a replica to an Availability Group

6. On the Endpoints tab and verify that the port selected is 5022.

7. On the Listener tab, click the radio button labeled Create an availability group listener. Next type a string that identifies the listener in DNS. Type 1433 for the listener port, as shown in Figure 43.


Figure 43. Creating an availability group listener

8. Next, click Add to add an IP address. Verify that the correct subnet is selected (192.168.40.x for this guide). Type an IP address and click OK to return to the Specify Replicas page. Click Next to continue.

9. On the Select Data Synchronization page, verify that Full is selected as the synchronization preference. Next, type a path to folder that is accessible from both SQL Servers, as shown in Figure 44. Ensure that the SQL Server service account has write permissions on the folder. This location will be used as a temporary location to initialize databases in the Availability Group. Microsoft recommends manually initializing the databases prior to configuring them, because your network bandwidth may not be able to accommodate the size of the database backups. Click Next to continue.


Figure 44. Configuring the synchronization folder

10. The Validation page will run a number of checks to ensure that the configurations are correct. Click Next to continue.

11. On the Summary page, click Finish.

Until the SharePoint databases have been manually added to the Availability Group, it is important that they are not replicated. This process is described in section, “Adding SharePoint databases to the AlwaysOn availability group”.


11 Installing and configuring SharePoint 2013 This section covers the steps required to install and configure SharePoint Server 2013.

11.1 Installing software prerequisites To install the SharePoint prerequisites for an internet connected server follow the steps below:

1. On the welcome splash click Install software prerequisites.

2. Accept the terms on the License Terms page, and click Next to being the prerequisite software install.

3. After the software installs, click Finish to reboot the VM.

For a server that is not connected to the internet the software installation is slightly more complicated. Follow the steps below to install the required software:

1. Copy the contents of the SharePoint 2013 SP1 install media to a local directory on the server or to a network share that is accessible by all the servers. For this example the contents are saved to the C:\Source directory.

2. Download the following prerequisites and save them to the C:\Source\ PrerequisiteInstallerFiles directory:

• SQL Server 2008 R2 SP1 Native Client: download.microsoft.com/download/9/1/3/9138773A-505D-43E2-AC08-9A77E1E0490B/1033/x64/sqlncli.msi

• Microsoft WCF Data Services 5.0: download.microsoft.com/download/8/F/9/8F93DBBD-896B-4760-AC81-646F61363A6D/WcfDataServices.exe

• Microsoft WCF Data Services 5.6 (Rename this download to WcfDataServices56.exe): download.microsoft.com/download/1/C/A/1CAA41C7-88B9-42D6-9E11-3C655656DAB1/WcfDataServices.exe

• Microsoft Information Protection and Control Client (MSIPC): download.microsoft.com/download/9/1/D/91DA8796-BE1D-46AF-8489-663AB7811517/setup_msipc_x64.msi

• Microsoft Sync Framework Runtime v1.0 SP1 (x64): download.microsoft.com/download/E/0/0/E0060D8F-2354-4871-9596-DC78538799CC/Synchronization.msi

• Windows Identity Extensions: download.microsoft.com/download/0/1/D/01D06854-CA0C-46F1-ADBA-EBF86010DCC6/r2/MicrosoftIdentityExtensions-64.msi

• Windows Identity Foundation (KB974405): download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.1-KB974405-x64.msu

• Windows Server AppFabric:

http://download.microsoft.com/download/9/1/3/9138773A-505D-43E2-AC08-9A77E1E0490B/1033/x64/sqlncli.msi

http://download.microsoft.com/download/9/1/3/9138773A-505D-43E2-AC08-9A77E1E0490B/1033/x64/sqlncli.msi

http://download.microsoft.com/download/8/F/9/8F93DBBD-896B-4760-AC81-646F61363A6D/WcfDataServices.exe

http://download.microsoft.com/download/8/F/9/8F93DBBD-896B-4760-AC81-646F61363A6D/WcfDataServices.exe

http://download.microsoft.com/download/1/C/A/1CAA41C7-88B9-42D6-9E11-3C655656DAB1/WcfDataServices.exe

http://download.microsoft.com/download/1/C/A/1CAA41C7-88B9-42D6-9E11-3C655656DAB1/WcfDataServices.exe

http://download.microsoft.com/download/9/1/D/91DA8796-BE1D-46AF-8489-663AB7811517/setup_msipc_x64.msi

http://download.microsoft.com/download/9/1/D/91DA8796-BE1D-46AF-8489-663AB7811517/setup_msipc_x64.msi

http://download.microsoft.com/download/E/0/0/E0060D8F-2354-4871-9596-DC78538799CC/Synchronization.msi

http://download.microsoft.com/download/E/0/0/E0060D8F-2354-4871-9596-DC78538799CC/Synchronization.msi

http://download.microsoft.com/download/0/1/D/01D06854-CA0C-46F1-ADBA-EBF86010DCC6/r2/MicrosoftIdentityExtensions-64.msi

http://download.microsoft.com/download/0/1/D/01D06854-CA0C-46F1-ADBA-EBF86010DCC6/r2/MicrosoftIdentityExtensions-64.msi

http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.1-KB974405-x64.msu

http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.1-KB974405-x64.msu


download.microsoft.com/download/A/6/7/A678AB47-496B-4907-B3D4-0A2D280A13C0/WindowsServerAppFabricSetup_x64.exe

• Cumulative Update 1 for AppFabric 1.1 (KB2671763): download.microsoft.com/download/7/B/5/7B51D8D1-20FD-4BF0-87C7-4714F5A1C313/AppFabric1.1-RTM-KB2671763-x64-ENU.exe

3. Run the following two commands from an elevated PowerShell prompt:

PS >SharePointPath = "C:\Source"

PS > Start-Process "$SharePointPath\PrerequisiteInstaller.exe" –ArgumentList

"/SQLNCli:$SharePointPath\PrerequisiteInstallerFiles\sqlncli.msi

/IDFX:$SharePointPath\PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu

/IDFX11:$SharePointPath\PrerequisiteInstallerFiles\MicrosoftIdentityExtensions-64.msi

/Sync:$SharePointPath\PrerequisiteInstallerFiles\Synchronization.msi

/AppFabric:$SharePointPath\PrerequisiteInstallerFiles\WindowsServerAppFabricSetup_x64.exe

/KB2671763:$SharePointPath\PrerequisiteInstallerFiles\AppFabric1.1-RTM-KB2671763-x64-ENU.exe

/MSIPCClient:$SharePointPath\PrerequisiteInstallerFiles\setup_msipc_x64.msi

/WCFDataServices:$SharePointPath\PrerequisiteInstallerFiles\WcfDataServices.exe

/WCFDataServices56:$SharePointPath\PrerequisiteInstallerFiles\WcfDataServices56.exe"

4. Halfway through the installation, you will be asked to reboot the server. After the server reboots, the installation should automatically continue. If it does not, just repeat the commands above.

5. Repeat this process on the remaining three VMs.

11.2 Installing SharePoint After the prerequisites have been installed, install SharePoint on the servers.

1. On the SharePoint installation splash screen click Install SharePoint.

2. After a number of checks are run, the Product Key page will appear. Enter your product key and click the Continue button.

3. Accept the terms on the License Terms page, and click the Continue button.

4. On the next page, on the Server Type tab, verify that the radio button labeled Complete is selected as the installation type, as shown in Figure 45, and then click the File Location tab.

http://download.microsoft.com/download/A/6/7/A678AB47-496B-4907-B3D4-0A2D280A13C0/WindowsServerAppFabricSetup_x64.exe

http://download.microsoft.com/download/A/6/7/A678AB47-496B-4907-B3D4-0A2D280A13C0/WindowsServerAppFabricSetup_x64.exe

http://download.microsoft.com/download/7/B/5/7B51D8D1-20FD-4BF0-87C7-4714F5A1C313/AppFabric1.1-RTM-KB2671763-x64-ENU.exe

http://download.microsoft.com/download/7/B/5/7B51D8D1-20FD-4BF0-87C7-4714F5A1C313/AppFabric1.1-RTM-KB2671763-x64-ENU.exe


Figure 45. Selecting the type of SharePoint installation

5. On the File Location tab, type a path to a location on the second 80 GB drive that was assigned to each of the VMs, as shown in Figure 46. This will isolate the SharePoint install files from the system drive.

Figure 46. Selecting a location for the SharePoint installation files

6. Finally, click the Install Now button.


7. After the installation completes, uncheck the checkbox labeled Run the SharePoint Products Configuration Wizard Now and click Close.

8. Repeat this process on the remaining SharePoint servers.

11.3 SharePoint 2013 products configuration wizard After SharePoint has been installed on the servers, the SharePoint 2013 Products Configuration Wizard performs the tasks necessary to join the server to an existing farm, or to provision a new farm.

The initial server that you run the Configuration Wizard on to provision the new farm will be the default server name used to access the SharePoint Central Administration site. In this example, the Central Administration site is located on an application server to limit exposure. Therefore, run the Configuration Wizard from an application server before adding the web servers to the farm.

To provision the SharePoint farm, follow the steps below:

1. Run the SharePoint 2013 Products Configuration Wizard from one of the application VMs.

2. On the Welcome to SharePoint Products page, click Next.

3. A warning will inform you that some services have to be restarted or reset. Click Yes to continue.

4. On the Connect to a server farm page, select the radio button labeled Create a new server farm and click Next.

5. On the Specify Configuration Database Settings page, as shown in Figure 47, type the name for the database server. Under Specify Database Access Account, type a username for an account that the machine will always use to connect to the configuration database. Use the format DOMAIN\username and then type the password for the account. The SharePointInstall account that was created earlier in section Assign permissions is used as the Database Access Account. Click Next.


Figure 47. Specify Configuration Database Settings page

6. On the Specify Farm Security Settings, type a passphrase to secure the farm configuration data. This passphrase will be used on each server that joins the farm. Click Next.

7. On the Configure SharePoint Central Administration Web Application page you have the option to accept the random port assignment for Central Administration or you can specify a custom port. In the Configure Security Settings section, choose NTLM or Kerberos authentication. Click Next.

8. The Completing the SharePoint Products Configuration Wizard page lists a summary of the selected options. Click Next to begin the configuration.

9. After configuration completes, click Finish.

10. Run the SharePoint 2013 Products Configuration Wizard on the remaining VMs. However, rather than selecting Create a new server farm on the Connect to a server farm page, select the radio button labeled Connect to an existing farm. On the Specify Configuration Database Settings page, type the name of the database server, and then click the Retrieve Database Names button. This will autopopulate the Database name field.

11.4 SharePoint service deployment To distribute the services that run on each server follow the steps below:

1. Open SharePoint 2013 Central Administration from a domain-joined computer.

2. Click Manage Services on Server, which is located in the System Settings section.

3. You can switch servers by clicking the server name dropdown in the upper-right area of the Services on Server page, as shown below in Figure 48.


Figure 48. Services on Server page of Central Administration

4. Select the server you wish to configure first, then activate services by clicking Start, which is located in the Action column.

Before enabling SharePoint Search components, there are a number of configuration steps that must be performed. Please see the following TechNet article for steps to configure Search: technet.microsoft.com/en-us/library/gg502597.aspx

11.4.1 Distributed cache service As a best practice, the distributed cache service should run only on the web servers. However, disabling the distributed cache service on the application servers requires careful attention. Follow the steps below to disable the distributed cache service on the application servers:

1. Verify that the Distributed Cache service is started on the application servers.

2. Open the SharePoint Management Shell as Administrator and run the following commands to shutdown the distributed cache service and unregister the server:

PS> Stop-SPDistributedCacheServiceInstance -Graceful

PS> Remove-SPDistributedCacheServiceInstance

For more information about disabling the Distributed Cache service please visit the following URL: technet.microsoft.com/en-us/library/jj219613.aspx#addremove

11.5 Adding SharePoint databases to the AlwaysOn availability group

A number of databases are created during the SharePoint install. Follow the steps below to manually add the databases to the Availability Group:

1. In SQL Server Management Studio, connect to the database engine of the appropriate instance.

2. Enable full recovery on all SharePoint databases by right-clicking each database and clicking

https://technet.microsoft.com/en-us/library/gg502597.aspx

https://technet.microsoft.com/en-us/library/jj219613.aspx%23addremove


Properties from the right-click menu. Click Options in the Select a page section and then, using the drop-down labeled Recovery Model select Full, as shown in Figure 49. Click OK and repeat this step on all SharePoint databases.

Figure 49. Enabling full recovery mode on SharePoint databases

3. To run the backup process on each of the SharePoint databases, right-click each database name, click Tasks from the right-click menu, and then click Back Up….

4. After the backups are complete, expand AlwaysOn High Availability then expand Availability Groups, as shown in Figure 50. The Availability group created earlier in section Configuring SQL Server AlwaysOn availability groups should be listed. Expand the availability group created earlier, right-click the folder Availability Databases and click Add Database from the right-click menu.


Figure 50. Availability Groups in Object Explorer

5. Click Next to bypass the Welcome page.

6. On the Select Databases page, checkmark all the SharePoint databases and click Next.

7. On the Select Data Synchronization page, select the radio button labeled Full. Verify that the path to a shared network drive is correct, as shown below in Figure 51 and click Next.


Figure 51. The Select Initial Data Synchronization page

8. On the Connect to Replicas page, click the Connect button to connect to the second SQL Server, then click Next.

9. After validation runs, click Next, then click Finish.

10. The SharePoint databases are now included in the Availability Group, as shown in Figure 52.


Figure 52. SharePoint databases as part of the Availability Group

11. Repeat this process as new SharePoint databases are created to ensure database high availability.


References • Lenovo Reference Architecture for Microsoft SharePoint Server 2013

lenovopress.com/tips1319

• Installing SharePoint 2013 technet.microsoft.com/en-us/library/Cc303424.aspx

• Installing SQL Server 2012 technet.microsoft.com/en-us/library/Bb500395(v=SQL.110).aspx

• Creation and Configuration of a SQL Server 2012 AlwaysOn Availability Group msdn.microsoft.com/en-us/library/ff878265(v=sql.110).aspx

• Create a Windows Server Failover Clustering cluster technet.microsoft.com/en-us/library/Dn505754.aspx

• Configure a Hyper-V virtual machine for high availability technet.microsoft.com/en-us/library/Dd759216.aspx

http://lenovopress.com/tips1319

https://technet.microsoft.com/en-us/library/Cc303424.aspx

https://technet.microsoft.com/en-us/library/Bb500395(v=SQL.110).aspx

https://msdn.microsoft.com/en-us/library/ff878265(v=sql.110).aspx

https://technet.microsoft.com/en-us/library/Dn505754.aspx

https://technet.microsoft.com/en-us/library/Dd759216.aspx


Trademarks and special notices

© Copyright Lenovo 2015.

References in this document to Lenovo products or services do not imply that Lenovo intends to make them available in every country.

Lenovo, the Lenovo logo, ThinkCentre, ThinkVision, ThinkVantage, ThinkPlus and Rescue and Recovery are trademarks of Lenovo.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

Information is provided "AS IS" without warranty of any kind.

All customer examples described are presented as illustrations of how those customers have used Lenovo products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

Information concerning non-Lenovo products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by Lenovo. Sources for non-Lenovo list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. Lenovo has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-Lenovo products. Questions on the capability of non-Lenovo products should be addressed to the supplier of those products.

All statements regarding Lenovo future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local Lenovo office or Lenovo authorized reseller for the full text of the specific Statement of Direction.

Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in Lenovo product announcements. The information is presented here to communicate Lenovo’s current investment and development activities as a good faith effort to help with our customers' future planning.

Performance is based on measurements and projections using standard Lenovo benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here.

Photographs shown are of engineering prototypes. Changes may be incorporated in production models.

Any references in this information to non-Lenovo websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this Lenovo product and use of those websites is at your own risk.

Date post:	29-Mar-2018
Category:	Documents
Upload:	dinhtram
View:	232 times
Download:	4 times

Installation and Configuration Guide for Microsoft ... · PDF file1 Installation and...

Documents