--- sourceDocument: zurich Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/delta-vancouver-zurich Release : - yokohama ft:locale : - en-US ft:publication_title : - zurich Combined Product Files ft:clusterId : - delta3zv bundleId : - delta3zv --- Combined Instance Data Replication release notes for upgrades from Vancouver to Zurich ====================================================================================== Combined Instance Data Replication release notes for upgrades from Vancouver to Zurich {#ariaid-title1} ======================================================================================================= * Release version: Yokohama * * Updated January 30, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read Consolidated page of all release notes for Instance Data Replication from Vancouver to Zurich. 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 Zurich. 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 Zurich ----------------------------------------------------------------------- Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-instancedatareplication-summary__entry__2} | 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](https://www.servicenow.com/docs/access?context=upgrading-legacy-replication-sets-v2&family=vancouver&ft:locale=en-US). 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](https://support.servicenow.com/kb?sysparm_article=KB1364728&id=kb_article_view). 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](https://www.servicenow.com/docs/access?context=upgrading-legacy-replication-sets-v2&family=washingtondc&ft:locale=en-US). 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](https://www.servicenow.com/docs/access?context=upgrading-legacy-replication-sets-v2&family=yokohama&ft:locale=en-US). 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. | | Zurich | * 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](https://www.servicenow.com/docs/access?context=upgrading-legacy-replication-sets-v2&family=zurich&ft:locale=en-US). * 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 composed 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 Zurich, new features were introduced for Instance Data Replication. {#dfrn3-instancedatareplication-summary__entry__14} | Release | Release notes | |---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Vancouver | [Compare replicated data between instances](https://www.servicenow.com/docs/access?context=comparing-replicated-data&family=vancouver&ft:locale=en-US) : Find missing or mismatched records after replication by creating a data comparison request. [Prevent replication of large attachments](https://www.servicenow.com/docs/access?context=instance-data-replication-properties&family=vancouver&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=instance-data-replication-properties&family=vancouver&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=set-up-scheduled-replication-idr&family=yokohama&ft:locale=en-US) : Replicate data from a producer to a consumer at scheduled times each day. [Multiple seeding requests](https://www.servicenow.com/docs/access?context=seed-consumer-instance&family=yokohama&ft:locale=en-US) : Run concurrent seeding requests across multiple replication sets, with up to one active request per set. [Automatically seed missing or mismatched records](https://www.servicenow.com/docs/access?context=compare-replicated-data&family=yokohama&ft:locale=en-US) : Automatically seed missing or mismatched records when you create a data comparison request. | | Zurich | [Monitor scheduled replication sets](https://www.servicenow.com/docs/access?context=instance-data-replication-dashboard&family=zurich&ft:locale=en-US) : Monitor the progress your scheduled replication sets in the IDR Monitoring Dashboard. [Track scheduled replication requests](https://www.servicenow.com/docs/access?context=set-up-scheduled-replication-idr&family=zurich&ft:locale=en-US) : Track the progress of scheduled replication requests in the Scheduled Replication Requests related list. | [ ] Changes ------- Between your current release family and Zurich, some changes were made to existing Instance Data Replication features. {#dfrn3-instancedatareplication-summary__entry__26} | Release | Release notes | |---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Vancouver | [Upgrading legacy replication sets to V2 in Instance Data Replication](https://www.servicenow.com/docs/access?context=upgrading-legacy-replication-sets-v2&family=vancouver&ft:locale=en-US) : All legacy replication sets are now eligible for upgrade V2, including bidirectional and discrete replication sets. | | Washington DC | [Hermes-only replication](https://www.servicenow.com/docs/access?context=exploring-instance-data-replication&family=washingtondc&ft:locale=en-US) : Newly-created replication sets now use Hermes Messaging Service. You can no longer create legacy replication sets. [Comparing replicated data between instances](https://www.servicenow.com/docs/access?context=comparing-replicated-data&family=washingtondc&ft:locale=en-US) : Compare data in replication sets with data transformations, bidirectional replication, and discrete replication. | | Xanadu | No updates for this release. | | Yokohama | [Seeding request improvements](https://www.servicenow.com/docs/access?context=exploring-instance-data-replication&family=yokohama&ft:locale=en-US) : In V2 replication sets, the number of records in a seeding request is now unlimited. [Data comparison improvements](https://www.servicenow.com/docs/access?context=comparing-replicated-data&family=yokohama&ft:locale=en-US) : In V2 replication sets, the number of records in comparison or reseeding counts is now unlimited. [Reseed missing attachments](https://www.servicenow.com/docs/access?context=comparing-replicated-data&family=yokohama&ft:locale=en-US) : Attachments are now included in data comparison requests. [Seeding performance improvements](https://www.servicenow.com/docs/access?context=seed-consumer-instance&family=yokohama&ft:locale=en-US) : Seeding throughput and message queue efficiency has been optimized in IDR. | | Zurich | No updates for this release. | [ ] Removed ------- Between your current release family and Zurich, some Instance Data Replication features or functionality were removed. {#dfrn3-instancedatareplication-summary__entry__38} | 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. | | Zurich | * The Key Management Service test has been removed from the IDR Diagnostics page. * The VAULT Service Status test has been removed from the IDR Diagnostics page. | [ ] Deprecations ------------ Between your current release family and Zurich, some Instance Data Replication features or functionality were deprecated. {#dfrn3-instancedatareplication-summary__entry__50} | 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](https://www.servicenow.com/docs/access?context=upgrading-legacy-replication-sets-v2&family=yokohama&ft:locale=en-US). | | Zurich | Legacy replication sets have been deprecated in the Zurich release and are no longer supported. | [ ] Activation information ---------------------- Review information on how to activate Instance Data Replication. {#dfrn3-instancedatareplication-summary__entry__62} | 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](https://www.servicenow.com/docs/access?context=request-instance-data-replication&family=vancouver&ft:locale=en-US). | | 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](https://www.servicenow.com/docs/access?context=request-instance-data-replication&family=washingtondc&ft:locale=en-US). | | 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](https://www.servicenow.com/docs/access?context=request-instance-data-replication&family=yokohama&ft:locale=en-US). | | Zurich | 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 a subscription](https://www.servicenow.com/docs/access?context=request-instance-data-replication&family=zurich&ft:locale=en-US). | [ ] Additional requirements ----------------------- If any additional requirements were introduced or changed for Instance Data Replication we have noted them here. {#dfrn3-instancedatareplication-summary__entry__74} | 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. | | Zurich | 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. {#dfrn3-instancedatareplication-summary__entry__86} | 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. | | Zurich | No updates for this release. | [ ] Accessibility information ------------------------- Review details on accessibility information for Instance Data Replication, such as specific requirements or compliance levels. {#dfrn3-instancedatareplication-summary__entry__98} | 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. | | Zurich | : | [ ] Localization information ------------------------ If there are specific localization considerations for Instance Data Replication we have noted them here. {#dfrn3-instancedatareplication-summary__entry__110} | 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. | | Zurich | No updates for this release. | [ ] Highlight information --------------------- If there are specific highlight considerations for Instance Data Replication we have noted them here. {#dfrn3-instancedatareplication-summary__entry__122} | 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](https://www.servicenow.com/docs/access?context=instance-data-replication&family=vancouver&ft:locale=en-US) 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](https://www.servicenow.com/docs/access?context=instance-data-replication&family=washingtondc&ft:locale=en-US) 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](https://www.servicenow.com/docs/access?context=instance-data-replication&family=yokohama&ft:locale=en-US) for more information. | | Zurich | * Monitor the progress of all your scheduled replication sets. * Track the progress of scheduled replication requests within a scheduled replication set. * Access details of scheduled replication requests within a scheduled replication set. See [Instance Data Replication](https://www.servicenow.com/docs/access?context=instance-data-replication&family=zurich&ft:locale=en-US) for more information. | [ ]