Events
31 Mar, 11 pm - 2 Apr, 11 pm
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayUse Remote Blob Store (RBS) with Always On availability groups
Applies to: 
SQL Server
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. |
- RBS maintainers need to be targeted on the primary replica.
- Use an availability group listener. For more information, see Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server).
Maintaining Remote BLOB Store (in SQL Server 2008 R2 (10.50.x) Books Online)
Running RBS Maintainer (blog)
Configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint 2010) (blog)
Always On Client Connectivity (SQL Server)
Remote Blob Store (RBS) (SQL Server)