Bca1931 final

BCA1931

Design, Deploy, and OptimizeSharePoint 2010 on VMware

Itzik Reich, EMC CorporationAlex Fontana, VMware, Inc.

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 feasibility and market demand will affect final delivery.

Pricing and packaging for any new technologies or features discussed or presented have not been determined.

3

Agenda

Introduction 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 Availability and Recovery

• High Availability

• Disaster Recovery

• Backup and Recovery

Customer Case Study with EMC

More Information

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

Key Benefits – Virtualizing SharePoint

Consolidation

Performance

Availability

Business Continuity

Maintenance

Load Balancing

Improved front end performance with more, smaller WFEs rather than few large WFEs

VM-based protection for SharePoint provides homogeneous high availability (VMware HA)

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

Simplified DR management with vCenter Site Recovery Manager

Live migration of SharePoint virtual machines (VMware vMotion)

Achieve 2-10x consolidation ratio, especially for larger deployments

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 concurrency, 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 (VMware ≤32 vCPU)

Failover Clustering, Mirroring, VMware HA

Server Roles/Priority What to Consider

4th

3rd

2nd

1st

Understanding your existing workload is better than any best practice!!!

7

Agenda












More Information

8

Maximum Scalability and Performance With vSphere 5

Application’s Performance Requirements

% o

f App

licat

ions

95% of Apps Require

IOPS

Network

Memory

CPU

< 10,000

<2.4 Mb/s

< 4 GB at peak

1 to 2 CPUs

VMware vSphere 4

300,000

30 Gb/s

256 GB per VM

8 VCPUs

VMware Inf.

100,000

9 Gb/s

16/64 GB per VM

4 VCPUs

VMwarevSphere 5

1,000,000

>36Gb/s

1,000 GB per VM

32 VCPUs

ESX 2

7,000

.9 Gb/s

3.6 GB per VM

2 VCPUs

ESX 1

<5,000

<.5Gb/s

2 GB per VM

1 VCPUs

3.0/3.5

9

SharePoint Performance – The User Experience

Server‒ CPU

‒ Memory

‒ HBA/CNA

‒ NIC

BLOB Storage

(Optional)

Storage− Content/Metadata− Search− System

Network Client

Document Request

Web Front End

SQL Server

BLOB Retrieval/Creation

Domain Controller

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

Authentication

Type Of operation

ExamplesAcceptable user response time

Common• Browsing to the home page • Browsing to a document library

<3 seconds

Uncommon• Creating a subsite Creating a list• Uploading a document to a document library

<5 seconds

Rare• Backing up a site• Creating a site collection

<7 seconds




10

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

11

Physical versus Virtual Study

Physical versus virtual Web front end (WFE) comparison shows the overall request per second (RPS) differs very little, 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)

12

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

13

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 a single ESX/ESXi host

• Provides fast access to a large number of performance 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/

http://vpivot.com/2009/09/17/using-perfmon-for-accurate-esx-performance-counters/

14

Agenda












More Information

15

Capacity Planning Process Summary

Estimate User Activity

Select a starting point architecture

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

Perform initial placement exercise to verify resource allocations and failover headroom

Plan the ESX/ESXi host hardware configuration (ESX/ESXi host requirements)

16

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 Characteristics ValueAverage 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


http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d95598d7-aa6e-4f24-82e3-81570c5384cb&DisplayLang=en

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=d95598d7-aa6e-4f24-82e3-81570c5384cb&DisplayLang=en

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=10986



17

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 technical case studies

• Published Microsoft technical case studies illustrating existing production environments

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

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



18

SharePoint Farm Topologies

Web

Application

Database

Small Medium LargeScale out approach = More servers ?

H/WMOSS 2007

SP2010

RAM >2GB 8GB

CPU>3.0GHz

Dual>2.5GHz

Quad

H/WMOSS 2007

SP2010

RAM 4GB 8GB

CPU>2.5GHz

Dual>2.5GHz

Quad

H/WMOSS 2007

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 Admin

/Office/Other

Features that impact SQL Server Sizing

• The size of content databases

• The addition of service applications or features into the environment

• The use of SQL Server mirroring

• The frequent use of files larger than 15MB

19

SQL Server Capacity and Performance

20

A Day in the life of SharePoint…SQL Server CPU

The majority of load comes from systematic operations…

21

A Day in the life of SharePoint…SQL Server Storage I/O

Plan for user load peaks, not systematic peaks…

22

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 full to 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

23

SQL Server Storage Best Practices

Plan for performance 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)

24

Deploying to ESX/ESXi

25

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 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 performance

degradation due to under-provisioned storage

• Use redundant paths to storage – Dual host-bus adapters or teamed network interface cards connected to separate switching infrastructures

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

26

Sample Architecture on vSphere

Based on Microsoft’s departmental collaboration environment technical case study (SharePoint Server 2010) at http://technet.microsoft.com/en-us/library/ff758649.aspx

The SQL Server configuration exceeded vSphere 4.1 limitations for vCPU allocation (maximum of 8 in vSphere 4.1), this large SQL Server was split into two SQL Server virtual machines with 8vCPUs each

Departmental Collaboration Environment Technical Case Study on vSphere Sample Architecture


27

Agenda












More Information

28

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

29

High Availability

30

SharePoint 2010 with Application-Aware HA

Protects all SharePoint server roles from hardwareand application failure

Does not require complex cluster setup or standby resources

Fully integrated with VMware HA and vCenter

31

VMware HA and High Availability Database Mirroring

SharePoint 2010 is mirroring-aware

Provides redundancy for SharePoint 2010 databases

Protection against HW/SW failures and DB corruption

Storage flexibility (FC, iSCSI, NFS)

RTO in few seconds

VMware HA + Database Mirroring

• Seamless integration, virtual machinesrejoin mirroring session after VMwareHA recovery

• Can shorten time that database is in unprotected state

• Reduces synchronization time after virtual machine recovery

32

Disaster Recovery

33

Disaster Recovery with Site Recovery Manager (SRM)

Relies on storage replication Allows creation, maintenance, and execution 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

34

Backup and Recovery

35

What to Backup

SharePoint 2010 Server Farm

ServersFront 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

36

VMware Data Recovery (VDR)

Quick, simple, and complete data protection for your SharePoint VMs with VDR, a disk-based backup and recovery solution

Integrated with vCenter to enable centralized and efficient management of backup jobs

Useful for small environments

Can be used for SQL Server if the service is STOPPED

37

SharePoint 2010 Backup using EMC Replication Manager

38

Summary

vSphere provides the foundation for high performance SharePoint environments

Virtualized SharePoint instances perform very well compared to equally sized physical instances

Tests of both Web front-end and SQL virtual machines show scaling out can provide increased throughput

Monitoring virtualized SharePoint remains the same as a physical deployment with additional visibility 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

39

Agenda












More Information

40

Customer Use Case

A Global company – 50,000 Employees

Is among the top 15 companies in it’s segmentation

Designed and Implemented fully virtualized SharePoint Solution for 120,00 Seats based on VMware vSphere & EMC Technologies

EMC VMAX

vSphere 4.1

Replication Manager

SRM 4.1

Solution Building Blocks

41

SAN Layout Considerations

V-M

AX

• Dedicated FA ports for Production, UAT & Test environments

• Dedicated FA ports for replication (mount hosts access)

• Shared/dedicated SRDF ports

• ESX ports connectivity to SAN as redundant conf.

• All FA/SRDF ports connected to high-speed SAN ports as redundant conf.

42

Thin Provisioning in VMware vSphere Environments

Decisions, Decisions, Decisions…..

vSphere provides native thin provisioning

VMAX provided array thin provisioning (Virtual Provisioning)

• Either one can be used, no performance penalty in any of them

• Both features can be used simultaneously but doing so increases risk

• We debated where to implement it..

• Decided on the Array level…why?

VMAX Virtual Provisioning simplifies drive and DA workload distribution

• Provides additional benefits besides optimizing storage use

• Ensure enough paths and TDEVs to support the workload

VMAX Virtual Provisioning provides additional benefits

• Zero Reclaim and Rebalancing

43

Storage Layout Decisions

Traditional Array Design(RAID 5 / 10 / SSD

Revolutionary Array Design (Storage Tiering)

Proven Fairly New

Very costly Hugh Savings

Not Flexible Highly Dynamic

We decided to go with Storage Tiering but why?

Saving money is an important thing but wasn’t the success criteria here..

The dynamic nature of the customer SharePoint environment was!

44

44

EMC Symmetrix FAST VP – overview

Automatic storage tiering for Virtual Provisioning thin pools

Analysis and data movement at sub-LUN level:

• Spreads data from a single thin device across multiple pools

• Places very active parts of a LUN on high-performing EFDs

• Places less active parts of a LUN on higher-capacity, more cost-effective FC or SATA drives

• Moves data at the extent group level - 7,680 KB

Moves data based on user-defined policies and application performance needs

Data movement is automatic and nondisruptive

SATA

FC

EFD

45

EMC FAST in Action

EMC Storage with an active ESX Cluster

VMware VMware VMware VMware

All Fibre Channel

Disk Drives

Disk Resources are ~80% Busy

46

EMC FAST in Action

Add Flash Drives and Apply FAST Policy

68% Less Disk I/O Contention

2.5X Faster Disk Response Time

VMware VMware VMware VMware

Tiered Storage

5% Flash Drives

65% FC Drives

30% SATA

47

Where did the customer use FAST VP

Is VMAX FAST VP a good fit for SharePoint 2010?

• Yes, but for maximum efficiency, it depends on which storage role

• Search Index component ? No

• Highly changing, throw-away data

• Search Query component ? Yes

• Highly-read data with small burst write changes

• TempDB? Yes

• The same blocks are re-used on disk and performance of TEMPDB directly affects SharePoint performance request - TempDB is used in every SharePoint request

• Helps to handle unanticipated performance requirements

48

Balancing the I/O

OK, so the storage will balance itself but what about the Queues up until we reach the storage subsystem layer..

The Customer evaluated PowerPath/VE

We were able to achieve up to X 2.5 the performance compared with RR

Why?

Because it does a predictive load balancing..

HBAHBA

vSphere server

PowerPath/VE

Storage

Port

Storage

Port

FC, iSCSI, FCoEFC, iSCSI, FCoE

Path Fault with PowerPath/VE

49

Set it and Forget it

It also helped the customer to find out about a flaky fiber cable using the VSI (Virtual Storage Integrator) Plugin VMware vCenter Server

50

This customer loves to take replicas on their SharePoint environment

But how do you take 40 Replicas?

Yes, 40…

51

Enabling the SharePoint Team

Self-provision and refresh dev/test environments

• Single console simplifies replica management

• Wizards step through the process for replica management

Replica 1

Replica 2

Replica 3

Replica 4

LOWEST

Replication Manager Administrator

Power Database Administrator

Database Administrator

Power User

Operator

USE

R R

OLE

PR

IVILE

GE

S

HIGHEST

• User roles facilitate self-sufficiency

• Integrate pre- and post-processes

• Schedule jobs or run ad hoc

• Auto-expire replicas basedon retention policies

52

Selecting A 3rd Party BLOB Software…

Your SharePoint SQL Server is NOT a File Server!

53


So let’s redirect these

Files OUTSIDE of the SQL Database

54


Together with the customer, we evaluated some 3rd party BLOB software and decided on Metalogix StoragePoint

We reduced the content DB by 90%

55

SharePoint Farm A

Secondary SitePrimary Site

BLOB Store

VMs

SRDF/S

VMs

VMs

VMs

• Resource/Protection Group

level granularity

• Active/Active (Sync distances)

or Active/Passive (Async

distances)

• Failover automation:

• VMware Site Recovery

Manager (SRM) Protection

Groups for all server roles

Databases

BLOB Store

VMs

VMs

VMs

VMs

Databases

E

SharePoint 2010 DR: Virtualized Farm (Full Replication)

56

Automated Site Failback with VSI 4

57

To Cluster or Not to Cluster….

Microsoft Clustering (MSCS)

VMware HA

Node Resource Failover Full VM Failover

Application Specific Application / OS agnostic

Complex to set up VERY easy to set up

Costly Cheap

We decided to go with VMware HA but why?

Ease of use was the key decision making..

58

Key Takeaways

SharePoint is more than just SQL…

• Leverage EMC Proven solutions and Best Practices for SharePoint storage, networking and compute design

• FAST, FAST Cache, VP improve efficiency & performance but require proper planning

• Use RBS to improve scalability and TCO and in some cases, performance

Full farm virtualization has great advantages overphysical/hybrid configurations

• Horizontal scaling is more efficient

• The best FULL farm protection when Integrated with EMC replication

• Simplifies, accelerates and automates SharePoint DR! (SRM)

EMC’s SharePoint VSS based replication can significantlyaccelerate replication and recovery of SharePoint

• A must for large deployments (TBs)

• Protects all farm components, not just content (solution dependent)

• Fast and simple Item level recovery while integrating with EMC partners (e.g. Kroll)

59

Agenda












More Information

60

Resources

• Visit us on the Web to learn more about specific apps

http://www.vmware.com/solutions/business-critical-apps/

• Best practices, reference architectures, and case studies• Microsoft Apps (Exchange, SQL, SharePoint)• Oracle• SAP

• Check out the VMTN user communities

• Email (Exchange, Lotus, BlackBerry) http://communities.vmware.com/community/vmtn/general/emailapps

• EMC SharePoint solutions http://www.emc.com/solutions/application-environment/microsoft/solutions-for-microsoft-office-system-sharepoint.htm

• Metalogix

• http://www.microsoft.com/casestudies/Case_Study_Detail.aspx?CaseStudyID=4000010759

http://www.vmware.com/solutions/business-critical-apps/

http://communities.vmware.com/community/vmtn/general/emailapps

http://www.emc.com/solutions/application-environment/microsoft/solutions-for-microsoft-office-system-sharepoint.htm



61

vSphere vSphere vSphere

vCenter Site Recovery Manager

vShield App with Data Security

vCenter Operations Advanced

Business Production Bundle

vCenter Site Recovery Manager vShield App with Data SecurityvCenter Operations Advanced

Introducing: Business Production Bundle

Automated Operations

Dynamic Security

Automated Disaster Recovery

New

Maximize the benefits of virtualizing business critical applications

62

Questions

BCA1931

Design, Deploy, and OptimizeSharePoint 2010 on VMware

65

vSphere Performance Enhancements

Feature Description

NUMA SupportVMware ESX®/VMware ESXi™ attempts to keep a virtual machine assigned to its home NUMA-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 Sharing

Page sharing allows the hypervisor to reclaim the redundant copies of memory created when multiple virtual machines run the same operating system and applications

Memory BallooningThe 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 performanceof the 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 cache versus paging out from disk

Large MemoryPage 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 largememory pages

Para-virtualized Network and Storage Controllers

High-performance virtual I/O adapters that can provide greater throughput while requiring lower CPU utilization

Distributed Resource Scheduler (DRSand vMotion)

As resource utilization fluctuates within a VMware vSphere® cluster, workloads are migrated with no impact to performance or uptime using VMware vSphere® vMotion®

66

Estimating User Activity (cont.)

Workload Characteristics 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 a request 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

67

Key Metrics to Monitor for ESX/ESXi

Resource Metric Host / VM Description

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 second

Both 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 BothAverage 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, %DRPTX

Both Drop packets per second

68

Key Metrics for SharePoint

Resource Metric Description

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/secRate 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/secRate at which pages are read from or written to disk to resolve hard page faults. Increases in page faults indicate system-wideperformance 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/secDisk Writes/sec

Number of disk reads and writes per second

Avg. Disk sec/ReadAvg. Disk sec/Write

Average 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

69

VMware HA and Failover Clustering

Supports two-node cluster

Failover cluster nodes can be physical or virtual or any combination 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.1http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959

Bca1931 final

Technology

Transcript of Bca1931 final