Skip to content

Latest commit

 

History

History
61 lines (42 loc) · 3.2 KB

File metadata and controls

61 lines (42 loc) · 3.2 KB
title Encrypted Databases with Always On Availability Groups (SQL Server) | Microsoft Docs
ms.custom
ms.date 05/17/2016
ms.prod sql-server-2016
ms.reviewer
ms.suite
ms.technology
dbe-high-availability
ms.tgt_pltfrm
ms.topic article
helpviewer_keywords
Transparent Data Encryption, AlwaysOn Availability Groups
TDE, AlwaysOn Availability Groups
Availability Groups [SQL Server], interoperability
ms.assetid 09eb6ebc-3051-4fff-86a5-93524507b1fc
caps.latest.revision 10
author MikeRayMSFT
ms.author mikeray
manager jhubbard

Encrypted Databases with Always On Availability Groups (SQL Server)

[!INCLUDEtsql-appliesto-ss2016-xxxx-xxxx-xxx_md]

This topic contains information about the using currently encrypted or recently decrypted databases with [!INCLUDEssHADR] in [!INCLUDEssCurrent].

In this Topic:

Limitations and Restrictions

  • If a database is encrypted or even contains a Database Encryption Key (DEK), you cannot use the [!INCLUDEssAoNewAgWiz] or [!INCLUDEssAoAddDbWiz] to add the database to an availability group. Even if an encrypted database has been decrypted, its log backups might contain encrypted data. In this case, full initial data synchronization could fail on the database. This is because the restore log operation might require the certificate that was used by the database encryption keys (DEKs), and that certificate might be unavailable.

    To make a decrypted database eligible to add to an availability group using the wizard:

    1. Create a log backup of the primary database.

    2. Create a full database backup of the primary database.

    3. Restore the database backup on the server instance that hosts the secondary replica.

    4. Create a new log backup from primary database.

    5. Restore this log backup on the secondary database.

Related Tasks

See Also

Overview of Always On Availability Groups (SQL Server)
Transparent Data Encryption (TDE)