Forum Discussion
SharePoint 2013 - Remote Blob Storage and Deduplication / Shredded Storage Migration
I believe this is only possible at the content DB level not site collections. If you have one site collection per DB then sure.
https://docs.microsoft.com/en-us/sharepoint/administration/migrate-content-into-or-out-of-rbs
To modify the shred size, you should modify the FileReadChunkSize and FileWriteChunkSize properties.
$webapp = Get-SPWebApplication http://yourwebappurl/
$webapp.WebService.FileWriteChunkSize = 4194304
$webapp.webservice.Update()
Some references:
- https://blogs.technet.microsoft.com/wbaer/2012/11/12/introduction-to-shredded-storage-in-sharepoint-2013-rtm-update/
- https://view.officeapps.live.com/op/view.aspx?src=http%3a%2f%2fvideo.ch9.ms%2fsessions%2fspc%2f2014%2fSPC416_Baer.pptx
- https://gavinmckay.wordpress.com/2015/01/08/howto-configure-shredded-storage-in-sharepoint-2013-using-filewritechunksize/
Thanks Doug for your response.
Do you have any input for the deduplication of the BLOB files?
- Jan 13, 2019Dedupe would be a product of the RBS provider and/or file system (e.g. NTFS dedupe).
I'd ask why you'd be using RBS. It is largely irrelevant, now.- Stephan GJan 19, 2019Brass Contributor
Hi Trevor,
why do you mean it's irrelavant?
The deduplication feature will save me (if allowed) about 2 TB of space and the RBS feature will help me to stay within the 200GB DB size
We are having SharePoint 2013 on prem with 4TB+ data and mostly office files 2mb+.
Sorry for the late response .. i did not get any mail
Best regards
Stephan
- Jan 19, 2019General usage scenarios support is 4TB. It's all about storage performance. There is no 200GB "limit" (except with RBS, there is a _hard limit_ of 200GB; your un-deduped is the size you need to calculate). Having run many farms with CDBs in excess of 1TB, as long as your storage subsystem isn't made of just a couple 7200 RPM consumer SATA drives, you're likely fine to meet the 4TB IOPS requirements.