Remote Blob Store (RBS) and Always On Availability Groups (SQL Server)

THIS TOPIC APPLIES TO: yesSQL Server (starting with 2016)noAzure SQL DatabasenoAzure SQL Data Warehouse noParallel Data Warehouse

Always On availability groups can provide a high-availability and disaster recovery solution for SQL ServerRemote Blob Store (RBS) BLOB objects (blobs). Always On 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 RBS 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

See Also

Always On Client Connectivity (SQL Server)
Remote Blob Store (RBS) (SQL Server)