From 16e609baa08b02ae6fec489e530463c0903a1ced Mon Sep 17 00:00:00 2001
From: amalhotra-mdb <135728846+amalhotra-mdb@users.noreply.github.com>
Date: Thu, 13 Mar 2025 11:50:31 -0400
Subject: [PATCH] DOCSP-48242-mongosync-metadata-post-sync (#651)

* DOCSP-48242-mongosync-metadata-post-sync

* capitalize heading

* reviewer updates

* clarification

(cherry picked from commit 8d1329a3c331a3a8fd5533174e355d8108225ab1)
---
 source/reference/mongosync/mongosync-behavior.txt | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/source/reference/mongosync/mongosync-behavior.txt b/source/reference/mongosync/mongosync-behavior.txt
index f666a862b..5ced9470f 100644
--- a/source/reference/mongosync/mongosync-behavior.txt
+++ b/source/reference/mongosync/mongosync-behavior.txt
@@ -279,6 +279,18 @@ Rolling Index Builds
 
 .. include:: /includes/rolling-build-limitation.rst
 
+``mongosync`` Metadata
+~~~~~~~~~~~~~~~~~~~~~~
+
+``mongosync`` stores its metadata in a database or multiple databases 
+during migration. The metadata databases can be named any of the following: 
+
+- ``mongosync_reserved_for_internal_use``
+- Anything beginning with ``mongosync_internal_``
+- Anything beginning with ``mongosync_reserved_for_verification_``
+
+You should drop any metadata databases after a successful migration. 
+
 Destination Clusters
 --------------------