Combined Instance Data Replication release notes for upgrades from Vancouver to Yokohama

How to use this page

To help you prepare for your upgrade, we have combined the cross-family Instance Data Replication release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Vancouver to Yokohama.

Tip:

If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

Important information for upgrading Instance Data Replication to Yokohama

Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed.


Release	Release notes
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.
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.
Xanadu	No updates for this release.
Yokohama	Improve the performance and processing efficiency of Instance Data Replication (IDR) by upgrading your replication sets to V2, which uses Hermes Messaging Service. For details, see Upgrading legacy sets. 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.

New features

Between your current release family and Yokohama, new features were introduced for Instance Data Replication.


Release	Release notes
Vancouver	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.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	Scheduled seeding Replicate data from a producer to a consumer at scheduled times each day. Multiple seeding requests Run concurrent seeding requests across multiple replication sets, with up to one active request per set. Automatically seed missing or mismatched records Automatically seed missing or mismatched records when you create a data comparison request.

Changes

Between your current release family and Yokohama, some changes were made to existing Instance Data Replication features.


Release	Release notes
Vancouver	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.
Washington DC	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.
Xanadu	No updates for this release.
Yokohama	Seeding request improvements In V2 replication sets, the number of records in a seeding request is now unlimited. Data comparison improvements In V2 replication sets, the number of records in comparison or reseeding counts is now unlimited. Reseed missing attachments Attachments are now included in data comparison requests. Seeding performance improvements Seeding throughput and message queue efficiency has been optimized in IDR.

Removed

Between your current release family and Yokohama, some Instance Data Replication features or functionality were removed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Deprecations

Between your current release family and Yokohama, some Instance Data Replication features or functionality were deprecated.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	Legacy replication sets are planned for deprecation by the Zurich release. To continue replicating data in Zurich, you must upgrade all legacy replication sets to V2. For details on upgrading legacy replication sets to V2 before the upgrade, see Upgrading legacy sets.

Activation information

Review information on how to activate Instance Data Replication.


Release	Release notes
Vancouver	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.
Washington DC	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.
Xanadu	No updates for this release.
Yokohama	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

If any additional requirements were introduced or changed for Instance Data Replication we have noted them here.


Release	Release notes
Vancouver	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.
Washington DC	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.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Browser requirements

If any specific browser requirements were introduced or changed for Instance Data Replication we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Accessibility information

Review details on accessibility information for Instance Data Replication, such as specific requirements or compliance levels.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Localization information

If there are specific localization considerations for Instance Data Replication we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.
Xanadu	No updates for this release.
Yokohama	No updates for this release.

Highlight information

If there are specific highlight considerations for Instance Data Replication we have noted them here.


Release	Release notes
Vancouver	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.
Washington DC	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.
Xanadu	No updates for this release.
Yokohama	Replicate data that's frequently updated in large tables on your instance by scheduling data replication. Queue multiple seeding requests from your producer instance. Reseed missing or mismatched records automatically when creating a data comparison request. See Instance Data Replication for more information.