Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Set up system clone

Log in to subscribe to topics and get notified when content changes.

Set up system clone

You can perform optional, pre-cloning tasks before you request a clone. For example, you can control the exclusion of certain tables from cloning and preserve data on the clone target instance.

Create a clone target

You create a target instance record before the instance can be selected as clone target.

Before you begin

Role required: clone_admin or admin

About this task

Note: If you are using IP Access Controls on your instance, the target instance must allow the IP range to communicate on a local network to allow the clone. For more information, see IP range based authentication.


  1. Navigate to System Clone > Clone Targets.
  2. Click New.
  3. Enter the URL for the receiving instance (target).
  4. Enter the basic authentication credentials for a user account with the admin role on the target instance.
    Clone target
    Note: These credentials must exist in the User [sys_user] table as a user record or as part of an LDAP integration. Clone requests cannot use single sign-on to authenticate users from an identity provider.
  5. Click Submit.
    The system checks connectivity and validates the user credentials against the target instance.

Exclude a table from cloning

Exclude a table to create an empty but usable table on the target instance.

About this task

The System Clone > Exclude Tables module lists the tables that are not copied during a system clone. By default, the system excludes tables for logging, auditing, notifications, workflow contexts, and license usage.

Note: Excluded workflow context data includes records stored in the wf_context table, and in related tables with names starting with a prefix of wf_. This also includes the workflow scheduler table. This prevents occurrence of workflow timer syncing issues that might take place due to the length of the cloning process if workflow contexts were included.

The system cannot exclude tables that extend the Task table and are also flattened into it as part of the table per hierarchy extension model. Since these extended tables are actually part of the same physical database table, the system clones the data when it clones the Task table. You can exclude tables that extend the Task table under two conditions. Either the system stores the tables in their own physical tables as part of the table per class extension model, or you exclude the Task table itself.

To preserve the existing data on the target instance, see Create a data preserver. Data on tables that reference the table, such as business rules, is not excluded.


  1. Navigate to System Clone > Exclude Tables.
  2. Click New.
  3. Enter the table Name.
  4. Click Submit.