Instance Data Replication release notes
-
- UpdatedFeb 1, 2024
- 2 minutes to read
- Washington DC
- 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 Washington DC release.
Instance Data Replication highlights for the Washington DC 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 Washington DC
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.
Log rotation is automatically enabled for the Replication Payload Error [idr_replication_payload_error] table after the upgrade. By default, the log rotation schedule is comprised of seven shards, with five days for each shard. All log entries in this table created before the upgrade are automatically truncated.
Changed in this release
- Hermes-only replication
- Newly-created replication sets now use Hermes Messaging Service. You can no longer create legacy replication sets.
- Comparing replicated data between instances
- Compare data in replication sets with data transformations, bidirectional replication, and discrete replication.
Activation information
Instance Data Replication is a ServiceNow AI Platform feature that 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.