From 8e19b7b19b224db67b34245eb68ab37dd53a7af8 Mon Sep 17 00:00:00 2001 From: VAL Date: Mon, 1 Apr 2024 10:38:00 -0700 Subject: [PATCH] Clarify DR perf-standby behavior (#26230) --- website/content/docs/concepts/seal.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/content/docs/concepts/seal.mdx b/website/content/docs/concepts/seal.mdx index 9a1c4460d285..6c44a8f3bc8b 100644 --- a/website/content/docs/concepts/seal.mdx +++ b/website/content/docs/concepts/seal.mdx @@ -110,6 +110,8 @@ that would be provided with Shamir. The process remains the same. For a list of examples and supported providers, please see the [seal documentation](/vault/docs/configuration/seal). +When DR replication is enabled in Vault Enterprise, [Performance Standby](/vault/docs/enterprise/performance-standby) nodes on the DR cluster will seal themselves, so they must be restarted to be unsealed. + -> **Warning:** Recovery keys cannot decrypt the root key, and thus are not sufficient to unseal Vault if the Auto Unseal mechanism isn't working. They are purely an authorization mechanism. Using Auto Unseal