Intelligent SharePoint Architecture and Storage Optimization Strategies

8/7/2019 Intelligent SharePoint Architecture and Storage Optimization Strategies

1/17

CodeCamp / SharePoint Saturday, March 26th 2011

Intelligent SharePointArchitecture and StorageOptimization Strategies

Michele Domanico

[email protected]


2/17


3/17


Global Leader in Microsoft SharePoint Infrastructure Management

, , ,D at a P r o t e c ti o n S t o r ag e O p t i m i za t i o n M a na g e m e n t, , ,I nt e g r a t i o n R e p o r t i n g C o m pl i a nc e M ig r a t i o n

Who We Are

Specialising in SharePoint since the platform s debut in2001

, ,Headquartered in Jersey City NJ with global offices on fivecontinents , +8 000 customers worldwide . 2010 Inc 500 s Fastest Growing Private Companies /2009 2010 Deloitte Fast 500 & ,2010 Ernst Young Entrepreneur of the Year &A Depth Managed Microsoft Gold Certified ISV and Portals

Collaboration Partner


4/17


Types of Content

What type of content can be stored on SharePoint?Legacy Content

, ,Document repositories such as file shares Lotus Notes EMC Documentum

Unstructured Content ( ) , ,Binary Large Objects BLOBS such as Word documents PDFs video and audiofiles

Inactive ContentDormant data no longer used by the organization but must be kept for

regulatory compliance


5/17


Implication of addingcontents

What happens when adding contents to SharePoint? , ,Scalability on settings permissions and policies Impact to SLAs for recoverability of content High cost of storage The BLOB problem

General performance decrease


6/17


Content in SharePoint

Problem beginswith initialmigration

Need data forlegal retention

SLAs still coverALL SharePoint

content


7/17CodeCamp / SharePoint Saturday, March 26th 2011

Impact on informationarchitecture

What do we need to plan for?

, .As SharePoint grows content often needs to be restructured These are just:common examples

, ,Documents between folders libraries and sites

Items between lists and sites Sites between Site Collections ( )Promotion and demotion of sites consolidate or expand



Optimise your StorageArchitecture

Extend BLOBs out of SQL :BLOBs Binary Large Objects = +SharePoint Content BLOB Metadata = +Content DB database of BLOBs Metadata ( / )SQL DB storage needs high IOPS input output operations per second and lowlatency

+ =High IOPS low latency storage $$$$ ,BLOBs do not participate in query operations so no real reason to have BLOBs

in a DB =DB full of BLOBs wasted $$$

Archive content Archive based on Business Rules from Site collection to item level


9/17


10/17CodeCamp / SharePoint Saturday, March th26 2011

-Impact of a BLOBScalability

,Expanding our SharePoint deployments increase our user base need toscale requests per second



:BLOB Externalization EBS& RBS

:EBS External BLOB Storage Introduced in SharePoint 2007 SP1 On deprecation list in SharePoint 2010

:RBS Remote BLOB Storage For SharePoint 2010 only Introduced in SQL Server 2008R2 Feature Pack EBS to RBS migration can be performed via Powershell or DocAve



Benefits of extendingBLOBs

-Performance Improving User Experience.Based on Microsoft Research< ,256kb SQL better

,256kb to 1mb SQL and file system comparable> ,1mb file system better

Saves storage costs Reuse existing storage to target the content offloaded from SharePoint Typically SQL storage is more expensive than other type of storages due to

latency time and number of IOPS

!Beware of Misconceptions&Backup Recovery operations are complicated

- % ,Databases are 60 80 smaller but need to backup BLOBs synchronously



Building a simpler story

,Three types of data treat themdifferently

Unstructured : DocAve Extender:Inactive DocAve Archiver

Legacy : DocAve Connector



AvePoint solutionoffering

DocAve Extender Externalizes SharePoint BLOBs Can be applied to both new uploads and retroactively to existing data

DocAve Connector Don t create the BLOB problem in the first place access content already

existing in external stores through SharePoint Implemented via special Document libraries types like DocAve Content and

Media Library

DocAve Archiver : (Add data lifecycle management to the picture archive SharePoint content from

/ )SQL and or extended to BLOB stores to lower tiered storage -Customizable business rule based archiving engine

* All of DocAve s Storage Optimization tools leverage supported BLOB APIs andutilize DocAve Media Services to support numerous storage devices including

, , , ,among the others Net Shares FTP TSM EMC Centera NetApp ONTAP and Cloud.Storage



Real World Scenario

-Access 44 TB of file share data within SharePoint without migration

>Have files 2GB in size , >Challenge is very deep file structure and complex long file names 256characters

Complex permission structure



Summary

.1 Three distinct types of content drive SharePoint usage, ,Legacy data unstructured data and inactive data all accumulate quickly in SQL

Server content databases as SharePoint usage evolves and expands

.2 Leverage BLOB Services APIs to Optimise SharePoint StorageBLOB APIs can be leveraged to store BLOBs outside of SQL with little impact on

- ,end users to save money and optimise hierarchal storage management

.3 Consider Infrastructure Implications of ExternalisationOptions for data protection and management must account for externalized

content

.4 Optimize SharePoint Performance and Availability with DocAve, , ,DocAve can streamline the deployment governance administration and

protection processes while accommodating for externalised BLOBs


17/17CodeCamp / SharePoint Saturday March 26th 2011

Thank you!