Remote Blob Store (RBS) and AlwaysOn Availability Groups (SQL Server)
AlwaysOn Availability Groups can provide a high-availability and disaster recovery solution for SQL Server Remote Blob Store (RBS) BLOB objects (blobs). AlwaysOn Availability Groups protects any RBS metadata and schemas stored in an availability database by replicating them to the secondary replicas. This is the SharePoint Content Database. Generally speaking, SQL Server stores this RBS metadata independently from the blob.
The protection for RBD BLOB data depends on the BLOB Store Location, as follows:
BLOB Store Location |
Can Availability Groups Protect This BLOB Data? |
|---|---|
The same database that contains the RBS metadata (stored using a RBS remote FILESTREAM provider) |
Yes |
Another database in the same instance of SQL Server (stored using a RBS remote FILESTREAM provider) |
Yes We recommend that you put this database in the same availability group as the database that contains the RBS metadata. |
Another database in a different instance of SQL Server (stored using a RBS remote FILESTREAM provider) |
Yes This database must be in a separate availability group. |
A third-party BLOB store |
No To protect this BLOB data, use the high-availability mechanisms of the BLOB store provider. |
Limitations
- RBS maintainers need to be targeted on the primary replica.
Recommendations
- Use an availability group listener. For more information, see Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server).
Related Content
Maintaining Remote BLOB Store (in SQL Server 2008 R2 Books Online)
Running RBS Maintainer (blog)
Configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint 2010) (blog)
See Also
Concepts
Prerequisites, Restrictions, and Recommendations for AlwaysOn Client Connectivity (SQL Server)