Set up scheduled replication

Replicate data from a producer to a consumer at scheduled times each day in Instance Data Replication (IDR).

Before you begin

Verify that the producer and consumer instances belong to the same customer.

Plan your data replication strategy by reviewing the important considerations described in Preparing for Instance Data Replication.

Note:

You can only create one scheduled replication set, with only one outbound entry in that set.

Role required: idr_admin or admin

Procedure

1. On the producer instance, navigate to Instance Data Replication > Producer Replication Sets.
2. Select New.
3. Enter a name and description for the producer replication set.
   • The name can only contain alphanumeric characters and hyphens.
   • Avoid using a name that applies only to the producer instance. You must provide the same name in the consumer replication set, so the name shouldn't be producer-specific.
4. Schedule replication from your producer instance to one or more consumer instances.
   1. Select Scheduled.
   2. Select an interval in the Schedule Interval drop-down list.
   3. Select a date and time to begin scheduled replication.
   The schedule interval is added to the start date and time, and the resulting next run time is displayed in the Next Schedule Run field.
5. Optional: Create the producer replication set from a list of outbound entries by selecting Entry set.
   If you imported an update set from another instance or you created one earlier on your instance, you can choose an existing entry set.
6. Select Submit.
   The producer replication set is created with an auto-generated producer ID that identifies the producer instance in the system.
7. Specify the table and columns on the producer instance that you want to replicate.
   1. Select the Outbound Entries related list.
   2. Select New.
   3. On the form, fill in the fields.

      Table 1. Replication entry form

      Field	Description
      Source Table Name	Name of one of the tables on the producer instance to replicate. For example, SAN Disk [cmdb_ci_san_disk].
      Filter	Filter criteria to control the records in the table that the system is replicating. Use the filter to limit the number of records in your replication set. For example, if the table has an Active field, add a filter condition like [Active] [is] [True] to replicate only active records. If you want to replicate and preserve a parent and child table hierarchy, add a filter for the sys_class_name column to each outbound entry. This ensures that all of the child table columns are replicated, and not just the parent the columns. For example, to replicate both the Task [task] parent table and the Incident [incident] child table, you must add [Task type] [is] [Task] as a filter in the parent table entry and [Task type] [is] [Incident] as a filter in the child table entry. In this example, Task type is the label for the sys_class_name column on each table. For details, see Preserving table hierarchy in Instance Data Replication.
      Include Attachments	Option to replicate the files associated with the records that you are replicating.
      Included Fields	Fields to include. Move table fields into the Selected column to replicate them or into the Available column to prevent replicating them. Note: The system must replicate some fields, such as sys_id (Mandatory). The system cannot replicate some fields, such as Edge Encrypted and Password1. They do not appear in either column.
      Enable Custom Coalesce	Option to enable you to choose a field other than the default sys_id field to coalesce IDR.
      Coalesce Field	Choose a field to use to coalesce IDR. Only unique fields are available. See Custom coalescing. This field only displays if you select Enable Custom Coalesce.

      Note:

      If a table that you select has child tables, create one or more continuous replication sets and add outbound entries for each child table to maintain data integrity.
8. Select Submit.
9. Make the producer data available for replication to consumers by selecting Activate.
   The producer is ready to send the data that is specified in the replication set to one or more consumer instances.
10. On a consumer instance, navigate to Instance Data Replication > Consumer Replication Sets.
11. Select New.
12. On the form, fill in the fields.

    Table 2. Consumer Replication Set form

    Field	Description
    Producer Instance URL	URL of the producer instance. For example, https://<producer_instance>.servicenow.com.
    Producer Replication Set Name	Name of the consumer replication set. The name on the consumer must match the name on the producer. Obtain the name from the producer administrator.
    Description	Description of the purpose of the replication.

13. Select Submit.
    The list of all consumer replication sets appears. The system sends a request to the producer replication set administrator to approve or deny the request.

Result

Scheduled replication begins on the scheduled start date and time. Until then, continuous data replication occurs. After that point, replication occurs only at each scheduled interval.

What to do next

• Track the status of each scheduled run by viewing the Seeding Requests related list or by navigating to Instance Data Replication > Seeding Requests. If a scheduled run fails, you can try replicating records using a partial seeding request or a data comparison request that covers the failed date range. Otherwise, contact Customer Service and Support for assistance.
• Track seeding progress from the producer side by viewing the Run Duration and Percent Complete columns. Track seeding progress for the consumer portion by viewing the same details in the consumer replication set.
• View scheduled seeding runs in the IDR Data Comparison Requests related list. You can add the Request Received From column to the list to distinguish scheduled seeding requests from data comparison requests.

• Cancel scheduled replication
  Cancel scheduled replication by deactivating or deleting a producer replication set.