{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":47423,"path":"servicenow-platform/instance-data-replication-idr/copying-replication-configuration.md","title":"Deploying a replication configuration from one instance to another in Instance Data Replication","bundle":null,"doc_type":null,"release":"australia","body":"\n# Deploying a replication configuration from one instance to another in Instance Data Replication\n\nCopy a replication configuration from one instance to another through an update set in Instance Data Replication \\(IDR\\).\n\nIn IDR, you can capture a snapshot of a replication configuration, including selected fields, filters, or data transformations using the **Track in Update Set** option, and then copy it to another instance using an update set.\n\n**Important:** The **Track in Update Set** option in IDR is the only supported method for capturing a replication configuration that you want to copy to another instance.\n\n## Key benefits\n\n-   Save time by defining a replication configuration once and using it as a template for new replication sets on other instances.\n-   Minimize potential impact to your production instance by developing a replication configuration in your sub-prod instance first.\n-   Verify a replication configuration in a sub-prod instance before rolling it out to a production instance.\n\n## Configuration entities\n\nThe following configuration entities are captured in an active update set when you select the **Track in Update Set** option.\n\n-   **Entry set**\n\n    An entry set is a bundle of replication entries \\(like a replication set\\), that doesn't contain any instance-specific metadata like the Producer ID. A new Producer ID is used in the target instance when you create a producer replication set based on an entry set.\n\n    Replication options that are tracked in an entry set and their status \\(active or inactive\\) include:\n\n    -   Bi-directional replication\n    -   Discrete value mapping\n-   **Replication entries**\n\n    A replication entry contains configuration settings for each table that you want to replicate. Replication entries are either outbound or inbound.\n\n    -   Outbound entries from a producer instance contain the source table, filter, fields you want to replicate, and data transformation settings.\n    -   Inbound entries from a consumer instance include the target table, the option to run business rules after replication, and data transformation settings.\n\n## Viewing an entry set and replication entries\n\nWhen you create a replication set, a new record is added to the Entry Sets \\[idr\\_entry\\_set\\] table. New records are added to the Replication Entries \\[idr\\_replication\\_entry\\] table for each outbound entry that you add to the replication set.\n\nAfter selecting **Track in Update Set**, you can view the entry set and its replication entries in the current update set by navigating to **All** > **System Update Sets** > **Local Update Sets**, selecting the update set, and then viewing the **Customer Updates** tab.\n\n-   **[Deploy a replication configuration through an update set in Instance Data Replication](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/instance-data-replication-idr/deploy-through-update-set.md)**  \nExport a replication configuration from one instance and import it on another instance through an update set in Instance Data Replication \\(IDR\\).\n\n**Parent Topic:**[Administering Instance Data Replication](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/instance-data-replication-idr/administering-instance-data-replication.md)\n\n**Related topics**  \n\n\n[Manage consumer access to replication data in Instance Data Replication]()\n\n[Comparing replicated data between instances in Instance Data Replication]()\n\n[Cloning options with Instance Data Replication]()\n\n[Monitoring replication status in Instance Data Replication]()\n\n[Monitoring queues in Instance Data Replication]()\n\n[Avoiding insert and update errors in Instance Data Replication]()\n\n[Resolving data replication errors in Instance Data Replication]()\n\n"}}