1 / 34

SharePoint Storage: Virtualize and Optimize

Ryan Tacy AvePoint. SharePoint Storage: Virtualize and Optimize. Agenda. Native SharePoint Storage BLOBs and Databases Storage Optimization Methods Summary. The Basics of. SharePoint Storage. Planning for SharePoint Storage. Recycle bin Versioning Search and index information

selah
Download Presentation

SharePoint Storage: Virtualize and Optimize

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ryan Tacy AvePoint SharePoint Storage: Virtualize and Optimize

  2. Agenda Native SharePoint Storage BLOBs and Databases Storage Optimization Methods Summary

  3. The Basics of SharePoint Storage

  4. Planning for SharePoint Storage • Recycle bin • Versioning • Search and index information • Growth • Good rule of thumb for initial planning is: 3.5 x file system

  5. Basics - Managing SharePoint storage • Set sight quotas and alerts! • 10 GB quota, 8 GB alert is my favorite • Monitor growth trends • Sites: slow over time or large jump in size? • Overall content DB size • Split Content DBs if they get “too big”

  6. How SharePoint “chooses” a Content DB for a site • Highest remaining allotment rule • Content DB 1: 100 sites max • Content DB 2: 100 sites max • Content DB 1: 100 sites max • Content DB 2: 200 sites max

  7. Optimal Content DB Sizing • Backup & Recovery operations(<50-100 GB) • Performance (<500 GB… nervous at 300 GB) • # of objects • size of objects • Hardware (servers and storage) • Storage Cost (as small as possible!) So what is too big?

  8. Size of Objects and Performance BLOBs

  9. BLOBs-- what’s the issue? • BLOBs = Binary Large OBjects • SharePoint Content = BLOB + Metadata • Content DB = Database of… BLOBs + Metadata • SQL DB storage needs high IOPS / low latency • 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 $$$

  10. Default SharePoint Storage SharePoint WFE SharePoint Object Model BLOBs & Metadata SQL Server Content DB Config DB

  11. Database Size Implications BLOBs increase DB size, creating issues with: Backup & Recovery operations Performance Storage Costs

  12. Issues with BLOBs get much worse over time Data Time

  13. SharePoint Storage Optimization Methods • Move the BLOBs out of the database • Archive content

  14. Moving the BLOBs out of the database Extending

  15. Available APIs for Extending SharePoint External BLOB Storage (EBS) SQL Remote BLOB Storage (RBS)

  16. EBS SharePoint WFE • API available in SharePoint 2007 SP1+ • EBS provider can take ownership of the BLOB • Provider generates a SharePoint token or stub • SharePoint knows how to retrieve the object  • Transparent to end-users  SharePoint Object Model BLOB BLOB Store SQL Server Content DB Config DB Metadata EBS Provider

  17. EBS • Implemented by SharePoint • Only 1 EBS Provider per SharePoint farm • Orphaned BLOBs- no direct method to compare BLOB store and Content DB • Compliance- what if I don’t want to allow SharePoint to delete the object?

  18. RBS SharePoint WFE • API available in SQL 2008R2 Feature Pack • Not unique to SharePoint, available to any application • A Provider Library can be associated with each database BLOB & Metadata SharePoint Object Model SQL Server Relational Access Provider Library X BLOB Metadata Content DB X Content DB Y RBS Client Library Provider Library Y BLOB Store BLOB Store

  19. RBS • Implemented by SQL • Only 1 RBS Provider per Content DB • Storage trigger on BLOB size • Orphaned BLOBs much less of an issue • Can lock down operations, from a unified storage perspective • Can be managed via Powershell

  20. EBS versus RBS, which is better? EBS Tighter integration with application, allows for more rules and settings

  21. EBS versus RBS, which is better? RBS EBS Simpler, allows unified storage architecture across applications Tighter integration with application, allows for more rules and settings http://www.codeplex.com/sqlrbs

  22. It looks like RBS has won… SharePoint 2007 SharePoint 2010 Future SharePoint Release (SPS 5?) SharePoint External BLOB Storage (EBS) SQL Remote BLOB Storage (RBS) SQL Server 2005 SQL Server 2008 Future SQL Releases Microsoft will provide a powershell solution to migrate from EBS to RBS

  23. 2 Approaches, Same Result • Backup & Recovery operations • Databases are 60-80% smaller • Need a method to backup BLOBs synchronously • Performance • Databases are 60-80% smaller • Performance improvement increase as the file/BLOB size increases. Microsoft research indicates: • <256kb, SQL better • 256kb to 1mb, SQL and file system comparable • >1mb, file system better • Storage Cost • “Not as expensive” storage • Archiving still needed for true savings

  24. Extended SharePoint Storage Web Services Search / App Services Extend Content out of SQL SQL Database Backup Cloud Storage Not involved in SharePoint Storage Tier 1 Tier 3 Tier 2

  25. Cloud Storage Use Case SharePoint “Overdraft Protection” DB alert set at 80 GB, limit at 100 GB 0 80 100 • Could be any storage • Cloud is ideal “insurance”--cheap to setup, expensive to use Alert sent to admin No action taken Cloud Storage

  26. An approach to not creating the BLOB problem in the first place Connecting

  27. Should you migrate data to SharePoint? • Business case • Value add of legacy system • Maintenance costs • Hardware • Licensing and support • Knowledge • Migration costs • Migration process • Tools • Training

  28. Migrating vs. Connecting Migrate Connect • Data is available in SharePoint • Data is moved into SharePoint • SharePoint replaced legacy system • Burden of storage is on SharePoint • Changes saved in SharePoint • Migrate and decommission • Data is available through SharePoint • Data is left in source (legacy) system • Give legacy system second life by increasing its value • Burden of storage is on legacy system • Changes propagate to source • Connect and forget

  29. Adding Data Lifecycle Management to the picture Archiving

  30. Data Lifecycle Management • Records Center • Another SharePoint site • Higher % inactive content • Consider separate Content DB, with an RBS provider implemented for this DB • Archiving • Backup and delete • Partner solutions

  31. Extending and Archiving Web Services Search / App Services Analyze data Apply business rules Fully utilize storage SQL Database Cloud Storage Tier 2 Tier 1 Tier 3

  32. Summary BLOBs aren’t required for queries, only the metadata is, hindering query performance RBS offers advantages over EBS RBS allows for a unified storage architecture across applications, not just SharePoint storage, but only available with SQL 2008 R2 Third Party solutions are required to leverage RBS/EBS Check out AvePoint’s solutions for Storage Optimization, includes tools for extending, connecting, and archiving SQL is not optimized for BLOBs Leverage BLOB Services Technology to Optimize SharePoint Storage BLOB API’s can be leveraged to store BLOBs outside of SQL with no negative end-user impacts, to save $$ and optimize storage

  33. Questions? ?

  34. Resources - www.AvePoint.com Ryan Tacy Ryan.Tacy@AvePoint.com (978) 409-2347 Download a FREE, fully-enabled 30 Day trial of DocAve at www.avepoint.com/download 34

More Related