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

1. Login 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 will be saved on the target instance by data preservers and create or modify data preservers as needed.
   The legacy clone engine does not support data preservers for these records.

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

   If you are preserving any data not supported by the legacy clone engine, verify there is a recent backup of the target instance available. Should the clone-from-backup-process fail 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. Select the Target instance to receive the cloned data.
   You must create a separate clone request for each target instance you want to receive clone data.
8. Complete the Options form section.

   Table 1. Clone options

   Field	Description
   Exclude tables specified in Exclusion List	Prevent 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. Excludes 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 it is a small file. Small attachments have table name values that start with ZZ_. The attachment data type value indicates it is a large file such as 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. This option is selected by default.
   Amount of data copied from the Task table	Select the amount of data to clone from the source instance Task table. By default, the target instance receives the last 90 days of Task table records from the source instance.
   Preserve theme	Enables data preservers for the target instance theme and CSS elements. This option is selected by default.

9. Select the Clone Scheduled Start Time.
   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 need to occur sequentially.
   The system verifies the scheduled start time and either accepts the date-time value 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, enter an address to receive alerts after the clone finishes, is canceled, or has an error.
11. Click Submit.
    The system displays an authentication window.
12. Enter the Username and Password for an administrator account on the target instance.
13. 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.