To effectively manage the instance cloning process, the Clone Admin console assists in defining clone profiles capturing what should be the preservers and exclusions during a clone process etc.,
The Clone Admin Console can be accessed by navigating to All -> Clone Admin Console -> Clone Home.
Note: Historical clone requests can be viewed from from the legacy clone feature by navigating to All -> Instance Clone -> Live Clones -> Clone History.
Clone Configurations page can be used to add clone instances or create clone profiles.
The Configurations Overview page displays the current no. of clone instances and clone profiles in your instance.
Clone Instances:
Displays all the available instances to clone, you can use instances added to this list as a clone source or clone target for your clones. To add non-production instance to your clone instances list, select "New".
Clone Profiles:
Clone profiles display all available profiles. Clone profiles are customizable templates for clones and can be saved and reused to achieve consistent outcomes with each of your clones. To learn more about Clone Profiles, see Create a custom clone profile. The Profile "system profile" is available by default and cannot be modified. The custom profiles can be used with the default exclusions, preservers and scripts from the system profile. All existing custom exclusions and preservers are automatically included when creating a custom profile.
To create a custom profile,
1. Navigate to All -> Clone Admin Console -> Home
2. Navigate to Configurations -> Clone Profiles
3. Select "New"
4. Fill in the new Clone Profile form, for more field related information, refer to Clone options.
Use clone definitions such as exclusions, preservers and cleanup scripts in your clone.
Exclusions, page lists the table that aren't copied during an instance clone. When excluding a table, the clone automation truncates the entire table including its child tables. The clone process removes data from both the parent and the child tables. However, the child tables aren't individually added to the list of excluded tables.
Preservers page displays a list of available data preservers, which are defined on the source instance. Preservers protect data on target instance from being overwritten. Unlike Exclusions, when preserving a table, the clone automation doesn't automatically preserve the child tables. Therefore, the child tables must be individually added to the preservers list.
Cleanup Scripts, page displays a list of your available scripts, which is automatically defined to execute after post-clone steps. Set an order number on each script to set the order that active scripts rung, with lower numbers having the highest priority. All cleanup scripts run in the global scope, irrespective of whichever scope you have configured before.
