Rob D’Oria, father of StoragePoint, has written a very comprehensive review of the new storage “guidance” from Microsoft with regard to the limits on ContentDB size when using RBSEBS.  It is a very long post, but completely worth reading from start to finish. 

For a peak at what you can expect, here is a direct excerpt from one of my favorite sections:

Everyone hold on, here’s the super-hard backup/restore process you have to follow in this brave new world:

Backup

1. Backup content database
2. Backup BLOB store(s) referenced by content database

Restore

1. Restore BLOB store(s) referenced by content database
2. Restore content database

Did anyone pass out?  Anyone hyper-ventilating?  Anyone soil themselves?  I didn’t think so.  That’s the process in all of its complicated ugliness.  In this scenario the worst thing you end up with is some orphaned BLOBs…you have some extra BLOBs in the BLOB store back-up that are not reflected in the content DB backup because it was taken first.  Upon restoring these datasets the extra BLOBs are orphaned, but they will be garbage-collected if the EBS/RBS solution supports it.

And, oh by the way, this is your worst case scenario.

Please take some time and read Rob’s full post, which can be found here: http://blog.sharepointedutech.com/2011/07/11/sharepoint-contentdb-guidance-too-many-shades-of-gray-along-with-a-little-brown/

Connect with Rob on Twitter at @robdoria or on LinkedIn at http://www.linkedin.com/in/robdoria

Rob’s opinions in his post of ISVs are his own.  I may or may not agree with everything he says, so be sure to rub a couple of brain cells together and form your own opinions.