--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform Release : - australia ft:locale : - de-DE ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Comparing replicated data # Comparing replicated data between instances in Instance Data Replication {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Find missing or mismatched records by comparing replication data between instances in Instance Data Replication (IDR). IDR synchronizes data between a producer instance and one or more consumer instances. After you activate a producer replication set and subscribe at least one consumer, you can send existing records from the producer to the consumer by seeding records. After seeding is finished, IDR maintains data synchronization between the instances by replicating new and changed records from the producer to the consumer. If an insert fails on the consumer or when producer and consumer records don't match after replication, you can use the data comparison feature in IDR to find these records and reseed them from the producer to the consumer. ## Key benefits {#comparing-replicated-data__section_mxv_qxp_1xb} * Identify records missing from the consumer instance after seeding. * Identify mismatched records and view their differences. * Keep data synchronized between instances by reseeding records. {#comparing-replicated-data__ul_lft_rxp_1xb} ## Comparing transformed data {#comparing-replicated-data__section_zmy_4pw_jzb} When comparing transformed data, note the following details: * The data comparison can return mixed results if records are added to a table on the producer and then a transformation replicates to a different table on the consumer instance. * Mapped fields with different field definitions are skipped. For example, if a field on the producer has a different column type or column length than the mapped field on the consumer, the field is skipped. * All fields that are modified by an adapter are skipped except for modifications made by the Task number adapter. For example, if a string is appended using the Concatenate String adapter, the data comparison can't undo the concatenation and compare the data using the original string, so the field is skipped. {#comparing-replicated-data__ul_drs_wpw_jzb} ## Compatibility {#comparing-replicated-data__section_sxp_45g_lzb} Beginning in the Washington DC release, you can compare replicated data in bidirectional replication sets, discrete replication sets, and replication sets with transformations configured on either the producer or the consumer. When comparing data on different family releases, note the following compatibility options.{#comparing-replicated-data__table_xxy_wtg_lzb__entry__4} | Data comparison | Producer | Consumer | Supported replication sets | |-|-|-|-| | Producer to consumer | Washington DC or later | Utah and earlier | None | | Producer to consumer | Washington DC or later | Vancouver | Supports unidirectional replication sets, but not the following: * bidirectional replication sets * discrete replication sets * replication sets configured with transformations {#comparing-replicated-data__ul_jtt_zxf_nzb} | | Producer to consumer | Washington DC or later | Washington DC or later | All replication sets | [Tabelle : 1. Producer to consumer compatibility] {#comparing-replicated-data__table_xxy_wtg_lzb}{#comparing-replicated-data__table_mt5_fs2_nzb__entry__4} | Data comparison | Consumer | Producer | Supported replication sets | |-|-|-|-| | Consumer to producer | Washington DC or later | Utah and earlier | None | | Consumer to producer | Washington DC or later | Vancouver | Supports bidirectional replication sets, but not the following: * unidirectional replication sets * discrete replication sets * replication sets configured with transformations {#comparing-replicated-data__ul_h1v_fyf_nzb} | | Consumer to producer | Washington DC or later | Washington DC or later | All replication sets, but not unidirectional replication sets | [Tabelle : 2. Consumer to producer compatibility] {#comparing-replicated-data__table_mt5_fs2_nzb} ## Limitations {#comparing-replicated-data__section_e3m_wxp_1xb} * Journal fields are excluded from the comparison due to the potential size of their content. * Sys Audit \[sys_audit\] table records are excluded from the comparison. {#comparing-replicated-data__ul_c41_xxp_1xb} * **[Find missing or mismatched records in Instance Data Replication](https://servicenow-prod.fluidtopics.net/G1EzME6kK0MXIVKITXNgfg)** Find records missing from the consumer instance or mismatched records after data has been replicated by creating a data comparison request in Instance Data Replication (IDR). * **[Reseed missing or mismatched records in Instance Data Replication](https://servicenow-prod.fluidtopics.net/8FnHUWSzyq5r6dJ35IiDsw)** Synchronize data between instances by reseeding records missing from the consumer instance or mismatched records between the producer and consumer instance in Instance Data Replication (IDR). **Zugehörige Konzepte** * [Deploying a replication configuration from one instance to another in Instance Data Replication](https://servicenow-prod.fluidtopics.net/aXyRqzpHtX5W3N3kqjQzXA "Copy a replication configuration from one instance to another through an update set in Instance Data Replication (IDR).") * [Cloning options with Instance Data Replication](https://servicenow-prod.fluidtopics.net/ijG7TplhGq_gs_fi8q13Ig "Ensure that certain tables are preserved or excluded to clone your database from one instance to another successfully with Instance Data Replication (IDR).") * [Monitoring replication status in Instance Data Replication](https://servicenow-prod.fluidtopics.net/7MlShe8RgKCxFHkxJjVA8w "Monitor the status of active producer and consumer replication sets, scheduled jobs, seeding requests, license usage, or scheduled replication through the Instance Data Replication (IDR) Monitoring Dashboard.") * [Monitoring queues in Instance Data Replication](https://servicenow-prod.fluidtopics.net/e0SGVzygdHddQhPJ79IhZg "Monitor the replication record queue, message produced queue, message consumed queue, and the messages processed for all replications sets through the Instance Data Replication (IDR) Queue Dashboard.") * [Avoiding insert and update errors in Instance Data Replication](https://servicenow-prod.fluidtopics.net/zuedDsXgZrqP_LPNLQ4a3Q "You can avoid insert and update failures in Instance Data Replication (IDR) by specifying a class name filter in the producer replication set.") **Zugehörige Tasks** * [Manage consumer access to replication data in Instance Data Replication](https://servicenow-prod.fluidtopics.net/57KB8hSq0ex92SNNnzhudQ "Approve a consumer's request to access replication data in Instance Data Replication (IDR).") **Zugehörige Verweise** * [Resolving data replication errors in Instance Data Replication](https://servicenow-prod.fluidtopics.net/fyKlmwPenOddr7Q2673pUA "Resolve errors and monitor the status of Instance Data Replication (IDR) replication sets.")