Request a clone

Request a clone to copy data from a production instance to a non-production instance or to copy data between non-production instances.

Before you begin

Role required: clone_admin

Note:

Configure a clone profile. See Create a custom clone profile.

For self-hosted customer instances that use an Oracle database, see https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0563847.

About this task

The ServiceNow AI Platform uses data from the most recent, daily backup of the source instance when cloning. Backups that are used for cloning are a maximum of 36 hours old. The initial preparation begins, including selecting the latest backup to use, only at the date and time processing is scheduled to start.

Procedure

1. Navigate to All > Clone Admin Console > Request Clone.

2. On the form, fill in the fields.

<table id=“table_ujp_cdf_gxb”><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Source instance

</td><td>

The original database where data is copied from.

</td></tr><tr><td>

Target instance

</td><td>

The new location where the data is copied to.Note: You can add an instance or select an existing instance without leaving the page.

</td></tr><tr><td>

Clone Profile

</td><td>

Apply a clone profile that you created previously. All exclusions, preservers, and scripts you added to the profile are applied to the clone request.

If clone profile is left empty the system will pull in all available preservers, exclusions and cleanup scripts

Note: If default is checked on the clone profile, the clone request loads this profile every time you open the clone request page.

</td></tr><tr><td>

Lock settings at the time of clone request

</td><td>

If you use a clone profile, this option locks the settings and options at the time of the clone request. Any subsequent changes to the clone profile, regardless of when the clone runs, don’t affect the clone request.

</td></tr><tr><td>

Clone Scheduled Start time

</td><td>

The start time to begin cloning your instance. After you select a start time, the form displays the estimated duration and estimated completion time of the clone. See Schedule recurring clones.Note: You may schedule multiple clones to the same target instance as long as they are scheduled at least five days apart. If two clone requests for the same target fall within a five day window, the system will return an error to prevent overlap. If a time you need is unavailable, check for any scheduled maintenance, upgrades, or existing clone requests affecting the relevant instances.

</td></tr><tr><td>

• Email updates about this clone

• External email address

</td><td>

The email or emails to be notified of the clone process and clone completion.

</td></tr></tbody> </table>3. Select the hyperlinked number under each item in the definitions section to review your exclusions, preservers, and cleanup scripts.[Omitted image “clone-definitions-numbers.png”] Alt text: Clone definitions numbers.

1. Select the options to configure for your clone.

   Note: For information on all available options see Clone options. For information on general guidelines to expedite your clone request see General guidelines for optimizing your clone duration.

2. Select Continue.

3. Review your clone request summary.

   If other clone requests involve the same target instance within 30 days, they appear highlighted in yellow. Review these requests for potential conflicts before submitting.

   The Clone request summary page displays the estimated clone duration, based on the scheduled start time and the size of the data to be copied to the target instance. For a new source-target pair, the estimate may be higher than expected and becomes more accurate after additional clones between the same instances.

4. Select Confirm and Submit Clone Request.