Combined Instance Data Replication release notes for upgrades from Vancouver to Xanadu
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.
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.
| 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. |
New features
Between your current release family and Xanadu, new features were introduced for Instance Data Replication.
| Release | Release notes |
|---|---|
Vancouver |
|
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.
| Release | Release notes |
|---|---|
Vancouver |
|
Washington DC |
|
Xanadu |
No updates for this release. |
Removed
Between your current release family and Xanadu, 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. |
Deprecations
Between your current release family and Xanadu, 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. |
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. |
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. |
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. |
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. |
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. |
Highlight information
If there are specific highlight considerations for Instance Data Replication we have noted them here.
| Release | Release notes |
|---|---|
Vancouver |
See Instance Data Replication for more information. |
Washington DC |
See Instance Data Replication for more information. |
Xanadu |
No updates for this release. |