Instance Data Replication release notes
-
- UpdatedAug 3, 2023
- 2 minutes to read
- Vancouver
- Release Notes and Upgrades
The ServiceNow® Instance Data Replication (IDR) application simplifies the data replication process between instances. Instance Data Replication was enhanced and updated in the Vancouver release.
Instance Data Replication highlights for the Vancouver release
- Keep data synchronized by replicating data from your producer instance to one or more consumer instances across different departments and business units.
- Maintain consistent data across different organizations in your company.
- Easily update records that have different sys_ids on the producer and consumer instances.
See Instance Data Replication for more information.
Important information for upgrading Instance Data Replication to Vancouver
Improve the performance and processing efficiency of Instance Data Replication (IDR) by upgrading your replication sets to V2, which uses the Hermes Messaging Service. For details, see Upgrading legacy replication sets to V2 in Instance Data Replication.
If the Replication Payload Error [idr_replication_payload_error] table on your instance has more than 10 million records, set up table rotation according to KB1364728. Using table rotation to delete records from the Replication Payload Error [idr_replication_payload_error] table is safe because that table only contains replication errors logged by IDR and not any replicated data.
New in the Vancouver release
- Compare replicated data between instances
- Find missing or mismatched records after replication by creating a data comparison request.
- Prevent replication of large attachments
- Prevent IDR from replicating excessively large attachments by adding a system property that limits the maximum attachment size.
- Improve replication availability and re-queue missing messages
- Prevent replication from stopping when an out-of-order issue occurs by adding a new system property that automatically re-queues missing messages without stopping active replication.
Changed in this release
- Upgrading legacy replication sets to V2 in Instance Data Replication
- All legacy replication sets are now eligible for upgrade V2, including bidirectional and discrete replication sets.
Activation information
Instance Data Replication is available with activation of the IDR (com.glide.idr) plugin, which requires a separate subscription. For details, see Request an Instance Data Replication subscription.
Additional requirements
The consumer and producer must both be running at least the San Diego release to support the custom coalesce feature.
This release requirement also applies to support for concurrent job execution.