I’ve had many people ask me about how Microsoft SharePoint 2013 Shredded Storage and Remote BLOB Storage work together, and how AvePoint supports this from a storage optimization perspective. Bill Baer, Senior Product Marketing Manager and Microsoft Certified Master for SharePoint, posted about this topic during SharePoint Conference 2012 and hopefully clarified a lot of the confusion around Shredded Storage. SharePoint MVP Dan Holme, AvePoint Enterprise Trainer & Evangelist Randy Williams, and I put together an article for Dan’s weekly column on Shredded Storage a few weeks ago which is also worth a read.
This white paper is the first of a series of storage optimization and management resources to be authored by a team of SharePoint MVPs. The goals of this white paper are to provide a comprehensive and balanced examination of the concepts and issues, and to equip you to fully understand, to communicate with your peers and your management, and to make an informed decision about the role of BLOB externalization in your storage architecture.
A solid backup & recovery strategy for your SharePoint platform in case of a disaster or a situation that creates a need for single item restores is an important step when maintaining strict SLAs.
Single item restores should be seamlessly possible regardless of where the SharePoint content is stored.
By default, content (including metadata & BLOBs) is stored in the content database. When content is offloaded out of SQL using RBS in combination with an ISV specific EBS/RBS provider, such as the one provided in AvePoint’s DocAve Software Platform for SharePoint, the metadata is stored in the AllUserData or AllDocs table. But the BLOB is offloaded to a NetShare of choice at upload or through scheduled jobs (determined by size, age or other metadata).