BCA2930-Virtualizing SharePoint Best Practices _Final_US.pdf

7/27/2019 BCA2930-Virtualizing SharePoint Best Practices _Final_US.pdf

1/59

Virtualizing SharePoint

Best Practices

Scott Salyer, VMware, Inc.

APP-BCA2930

#vmworldapps


2/59

2

Disclaimer

This session may contain product features that are

currently under development.

This session/overview of the new technology represents

no commitment from VMware to deliver these features in

any generally available product.

Features are subject to change, and must not be included in

contracts, purchase orders, or sales agreements of any kind.

Technical feasibi lity and market demand will affect final delivery.

Pricing and packaging for any new technologies or features

discussed or presented have not been determined.


3/59

3

Agenda

Introduct ion and Benefits

SharePoint on vSphere Performance

SharePoint on vSphere Capacity Planning Workload Modeling and Architectural Design

SQL Server Capacity and Performance

Deploying to ESX/ESXi

SharePoint on vSphere Availabili ty and Recovery

High Availability

Disaster Recovery

Backup and Recovery

More Information


4/59

4

SharePoint What is it?

Mostly an intranet portal for collaboration

It can be customized for all sorts of uses

Varies from insignificant to critical

http://www.topsharepoint.com


5/59

5

Key Benefits Virtualizing SharePoint

Lower TCO Significant savings in power, cooling, and datacenter

space

Avai labi li ty VM-based protection for SharePoint provides

homogeneous high availabili ty (VMware HA)

Load Balancing

Maximized overall performance with balanced HWutilization across the farm (VMware DRS)

Business Continuity Simplified DR management with vCenter Site Recovery

Manager

Maintenance vMotion of SharePoint vi rtual machines

Consolidation Achieve 2-10x consol idat ion ratio, especially for larger

deployments

Rapid Provisioning

And Scaling VM templates for fast provisioning and easier scale-out


6/59

6

Virtualizing Server Roles In SharePoint

Application (Excel, Doc Conv, etc)

Index/Crawl

SQL

Web Front End / Query

CPU Application dependent

Scaling out is more efficient

CPU User concur rency, Search requests

Scaling out is more efficient

Network segment vNICs and vSwitches

Redundant (Non redundant in MOSS 2007)

CPU Crawling, indexing (depends on content type/size)

Scale out (Up only with MOSS 2007)

Memory intensive

CPU Document updates, Search, Backup

VMFS/RDM

Scale up/out

Failover Clustering, Mirror ing, VMware HA

Server Roles/Priority What To Consider

4th

3rd

2nd

1st

Understanding your exist ing workload is better than any best practice!!!


7/59

7

Agenda







High Availability

Disaster Recovery

Backup and Recovery

More Information


8/59

8

Maximum Scalability and Performance With vSphere 5

Applications Performance Requirements

%o

fApplica

tions

95% of AppsRequire

IOPS

Network

Memory

CPU

< 10,000


9/59

9

Maximum Scalability and Performance With vSphere 5

Applications Performance Requirements

%o

fApplica

tions

95% of AppsRequire

IOPS

Network

Memory

CPU

< 10,000


10/59

10

SharePoint performance - The user experience

Server CPU

Memory

HBA/CNA

NIC

BLOB

Storage

(Optional)

Storage Content/Metadata

Search

System Network Client


11/59

11

SharePoint performance - The user experience

Server CPU

Memory

HBA/CNA

NIC

BLOB

Storage

(Optional)

Storage Content/Metadata

Search

System Network Client

Document

RequestWeb Front End

SQL Server

BLOB

Retrieval/Creation

Domain

Controller

http://technet.microsoft.com/en-us/library/cc287790(office.12).aspx

Aut hen tic ation

Type Of

operation Examples

Acceptable user

response time

Common Brows ing to the home page

Browsing to a document library


12/59

12

SharePoint 2010 Performance Test Logical Architecture

Workload

Root portal configured with collaboration template

260GB content, approximately 600K items in 10 site collections

Incremental crawl every four hours and weekly full crawl

VSTS load generator Zero think time (per Microsoft guidelines)

Transaction mix 80-10-10 read-write-search

Real world settings IIS logging on, SharePoint caching disabled


13/59

13

Physical versus Virtual Study

Physical versus vir tual Web front end (WFE) comparison shows the

overall request per second (RPS) dif fers very l itt le, even at higher

CPU saturation levels

Physical Versus Virtual WFE CPU Comparison

Physical

Physical

Virtual

Virtual

0

5

10

15

20

25

30

35

40

45

50

RPS

Physical

Virtual

1 CPU (95%+ Saturation) 2 CPU (75-90% Saturation)


14/59

14

Scaling Out the SQL Server Back-End

60-20-20 Mix

Test compares one SQL instance versus two SQL instances

Scaling out SQL Server provides better throughput!

Test with your workload for best SQL server scale out throughput


15/59

15

Performance Monitoring

vSphere Client:

GUI interface, primary tool for observing one or

more ESX/ESXi hosts Does not require high levels of privilege

Resxtop/Esxtop

Gives access to detailed performance data of asingle ESX/ESXi host

Provides fast access to a large number ofperformance metrics

Requires root-level access

Runs in interactive, batch, or replay mode

In-guest Monitoring tools

SQL Server: Perfmon, Profiler, Dynamic Manage Views

Use ESX Counters in PerfMon for more accurate results -http://vpivot.com/2009/09/17/using-perfmon-for-accurate-esx-performance-counters/


16/59

16

Agenda







High Availability

Disaster Recovery

Backup and Recovery

More Information


17/59

17

Capacity Planning Process Summary

Estimate User Activity

Select a starting point architecture

Map out resource requirements by server role(virtual machine requirements)

Perform in itial placement exercise to verify resource allocations

and failover headroom

Plan the ESX/ESXi host hardware configuration

(ESX/ESXi host requirements)


18/59

18

Estimating User Activity

Upgrading from SharePoint 2007

Mine IIS logs and utilize Microsoft or 3rd party testing tools

SharePoint 2010 Load Testing Kithttp://technet.microsoft.com/en-us/library/ff823736.aspx.

Visual Studio 2008 Team Systemhttp://www.microsoft.com/downloads/en/details.aspx?FamilyID=d95598d7-aa6e-4f24-

82e3-81570c5384cb&DisplayLang=en.

Visual Studio 2008 Service Pack 1http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=10986

New installation

Requests per second

Concurrent users

Total daily users

Total daily requests

Workload Characteris tics Value

Average daily RPS 157

Average RPS at peak time 350

Total number of unique users per day 69,702

Average daily concurrent users 420

Peak concurrent users at peak time 1,433

Total number of requests per day 18,866,527

Enterprise Intranet Collaboration Environment Technical Case Study Example

http://technet.microsoft.com/en-us/library/ff758650.aspx


19/59

19

Workload Modifiers

Workload distribution

Understand the distribution of the requests based on the client applications

that are interacting with the server farm Newer clients, such as Office 2010, offer new capabilities that can increase the

overall load on the system


Concurrency/peak usage

Active Users Start by considering the actual number of SharePoint users

Concurrent users Out of the active users, consider how many users areaccessing the system simultaneously at any given time

Peak Usage Period SharePoint concurrent usage might vary significantlyover the course of any given 24-hour period. The peak usage period is the

point in time where the maximum number of concurrent users are accessing

the SharePoint environment


20/59

20

Selecting a Starting Point Architecture

SharePoint 2010 topologies

Published Microsoft topologies from

small to large enterprise farms Use recommended role requirements

to plan resource allocation for VMs

http://technet.microsoft.com/en-us/library/cc263044.aspx

SharePoint 2010 Medium Topology Example

SharePoint Server 2010 technicalcase studies

Published Microsoft technical case

studies illustrating existing production

environments

Select the case study that is most applicable to your organizations expectedusage patterns http://technet.microsoft.com/en-us/library/cc261716.aspx .


21/59

21

SharePoint Farm Topologies

Web

Appl ication

Database

Small Medium Large

H/WMOSS

2007

SP

2010

RAM >2GB 8GB

CPU>3.0GHz

Dual

>2.5GHz

Quad

H/W MOSS2007 SP2010

RAM 4GB 8GB

CPU>2.5GHz

Dual

>2.5GHz

Quad

H/W MOSS2007 SP2010

RAM >2GB 8 - 64GB

CPU >2.0GHz>2.5GHz

Quad

Web/Query

All DBs

App

Web

Query/Crawl

Search DBs SharePoint DBs

App

Web Servers Groups

Query Crawl

Search DBs SharePoint DBs Content DBs

User requests Crawling/Admin

App Servers Groups

Central Admi n

/Office/Other


22/59

22

SharePoint Farm Topologies

Web

Appl ication

Database

Small Medium Large

H/WMOSS

2007

SP

2010

RAM >2GB 8GB

CPU>3.0GHz

Dual

>2.5GHz

Quad

H/W MOSS2007 SP2010

RAM 4GB 8GB

CPU>2.5GHz

Dual

>2.5GHz

Quad

H/W MOSS2007 SP2010

RAM >2GB 8 - 64GB

CPU >2.0GHz>2.5GHz

Quad

Web/Query

All DBs

App

Web

Query/Crawl

Search DBs SharePoint DBs

App

Web Servers Groups

Query Crawl

Search DBs SharePoint DBs Content DBs

User requests Crawling/Admin

App Servers Groups

Central Admi n

/Office/Other

Features that impact SQL Server Sizing

The size of content databases

The addition of service applications or features into theenvironment

The use of SQL Server mirror ing

The frequent use of files larger than 15MB (think about

using BLOB)

Scale out approach = More servers ?


23/59

23



24/59

24

A Day in the life of SharePointSQL Server CPU

The majority of load comes from systematic operations


25/59

25

A Day in the life of SharePointSQL Server Storage I/O

Plan for user load peaks, not systematic peaks


26/59

26

Database Sizing

Central Administration

2GB capacity; minimal disk throughput required

Configuration Database

2GB capacity; minimal disk throughput required

Can slowly grow beyond 1GB; approx. 40MB for every 50K site

collections

Transaction logs can be large; change recovery model from fullto simple unless mirroring

Content Databases

Database size = ((D V) S) + (10KB (L + (V D)))

D = the number of documents you expect to host

S = the average size of each document

L = the number of list items in the environment; start with 3 X D

and adjust

V = the approximate number of document versions


27/59

27

Content Database Sizing and Performance

SharePoint features that impact content database size

Recycle bin contents http://technet.microsoft.com/en-

us/library/cc263125.aspx Auditing data http://technet.microsoft.com/en-us/library/cc298801.aspx

Office Web Apps http://technet.microsoft.com/en-us/library/ee837422.aspx

Content database size guidelines

Microsoft recommends that you limit the size of content databases to 200GB A site collection should not exceed 100GB unless it is the only site collection in

the database

Content database sizes up to 1TB are supported only for large, single-siterepositories and archives in which data remains reasonably static

Disk throughput requirements for content databases

Disk throughput requirements can vary significantly between implementations.Microsoft recommends that you match your expected workload to one of their

tested solutions at http://technet.microsoft.com/en-us/library/ff608068.aspx


28/59

28

SQL Server Storage Best Practices

Plan forperformance in addition to capacity

Search database and temp database are the most demanding for

disk I/O. Search database is write intensive when crawling.

When possible, place SQL transaction log and database files on

physically separate disk pools

Place transaction log files on RAID1/0 volumes/pools for high write

performance and faster rebuilds Most of SharePoint data (content databases) can use

RAID5 volumes

RAID5 for more read intensive workloads (common, mainly publishing farms)

RAID1/0 for higher random write workloads (heavy collaboration, tempdb,

search)

RAID 6 usually for higher availability with large amount of drives(Virtual Pools)


29/59

29

Additional Considerations for SQL Server

Network topology requirements

Be sure to establish LAN-class bandwidth and latency between Web servers,

application servers, and the SQL Servers. Network latency should be


30/59

30


Vi l M hi R All i


31/59

31

Virtual Machine Resource Allocation

Virtual CPUs

Allocate the minimum requirement and adjust as needed; use HotAdd.

If overcommitting processors, monitor %RDY, %MLMTD, and %CSTP Keep NUMA node size in mind with sizing virtual machines

Virtual Memory

Right-size memory allocations for efficient use of host memory

Use vSphere 4.1 or above to take advantage of memory compression If overcommitting memory, monitor SWAP /MB: r/s, w/s and MCTLSZ

Storage

Understand I/O requirements for each application tier to avoid performancedegradation due to under-provisioned storage

Use redundant paths to storage Dual host-bus adapters or teamed networkinterface cards connected to separate switching infrastructures

Avoid partition misalignment by creating VMFS partitions from within thevSphere client If creating VMFS from the CLI use fdisk to align

S l A hit t S h


32/59

32

Sample Architecture on vSphere

Based on Microsofts departmental collaboration environment

technical case study (SharePoint Server 2010) at


Departmental Collaboration Environment Technical Case Study on vSphere Sample Architecture

I i C lid ti R ti


33/59

33

Improving Consolidation Ratios

According to the case study, actual utilization of memory and

processor are fairly low, offering the opportunity to improve

consolidation ratios by making adjustments to the environment If this were a real product ion environment on vSphere, you could

Reduce the number of vCPUs allocated to the application Servers, freeing upmore cores and allowing increased virtual machine density on each host

Utilize vCPU shares to throttle the amount of actual processor each virtual

machine is consuming without having to change its configuration

Departmental

Collaboration Case

Study ProcessorUtilization


34/59

34

Agenda







High Availability

Disaster Recovery

Backup and Recovery

More Information

Sh P i t 2010 A il bilit


35/59

35

SharePoint 2010 Availability

What to protect? (Service Level Agreements)

Recovery Point Objectives (RPO)

Recovery Time Objectives (RTO)

Recovery Level Objectives (RLO)

How to protect?

Tools and technologies available from SharePoint 2010 natively

VMware vSphere additions


36/59

36

High Availability

SharePoint 2010 High A ailabilit


37/59

37

SharePoint 2010 High Availability

Web and application server role

Software or hardware load balancing

SharePoint 2010 search Multiple crawl servers/databases

Multiple query components with mirrorindex partitions

Database server role

Synchronous database mirroring orAlwaysOn

Failover clustering

Use VMware HA, vMotion, DRS

to increase host availability Use DRS affinity/anti -aff inity

rules to spread server roles

across hosts

SharePoint 2010 with Application Aware HA


38/59

38

SharePoint 2010 with Application-Aware HA

Protects all SharePoint server roles from hardware and application

failure

Does not require complex cluster setup or standby resources

Fully integrated with VMware HA and vCenter

VMware HA and SQL Server Database Mirroring / AlwaysOn


39/59

39

VMware HA and SQL Server Database Mirroring / AlwaysOn

SharePoint 2010 is mirror ing-aware

Provides redundancy for

SharePoint 2010 databases

Protection against HW/SW failures

and DB corruption

Storage flexibil ity (FC, iSCSI, NFS)

RTO in few seconds

VMware HA + Database Mirroring

Seamless integration, virtual machinesrejoin mirroring session after VMware HA

recovery

Can shorten time that database is inunprotected state

Reduces synchronization time aftervirtual machine recovery

VMware HA and Failover Clustering


40/59

40

VMware HA and Failover Clustering

Supports two-node cluster

Failover cluster nodes can be

physical or virtual or anycombination of the two

Host attach (FC) or in-guest (iSCSI)

Supports RDM only

VMware HA + failover clustering Seamless integration, virtual machines

rejoin clustering session after

VMware HA recovery

Can shorten time that database is in

unprotected state

Failover clustering now supported with VMware

HA with vSphere v4.1 and abovehttp://kb.vmware.com/selfservice/microsites/search.do?language=en

_US&cmd=displayKC&externalId=1037959


41/59

41

Disaster Recovery

Disaster Recovery with Site Recovery Manager (SRM)


42/59

42


Relies on storage or vSphere Replication

Allows creation, maintenance, and execut ion of automated process to facilitate

site recovery

Safe testing without impacting production environment

Improves hardware utilization with co-located test/dev with DR

Self-documenting



43/59

43


Relies on storage or vSphere Replication

Allows creation, maintenance, and execut ion of automated process to facilitate

site recovery

Safe testing without impacting production environment

Improves hardware utilization with co-located test/dev with DR

Self-documenting


44/59

44

Backup and Recovery

What to Backup


45/59

45

What to Backup

SharePoint 2010 Server Farm

Servers

Front End, Application, Index, Search, SQL

SQL Server Databases

Configuration, Search,Services, and so on Content Databases

Web Applications

Site Collections

Sites

Lists (document libraries, events,contacts, and the like)

Documents and Items

VMware Data Recovery (VDR)


46/59

46

VMware Data Recovery (VDR)

Quick, simple, and complete data protection for your SharePoint VMs

with VDR, a disk-based backup and recovery solut ion

Integrated with vCenter to enable centralized and efficientmanagement of backup jobs

Useful for small environments

Can be used for SQL Server if the service is STOPPED

SharePoint 2010 Backup using EMC Replication Manager


47/59

47

SharePoint 2010 Backup using EMC Replication Manager

Summary


48/59

48

Summary

vSphere provides the foundation for high performance SharePoint

environments

Virtualized SharePoint instances perform very well compared toequally sized physical instances

Tests of both Web front-end and SQL vir tual machines show

scaling out can provide increased throughput

Monitoring virtualized SharePoint remains the same as a physical

deployment with additional visibil ity into the underlying

infrastructure

Use VMware HA to protect SharePoint from downtime; for higher

availability, consider:

Symantec Application HA for more granular control at the service level Combining VMware HA with SQL Server Mirroring

Use SRM for site recovery; co-locate test/dev and recovery VMs


49/59

49

Agenda



SharePoint on vSphere Capacity Planning

Workload Modeling and Architectural Design




High Availability

Disaster Recovery

Backup and Recovery

More Information

Resources


50/59

50

Resources

Visit us on the Web to learn more about specific apps

http://www.vmware.com/solutions/business-critical-apps/ Visit the BCA Blog site at: http://blogs.vmware.com/apps/

Includes best practices, design guidance, and success

stories for:

Microsoft Apps

Exchange

SQL Server

SharePoint

Oracle

SAP

Java Applications

Questions


51/59

51

Questions

Learn more about VMware for SMBs


52/59

52

vmware.com/go/smb

blogs.vmware.com/smb

VMwareCloudContest.com

bit.ly/VMworld_SMB

Learn more about VMware for SMBs


53/59

FILL OUT

A SURVEY

EVERY COMPLETE SURVEY

IS ENTERED INTO

DRAWING FOR A

$25 VMWARE COMPANY

STORE GIFT CERTIFICATE


54/59

Virtualizing SharePoint

Best Practices

Scott Salyer, VMware, Inc.

APP-BCA2930

#vmworldapps


55/59

55

Backup Slides

vSphere Performance Enhancements


56/59

56

p

Feature Description

NUMA Support VMware ESX

/VMware ESXi attempts to keep a virtual machine assigned to its homeNUMA-node. Because memory for the virtual machine is allocated from the home node

memory access is local and provides the best performance possible

Transparent Page

SharingPage sharing allows the hypervisor to reclaim the redundant copies of memory createdwhen multiple virtual machines run the same operating system and applications

Memory Ballooning

The balloon driver allows the hypervisor to reclaim host physical memory if memory

resources are under contention. This is done with little to no impact to the performance ofthe application

Memory CompressionPages elected to be swapped that can be compressed are stored in a compression cache

in main memory. When required, pages are decompressed from compression cacheversus paging out from disk

Large Memory Page

Support

Applications that can benefit from large pages on native systems, such as MS SQL, can

achieve similar performance improvement on a virtual machine backed with large memorypages

Para-virtualized Network

and Storage ControllersHigh-performance virtual I/O adapters that can provide greater throughput while requiringlower CPU utilization

Distributed Resource

Scheduler (DRS and

vMotion

As resource utilization fluctuates within a VMware vSphere cluster, workloads are

migrated with no impact to performance or uptime using VMware vSphere vMotion

Estimating User Activi ty (cont.)


57/59

57

g y ( )

Workload Characteris tics Value

Average daily RPS 157

Average RPS at peak time 350

Total number of unique users per

day

69,702

Average daily concurrent users 420

Peak concurrent users at peak time 1,433

Total number of requests per day 18,866,527

User Load Request Rate Requests Per Second Per User

Light 20 requests per hour. An active user generates a

request every 180 seconds

.006

Typical 36 requests per hour. An active user generates arequest every 100 seconds

.010

Heavy 60 requests per hour. An active user generates a

request every 60 seconds

.017

Extreme 120 requests per hour. An active user generates

a request every 30 seconds

.034

Enterprise Intranet Collaboration Environment Technical Case Study Example

SharePoint 2007 User Loads from Microsoft TechNet

Key Metrics to Monitor for ESX/ESXi


58/59

58

y

Resource MetricHost /

VMDescription

CPU

%USED Both CPU used over the collection interval (%)

%RDY VM CPU time spent in ready state

%SYS Both Percentage of time spent in the ESX host VMkernel

Memory

Swapin, Swapout BothMemory ESX/ESXi host swaps in/out from/to disk (per

virtual machine, or cumulative over host)

MCTLSZ (MB) BothAmount of memory reclaimed from resource pool by

way of ballooning

Disk

READs per second,

WRITEs per secondBoth Reads and writes issued in the collection interval

DAVG/cmd Both Average latency (ms) of the device (LUN)

KAVG/cmd BothAverage latency (ms) in the VMkernel, also known as

queuing time

GAVG/cmd Both

Average latency (ms) in the guest. GAVG = DAVG +

KAVG

Network

MbRX/s, MbTX/s Both Amount of data transmitted per second

PKTRX/s, PKTTX/s Both Packets transmitted per second

%DRPRX,

%DRPTXBoth Drop packets per second

Key Metrics for SharePoint


59/59

y

Resource Metric Descr iption

CPU % Processor Time

Processor usage over a period of time. Consistently high utilization can

adversely affect performance. Remember to count "Total" in

multiprocessor systems. Maintain balanced performance between cores

by also measuring individual core utilization

Memory

Available MbytesPhysical memory available for allocation. Insufficient memory leads to

excessive use of page file and increase in page faults

Cache Faults/sec

Rate at which faults occur when a page is sought in the file system

cache and is not found. Effective use of cache for read and write

operations can have a significant effect on performance

Pages/sec

Rate at which pages are read from or written to disk to resolve hard

page faults. Increases in page faults indicate system-wide performance

degradation

Paging File% Used

% Used Peak

High page file utilization can mean an increase in hard page faults,

monitor this counter along with Pages/sec and Available Mbytes to

determine if allocated memory is inadequate

Disk

Disk Reads/sec

Disk Writes/sec Number of disk reads and writes per second

Avg. Disk sec/Read

Avg. Disk sec/WriteAverage latency (seconds) of reads and writes of data from disk

Network Total Bytes/sec Rate at which data is sent and received through the network interface