---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Clone terminology

# Clone terminology {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Key terms and definitions used in instance clone documentation and the Clone Admin Console.
{#clone-terminology__table_gkn_h2c_zfc__entry__2}

| Term | Description |
|-|-|
| Preflight Check | A stage in the clone process that verifies the source and target instances are in a healthy state before the clone proceeds. |
| Provision DBI | A stage in the clone process where a new target database instance (DBI) is set up to receive the restored data. |
| Source Instance | The original database where data is copied from. |
| Target Instance | The new location where the data is copied to. |
| Data Preservers | Specified data from the target instance that is retained on the target instance during the clone. Preservers are defined on the source instance. |
| Table Exclusions | Data that is not cloned to your target instance. |
| Client ID / OAuth | An authentication method used to preserve OAuth credentials on the target instance during a clone. The identity type for OAuth is human. The oauth_admin role is required to manage OAuth credentials preserved during a clone. |
| Cleanup Scripts | Automated steps that run after cloning, such as changing data or settings. |
| Clone Profiles | Reusable template for clone settings, exclusions, preservers, and scripts. |
| Multi-Instance View | A feature in the Clone Admin Console that enables administrators to monitor and manage clone operations across multiple linked instances from a single primary instance, without logging in to each instance separately. |
| Node Repoint | A stage in the clone process where the system switches traffic from the old target instance to the newly cloned instance. Node Repoint is a clone stage, not a clone state. |
| Clone Admin Console | The Clone Admin Console is the default user interface that enables you to manage and track the cloning process. |
| On-Demand Backup | With on-demand backup enabled, clone takes a fresh on-demand differential backup at the specified clone start time. Clone uses this backup during the restore phase of the clone. |
| Clone Chaining | You can divide your clone operation into 2 steps. 1. Cloning from production to your test (non-production) environment. 2. Cloning from test to all your other environments. {#clone-terminology__ol_uc4_zc1_dgc}You can save time if you're dealing with multiple instances and experience long clone durations. Using this strategy, you perform lengthy operations such as post-clone cleanup scripts or excluding Task data older than 90 days only once. The clones in step 2 have a lighter footprint and complete faster. |
[Table 1. Terminology]

{#clone-terminology__table_gkn_h2c_zfc}