1. Maxim Zhvirblya EPAM Systems © 2013 Or make MSSQL breathe easily RBS and Blob Cache in SharePoint 2013

2.  Blob Cache  IIS  Cache content on WFE  Traffic reduction  Renditions  RBS  SQL  Remove BLOBs from Database  Storage cost reduction  SQL improve performance RBS VS Blob Cache

3. Cache

4.  Page output cache  Object cache  Anonymous search results cache  BLOB cache Note: To use the page output cache or the object cache, you must be using the Publishing feature on your site. Types of cache in SharePoint 2013

5. Blob Cache  Improve SQL performance by saving data on WFE  Persistent Cache  Improves HTTP Responses  HTTP range request  Reduce time to open page  Enabling Renditions

6. Blob Cache saving data on WFE  Save Data on WFE’s local drive  Works perfectly with anonymous access  BUT!  Increasing SQL requests in 5 times in order to create cache  Need to enable on all WFE’s  Add additional 800bytes of memory for each file to keep index

7. Persistent Cache  Don’t expire after IIS reset  But!  If you change data in pages library during Update Solution/Update Features you need to Flush BLOB Cache

8.  Add Information for browser to cache items  Allows HTTP request for part of a file  Some content viewer, like PDF viewer or media players can request only part of data HTTP range request

9.  SharePoint optimized for small size files  Low size files FileReadChunkSize (100kb) with one request  LargeFileChunkSize < 5mb – from SQL without disk buffer  > LargeFileChunkSize - from SQL with WFE buffer Reduce time to open page

10.  Image rendition is a new capability in SharePoint 2013 helps you to optimize images in your SharePoint site through having the same image but in different sizes.  Image Rendition gives you control over the size of your images and allows you to further crop images to get the results you need. Images can be fixed to certain sizes for WebPart use or for use on SharePoint page. Renditions

11.  Prerequisites for managing image renditions  A publishing site collection.Or, publishing features must be enabled on the site collection where you want to use image renditions.  A configured BLOB cache  An asset library (recommended)

12. Renditions

17.  Specify the image rendition in the image URL  RenditionID  Width  Height  Width and Height Renditions

18.  Limitations:  Size ~25MB  Maximum Pixel Count 40043584 Renditions

19.  Enable on each IIS site  Enable on each WFE BLOB Cache How to

21. BLOB Cache  Attributes that can be changed

22.  Change this attributes only when planning to use large BLOBS BLOB Cache

23. BLOB Cache example http://social.technet.microsoft.com/Forums/sharepoint/en-US/53fe4b17-5674-4eea-81b1-e4cf6a562836/image-rendition-file-size- restriction?forum=sharepointgeneral#07add00a-08e7-48f1-8c37-01a57418bb44

24.  IIS Reset – to reinitialize index  Flush BLOB Cache  Disable BLOB cache, delete cache folder, enable cache. BLOB Cache troubleshooting

25.  SQL Server Remote BLOB Store (RBS) is an optional add-on component that lets database administrators store binary large objects in commodity storage solutions instead of directly on the main database server.  In SharePoint 2013 BLOB is a large block of data stored in a database that is known by its size and location instead of by its structure. RBS

26.  SharePoint stores all data in MSSQL  MSSQL not very suitable for storing large objects  RBS helps to reduce size of content DB  SharePoint can use FILESTREAM or any other RBS Provider RBS

27.  Multi-layer data storage  BLOB archiving  Adding not SharePoint libraries to BLOB Storage  Caching of BLOB-object in memory RBS

28.  Use Fast and expensive storage for actual documents, slow and cheap storage for large, old objects  Filtering for storage data RBS Multi-layer data storage

29.  Some RBS Providers can archiving specific data even after deleting in SharePoint  Archives works offline and SharePoint doesn’t know about them  Auto-deleting archives after specific time BLOB archiving

30.  RBS can provide access for SharePoint to third party libraries as it his own  SharePoint create index for this libraries, and end user don’t even know that he use something else. Adding not only SharePoint libraries to BLOB Storage

31.  Almost the same as IIS BLOB cache Caching of BLOB-object in memory

32.  BLOB store must be local to SQL Server for Standard license  Basic Orphaned BLOB Garbage Collection  Search for BLOB objects Sadly, but they are all features provided by FILESTREAM  FILESTREM RBS

33.  Enable FILESTREM on MS SQL Server Install FILESTREAM RBS

34.  Configure MSSQL Server Install FILESTREAM RBS

35.  Create Content Databse  Create Database master Key Install FILESTREAM RBS

36.  Create File Group for RBS Provider Install FILESTREAM RBS

37.  Create File Stream File for designed path Install FILESTREAM RBS

38.  Install the RBS package  Ensure that RBS Package installed successfully Install FILESTREAM RBS

39.  Activate RBS for your Content Databases with PowerShell Install FILESTREAM RBS

40.  You will need perform an IISRESET and restart the SP Timer Service on all machines in the farm.  Link http://sharepoint-channel.com/i-padabed-shredded- storage-in-sharepoint-2013-video-zapis-doklada-na-spcua- 2013http://sharepoint-channel.com/i-padabed-shredded- storage-in-sharepoint-2013-video-zapis-doklada-na-spcua- 2013  http://hellebuyck.net/?p=109 RBS and Shredded Storage

41.  MS SQL backups doesn’t save content of RBS  SharePoint backup whole content using FILESTREAM provider  Also Third Party Backup System provide saving content (AveDoc, Symantec, etc.) FILESTREAM RBS provider and Backups

42.  RBS has specific content database size limitations for specific scenarios. (200GB)  Encryption is not supported on BLOBs, even if Transparent Data Encryption is enabled.  RBS does not support using data compression.  Support for database mirroring and log shipping is altered  New Version of file create additional file in RBS FILESTREAM RBS provider limitations

43.  Files changes frequently  Files that used but not very often Not very useful  Using a lot of different page components ex: JavaScript, CSS  Using a lot of graphical files  Large Multimedia, video  Planning use of renditions Useful Final Notes, BLOB Cache

44.  A large amount of small BLOBs that change often  Encryption of DB Not very useful  Large BLOBs with mostly read-only access  Improve SQL Service Performance  Use more cheap storage for specific data Useful Final Notes, RBS

45. Questions & Discussion