Forum Discussion
SharePoint 2013 - Remote Blob Storage and Deduplication / Shredded Storage Migration
Hi there, i only found 2 blogs mentioning that this is possible. But is it also supported? Anyone is using this configuration? I want to move most of our sitecollections "to" Remote Blob Stor...
I don't think it is fair to compare ODfB/SPO services with on-prem capabilities. They use Azure Blob Storage which isn't quite the same and runs through a bunch of different code paths (see https://thesharepointfarm.com/2015/08/azure-blob-storage-for-sharepoint-documents/). You can have the performance you need to by monitoring your SQL Servers; using SSDs or other flash storage is going to be the best bet, performance-wise. No site size will "shrink" if using RBS or not.
Hi Trevor,
i know that it will not shrink - only if i use deduplication on the RBS file partition on the SQL server.
We are having a good performance.
But what is your best practice to archive complete site collections so that users can still access them read-only (working documents) the normal way for 5 years and still have a "normal" farm size that can be handled by one sql server and can be restored within hours (and maybe be used with azure site recovery)?
Best regards
Stephan
- What backup strategy are you using? The proper way would be to establish a proper SQL backup strategy, e.g. taking T-Log backups on regular intervals (we use 15 minute intervals) and full backups as appropriate, e.g. once per day, once per week, whichever works.
Farms in excess of 2TB aren't difficult to manage. In a general sense, business users do not want to 'archive' things. We see this with file servers all the time, with irrelevant data ranging back to pre-2010 or even pre-2000.
I suppose my point is you're introducing significant complexity for no _good_ reason. You're also not 'saving' yourself any work, only adding more. You still have to back that data up and you still need to maintain SQL database backups. Instead, now you're having to maintain two backups and sync their backup intervals. And maintain the RBS maintainer job. Hi Trevor,
a normal size would be (for a 1000 employee company) about 1-2 TB of active files.
So there must be a way to archive the "waste" to accomplish good backup times.
Farms can grow that big ... but it is not in the interest of the one who has to manage them.
- Archiving would be to simply place the site into a Read Only mode. Farms can grow to hundreds of TB so I'm not sure what you mean by "normal". RBS doesn't absolve you of any site/size limitations.
Using a single point of failure (SQL) is clearly an issue. You should have an AOAG setup and potentially a remote DR site.
Azure Site Recovery is fine, but it is a complicated ask. Running SharePoint in Azure isn't cheap and you cannot run Office Web Apps/Office Online Server in Azure due to licensing restrictions.