Did you run the SMSQL configuration wizard on the database server after enabling the RBS FILESTREAM?
It may be that SMSQL is not aware of the new FILESTREAM object. It can account for new databases, but it may be that SMSQL does not know about the FILESTREAM object and the backup fails. Attaching the SMSQL backup report file from a failed backup may help confirm this.
Just to let you know SMSP RBS has both the capability of externalizing content as well as archiving content. The extender function in Storage Optimization in SMSP handles the policies to externalize the content. The extender policies are based on database and content size.
The archiver function is used in records retention scenarios where you want to age out content using business rules based on records retention policies.
In the case of the video, you would apply extender policies to the web application with the video content.
I think that you might get better performance with the SMSP RBS provider instead of FILESTREAM RBS.
When comparing the video access from FILESTREAM RBS or SMSP RBS, when you get video data from SharePoint, it is actually treated as HTTP download because SharePoint itself doesn’t support streaming protocol.
First for FILESTEAM blob data access, the request is sent from WFE to SQL, and then converted by SQL and mapped to a file share UNC path to FILESTREAM data store, and then FILESTREAM RBS provider on WFE access the data using the file share UNC path. The SQL FILESTREAM RBS provider needs SQL to convert the FILESTREAM to file hare UNC path, and then it rely on the windows file server on SQL to expose the share, in the case the FILESTREAM is on iSCSI based LUN (on the filer), the file server on SQL also needs read data from SAN first and then pass to WFE. SQL server also rely on an additional file system filter driver to process the UNC path to FILESTREAM share, which will add more overhead for FILESTREAM read/write.
For SMSP RBS provider, the RBS provider gets the blob requests and then directly reads the path on NetApp storage so the CIFS read/write between WFE and filer can have greater performance than reading from local disk on the SQL server. The performance depends on the type and number of disk drives on the NetApp where the BLOBs are stored.
There is a tool in SMSP 6.1 that will allow you to convert SharePoint FILESTREAM RBS stubs into SMSP RBS stubs. The tool is called SMSP2010StorageRBSTool.exe and the procedure to convert the stubs is on page 227 of the SMSP 6.1 IAG.
Thanks,
Mark