From a65f4fed92dc58c21c69a9f07448693ee93128ac Mon Sep 17 00:00:00 2001 From: Graham Land Date: Wed, 18 Sep 2019 22:19:32 +0100 Subject: [PATCH] Early indication of storage backend requirements (#7472) A Vault Enterprise Pro customer in Japan has tried to get Vault DR replication working using Google Cloud Storage. They were frustrated to learn that GCS may not have support for transactional updates which has resulted in a lot of wasted time. The complaint was that this was not clear from our documentation. This note may help customers to understand sooner that not all highly available backends support transactional updates. --- website/source/docs/enterprise/replication/index.html.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/source/docs/enterprise/replication/index.html.md b/website/source/docs/enterprise/replication/index.html.md index c35dd0cf9a..0549324e45 100644 --- a/website/source/docs/enterprise/replication/index.html.md +++ b/website/source/docs/enterprise/replication/index.html.md @@ -23,6 +23,8 @@ applications that need to interoperate. Vault replication addresses both of these needs in providing consistency, scalability, and highly-available disaster recovery. +Note: Using replication requires a storage backend that supports transactional updates, such as Consul. + ## Architecture The core unit of Vault replication is a **cluster**, which is comprised of a