SharePoint 2010_Briefing.pdf - EMC Community Network

EMC Global Solutions 

Eyal Sharon – Global Solution Practice Manager 

© Copyright 2011 EMC Corporation. All rights reserved. 

1

Agenda 

• SharePoint architecture and performance factors 

• SharePoint farm virtualization 

• Storage best practices – Sizing and performance 

• Remote BLOB Storage 

• EMC Storage options and features 

• SharePoint farm DR 

• Demo 

• Q&A 


2

1 2 3 4 

Capture 

& Define 

Test and 

Validate 

Document 

Publish 

Hopkinton, MA 

Santa Clara, CA 

Cork, Ireland 

Vienna, Austria 

Shanghai, 

China 

Singapore 


3

SharePoint performance - The user experience 

SQL Server 

Domain 

Controller 

Authentication 

Storage 

- Content/Metadata 

- Search 

- System 

BLOB 

Storage 

(Optional) 

Web Front End 

Type Of 

operation 

Server 

CPU 

Common Memory 

HBA/CNA 

NIC 

Uncommon 

Rare 

Network 

Examples 

• Browsing to the home page 

• Browsing to a document library 

• Creating a subsite Creating a list 

• Uploading a document to a document library 

• Backing up a site 

• Creating a site collection 

Document 

Request 

Client 

Acceptable 

user response 

time 

SharePoint Farm Topologies 

Small Scale Medium out approach = More servers Large 

? 

Web 

H/W 

MOSS 

2007 

SP 

2010 

Web Servers Groups 

RAM >2GB 8GB 

CPU 

>3.0GHz 

Dual 

>2.5GHz 

Quad 

Web/Query 

Web 

User requests 

Crawling/Admin 

Application 

App Servers Groups 

H/W 

MOSS 

2007 

SP 


RAM 4GB 8GB 

CPU 

>2.5GHz 

Dual 

>2.5GHz 

Quad 

App 

Query/Crawl 

App 

Query 

Crawl 

Central Admin 

/Office/Other 

Database 

H/W 

MOSS 

2007 

SP 


RAM >2GB >8GB 

CPU 

>2.0GHz 

>2.5GHz 

Quad 

All DBs 

Search DBs 

SharePoint DBs 

Search DBs SharePoint DBs Content DBs 


5

Key Benefits – Virtualizing SharePoint 

• Consolidation – Achieve 2-10x consolidation ratio, especially for 

larger deployments 

• Performance – Improved front end performance with more, smaller 

WFEs rather than few large WFEs. 

• Availability – VM based protection for SharePoint provides 

homogeneous high availability (VMware HA, WFC). 

• Business Continuity - Simplified DR management (vCenter Site 

Recovery Manager, Cluster Enabler) 

• Maintenance – Live migration of virtual machines (VMware vMotion, 

Hyper-V Quick/Live Migration) 

• Load Balancing – Maximized overall performance with balanced HW 

utilization across the farm (VMware DRS, SCVMM PRO) 


6

Virtualizing Server Roles In SharePoint 

Server Roles/Priority 

What To Consider 

1 st 

Web Front End / Query 

CPU – User concurrency, Search requests 

Scaling out is more efficient 

Network – segment vNICs and vSwitches 

2 nd 

Application (Excel, Doc Conv, etc) 

CPU – Application dependent 

Scaling out is more efficient 

3 rd 

Index/Crawl 

Redundant (Non redundant in MOSS 2007) 

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

Scale out (Up only with MOSS 2007) 

Memory intensive 

4 th 

SQL 

CPU – Document updates, Search, Backup 

VMFS/RDM, VHD/Pass-Through 

Scale up/out (Hyper-V = 4 vCPU, VMware =8 vCPU) 

Failover Clustering, Mirroring, VMware HA 

Understanding your existing workload (WFE to SQL) and requirements is better than 

any best practice!!! 


7

A Day in the life of SharePoint… 

SQL Server CPU 

The majority of load comes from systematic operations… 

Sample anonymous customer data 


8

A Day in the life of SharePoint… 

SQL Server Storage I/O 

Plan for user load peaks, not systematic peaks… 

Sample anonymous customer data 


9

Virtualized SharePoint - Reference Architecture 

• 1 TB User content 

• 10 DBs/Site Collection 100GB each 

• 110 GB data files on 130 GB R5 LUNs 

• 9 GB log files on 10 GB LUNs 

• 100GB R1/0 LUNs for Search DBs 

(Property & Crawl Stores) 

• R5 LUNs for Crawl Index 

Role Qty VM specs 

VMware vSphere 4.0 ESX servers (physical) 3 Nodes 4-socket quad-core (16 cores), 48 GB RAM 

SQL Server 2008 2 8 vCPU, 32 GB RAM 

Web front ends 6 4 vCPU, 8 GB RAM 

Application servers (Incl. Central Admin) 2 2 vCPU, 4 GB RAM 

Search Crawl Servers 2 4 vCPU, 8 GB RAM 

Search Query Servers 2 4 vCPU, 8 GB RAM 

Domain Controllers 2 2 vCPU, 4 GB RAM 

Maximum capacity achieved at 10% concurrency = 20,490 Users 


10

SharePoint 2010 Storage Elements 

Content 

SQL Server 

System and Configuration 

Shared Service Applications 

Content Databases 

Configuration Databases 

Usage & Health Data Collection - Logging 

BLOB Store 

Central Admin 

Search – Admin, Property, Crawl 

tempdb, master ,model , msdb 

Web Analytics – Staging, Reporting 

User Profiles – Profile, Synchronization, Social Tagging 

Index Partition/s 

Search Index 

Query Component/s 

Service Application Data 

Managed Metadata- Term Store 

State 

Business Data Connectivity 

Secure Store 

SA Volumes 

System Volumes 

Boot/OS/VMs 

Web Parts & Features 

SharePoint Binaries 


11

SharePoint 2010 Storage I/O Characteristics 

I/O Type 

Content 

Databases 

SQL Server 

tempdb 

Search 

Databases 

(property & crawl stores) 

Search Servers 

Index 

Component 

Query 

component 

Read (KB) 16 8 8 32 32 

Write (KB) 16 32 16 64 64 

R:W Ratio 95:5 50:50 60:40 90:10 70:30 

* Based on average workloads in a collaboration farm (Browse/Search/Modify – 80/10/10) 

SQLIO.exe is a stress tool and its results should not be considered as “requirements” ! 


12

SharePoint 2010 Storage performance 

Requirements/estimates for Search 

Query 

Crawler 

SQL Server 

Query Component 

Crawl Component 

Search Admin 

DB 

Property 

DB 

Crawl 

DB 

Database Role Microsoft’s Estimate IOPS Typical averages observed 

Crawl Database 3,500 – 7,000 (R70:W30) 2,000 

Property Database 2,000 (R30:W70) 600 


2,000 per Active/Failover pair 

(Load/Write/Merge) 

Based on a Microsoft case study – Mileage may vary!!! 

450 

Crawl Component 300-400 IOPS 80-100 

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


13

SharePoint 2010 Storage I/O Characteristics 

Search 

600 

500 

I/O Profile 

(During Full Crawl) 

400 

300 

200 

Content DB 

Index Component 

Search Store 

100 

0 

I/O Ratio Comparison 

(During Full Crawl) 

SQL Search Store LUN 

Index Component LUN 

Content DB LUN 

WRITE IOPS 

READ IOPS 

Total IOPS 

0 50 100 150 200 250 300 350 

* Based on average usage 


14

Reference Architecture – Storage Layout 

Cost driven configuration 

13,000 Heavy SharePoint users 

1 TB User content with RBS FILESTREAM Externalization 

Protected with EMC RecoverPoint 

SATA Disks 

RAID5 –VM Boot Luns, Content Databases 

RAID10 – Search Databases, TempdDB, 

FAST Cache to compensate for disk latencies 

Fibre Channel 

RAID10 – RecoverPoint LUNs (Target & Repository) 


15

SharePoint Storage Sizing 

Volume Sizing 

Storage Role 

% of 

Corpus 

Size 

Typical sizes GB 

Recommended 

RAID 

Virtual Machine Boot Volumes - 80 R-5 

Application Volumes - 50 – 300+ R-5 

Content 

Databases 

tempdb 

Data File Volume - 100 – 200 R-5 

Log File Volume 

10% of Data 

File 

10 – 20 R-5 / R-10 

Data File Volume 10% 100 – 300 R-10 

Log File Volume 2% 10 – 100 R-10 

Storage and SQL Server capacity planning and configuration 

Hardware and software requirements 




16

SharePoint Storage Sizing 

Volume Sizing 

Storage Role 

% of 

Corpus Size 

Sample size 

(1TB Content) 

Recommend 

RAID 

FASTCache? 

SQL Search 

Databases 

Crawl Store DB 

Property Store DB 

0.046 × (sum of 

content databases) 

0.015 × (sum of 

content databases) 

46GB R-10 Yes 

15GB R-10 Yes 

Search Server 

Volumes 

Index Component 10% 100GB R5 / R10 No 

Query Component 10 – 35% * 2.85 150 – 1TB R-5 / R-10 No 

SharePoint 

Configuration 

Databases 

- Data & Log 

Volume 

SharePoint_Config - 5GB R-5 No 

SP_AdminContent - 15GB R-5 No 

Usage and Health Data 

Collection Database 

- (based on % 

monitoring) 

50 - 

500GB(?) 

R-5 No 

SharePoint 2010 Database sizing characteristics 


http://technet.microsoft.com/en-us/library/cc678868(office.14).aspx 


17

SharePoint Storage Best Practices 

SQL Server – Storage Allocation 

Use 64KB unit allocation size when formatting a DB Volume 

Plan Database file sizes accordingly 

– Don’t rely on autogrowth 

File growth can cause locking, set files size and autogrowth increments 

appropriately 

– Using RBS would keep the SQL Database files small 

When using Thin/Virtual provisioning 

– Use the “Quick Format” option 

– Enable Instant file initialization* 

Enhances the speed for data file creations, restores, data file growth 

Assign SQL service account to “Perform Volume Maintenance Tasks” permission 

– Log files are fully allocated and zeroed upon creation or growths 

* http://msdn.microsoft.com/en-us/library/ms175935.aspx 


18

SharePoint Storage Best Practices 

SQL Server - Performance 

Plan for optimal disk response times 

Data file Latency 

Read/Write Operations 

Log file Latency 

Write Operations 

Recommendation 

< 10 ms < 5 ms Very Good 

< 20 ms 5 – 10 ms Acceptable 

> 20 ms > 15 ms Investigate and Improve 

Important Perfmon I/O counters 

Average Disk/sec Read or Write 

Current Disk Queue Length* 

Disk Reads/Writes per Second 

Average Disk Bytes/Read & Write 

Real Meaning! 

Disk Latency 

Outstanding I/Os 

IOPS 

I/O Size (KB) 

* Hard to interpret due to virtualization of storage. Consider in combination with response times 


19

EMC Storage Technologies for SharePoint 2010 

Symmetrix VMAX 

• Should I use Thin Provisioned Pools on VMAX? 

Yes, reduce initial storage requirement 

Thin device performance is equal to thick on VMAX 

• 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 


20

EMC Storage Technologies for SharePoint 2010 

VNX/CX 

• Should I use Thin provisioning with CX/VNX for SharePoint? 

- In most cases, yes 

Storage Role 

LUN 

Compression? 

• How can SharePoint benefit from FAST Cache? 

- Performance boost, mainly for Search 

Thin 

Provisioning? 

Index/Query Component Storage No No 

SQL Search Database No No 

SQL TempDB No Maybe 

SQL Content Databases No Yes 

BLOB Store Yes Yes 

W/O FAST Cache 

FAST Cache 

Maximum user capacity 12,240 13,080 

RPS 20.4 21.8 

Crawl operations 45 items/second 86 items/second 

Browse - Avg. User Response time (sec) 2.42 2.31 

Search – Avg. User Response time (sec) 1.37 1.0 


21

Storage tiering and SharePoint 

OOTB RBS – – Externalizing BLOBs stored the in BLOBs SQL databases to SAN/NAS/CAS/Cloud Storage 

3 TB of SharePoint 

SQL content databases 

240 GB metadata 

(SQL) 

2.76 TB BLOBs 

(EBS/RBS) 

150GB 

150GB 

150GB 

150GB 

12G 

12G 

12G 

12G 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

150GB 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

12G 

SAN/NAS/CAS/Cloud 

150GB 

150GB 

150GB 

150GB 

EMC partners with Metalogix for SharePoint BLOB externalization 

– RBS can sit on Block/File/Object (VMAX, VNX, DataDomain) 

– Atmos/Atmos VE - Cloud Optimized Storage 

– Centera API 

Performance improvement for large objects retrieval mainly 

Note: SharePoint 2GB file size limit is not lifted by using RBS (SQL Server limitation) 


22

BLOB externalization methods 

External BLOB storage (EBS) API 

– SharePoint introduced EBS in SharePoint 2007/WSS 3.0 SP1 

– Provider dependent, can’t be used out of the box 

– Still supported with SharePoint 2010 

Remote BLOB store (RBS) API 

– SharePoint 2010 introduced SQL Server 2008 R2 RBS support 

– Can use external RBS provider or RBS FILESTREAM to a local drive 

– EBS RBS migration can be performed via PowerShell commands 

SQL Remote BLOB Storage (RBS) 

WSS External BLOB Storage (EBS) 

WSS 3.0 

SP1 




2010 SPx 

SharePoint vNext 

(EBS Support Ends) 

12/2007 05/2010 Q1/2010 

BLOB is a Binary Large Object 


23

Storage tiering and SharePoint 

Feature 

SQL Server 

RBS FILESTREAM 

3 rd Party RBS 

provider 

Externalization using SMB/CIFS/NFS protocols No (Local volumes only) Yes 

Multiple storage endpoints per content database No Yes 

Use SharePoint filename or folder on offloaded BLOBs No (GUID based) Yes 

User Interface Powershell Central Admin 

BLOBs tiering based on age/size/version policies No Yes 

Orphaned BLOB Garbage Collection Basic (RBS Maintainer) Policy-based 

EMC partners with several vendors for BLOB externalization (EMC Select- 

Metalogix) 

– RBS can reside on Block/File/Object (VMAX, VNX, Isilon, DataDomain) 

– Atmos/Atmos VE - Cloud Optimized Storage 

– Centera API 

Performance improvement for large objects retrieval mainly 

SharePoint 2GB file size limit is not lifted by using RBS (SQL Server limitation) 


24

Considerations for Remote BLOB storage 

Replication, Backup and Recovery 

– Native/Item level backup (stsadm based) would include BLOBs 

– SQL based backup would only protect the content database metadata 

– To maintain consistency: 

Backup – First Content Databases then BLOB Store 

Restore – First BLOB Store then Content Databases 

– For DR purposes always tie RBS volumes with SQL Server volumes 

– For faster recovery, consider larger intervals of garbage collection jobs (Keeps 

previous BLOB versions) 

Block, File or Object storage? 

– Performance: Block would be faster but RBS has typically low I/O 

– Storage Efficiency 

– Block-level LUN Compression – increases storage efficiency, may affect backup performance 

– Filesystem-Deduplication – better performance and increased dedup rates 

– Object based storage (Atmos/Centera) is viable and extensible 

http://www.emc.com/collateral/hardware/white-papers/h7048-sharepoint-blob-clariion-atmos-wp.pdf 


25

Reference Architecture - BLOB Externalization 

• Farm Profile 

– Total content ~1TB 

– 4.4M documents 

– Avg. File Size - 220K 

– 1 Site Collection/10 Sites 

• Storage Profile 

– EMC VNX5300 

– SQL Database: 15K SAS 

– BLOB Store: 7.2K NL-SAS 

– CIFS Share for RBS 

• Results 

– Max user capacity – 8,630 (10%) 

– BLOBs consumed 92% of content databases 

– Full crawl duration – 34 hours 

– 20% capacity saved with RBS File system de-duplication 


26

Defining SharePoint SLAs 

Recovery Point Objective (RPO) 

The maximum amount of time between the 

last available backup and the point of failure 

Determined by the amount of 

data that the business can afford 

to lose in the event of a failure 

Recovery Time Objective (RTO) 

The maximum amount of time a data recovery 

process will take 

Determined by the amount of 

time the business can afford 

service unavailability 

Recovery Level Objective (RLO) 

The required granularity of data recovery 

Entire farm 

Site collection 

Site 

List 

Library 

Item 

Plan for backup and recovery (SharePoint Server 2010) 

http://technet.microsoft.com/en-us/library/cc261687(office.14).aspx 


27

SharePoint Backup, Recovery and Replication 

The Options 

Large Farm (5TB+) 

Small Farm (x00 GB) 

– Central Administration Backup 

– STSADM /PowerShell 

– EMC Replication Manager 

– EMC Avamar 

– EMC NetWorker 

– SQL Server Backup* 

Method 

Medium Farm (1-2TB) 

– EMC Replication Manager 


– EMC Avamar 

Granular/SW VSS* 

– SQL Server Backup* 

Farm 

backup 

– EMC Replication Manager* 


HW VSS* 

– SQL Server Replication 

(VSS/VDI)* 

Backup 

Size 

Supported 

Backup 

Type(s) 


Server 2010 

Y 

< 200 GB 

Full, 

differential 

VSS Writer * 

Y 

Solution 

specific 

Full, 

differential 

SQL Server 

N 

* For item level recovery consider Kroll Ontrack® PowerControls / Metalogix® Selective Restore Manager 

28 


28

SharePoint 2007-2010 replication options 

EMC Replication Manager for SharePoint 

Granularity: 

Farm, Content Database 

– HW VSS based coordinated SharePoint 

replication, enabling cross-app consistency 

– Utilizing EMC storage replication 

capabilities for maximum scalability 

• Snaps/Clones 

– Simple, intuitive SharePoint discovery and 

application set configuration 

– Works with SQL RBS FILESTREAM 

– Full farm restore include search index 

consistency on recovery 

For item level recovery consider Kroll Ontrack® PowerControls / Metalogix® Selective Restore Manager 


29

SharePoint Replication Management – Reference Architecture 

Enabled by EMC Replication Manager, Kroll Ontrack PowerControls 

• Hybrid farm (Physical/Virtual) 

• 1.5 TB of content (6,818,250 

objects) 

• 15 SharePoint sites, each 

populated with 100 GB of random 

user data 

• All RAID5 FC 15K 

• EMC Replication Manager for 

SharePoint to create MOSS 

consistent replicas 

• Both SnapView Snaps and 

Clones used 


30

SharePoint Replication Management – Reference Architecture 

Item Level Recovery 

• PowerControls for SharePoint was 

installed on RM mount host 

• EMC Replication Manager supports the 

recovery of the farm content and index, 

or selective content 

• Simple three-step process to recover a 

Site/Folder/Item: 

1. Mount the RM replica volumes 

2. Open PowerControls and point to the 

mounted RM database files 

3. Browse the content and restore the 

required file(s) 

PowerControls opened a 100 GB content database (465,000 documents) in ~10 minutes! 


31

Proven Solution: 

SharePoint Replication Management 

Comparison 

SharePoint action 

Duration with 

EMC technologies 

Duration with native 

SharePoint tools 

Backup configuration and scheduling ~4min ~30min 

Full farm backup (2.5 TB) 

Clone: 3hr 11min 

Snapshot: 9min 

39hr 30min 

(14.8 MB/s) 

Daily incremental SharePoint backup 

(~1% daily change rate) 

Content database recovery (online) 

Item-level recovery 

Clone: 11min 

7min 

10min 

Not tested in this environment 

3hr 12min 

(12 MB/s) 

Not tested in this environment 

(requires recovery farm) 


32

Networker-Data Domain testing for MOSS 2007 

Architecture 

Main Storage: EMC CLARiiON CX4-480 

Backup Storage: Data Domain 690 

Hypervisor: 7 VMs on vSphere ESX 4 

Content: 1TB of SharePoint content 

Backup 

Total backup >1.1TB (including search, system 

and configuration databases) 

SQL and Content Index servers leverage HW 

VSS (EMC storage) WFEs use MS VSS 

SnapView Clones used for rapid SharePoint 

backup 

All backup LUNs were RAID5 SATA disks 


33

Business Continuity for SharePoint 2010: 

Options 

SQL 

DB Mirroring 

Log Shipping 

Stretched Farm 

(Partial Replication) 

Mirror Farm 

(Partial Replication) 

SAN 

Virtualized Farm 

(Complete Replication) 

RecoverPoint 

SRDF 

MirrorView 

VPLEX 

Point in 

Time 

RM 

(Avamar) 

(Networker) 


34

SharePoint 2010 Disaster Recovery: 

Stretched Farm (Partial Replication) 

SharePoint Farm A 

Primary Site 

Secondary Site 

OS 

• One logical farm 

OS 

WFE/Query Servers 

Index Partition 1 


1 

OS 

• SharePoint distribution of web, 

search and application 

components 

• NLB solution for client traffic 

control 



1-Mirror 

OS 


Application Server/s 

OS 

• Active/Active 

• Automated Failover 

OS 


Crawl Server/s 

Crawler 

Crawl 

Configuration 

• Limited to 1ms latencies (SQL- 

WFE), min 1GigE 

Crawler 

Crawl 

Configuration 


Central Admin 

Witness 

Central Admin 

SQL Cluster 

Services DBs 

Content 

EMC Cluster Enabler 

Database Mirroring (Synchronous) 

Services DBs 

Content 

SQL Cluster 

BLOB Store 

BLOB Store 


35


Mirror Farm (Partial Replication) 


Primary Site 

SharePoint Farm B 



OS 



1 

• Two independent farms 

• Content replication only 

• Independent search 

OS 



1-Mirror 


OS 

• Consistency grouping for BLOB 

and metadata (SAN) 

OS 


OS 

Crawler 

• Remote snaps/clones to enable 

RW copies 

• Requires refreshing configuration 

regularly 

OS 

Crawler 



Crawl 

Configuration 

• Long recovery time (RTO) 

Crawl 

Configuration 


Central Admin 

Central Admin 

SQL Cluster 

Services DBs 

Content 

BLOB Store 

RecoverPoint 

SRDF 

MirrorView 

SQL Database Mirroring 

Services DBs 

Content 

BLOB Store 

SQL Cluster 


36


Virtualized Farm (Full Replication) 

Demo available at Proven 

Solutions Booth 


Primary Site 


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 

EMC Cluster Enabler with Hyper- 

V failover clustering 

VMs 

VMs 

VMs 

VMs 

Databases 

RecoverPoint 

SRDF 

MirrorView 

VMs 

Databases 

BLOB Store 

BLOB Store 


37

Designing DR consistency for SharePoint 

Automated DR 

Consistency Group 

(RP/SRDF/MV) 

LUNs Grouping SRM CE 

Web Front Ends Boot + Query (optional) 

Protection 

Group 

Query Servers Boot + Query Component 

Protection 

Group 

Index Servers Boot + Index Component 

Protection 

Group 

Application Servers Boot + Application Volumes 

Protection 

Group 

Boot + Pagefile (optional) 

SQL System Databases 

Cluster Group 

Cluster Group 

Cluster Group 

Cluster Group 

SQL Server(s) 

Configuration Databases 

Search Databases 

Protection 

Group 

Cluster Group 

Content Databases 

RBS BLOB Store 

Externalized Content consistency 

Search consistency 


38

Protecting SharePoint 

Business Continuity – vCenter SRM with RecoverPoint CRR 

Production Site 

Outage 


39

Protecting SharePoint 

Business Continuity – vCenter SRM with RecoverPoint CRR 

Proven Solution Test Results 

– 13,080 heavy users @ 10% concurrency - Sustained Performance 

– 30% reduced cost of BLOB Storage with EMC LUN Compression 

– 6 minutes to restore 100GB Content Database 

–

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 over physical/hybrid configurations. 

– Horizontal scaling is more efficient 

– The best FULL farm protection when Integrated with EMC replication. 

– Simplifies, accelerates and automates SharePoint DR! (SRM, CE) 

• EMC’s SharePoint VSS based replication can significantly accelerate 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) 


41

Additional References 

EMC Solutions for SharePoint Portal 

– http://www.emc.com/sharepoint 

Technical Whitepapers 

• Virtualized SharePoint 2010 (ESX 4.0, CX4-240) 

– http://www.emc.com/collateral/software/white-papers/h8024-virtual-sharepoint-clariion-vsphere-wp.pdf 

• Continuous protection for virtual SharePoint 2010 (ESX 4.1, RBS, RP, RM, CX4-120) 

– http://www.emc.com/collateral/software/white-papers/h8139-protection-virtualized-sharepoint-wp.pdf 

• SharePoint 2010 BLOB externalization (Hyper-V, Metalogix StoragePoint, VNX5300) 

– http://www.emc.com/collateral/hardware/technical-documentation/h8185-sharepoint-vnx-metalogix-psg.pdf 

• SharePoint 2007 Business Continuity (Hyper-V, Cluster Enabler, CX4-120) 

– http://www.emc.com/collateral/solutions/reference-architecture/h7041-bc-sharepoint-clariion-recoverpointhyperv-ref-arc.pdf 

SharePoint Blogs - EMC 

– http://sharepointintheprivatecloud.wordpress.com 

– http://sustainablesharepoint.com 


42


43


44

This document was created with Win2PDF available at http://www.win2pdf.com. 

The unregistered version of Win2PDF is for evaluation or non-commercial use only. 

This page will not be added after purchasing Win2PDF.

SharePoint 2010_Briefing.pdf - EMC Community Network

Create successful ePaper yourself

Delete template?

Save as template?