Configure clone exclusion to avoid data loss #
When cloning into an instance where the Quality Clouds application is installed, it is important to avoid overwriting or deleting data which the application needs to work correctly.
The recommend configuration for the Quality Clouds application tables when preparing for a clone is as follows.
The above configuration will ensure that the clone target instance can be used o perform LiveChecks with minimal disruption. Depending on whether you are interested in keeping the LiveCheck history in the clone target instance, you may configure the clone process to keep the data in the LiveCheck tables as well, but note that references to configuration element versions stored in the issues and write-offs executed before the clone the clone will not be valid after the clone. This means that you will not be able to navigate to the Configuration Element versions from these records, which may create some confusion.
Any table not listed in the table above does not require a specific configuration, which means that the data in the clone target instance will be replaced by the data in the clone source instance.
Note: The above configuration assumes that the same version of the application is installed in the clone source as in the clone target instance.
