Transcript Note

Maxim Zhvirblya
EPAM Systems © 2013
RBS and Blob Cache in
SharePoint 2013
Or make MSSQL breathe easily
RBS VS Blob Cache
 RBS
SQL
Remove BLOBs from
Database
Storage cost reduction
SQL improve
performance
 Blob
Cache
IIS
Cache content on WFE
Traffic reduction
Renditions
Cache
Types of cache in SharePoint 2013
 Page
output cache
 Object
cache
 Anonymous
 BLOB
search results cache
cache
Note:
To use the page output cache or the object cache, you
must be using the Publishing feature on your site.
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
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
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
HTTP range request
 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
Reduce time to open page
 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
Renditions
 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
 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)
Renditions
Renditions
Renditions
Renditions
Renditions
Renditions
 Specify the image
 RenditionID
 Width
 Height
 Width and Height
rendition in the image URL
Renditions
 Limitations:
 Size
~25MB
 Maximum
Pixel Count 40043584
BLOB Cache How to
 Enable
on each IIS site
 Enable
on each WFE
BLOB Cache How to
BLOB Cache
 Attributes
that can be changed
BLOB Cache
 Change
BLOBS
this attributes only when planning to use large
BLOB Cache example
http://social.technet.microsoft.com/Forums/sharepoint/en-US/53fe4b17-5674-4eea-81b1-e4cf6a562836/image-rendition-file-sizerestriction?forum=sharepointgeneral#07add00a-08e7-48f1-8c37-01a57418bb44
BLOB Cache troubleshooting
 IIS
Reset – to reinitialize index
 Flush
BLOB Cache
 Disable
BLOB cache, delete cache folder, enable cache.
RBS
 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
 SharePoint
 MSSQL
 RBS
stores all data in MSSQL
not very suitable for storing large objects
helps to reduce size of content DB
 SharePoint
can use FILESTREAM or any other RBS Provider
RBS
 Multi-layer
 BLOB
data storage
archiving
 Adding
not SharePoint libraries to BLOB Storage
 Caching
of BLOB-object in memory
RBS Multi-layer data storage
 Use
Fast and expensive storage for actual documents,
slow and cheap storage for large, old objects
 Filtering
for storage data
BLOB archiving
 Some
RBS Providers can archiving specific data even after
deleting in SharePoint
 Archives
them
works offline and SharePoint doesn’t know about
 Auto-deleting
archives after specific time
Adding not only SharePoint libraries to BLOB
Storage
 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.
Caching of BLOB-object in memory
 Almost
the same as IIS BLOB cache
FILESTREM RBS
 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 
Install FILESTREAM RBS
 Enable
FILESTREM on MS SQL Server
Install FILESTREAM RBS
 Configure
MSSQL Server
Install FILESTREAM RBS
 Create
Content Databse
 Create
Database master Key
Install FILESTREAM RBS
 Create
File Group for RBS Provider
Install FILESTREAM RBS
 Create
File Stream File for designed path
Install FILESTREAM RBS
 Install
the RBS package
 Ensure
that RBS Package installed successfully
Install FILESTREAM RBS
 Activate
RBS for your Content Databases with PowerShell
RBS and Shredded Storage
 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-shreddedstorage-in-sharepoint-2013-video-zapis-doklada-na-spcua2013
 http://hellebuyck.net/?p=109
FILESTREAM RBS provider and Backups
 MS
SQL backups doesn’t save content of RBS
 SharePoint
provider
 Also
backup whole content using FILESTREAM
Third Party Backup System provide saving content
(AveDoc, Symantec, etc.)
FILESTREAM RBS provider limitations
 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
 New
for database mirroring and log shipping is altered
Version of file create additional file in RBS
Final Notes, BLOB Cache
Useful
Not very useful
 Using
a lot of different
page components ex:
JavaScript, CSS
 Using
files
 Large
a lot of graphical
Multimedia, video
 Planning
use of renditions
 Files
 Files
changes frequently
that used but not very
often
Final Notes, RBS
Useful
Not very useful
 Large
A
 Improve
 Encryption
BLOBs with mostly
read-only access
SQL Service
Performance
 Use
more cheap storage
for specific data
large amount of small
BLOBs that change often
of DB
Questions & Discussion