List of preservers and exclusions tables for cloning
Summarize
Summary of List of preservers and exclusions tables for cloning
When installing Service Exchange in ServiceNow, it is crucial to manage certain tables carefully during cloning to maintain connectivity between instances. The default system clone profile does not preserve all necessary Service Exchange table data, so creating a custom clone profile is required. This custom profile ensures that specific tables are preserved or excluded appropriately to prevent data loss or connectivity issues after cloning.
Show less
Key Configuration Steps
- Create a custom clone profile via All > System Clone > Clone Profiles.
- Remove the Remote Process Sync Disable Records script from the Cleanup scripts list in the clone profile.
- Verify and update the clone profile’s Preservers and Exclusions lists to include the correct Service Exchange tables as specified.
- After cloning, manually reestablish connections and activate Capture Definitions on both provider and consumer instances.
Clone Behavior Based on Table Configuration
The behavior of tables during cloning depends on whether they are included in the Preservers and/or Exclusions lists:
| Preservers Table | Exclusions Table | Clone Result on Target Instance |
|---|---|---|
| Included | Included | Target keeps existing data; no records copied from source. |
| Included | Not included | Target keeps existing data and adds source records; no overwrites. |
| Not included | Included | Target table is emptied; no source records copied. |
| Not included | Not included | Target table replaced entirely with source data. |
Practical Examples
- snsbservicebridgesettings (in both lists): preserves existing target settings; source data does not overwrite.
- snsbconentitlement (Preservers only): target retains existing records and adds source records.
- snsberror (Exclusions only): target table is emptied after clone; no data copied from source.
- snfdsoffering (not in either list): target data fully replaced by source data.
Tables to Include in Custom Clone Profile
ServiceNow customers must ensure their custom clone profile includes the exact Service Exchange tables listed under the Preservers and Exclusions categories to maintain system integrity. These include key tables related to synchronization, service bridge settings, entitlement, error tracking, and data sync components for both providers and consumers.
Key Outcomes
- Maintains critical Service Exchange connectivity and configurations after cloning.
- Prevents accidental data loss or overwriting of important records on the target instance.
- Enables selective preservation or exclusion of tables based on business needs.
- Requires manual reestablishment of connections post-clone to fully restore integrations.
When installing Service Exchange, certain tables must be preserved or excluded to maintain connectivity after a clone.
- Remove the Remote Process Sync Disable Records script from the Cleanup scripts related list,
- Validate if the following Service Exchange tables are included in the custom profile.
Service Exchange tables to preserve and exclude
The following scenarios describe how clone operations affect table data based on table configuration in the preservers and the exclusions tables list.
| Preservers tables | Exclusions tables | Result on target instance |
|---|---|---|
| Included | Included | Target table retains existing data. The system preserves existing records and copies no records from the source. |
| Included | Not included | Target table retains existing records and receives additional records from the source table. The system does not overwrite existing records. |
| Not included | Included | Target table is empty after the clone. The system discards existing target records and copies no records from the source. |
| Not included | Not included | Target table contains only source table data. The system replaces all pre-existing target records with records from the source. |
Update the Clone Profile Preservers and Exclusions lists to include only the Service Exchange tables specified in the following preservers and exclusions tables. Add any missing tables from the specified lists and remove any Service Exchange tables that are not included in these lists.
| Preservers table | Exclusions table | |
|---|---|---|
| Global |
|
|
| Base |
|
|
| Provider |
|
|
| Consumer |
|
|
| Remote Process Sync Transport | sn_sb_rps_connection (Provider only) | sn_sb_rps_connection (Provider only) |
| Transporter |
|
N/a |
| Employee Profile |
|
sys_alias |
| Foundation Data Sync |
|
|
| Foundation Data Sync for Providers |
|
|
| Foundation Data Sync for Consumers |
|
|
| Health |
|
|
"*" - Applicable for both provider and consumer.
The following scenarios describe how clone operations affect table data based on table configuration in the Clone profile preservers list and the Exclude tables list.
The following examples use tables from this page to illustrate each scenario:
sn_sb_service_bridge_settings (included in both lists): The system preserves connection settings you configured on the target instance after the clone. Settings from the source instance do not overwrite them.
sn_sb_con_entitlement (included in Clone profile preservers only): The target instance retains existing entitlement records and receives additional entitlement records from the source instance.
sn_sb_error (included in Exclude tables only): The error records table is empty on the target instance after the clone. The system discards error records that existed on the target and copies none from the source.
sn_fds_offering (not included in either list): The system replaces the target table with source data. Records that existed on the target instance before the clone are replaced by source instance records.