An instance copy replaces the contents of one instance with the configuration and data of another, for example to refresh a test instance with the latest data from production. This article explains what a copy includes, what it overwrites, and how to request one.
What an Instance Copy Does
An instance copy takes a source instance (usually production) and copies it over a target instance (usually test or UAT). The copy is a full replacement, not a merge.
A standard instance copy works as follows:
Copied from the source:
Configuration: objects, attributes, screens, modules, processes and all other solution design items.
Data: the records held in the source instance.
Emptied in the target:
Record versions and audit history
Process and file monitor executions, and their history
Email history (sent and received emails and attachments)
Files
Notifications
Report requests and generated report files
Kept in the target:
User roles and data security roles
Email accounts and recipients
Timers
Instance system settings (technical settings specific to the instance)
Copy Options
You can choose to copy some of the items that are emptied or kept in the target from the source as well. Every option replaces the target's configuration and data.
Option A: Standard copy (configuration and data) (default). Follows the lists above.
Option B: Standard copy plus user and security roles. As A, but user roles and data security roles are also copied from the source.
Option C: Standard copy plus roles, email accounts and timers. As B, but email accounts, email recipients and timers are also replaced with those from the source.
Option D: Full copy. As C, but audit history, email history, executions and files are also copied from the source.
After the copy, the outbound email service on the target is set to Suspended. See Enable or Disable the Email Service to re-enable it.
Configuration in the Target is Overwritten
Every copy option replaces the configuration in the target instance with the configuration from the source. Any configuration changes in the target that do not also exist in the source are lost when the copy runs, including work in progress in a test or UAT instance.
You cannot refresh only the data and leave the target's configuration unchanged.
Keep Your Test Instance Configuration
If your target instance contains configuration you need to keep, export it before the copy and re-import it afterwards:
1. In the target instance, run ENERGYSYS Export Config Since Date, using a date that covers all the changes you want to keep.
2. Save the exported file.
3. Request the instance copy (see below) and wait for confirmation that it has completed.
4. In the target instance, run ENERGYSYS Import Config Since Date Step 1 with the exported file.
5. Publish any imported Virtual Objects
6. Run ENERGYSYS Import Config Since Date Step 2.
7. Check that your configuration changes are present and working.
See Migrating Configuration Between Instances for how to import these processes if they are not already in your instance.
If you are unsure whether you have configuration to keep, mention this when you raise the request and we will discuss options before scheduling the copy.
Request an Instance Copy
Raise a support ticket or email support confirming the source and target instance, and which copy option you require - Option A, B, C or D. Include when you would like the instance copied.
Check Your Confirmation
Before the copy runs, support will send you a confirmation listing:
the source and target instances
the copy option selected
what will be overwritten in the target
the scheduled date and time
Please check it carefully. if anything is wrong, reply before the scheduled time and we will cancel or reschedule the copy.