--- sourceDocument: xanadu Combined Product Files sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/delta-vancouver-xanadu Release : - yokohama ft:locale : - en-US ft:publication_title : - xanadu Combined Product Files ft:clusterId : - delta3xv bundleId : - delta3xv --- Combined Instance Data Replication release notes for upgrades from Vancouver to Xanadu ====================================================================================== Combined Instance Data Replication release notes for upgrades from Vancouver to Xanadu {#ariaid-title1} ======================================================================================================= * Release version: Yokohama * * Updated January 30, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Consolidated page of all release notes for Instance Data Replication from Vancouver to Xanadu. 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 Xanadu. 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 Xanadu ----------------------------------------------------------------------- Before you upgrade to Xanadu, 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. | [ ] New features ------------ Between your current release family and Xanadu, new features were introduced for Instance Data Replication. {#dfrn3-instancedatareplication-summary__entry__10} | 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. | [ ] Changes ------- Between your current release family and Xanadu, some changes were made to existing Instance Data Replication features. {#dfrn3-instancedatareplication-summary__entry__18} | 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. | [ ] Removed ------- Between your current release family and Xanadu, some Instance Data Replication features or functionality were removed. {#dfrn3-instancedatareplication-summary__entry__26} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Deprecations ------------ Between your current release family and Xanadu, some Instance Data Replication features or functionality were deprecated. {#dfrn3-instancedatareplication-summary__entry__34} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Activation information ---------------------- Review information on how to activate Instance Data Replication. {#dfrn3-instancedatareplication-summary__entry__42} | 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. | [ ] Additional requirements ----------------------- If any additional requirements were introduced or changed for Instance Data Replication we have noted them here. {#dfrn3-instancedatareplication-summary__entry__50} | 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. | [ ] Browser requirements -------------------- If any specific browser requirements were introduced or changed for Instance Data Replication we have noted them here. {#dfrn3-instancedatareplication-summary__entry__58} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | 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__66} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | No updates for this release. | [ ] Localization information ------------------------ If there are specific localization considerations for Instance Data Replication we have noted them here. {#dfrn3-instancedatareplication-summary__entry__74} | Release | Release notes | |---------------|------------------------------| | Vancouver | No updates for this release. | | Washington DC | No updates for this release. | | Xanadu | 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__82} | 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. | [ ]