Since 8th of july 2011, the product group has published a new post regarding changes on database size limitations and guidance.
The most interesting key points out of the above mentioned post are as follows:
Requires disk sub-system performance of 0.25 IOPS per GB, 2 IOPS per GB is recommended for optimal performance.
Requires the customer to have plans for high availability, disaster recovery, future capacity, and performance testing.
And you need to review additional considerations in the TechNet Boundaries and Limits article.
Please review the full TechNet Article SharePoint Server 2010 capacity management: Software boundaries and limits document. We have also published a guide on SharePoint 2010 scalability here: http://go.microsoft.com/fwlink/?LinkId=223599. In the near future we will publish a test report of large scale testing that supports these new size limits.
Also added by Stefan Goßner (thnx for admission to repost), the information to the official statement about RBS:
See Stefan's full post's here: http://blogs.technet.com/b/stefan_gossner/archive/2011/07/08/paul-andrew-talks-about-new-larger-sharepoint-content-database-size-limits-and-rbs-clarifications.aspx http://blogs.technet.com/b/stefan_gossner/archive/2011/06/23/sharepoint-2010-rbs-documentation-has-been-updated.aspx
More from the SharePoint Team Blog: The following considerations have to be taken into account when using RBS with SharePoint:
Please see more details and the “Q & A” section on the original post from the SharePoint Team Blog: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=988
Move-SPSite cmdlet extended with a new parameter!
Another important info is the new added parameter [RbsProviderMapping], which was added in Microsoft SharePoint Server 2010 with Service Pack 1 (SP1) and Microsoft SharePoint Foundation 2010 with Service Pack 1 (SP1). This parameter is used to move an RBS-enabled site collection from one RBS-enabled content database to another RBS-enabled content database without moving the underlying BLOB content. If the content database has more than one RBS provider associated with it, you must specify all providers. The same providers must be enabled on the target content database and the source content database.
Other related blogs and posts:
Announcing: New Larger Content Database Size Limits and RBS Clarifications by Paul Andrew
Now Serving Larger Databases… by Bill Baer
Limitations of FileStream provider with RBS
FileStream Provider only allows for storing BLOBs on the same location as your SQL Server data files and therefore does not reduce I/O burden. In fact, it slows things down even further in some cases.
- FileStream Provider only offers a basic level of garbage collection.
- RBS FileStream Provider doesn’t support multiple storage tiers to help you optimize your storage cost (see my blog on SharePoint Archiving with multiple storage tiers).
- No compression or encryption options are afforded.
- RBS FileStream Provider is only supported in SharePoint 2010.
- Much more…
So before using the RBS FileStream Provider, you should be very careful in analyzing the costs of its limitations.
However StorageEdge a 3rd party tool provides a much superior alternative to the RBS FileStream Provider. Here are some important benefits of using StorageEdge FileStream Provider.