|
| 1 | +.. _rm-use-data-verification: |
| 2 | + |
1 | 3 | =====================
|
2 | 4 | Use Data Verification
|
3 |
| -===================== |
| 5 | +===================== |
| 6 | + |
| 7 | +.. contents:: On this page |
| 8 | + :local: |
| 9 | + :backlinks: none |
| 10 | + :depth: 1 |
| 11 | + :class: singlecol |
| 12 | + |
| 13 | +Data verification runs as a separate process that is tightly |
| 14 | +coupled to a sync job. Data verification can be enabled for one-time |
| 15 | +sync jobs. This page details how to enable and debug the |
| 16 | +data verification process. |
| 17 | + |
| 18 | +Enable Data Verification |
| 19 | +------------------------ |
| 20 | + |
| 21 | +You can enable data verification when :ref:`creating a sync job <rm-create-jobs>` |
| 22 | +on the :guilabel:`Data Migration` tab. |
| 23 | + |
| 24 | +On the :guilabel:`Migration Options` module, click the |
| 25 | +:guilabel:`Verify migrated data` check box for your sync job. |
| 26 | + |
| 27 | +.. note:: Data Verification Duration |
| 28 | + |
| 29 | + The Data Verification process can take as long or longer than the data sync job. |
| 30 | + You can click :guilabel:`Terminate` to cancel a Data Verification process. |
| 31 | + |
| 32 | +To view status and metadata information about the data verification process |
| 33 | +for a sync job, click the :guilabel:`SYNC JOB / DATA VERIFICATION` slider. |
| 34 | + |
| 35 | +.. image:: /img/jobs/data-verification/data-verification-click-slider.png |
| 36 | + :alt: Click Data Verification Slider |
| 37 | + |
| 38 | +Data Verification Overview |
| 39 | +-------------------------- |
| 40 | + |
| 41 | +On the :guilabel:`Data Verification` pane, you can view the metadata |
| 42 | +about a sync jobs verification process. |
| 43 | + |
| 44 | +.. list-table:: |
| 45 | + :header-rows: 1 |
| 46 | + |
| 47 | + * - Syntax |
| 48 | + - Description |
| 49 | + * - Verification Status |
| 50 | + - The state of the verification process. |
| 51 | + * - Started |
| 52 | + - The date time stamp that data verification process started. |
| 53 | + * - Duration |
| 54 | + - The total elapsed time of the data verification process. |
| 55 | + * - Collections verified |
| 56 | + - The total number of collections verified by the data verification process. |
| 57 | + * - Documents verified |
| 58 | + - The total number of documents verified by the data verification process. |
| 59 | + * - Verification progress |
| 60 | + - A real time percentage indicator of total work completed by the data verification process. |
| 61 | + |
| 62 | + |
| 63 | +Data Verification Statuses |
| 64 | +-------------------------- |
| 65 | + |
| 66 | +A data verification process can be any of the following statuses: |
| 67 | + |
| 68 | +.. list-table:: |
| 69 | + :header-rows: 1 |
| 70 | + :widths: 20 80 |
| 71 | + |
| 72 | + * - Status |
| 73 | + - Description |
| 74 | + * - ABORTED |
| 75 | + - A running data validation was unable to complete due to an error. |
| 76 | + * - CANCELLED |
| 77 | + - The data validation process was cancelled by clicking :guilabel:`TERMINATE`. |
| 78 | + * - CANCELLING |
| 79 | + - The data validation process is being canceled. |
| 80 | + * - FAILED |
| 81 | + - The source and destination databases do not match. The corresponding errors are listed on the :guilabel:`Issues` pane. |
| 82 | + * - VERIFIED |
| 83 | + - Data validation is successful, the source and destination databases match. |
| 84 | + * - VERIFYING |
| 85 | + - The data validation is in progress. Backend SQL and MongoDB query API commands are running to validate the migration. |
| 86 | + |
| 87 | +Successful Data Verification |
| 88 | +---------------------------- |
| 89 | + |
| 90 | +When a sync job is successful the status updates to :guilabel:`VERIFIED` |
| 91 | +and a double checkmark is displayed in the :guilabel:`History` pane. |
| 92 | + |
| 93 | +.. image:: /img/jobs/data-verification/data-verification-double-checkmark.png |
| 94 | + :alt: History pane double checkmark |
| 95 | + |
| 96 | + |
| 97 | +Data Verification Issues |
| 98 | +------------------------ |
| 99 | + |
| 100 | +If the data verification process detects any differences between the |
| 101 | +source database and destination collections, the errors are |
| 102 | +reported in the Data Verification :guilabel:`Issues` pane. |
| 103 | + |
| 104 | +In this example, the data verification process is detecting that the |
| 105 | +number of documents in the target collection do not match the source |
| 106 | +database. |
| 107 | + |
| 108 | +#. The Verification status is :guilabel:`FAILED`. |
| 109 | +#. The specific issue and error detail is displayed in the :guilabel:`Issues` pane. |
| 110 | + |
| 111 | +.. image:: /img/jobs/data-verification/data-verification-view-issues.png |
| 112 | + :alt: Data verification issues |
0 commit comments