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

1. Log in to the instance you want to clone.
   This instance becomes the source instance of the clone request.
2. Create a clone target record for each target instance you want to receive clone data.
3. Verify the list of tables excluded from cloning and add or remove tables to exclude from the target instance.
4. Verify the list of tables and system properties that you want saved on the target instance by data preservers. You can also create or modify data preservers, as needed.
   The legacy clone engine does not support data preservers for these records.

   • Tables that extend the Task table
   • Relationships
   • Hierarchies
   • Dot-walked queries

   If you are preserving any data not supported by the legacy clone engine, verify that there is a recent backup of the target instance available. If the clone-from-backup-process fails for any reason, you can restore the target instance from the backup.

5. Preserve any unpublished applications on the target instance.
6. Navigate to System Clone > Request Clone.
7. (Optional) Specify a predefined clone profile.
   A clone profile stores target and clone options. The clone profile automatically populates your clone request with your selected profile settings. See clone profiles for clone requests.
8. n the Target instance field, select the target instance that you want to receive the cloned data.
   Create a separate clone request for each target instance that you want to receive clone data.
9. In the Clone Scheduled Start Time field, select the time that you want the cloning to start.
   You can schedule multiple clone requests for the same source instance. For example, create one clone request to copy data to non-production instance A and another clone request to copy data to non-production instance B. The scheduling engine determines whether multiple clone requests against the same source instance can occur simultaneously or whether they must occur sequentially.
   The system verifies the scheduled start time and either accepts the date-time value that you selected or suggests an available date-time value. The validation process prevents scheduling conflicts with other automations using the same target instance.
10. In Email upon completion field, enter your email address so that you can receive alerts after the cloning finishes, is canceled, or has an error.
11. Click the Options arrowhead so it turns downward and use the following table to make appropriate selections in the Options pane.

    Table 1. Clone options

    Field	Description
    Exclude tables specified in Exclusion List	Prevents cloning records from the source instance specified in the System Clone > Exclude Tables module. Use this option to create empty but usable tables on the target instance. By default, the system excludes tables for auditing, license usage, logging, and notifications. This option is selected by default. Note: This option is not supported by the legacy clone engine.
    Exclude audit and log data	Prevents cloning audit and log records from the source instance. Use this option to create empty but usable audit and log tables on the target instance. This option is selected by default.
    Exclude large attachment data	Prevents the cloning of large attachments such as video files, image files, and other typically large binary file types. Use this option to exclude all common binary file types, regardless of file size. When selected, the clone also excludes attachments from the Attachments [sys_attachment] and Attachment Documents [sys_attachment_doc] tables that meet all these criteria. The attachment table_name value does not indicate that it is a small file. Small attachments have table name values that start with ZZ_. The attachment data type value indicates that it is a large file such as an application or video. The attachment table_name is not one of these system tables: sys_certificate, ecc_agent_jar, ecc_agent_mib, sys_store_app, or invisible.sys_store_app.
    Preserve theme	Preserves the theme and CSS elements on the target clone.
    Lock settings for this clone request	Option that locks the setting and options at the time of the clone request if you use a clone profile. Any subsequent changes to the clone profile, regardless of when the clone runs, do not effect the clone request.
    Amount of data copied from large tables	Clones the number of days of historical data to clone from large source tables, including task, pa_scores, and metric_instance. By default, the target instance receives the latest 90 days of historical data from the source instance.
    Preserve In Progress Update Sets	Preserves update sets during the clone process. This option eliminates the need to export in-progress, global update sets before you initiate a clone. The default is none. You can select the latest 90 days to preserve the in-progress update sets during this time. Note: Review and commit the update sets after the clone.
    Preserve users and related tables	Prevents users and user-related tables from being overwritten on the target clone.
    Clone frequency	Defines how often this target automatically receives clone data. For more information about scheduling cloning, see Schedule cloning.

12. Click Submit.
    If there are no issues with the clone request, the system displays the Authenticate Target modal.
    If your clone request preserves large tables, a warning message displays the large tables from your preserver list. You can cancel your clone request and remove the tables from your preserver list, or you can specify a reason and continue the clone request.
13. In the Username and Password fields, enter the username and password for an administrator account on the target instance and then click Authenticate.
14. Review the clone settings and click OK.
    An email is sent to the supplied address after the clone finishes, is canceled, or has an error.