If you are considering enabling RBS in SharePoint 2013 and additionally if you are having scheduled SQL Backup or any other DR System in place then you should understand the implications of the effect of Document Shredding with RBS. Please read and understand how document shredding works outlined by Chris Mullendore [MSFT] in his article (link provided below).
Document Shredding in SharePoint 2013 directly conflicts with the understanding RBS in SharePoint 2010. In simple words to conclude, RBS will not work same as how it worked in SharePoint 2010. Is because of the file chunk treatment implementation in Document Shredding. In a typical configuration scenarios, it may happen so that the chunks of content that belongs to same version of one Document, could be saved in a hybrid Storage structure, meaning, chunks of file content may be stored in parts in File System and in Content Database. Additionally, the document type if it is a ‘Office Document’ or ‘Non-Office document’, will also play a role on defining size of chunks which in-turn affect RBS Storage depending on how the RBS threshold value is set in the configuration.
It is even more complicated, if a DR System is in place with RBS enabled, in the situations if you have to restore Content Databases from SQL Backups, and if File System Data in RBS is not in sync with the timestamp of the SQL Backup, then the documents and it’s versions restored content may lose their integrity and finally corrupting the critical business data.
*Please have a thorough understanding of the effect of ‘Document Shredding’ on ‘RBS’ in SharePoint 2013 or discuss with a professional before you enable RBS in your SharePoint 2013 environment.
Based on Article: Shredded Storage vs. RBS by Chris Mullendore [MSFT]
http://blogs.msdn.com/b/mossbiz/archive/2013/09/13/shredded-storage-vs-rbs.aspx
No comments:
Post a Comment