Export (0) Print
Expand All

Remote Blob Store (RBS) and AlwaysOn Availability Groups (SQL Server)

Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

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)


Another database in the same instance of SQL Server (stored using a RBS remote FILESTREAM provider)


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)


This database must be in a separate availability group.

A third-party BLOB store


To protect this BLOB data, use the high-availability mechanisms of the BLOB store provider.

  • RBS maintainers need to be targeted on the primary replica.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft