MICROSOFT SHAREPOINT SERVER 2013 AND WITH SMB 3.0

White Paper
MICROSOFT SHAREPOINT SERVER 2013 AND
LYNC SERVER 2013 ENHANCED BY EMC VNX
WITH SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft
SharePoint Server 2013, Microsoft Lync Server 2013
• Provides an efficient virtualized infrastructure
• Ensures a cost efficient storage design
EMC Solutions Group
Abstract
This white paper documents a flexible, high-availability, and efficient
infrastructure solution for Microsoft collaboration environments using EMC®
VNX® series. The solution improves collaboration by using an efficient
virtualized infrastructure and a cost-efficient storage design to advance your
business.
August 2013
Copyright © 2013 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its
publication date. The information is subject to change without notice.
The information in this publication is provided “as is.” EMC Corporation makes
no representations or warranties of any kind with respect to the information in
this publication, and specifically disclaims implied warranties of
merchantability or fitness for a particular purpose.
Use, copying, and distribution of any EMC software described in this
publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC Corporation
Trademarks on EMC.com.
All trademarks used herein are the property of their respective owners.
Part Number H11751
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
2
Table of contents
Executive summary............................................................................................................................... 5
Business case .................................................................................................................................. 5
Solution overview ............................................................................................................................ 5
Key results ....................................................................................................................................... 5
Introduction.......................................................................................................................................... 6
Purpose ........................................................................................................................................... 6
Scope .............................................................................................................................................. 6
Audience ......................................................................................................................................... 6
Terminology ..................................................................................................................................... 6
Technology overview ............................................................................................................................ 8
Overview .......................................................................................................................................... 8
EMC VNX series ................................................................................................................................ 8
Microsoft Windows Server 2012 with Hyper-V .................................................................................. 8
Microsoft SMB 3.0 ........................................................................................................................... 9
Microsoft SharePoint Server 2013 .................................................................................................... 9
Microsoft Lync Server 2013 .............................................................................................................. 9
Solution architecture and design........................................................................................................ 10
Configuration overview .................................................................................................................. 10
Solution architecture...................................................................................................................... 11
Environment profile........................................................................................................................ 12
Hardware resources ....................................................................................................................... 13
Software resources ........................................................................................................................ 13
Storage design ............................................................................................................................... 13
Network design .............................................................................................................................. 14
File storage best practices.............................................................................................................. 16
Application design and implementation ............................................................................................. 17
Overview ........................................................................................................................................ 17
Hyper-V virtualization..................................................................................................................... 17
Failover Clustering ......................................................................................................................... 17
SMB 3.0 enhancements and features............................................................................................. 18
Multichannel ............................................................................................................................. 18
Continuous Availability on Data Mover failover .......................................................................... 19
Copy Offload ............................................................................................................................. 19
AES128 encryption .................................................................................................................... 19
Microsoft SharePoint Server 2013 .................................................................................................. 20
Design ....................................................................................................................................... 20
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
3
Configuration ............................................................................................................................ 20
Search topology ........................................................................................................................ 21
Microsoft Lync Server 2013 ............................................................................................................ 22
Design ....................................................................................................................................... 22
Configuration ............................................................................................................................ 24
Storage design .......................................................................................................................... 24
Baseline testing and validation .......................................................................................................... 26
Overview ........................................................................................................................................ 26
Failover Clustering over SMB 3.0 .................................................................................................... 26
SMB 3.0 feature support validation ................................................................................................ 26
Multichannel ............................................................................................................................. 26
Continuous Availability ............................................................................................................. 27
Copy Offload ............................................................................................................................. 29
AES128 encryption .................................................................................................................... 29
Application baseline test overview ................................................................................................. 30
SharePoint Server 2013 baseline test ............................................................................................ 30
Validation setup ........................................................................................................................ 30
SharePoint 2013 results ............................................................................................................ 31
Lync Server 2013 baseline test ...................................................................................................... 33
Stress and performance tool ..................................................................................................... 33
Test scenario ............................................................................................................................. 33
Test results................................................................................................................................ 34
Combined workloads ..................................................................................................................... 36
Overview ................................................................................................................................... 36
Impact of combined load on Lync .............................................................................................. 36
Impact of combined load on SharePoint .................................................................................... 37
Conclusion ......................................................................................................................................... 38
Summary ....................................................................................................................................... 38
Findings ......................................................................................................................................... 38
Reference ........................................................................................................................................... 39
White Papers.................................................................................................................................. 39
Product documentation.................................................................................................................. 39
Other website ................................................................................................................................ 39
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
4
Executive summary
Business case
Customers demand a lot from their storage technology. They want to simplify
management and increase service levels while reducing the total cost of the solution.
To support the broad range of new operating system (OS) features delivered by
Microsoft in Windows Server 2012, EMC has enabled its EMC® VNX® series of
products to support and take advantage of those features.
EMC has tested and documented a low-cost, flexible, and highly available reference
architecture, which takes advantage of key technologies from Microsoft and EMC.
This reference architecture showcases the application of those technologies in best
practice configurations. This white paper demonstrates a solution based on this
reference architecture. The solution supports two key collaboration technology
products from Microsoft—Microsoft SharePoint Server 2013 and Microsoft Lync
Server 2013—with a scalable SMB 3.0-based storage architecture provided by the
VNX series of storage arrays.
Solution overview
This solution is an efficient virtual infrastructure with a cost-effective storage design
that enhances customers’ collaboration experience.
The solution provides the following configurations:
Key results
•
An end-to-end infrastructure for Microsoft Office 2013 Servers, SharePoint
2013, and Lync Server 2013 for up to 10,000 users.
•
The environment runs on Windows Server 2012 and uses the features and
functionality supported by Microsoft's Hyper-V technology.
•
The storage is EMC VNX.
•
The Microsoft Server Message Block (SMB) 3.0 protocol.
This solution illustrates that:
•
The EMC VNX series arrays, together with SMB 3.0 and Microsoft Windows
Server 2012, support a 10,000-user Microsoft application environment for
SharePoint and Lync Servers 2013.
•
SMB 3.0 features supported by the VNX series provide functionality such as
Copy Offload, Multichannel, and data encryption, to improve the performance
and security of your application data.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
5
Introduction
Purpose
The purpose of this paper is to demonstrate an efficient virtual infrastructure with a
cost-effective storage design that enhances customers’ collaboration experience.
Scope
The scope of this solution is to test and validate the enhancement of a Microsoftbased collaboration environment using EMC technologies.
We 1 validated the following Microsoft Office Server components:
•
Microsoft SharePoint Server 2013
•
Microsoft Lync Server 2013
We tested the following EMC product: EMC VNX5500.
Audience
This white paper is intended for EMC employees including business developers and
solution architects, EMC partners, and EMC customers such as product managers and
service providers’ technologists and architects.
Terminology
This white paper includes the terminology listed in Table 1.
Table 1.
Terminology
Term
Definition
AVM
Automatic Volume Management
CA
SMB 3.0 Continuous Availability
CIFS
Common Internet File System
DM
Data Mover
FQDN
Fully qualified domain name
GB
Gigabyte
GbE
Gigabit Ethernet. A term describing various technologies
for transmitting Ethernet frames at a rate of a gigabit per
second.
IM
Instant messaging
I/O
Input/output
IOPS
Input/output operations per second
NAS
Network-attached storage
NIC
Network interface card
NFS
Network File System
1
In this white paper, "we" and “our” refers to the EMC Solutions engineering team that
validated the solution.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
6
Term
Definition
OE
Operating Environment
OS
Operating System
PSTN
Public Switch Telephone Network
SAN
Storage area network
SMB 3.0
Microsoft Server Message Block 3.0
SSD
Solid-state drive
TB
Terabyte
VHDX
Hyper-V virtual hard disk format—an enhanced format
available in Microsoft Windows Server 2012
VSTS
Microsoft Visual Studio Team System
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
7
Technology overview
Overview
This section provides an overview of the key components of this solution, as listed in
Table 2.
Table 2.
Solution components
System
Components
Storage platform
EMC VNX series
Virtualization platform
Microsoft Windows Server 2012 with Microsoft Hyper-V
Connectivity
Microsoft SMB 3.0
Applications
• Microsoft SharePoint Server 2013
• Microsoft Lync Server 2013
EMC VNX series
The EMC VNX series storage platform provides a dedicated network server optimized
for file and block storage access. The VNX series delivers high-end features in a
scalable, easy-to-use package. With a single-box block and file solution containing a
central management point for a distributed environment, it is possible to dynamically
grow, share, and cost-effectively manage multiprotocol file systems and provide
multiprotocol block access.
Administrators can also take advantage of simultaneous support for Network File
System (NFS) and Common Internet File System (CIFS) protocols and the storage
management framework for any network-attached storage (NAS), storage area
network (SAN), and replication needs. FAST Suite improves the performance of your
applications and resolves existing array bottlenecks by increasing cache and
relocating data to a different tier.
Microsoft Windows Microsoft Windows Server 2012 with Hyper-V provides a complete virtualization
platform, which offers increased scalability and performance with a flexible solution
Server 2012 with
from
the data center to the cloud. It makes it easier for organizations to realize the
Hyper-V
cost savings from virtualization and to optimize server hardware investments.
Windows Server 2012 Hyper-V high-availability options include incremental backup
support, enhancements in clustered environments to support virtual adapters within
the virtual machine, and inbox network interface card (NIC) teaming. In Hyper-V,
shared nothing live migration enables the migration of a virtual machine from a server
running Hyper-V to another one without the need for both servers to be in the same
cluster or to share storage.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
8
Microsoft SMB 3.0
SMB 3.0 is an application-layer network protocol that provides shared access
between nodes on a network. It also provides an authenticated inter-process
communication mechanism. For VNX File Operating Environment (OE) version 7.1.65
and later, the SMB 3.0 protocol is supported on VNX. VNX supports SMB 1.0, SMB
2.x, and SMB 3.0 protocol communications between client and server. VNX supports
SMB 3.0 enhancements that include Continuous Availability (CA), Multichannel, Copy
Offload, SMB Encryption, and other enhancements.
Microsoft
SharePoint Server
2013
Microsoft SharePoint Server 2013 provides a business-collaboration platform for
enterprise and commercial organizations. SharePoint enables organizations to share
content and information through websites, blogs, wikis, and document libraries.
These are just some of the many features of a SharePoint environment. Content
within these features can be managed collectively from start to finish.
Microsoft Lync
Server 2013
Microsoft Lync Server 2013 is an enterprise real-time communications server, which
provides the infrastructure for enterprise instant messaging, presence, and structured
conferences connectivity.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
9
Solution architecture and design
Configuration
overview
We deployed Lync Server 2013 and SharePoint Server 2013 as virtual machines on a
Windows Server 2012 Hyper-V cluster. We placed all virtual hard disks (VHDXs) on
CIFS shares exported from the VNX5500 file system via 10 gigabit Ethernet (GbE)
network and used SMB 3.0 as the communications protocol for Hyper-V cluster
connectivity to the VNX5500.
Figure 1 shows the logical view of this solution, 10,000 users for SharePoint and Lync
Servers 2013.
Figure 1.
Solution overview
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
10
Solution
architecture
Figure 2 illustrates the solution architecture. All the virtual machines were hosted on
a Windows Server 2012 Failover Cluster. Hyper-V was used for virtualization. Each
node was connected by two switches to both Data Movers on the VNX allowing for full
redundancy for the virtual machines.
Figure 2.
Solution architecture
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
11
Environment
profile
Table 3 details the solution environment.
Table 3.
Solution environment profile
Environment
Quantity
Customer configured users profile
Number of SharePoint/Lync users in the
environment
10,000
SharePoint 2013
Browse:60%
Modify:10%
Profile
Search:15%
Download:10%
Upload:5%
User concurrency
10%
4.3 TB
Total data
1 x 100 GB content database
1 x 200 GB content database
1 x 4 TB content database
Document types
Docx, xlsx, pptx, doc, xls, ppt, jpg
Site collections size
100–4,000 GB
Number of site collections
3
Sites per site collection
10–100
Document size range
10 k–10 MB (Avg. 256 kb)
Lync 2013
Audio conferences
High (375 users)
Application sharing
High (185 users)
Data collaboration
High (75 users)
Instant messaging
High (9,365 users)
Note: There are three load types in the Lync Stress and Performance Tool: Low, Medium, and
High. In this solution, we used the High load for simulation and the user number for each
test scenario is defined by the tool itself.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
12
Hardware
resources
Table 4 details the hardware resources used for testing this solution.
Table 4.
Solution hardware resources
Hardware
Quantity
Configuration
EMC VNX5500
1
EMC VNX5500 with:
• Two Data Mover 2.13-GHz CPU modules with 12 GB
memory
• Two storage processor 2.0-GHz CPUs with 12 GB
memory
• Two-port 10-GB/s Ethernet Optical I/O module
• 60 x 2 TB NL-SAS disks, 75 x 900 GB SAS disks, 5 x
200 GB flash disks
Switches
2
40-port 10-GbE switches
Physical servers
(blade servers)
4 (blades)
Single chassis, 4 x blades. Each blade contains:
• 2 x processors (20 cores total)
• 256 GB DDR3 RAM
Software resources Table 5 details the software resources for the solution.
Table 5.
Storage design
Solution software resources
Software
Version
Purpose
EMC VNX OE for Block
05.32.000.5.201
VNX operating environment
EMC VNX OE for File
7.1.65-8
VNX operating environment
Microsoft Windows Server
2012 Datacenter
Hyper-V nodes and virtual machine OS
Microsoft SharePoint Server
2013
SharePoint farm
Microsoft Lync Server
2013
Conference and instant messaging
Table 6 details the VNX5500 storage configuration used for this solution.
Table 6.
EMC VNX5500 storage configuration
Application
Storage pool
Number of
LUNs
File system
CIFS share
Lync
Lyncpool
10
LyncFS
LyncShare
SharePoint
Sppool
10
SPFS
SPShare
Virtual
machine OS
OSpool
10
OSFS
OSShare
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
13
Table 7 details the storage pool configuration for this solution.
Table 7.
Storage pool
Number of disks
RAID type
Disk type
Lyncpool
16
RAID 10
900 GB 10k rpm SAS
Sppool
10
RAID 5
900 GB 10k rpm SAS
8
RAID 6
2 TB 7.2k rpm NL-SAS
4
RAID 10
900 GB 10k rpm SAS
OSpool
Network design
Design of storage pool for application
To obtain redundancy between the Data Mover and the switch, each Data Mover was
connected to both Ethernet switches. This also enabled us to test the multichannel
features of SMB 3.0.
Table 8 details the VNX Data Mover connectivity to the network switch infrastructure.
Table 8.
IP network design
DM port
Switch port
DM2 10GbE port 0
Switch 1 Port0
DM2 10GbE port 1
Switch 2 Port1
DM3 10GbE port 0
Switch 2 Port0
DM3 10GbE port 1
Switch 1 Port1
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
14
Figure 3 shows the physical connectivity topology of the network design.
Figure 3.
Physical connectivity topology
Each Hyper-V host had four physical adapters used as virtual Ethernet adapters, as
shown in Table 9:
Table 9.
Physical adapters
Virtual adapter
Network
1
Cluster traffic
2
Management
3
4
SMB 3.0
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
15
We used one adapter for cluster communication, one for management, and two for
SMB communication. Only the management interface had external Ethernet access.
We configured all the other interfaces on private network IP addresses.
File storage best
practices
The suggested file system layout included these configurations and settings:
•
When the number of disks is set, the number of storage pools does not affect
file system performance.
•
In order to spread input/output (I/O) evenly across all the disks in a storage
pool, we used this calculation: divided the number of disks in the pool by 4 and
rounding up to the nearest 10. The result is the number of LUNs to create in the
pool.
•
Use Automatic Volume Management (AVM) to create the file system to achieve
balance between performance and capacity.
•
Enable direct writes to the file system, as shown in Figure 4, so that async
writes can be written directly to the back end to achieve better performance.
Figure 4.
•
Enable direct writes on Unisphere
Set the parameter asyncUncachedOpt as true on the Data Mover. If set to 1,
asynchronous writes to a file system mounted with the uncached option will be
written out without being buffered in cache. If set to 0, writes to a file system
mounted with the uncached option will be written out via the buffer cache. The
setting has no impact on file systems mounted without the uncached option.
Execute the following command to set the parameter:
server_param server_2-facility file-modify asyncUncachedOptvalue 1
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
16
Application design and implementation
We designed this solution for a mixed Microsoft application workload, including
SharePoint Server 2013 and Lync Server 2013, on CIFS shares exported from a
VNX5500 file system. Microsoft Windows Server 2012 Hyper-V provides the
virtualization platform for all Microsoft applications.
Overview
The following sections provide the design methodology for all Microsoft applications,
SMB 3.0 feature enhancements, Failover Clustering, and Hyper-V virtualization used
in this solution.
We used Windows Server 2012 Hyper-V as our virtualization platform for both the
SharePoint farm and the Lync system.
Hyper-V
virtualization
In Windows Server 2012, SMB 3.0 file shares can be used as shared storage for
Hyper-V. With this capability, Hyper-V can store virtual machine files, including
configuration files, VHDX files, and snapshots on SMB file shares.
Failover Clustering
This solution deploys Windows Server 2012 Failover Clustering with four nodes at the
production site. We used the Node and File Share Majority quorum configuration.
When determining where to place the virtual machines, it is important to consider
load balancing and failure protection. You should distribute virtual machines with the
same application roles across different nodes. For example, this solution separates
Lync Server virtual machines between different nodes, so if a node fails, only one of
the front-end servers is affected.
Table 10 shows the virtual machine placement on each of the solution’s failover
cluster nodes and summarizes the total resources allocated to the virtual machines.
Table 10.
Virtual machine distribution in Failover Clustering nodes
Production
site server
Virtual machine role
Virtual machine
host name
vCPU
Memory
(GB)
Node1
Lync front-end
Lync01
4
32
SharePoint Index
SPIndex01
16
16
20
48
Total
Node2
SharePoint SQL
SPSQL01
8
64
Domain controller
DC02
2
4
10
68
Total
Node 3
SharePoint app
SPAPP01
2
4
SharePoint web server
SPWFE02
8
16
SharePoint web server
SPWFE01
8
16
18
36
Total
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
17
Production
site server
Virtual machine role
Virtual machine
host name
vCPU
Memory
(GB)
Node 4
Lync front-end
Lync02
4
32
Lync back-end
Lync03
4
32
8
64
Total
For each virtual machine, we configured a fixed size VHDX disk for the virtual machine
OS. The virtual machine configuration file and the virtual machine memory swap file
(which is the same size as the memory configured for the virtual machine) are located
in the same folder as the VHDX.
There are no cluster disks in the cluster resources. All virtual disks are located in a
CIFS share, using it as the storage location.
Figure 5 shows the typical storage configuration for all virtual machines.
Figure 5.
Storage path for virtual machine OS VHDX file
The VNX series incorporates the SMB protocol as an open standard for network file
SMB 3.0
enhancements and services. SMB is a file access protocol designed for the internet and is based on the
CIFS protocol that the Microsoft Windows operating system uses for distributing file
features
sharing, printing, and communication services from a server over a network. SMB 3.0
protocol support is available with Windows Server 2012. To show the value of EMC
VNX support for SMB 3.0, the following enhancements and features have been
enabled or configured in this solution.
Multichannel
This feature uses multiple network interfaces and connections to provide higher
throughput and fault tolerance. This is achieved without any additional configuration
steps for network interfaces.
Feature benefits
SMB Multichannel provides network high availability. If one NIC fails, the applications
and clients continue operating at a lower throughput potential without any errors.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
18
SMB Multichannel is automatically configured. All network paths are automatically
detected and connections are added dynamically if the share is accessed via a fully
qualified domain name (FQDN).
Continuous Availability on Data Mover failover
The SMB 3.0 CA feature ensures the transparent failover of the VNX file server when
faults occur. It enables clients connected to SMB 3.0 shares to transparently
reconnect to another file server node when one node fails. All open file handles from
the faulted server node are transferred to the new server node, which eliminates
application errors.
Feature benefit
When a Data Mover fails, clients accessing SMB 3.0 shares created with Continuous
Availability do not perceive any application errors. Instead, they experience a small
I/O delay due to the primary Data Mover failing over to the standby Data Mover.
During the failover, the application may experience a brief spike in transactional
latency, but soon resumes normal operation.
Copy Offload
Copy Offload enables the array to copy large amounts of data without involving
server, network, or CPU resources. The server offloads the copy operation to the
physical array where the data resides. The source and destination file system should
be on the same Data Mover.
Feature benefits
Copy Offload enables faster data transfer from the source to destination system
because it does not use any client CPU cycles. This feature is most beneficial for the
following operations:
•
Deployment operations: Deploy multiple virtual machines faster. The baseline
VHDX can reside on an SMB 3.0 share, with new virtual machines deployed on
SMB 3.0 shares with Hyper-V Manager by pointing to the baseline VHDX.
•
Cloning operations: Clone virtual machines from one SMB 3.0 share to another
in minutes.
•
Migration operations: Move virtual machines between file shares on the same
Data Mover.
AES128 encryption
SMB 3.0 encryption provides secure access to Data Mover untrusted networks by
providing end-to-end encryption between the client and VNX system. It does not
require specialized hardware, IPSec, or WAN accelerators. This feature works with
SMB 3.0 clients only.
Feature benefit
SMB 3.0 encryption does not require any additional software or hardware. It protects
data on the network from attacks and eavesdropping.
For more information about SMB 3.0 support on EMC VNX series, refer to the EMC VNX
Series: Introduction to SMB 3.0 Support white paper.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
19
Microsoft
SharePoint Server
2013
Design
We designed the SharePoint farm as a medium-sized farm with two web servers, one
crawl server, one Microsoft SQL Server 2012, and an application server. The farm was
a publishing portal with site collections containing several Document Center sites.
The entire farm, not including boot volumes for the virtual machines, was stored on a
single large mixed-storage pool.
The farm consisted of three content databases (4 TB, 100 GB, and 200 GB).
Configuration
We designed the storage for performance and capacity with all volumes, except the
boot volumes, stored on NL-SAS disks in a RAID 6 6+2 configuration and SAS disks in
a RAID 5 4+1 configuration in a mixed storage pool.
We created ten LUNs in the storage pool and used AVM to create the SharePoint file
system. The SharePoint file system was exported as a CIFS share over SMB 3.0 to the
Windows Server 2012 Hyper-V nodes.
Figure 6 shows the solution’s disk layout.
Figure 6.
Disk layout
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
20
Table 11 details the SharePoint virtual machine and disk configurations.
Table 11.
SharePoint virtual machine configuration
Virtual machine
role
Quantity
vCPU
Memory
(GB)
VHDX disk
(GB)
Description
Web and query
2
8
16
40
Boot
300
Query
Application
1
2
4
40
Boot
Index
1
16
16
200
Boot
200
Index
40
Boot
7000
Content databases
520
Content database logs
200
Temp databases
40
Temp database logs
100
Config databases
10
Config database logs
550
Search databases
55
Search database logs
SQL Server
1
8
64
Search topology
Table 12 shows that the Index server performed the crawls as well as content and
analytics processing. The content and analytics processing occurs while the crawl is
running and its default path is the C: drive. We allocated a 200 GB boot drive for this
purpose and located this drive on the SharePoint file system instead of the host OS
file system. Our recommendation is to choose a different path for content and
analytics processing when installing SharePoint.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
21
Table 12.
Search topology
Search role
Server
Admin
Crawler
Content
processing
Analytics
processing
X
X
X
Query
processing
Index
partition
SPWFE01
X
X
SPWFE02
X
X
SPAPP01
X
SPINDEX01
X
The query processing was mirrored across the web servers.
Microsoft Lync
Server 2013
Design
In this solution, we used the Microsoft Lync Server Planning Tool to design the Lync
Server topology. The Planning Tool uses the information supplied, coupled with
preferred practices for topology design and capacity, to present a recommended
topology.
You can download the Planning Tool from the Microsoft Download Center.
Based on a 10,000-user profile, we deployed one front-end pool containing two frontend servers and one SQL Server server.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
22
Figure 7 shows the entire Lync system topology. For test purposes, only the front-end
servers and one SQL Server database server were deployed.
Figure 7.
Lync system topology
After deploying the Lync system, you can check the system status from the Lync
Server 2013 Control Panel. Figure 8 shows that the system is healthy and ready for
the stress and performance tool to simulate the load.
Figure 8.
System status in the Lync Server 2013 Control Panel
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
23
Configuration
For each Lync Server virtual machine, Microsoft recommends the configuration shown
in Table 13.
Table 13.
Lync Server virtual machine recommended configuration
Hardware component
Recommended
CPU
64-bit dual processor, hex-core, 2.26 gigahertz (GHz) or higher
Memory
32 gigabytes (GB)
According to Microsoft’s recommendation, we set the memory and CPU as shown in
Table 14.
Table 14.
Lync Server virtual machines configuration
Server name
Roles
vCPU
Memory (GB)
Notes
Lync01
Front-end
server
4
32
In front-end pool
Lync02
Front-end
server
4
32
In front-end pool
Lync03
Back-end
SQL Server
server
4
32
In front-end pool
Storage design
Microsoft suggests a number of options for storage design for each Lync Server:
•
Eight or more 10,000-RPM hard disk drives with at least 72 GB free disk space.
Two of the disks should use RAID 1, and six should use RAID 10.
•
Solid-state drives (SSDs), which provide performance similar to eight 10,000RPM mechanical disk drives.
This solution uses a SAS drive-based configuration and pool for optimal price and
performance. Besides, most simulated loads were generated on two front-end
servers, so we configured the disks as follows:
•
One storage pool created with 16 SAS disks in RAID 10.
•
All Lync server OS files, applications, and databases placed in this pool.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
24
Figure 9 shows the storage layout for the Lync servers.
Figure 9.
Storage pool
For more information about Lync server configuration, refer to the Microsoft Lync
Server 2013 website.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
25
Baseline testing and validation
In this solution, we tested and validated the following features:
Overview
•
Failover clustering over SMB 3.0
•
SMB 3.0 feature support

Multichannel performance

Client availability on Data Mover failover

Copy Offload

AES128 encryption
•
Baseline test of SharePoint Server 2013
•
Baseline test of Lync Server 2013
Failover Clustering
over SMB 3.0
We deployed Failover Clustering in this solution by using an SMB 3.0 file share as
shared storage. We also tested and validated live migration, quick migration, and
storage migration functions. They all worked successfully across all nodes.
SMB 3.0 feature
support validation
This section describes how to enable and validate the Multichannel, Continuous
Availability, Copy Offload, and AES128 encryption features available in SMB 3.0.
Multichannel
SMB Multichannel is enabled by default on VNX File OE version 7.1.65 and later. No
parameter needs to be set on the system. This feature is also enabled by default on
Windows 2012.
Validating the feature
Each SMB 3.0 client in the test environment has two network interfaces. When one
interface is disabled, the surviving interface services the traffic, though traffic on the
surviving interface also drops as the path needs to be chosen again. This is evident
from Figure 10, which shows the throughput doubled on one NIC, and the throughput
dropping to zero on the disabled NIC. After the disabled NIC was enabled again, the
load balances across both NICs.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
26
70000
60000
Traffic is even
on both NIC
50000
Traffic flows to the
other NIC when
one is disabled
40000
30000
20000
Traffic is evenly
distributed again after
NIC is enabled
10000
0
1 4 7 10 13 16 19 22 25 28 31 34 37 40 43 46 49 52 55 58 61 64 67 70 73 76 79 82 85
fxg-1-0
Figure 10.
fxg-1-1
SMB 3.0 client network throughput on both interfaces
Continuous Availability
Enabling the feature
To enable this feature, from the VNX Control Station:
1.
Run the following command with the smbca option to mount the file system
through which the share will be exported:
server_mount <server_name> -o smbca <fsname> /<fsmountpoint>
2.
Run the following command with the CA option to export the share with the
CA option:
server_export <server_name> -P cifs -n <sharename> -o
type=CA /<fsmountpoint>
Validating the feature
Figure 11 shows the sequence of events for a Data Mover failover with CA enabled:
1.
The client (Windows Server 2012) requests a persistent handle by opening a
file with associated leases and locks on a CIFS share.
2.
The CIFS server saves the open state and persistent handle to disk.
3.
If the primary Data Mover (Data Mover 2) fails, it fails over to the standby Data
Mover (Data Mover 3).
4.
The standby Data Mover reads and restores the persistent open state from the
disk before starting the CIFS server.
5.
Using the persistent handle, the client re-establishes the connection to the
same CIFS server, and recovers the same context associated with the open
file as before the failover occurred.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
27
Figure 11.
SMB 3.0 Continuous Availability
The following procedure describes how CA maintains file locking even during Data
Mover failure:
1.
CAUser01 opens a file and begins making changes.
2.
CAUser02 opens the same file and receives a locked notification. The user
requests a notification when the file is available as shown in Figure 12.
Figure 12.
File in use
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
28
3.
The Data Mover fails over to the other node:

Without CA: CAUser01 loses the lock during failover and CAUser02
receives a notification that the file is available as shown in Figure 13.
Figure 13.

Available file
With CA: CAUser01 retains the lock during the failover.
Copy Offload
Copy Offload saves time when the user performs actions such as file copy or virtual
machine migration.
Table 15 shows the time taken to move virtual machine storage with and without the
Copy Offload feature.
Table 15.
Storage migration improvement with Copy Offload
Number of virtual
machines (10 GB each)
Time without Copy
Offload
Time with Copy
Offload
Time saved
1
03:02 min
01:26 min
53%
5
31:45 min
03:56 min
87%
AES128 encryption
This feature is not enabled by default on VNX. To enable it, run the following
command:
[nasadmin@CS ~]$ server_export server_2 -name SMB3_FS -o
type=Encrypted /SMB3_FS
server_2: done
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
29
Figure 14 shows the increase in Data Mover utilization with encryption enabled on the
SMB 3.0 shares.
CPU busy rate
60%
50%
40%
30%
20%
10%
0%
Encryption
Figure 14.
non-encryption
CPU busy rate
Note: Encryption of packets causes higher CPU usage on both client and VNX to encrypt or
decrypt the packet, so use this feature selectively for sensitive data instead of encrypting all
data.
Application
baseline test
overview
We performed baseline testing for SharePoint 2013 and Lync 2013 individually so
that the initial baseline performance could be set for each application and later
compared with the combined application performance. The baseline tests also
confirmed that the target of 10,000 users is achievable.
SharePoint Server
2013 baseline test
Validation setup
We used Microsoft Visual Studio Team System (VSTS) to simulate the load on the
SharePoint farm.
All users adhered to a Microsoft heavy-user profile, which specifies 60 requests per
hour. We applied a think time of zero percent to all tests. “Zero think time” is the
elimination of typical user decision-making time when browsing, searching, or
modifying data using Microsoft Office SharePoint Server. Every user request
completes from start to finish without a pause, which generates a continuous
workload on the system.
We calculated the maximum user capacity using the following formula:
# = seconds per hour / RPH / Concurrency% x RPS
Example: 3600/60/1% x 34.15 = 204,900
Example: 3600/60 /10% x 34.15 = 20,490 (supported user capacity for 10 percent
concurrency)
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
30
Table 16 lists the response time limits.
Table 16.
Response time limits
Test type
Action
Percentage
Response time
Browse
User browse
60
Less than 3 seconds
Search
Unique value
search
15
Less than 3 seconds
Modify
Metadata modify
and upload
10
Less than 3 seconds
Download
Download a
document
10
Less than 3 seconds
Upload
Upload a
document
5
Depends on document
size
SharePoint 2013 results
The SharePoint requirements were to maintain:
•
Average test times of browse, search, modify, and download actions below 3
seconds for 10,000 users.
•
Average test times of upload. These depend on the document upload size and
so have no specific limit.
Passed tests/sec were constant, averaging 25.45, which equates to 15,270 users
and comfortably exceeded our requirement of 10,000 users. All browse, modify,
search, and download test times were completed in less than three seconds. Upload
test times were just above five seconds. Average CPU utilization for the SharePoint
farm web server was 45.55 percent.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
31
Figure 15 shows the load profile of an active SharePoint farm with the active user load
achieved during the test.
20000
18000
16000
14000
12000
10000
8000
6000
4000
2000
0
00:10:00
00:12:30
00:15:00
00:17:30
00:20:00
00:22:30
00:25:00
00:27:30
00:30:00
00:32:30
00:35:00
00:37:30
00:40:00
00:42:30
00:45:00
00:47:30
00:50:00
00:52:30
00:55:00
00:57:30
01:00:00
01:02:30
01:05:00
01:07:30
01:10:00
Active Users
User load profile at 10% concurrency
Figure 15.
User count
Figure 16 shows the average test times in this test:
•
Browse: 0.46 sec
•
Search: 1.36 sec
•
Modify: 1.36 sec
•
Download: 0.28 sec
•
Upload: 5.01 sec
9
8
7
6
5
4
3
2
1
0
Browse
Modify
Download
Search
Upload
00:10:00
00:12:45
00:15:30
00:18:15
00:21:00
00:23:45
00:26:30
00:29:15
00:32:00
00:34:45
00:37:30
00:40:15
00:43:00
00:45:45
00:48:30
00:51:15
00:54:00
00:56:45
00:59:30
01:02:15
01:05:00
01:07:45
Seconds
Average test times
Figure 16.
Average test times
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
32
Lync Server 2013
baseline test
Stress and performance tool
To simulate Lync client load in this solution, we used the Lync Server 2013 Stress and
Performance Tool to generate and simulate user loads. This tool includes tools that
simplify capacity planning for Lync Server 2013. This tool helps you to:
•
Simplify your hardware planning for Lync Server 2013
•
Provide you with increased knowledge and best practices for performance
tuning
•
Measure the performance of your intended Lync Server 2013 deployments
Test scenario
We simulated two user loads: 1,000 users with high load and 10,000 users with high
load. Each test scenario included:
•
Instant messaging (IM)—Provides an instant messaging platform with
conversation history. Supports public IM connectivity with users of public IM
networks such as MSN/Windows Live, Yahoo!, AOL, and Google Talk.
•
Application sharing—Enables users to share Microsoft Office applications such
as Microsoft Word, Microsoft Excel, and Microsoft OneNote.
•
Audio conference—Provides a user experience that is familiar to users of
traditional audio bridge services including Public Switch Telephone Network
(PSTN) dial-in services with touch-tone call control commands.
•
Data collaboration—Enables users to create whiteboards and polls, or share
Microsoft PowerPoint slides.
Table 17 and Table 18 show the number of users in each scenario.
Table 17.
10,000-user scenario
Name
Load level
Number of users
Audio conferences
High
375
Application sharing
High
185
Data collaboration
High
75
Instant messaging
High
9,365
Table 18.
1,000-user scenario
Name
Load level
Number of users
Audio conferences
High
37
Application sharing
High
18
Data collaboration
High
9
Instant messaging
High
936
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
33
Note: There are three load types in the Lync Stress and Performance Tool: Low, Medium, and
High. In this solution, we used the High load for simulation and the user number for each
test scenario is defined by the tool itself.
For detailed instructions about using the Lync Server 2013 Stress and Performance
Tool, see the Microsoft TechNet website.
Test results
After running the 1,000-user load and 10,000-user load separately for two hours, we
gathered the following results from the performance monitor on each front-end
server.
Figure 17 shows scalability testing (from 1,000 to 10,000 users) of storage
performance.
Figure 17.
Comparison of storage performance
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
34
Figure 18 shows scalability testing (from 1,000 to 10,000 users) of Lync Server CPU
and memory utilization.
Figure 18.
Comparison of CPU and memory utilization
Figure 19 shows scalability testing from 1,000 to 10,000 users of Lync Server network
throughput.
Network Throughput
10
9
8
7
6
5
4
3
2
1
0
3.8
3.3
0.8
0.6
10000 users
1000 users
Network Throughput (MB)
Lync01
Figure 19.
Lync02
Comparison of network throughput
These figures show that the increase in load from 1,000 users to 10,000 users raises
disk IOPS almost 10 times, but the disk latency is still 1 ms. If we enable more users
in the Lync system, we can keep the current storage configuration and add more
front-end servers by adding more CPU and memory resources.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
35
Combined
workloads
Overview
Besides individual baseline testing, we also did a combined application test, running
both SharePoint and Lync simulations concurrently, to understand the performance
impact on both applications.
Impact of combined load on Lync
Figure 20 shows the disk read latency increased by only 2 ms and the disk write
latency increased by only 1 ms, although the SharePoint and Lync servers in different
storage pools affect each other’s performances when they use the same Data Mover
on VNX.
Storage Performance
174
175
3
Disk IOPS
Disk Read Latency (ms)
Lync01
Figure 20.
3
2
2
Disk Write Latency (ms)
Lync02
Impact between SharePoint and Lync
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
36
Impact of combined load on SharePoint
The 23.80 passed tests/sec shows a reduction of almost seven percent from the
baseline test. This is equivalent to 14,280 users at 10 percent concurrency, which is
well above the target 10,000 users.
Figure 21 shows a reduction from the baseline in the active user count by 6.93
percent.
20000
18000
16000
14000
12000
10000
8000
6000
4000
2000
0
00:25:00
00:27:30
00:30:00
00:32:30
00:35:00
00:37:30
00:40:00
00:42:30
00:45:00
00:47:30
00:50:00
00:52:30
00:55:00
00:57:30
01:00:00
01:02:30
01:05:00
01:07:30
01:10:00
01:12:30
01:15:00
01:17:30
01:20:00
01:22:30
01:25:00
Active Users
User load profile at 10% concurrency
Figure 21.
Combined test user count
The average test times of user action increased over the baseline but the common
operations were well below three seconds, as shown in Table 19.
Table 19.
User action average test times
User action
Baseline time
(seconds)
Combined time
(seconds)
Degradation (%)
Browse
0.46
0.50
-8
Search
1.36
1.01
34.6535
Modify
1.36
1.49
-8.724832
Download
0.28
0.36
-22.22222
Upload
5.01
5.71
-12.25919
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
37
Conclusion
Summary
Findings
To support the recent release of a broad set of new server and operating system
products from Microsoft, we deployed and tested a flexible, high-availability
infrastructure for combined Microsoft SharePoint 2013 and Microsoft Lync 2013
applications, based on a cost-effective and scalable EMC VNX with SMB 3.0 storage
architecture. This white paper demonstrates that:
•
VNX series arrays, along with SMB 3.0 and Microsoft Windows Server 2012,
easily support a 10,000-user Microsoft application environment for SharePoint
and Lync.
•
SMB 3.0 features provide functionality such as Copy Offload, Multichannel, and
data encryption that improve the speed and security of application data.
In this solution, we found that:
•
Windows Server 2012 supports SMB 3.0 multichannel, which means that you
can use different adapters with different speeds and these can automatically
be combined to provide more bandwidth, which was not possible in SMB 1.0
and 2.x.
•
SMB Multichannel ensures the distribution of network traffic between NICs on a
host and the VNX Data Movers, and allows for NIC failure with no user affected.
•
Copy Offload saves at least 50 percent storage migration time.
•
In-flight encryption of SMB 3.0 encrypts data over the network by using more
VNX Data Mover CPU resources.
•
With the storage configuration in VNX for this solution, Lync Server successfully
supports 10,000 users over SMB 3.0.
•
A SharePoint medium farm is suited to SMB 3.0 with common operations
completing in much less than three seconds.
•
With the storage configuration in VNX for this solution, SharePoint successfully
supports over 15,000 users at 10 percent concurrency.
•
Live Failover Clustering of virtual machines is possible with the virtual machine
disks on CIFS shares through SMB 3.0.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
38
Reference
White Papers
Product
documentation
Other website
For additional information, see the white papers listed below:
•
EMC VNX Series: Introduction to SMB 3.0 Support
•
EMC VNX Unified Best Practices for Performance
•
Introduction to the EMC VNX Series—A Detailed Review
•
EMC VNX Virtual Provisioning—Applied Technology
For additional information, see the product document websites listed below:
•
SharePoint 2013
•
Lync Server 2013
•
Windows Server 2012
For additional information, see the SMB 3.0 website.
Microsoft SharePoint Server 2013 and Lync Server 2013 Enhanced by EMC VNX with SMB 3.0
EMC VNX, Microsoft Windows Server 2012 Hyper-V, Microsoft SharePoint Server 2013, Microsoft
Lync Server 2013
39