From d686d3f77fa874c5b88138a87d2faee123f10ba1 Mon Sep 17 00:00:00 2001 From: Jim Kalafut Date: Tue, 4 Dec 2018 08:49:42 -0800 Subject: [PATCH] Update operator migrate docs (#5895) --- website/source/docs/commands/operator/migrate.html.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/source/docs/commands/operator/migrate.html.md b/website/source/docs/commands/operator/migrate.html.md index f1bba4dac5..1afb014cee 100644 --- a/website/source/docs/commands/operator/migrate.html.md +++ b/website/source/docs/commands/operator/migrate.html.md @@ -14,7 +14,8 @@ description: |- The `operator migrate` command copies data between storage backends to facilitate migrating Vault between configurations. It operates directly at the storage level, with no decryption involved. Keys in the destination storage backend will -be overwritten. The source data is not modified, with the exception of a small lock +be overwritten, and the destination should _not_ be initialized prior to the +migrate operation. The source data is not modified, with the exception of a small lock key added during migration. This is intended to be an offline operation to ensure data consistency, and Vault