Skip to content

Latest commit

 

History

History
44 lines (31 loc) · 3.34 KB

File metadata and controls

44 lines (31 loc) · 3.34 KB
title Remote Blob Store (RBS) with availability groups
description A description of how to use the Remote Blob Store (RBS) with databases that are part of an Always On availability group.
author MashaMSFT
ms.author mathoma
ms.date 05/17/2016
ms.service sql
ms.subservice availability-groups
ms.topic conceptual

Use Remote Blob Store (RBS) with Always On availability groups

[!INCLUDE SQL Server]

[!INCLUDEssHADR] can provide a high-availability and disaster recovery solution for [!INCLUDEssNoVersion]Remote Blob Store (RBS) BLOB objects (blobs). [!INCLUDEssHADR] 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, [!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] (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 [!INCLUDEssNoVersion] (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

Related Content

See Also

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