Skip to content

Latest commit

 

History

History
46 lines (33 loc) · 3.25 KB

File metadata and controls

46 lines (33 loc) · 3.25 KB
title Remote Blob Store (RBS) and AlwaysOn Availability Groups (SQL Server) | Microsoft Docs
ms.custom
ms.date 06/13/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology high-availability
ms.topic conceptual
ms.assetid 01a70258-d4fd-40bc-bc44-c490b5d6c420
author MashaMSFT
ms.author mathoma
manager craigg

Remote Blob Store (RBS) and AlwaysOn Availability Groups (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 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 [!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

AlwaysOn Client Connectivity (SQL Server)
Remote Blob Store (RBS) (SQL Server)