Clone terminology
A reference topic that contains various terms and definitions for cloning.
| Term | Description |
|---|---|
| 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. |
| 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. |
| 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. 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. |
Parent Topic:Instance Clone reference