Skip to content
This repository was archived by the owner on May 1, 2025. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 2 additions & 5 deletions source/reference/verification.txt
Original file line number Diff line number Diff line change
Expand Up @@ -44,8 +44,8 @@ source to the destination cluster.
- Starting in 1.9, ``mongosync`` includes an embedded
verifier, which runs a series of verification checks on
the source and destination clusters to confirm that the
migration was successful. This is the preferred
verification method for deployments that meet the
migration was successful. **This is the preferred
verification method for deployments that meet the**
:ref:`requirements <c2c-verify-embedded-limitations>`.

When the ``mongosync`` process starts, it prompts the
Expand Down Expand Up @@ -159,9 +159,6 @@ source to the destination cluster.
comparing documents, views, and indexes to confirm the
sync was successful.

Migration Verifier is an experimental and unsupported
tool.

The specific method you use to verify your data depends on your
application workload and the complexity of the data.

Expand Down
2 changes: 0 additions & 2 deletions source/reference/verification/verifier.txt
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,6 @@ About This Task
Migration Verifier does not support DDL operations. Do not run any DDL
operations on the source cluster while verifying data with Migration Verifier.

Migration Verifier is an experimental and unsupported tool.

For installation instructions and usage limitations, see
`GitHub <https://github.com/mongodb-labs/migration-verifier>`__.

Expand Down