Important Considerations for Cloning Environments
This topic gives you important considerations for the Cloning Environment feature. To learn more, read:
Supported Cloning Scenarios
The following cloning scenarios are supported:
-
Migrating to another NetSuite EPM SKU
-
Production to test cloning
-
Test to production cloning
Unsupported Cloning Scenarios
The following scenarios for cloning aren't supported:
-
NetSuite Account Reconciliation and NetSuite Narrative Reporting don't support cloning one environment to another that's on an older monthly update.
-
Cloning might fail if NetSuite Planning and Budgeting has a renamed seeded period member that's been replaced by a custom period member. For example, if you renamed the seeded YearTotal period member to unused_YearTotal. Then, you added an alternate type period member with the original seeded member name (called YearTotal).
Cloning Uses Current Snapshot
The Clone Environment feature uses the latest snapshot (named Artifact Snapshot) created during the last daily maintenance.
After the snapshot that you'll use for cloning is created, don't make changes to your source application. Any changes you make to after the snapshot is created won't be included when you clone the environment.
If you need to change the source environment, you'll have to take a new snapshot with those updates and redo the cloning process. Before you clone the source environment again, you'll need to remove the application on the target environment using the Recreate Service feature. Click your user name in the upper-right corner, and from the Settings and Actions menu, select Recreate Service.
Compatibility Between Source and Target Environments
NetSuite Cloud EPM lets you clone from a source environment to a target environment if their monthly updates are within one month of each other. For example, if the source environment is on the 24.08 update, the target environment can be on 24.07, 24.08, or 24.09. The exception is NetSuite Account Reconciliation.
For NetSuite Account Reconciliation, you can only clone between environments that are on the exact same monthly update. For example, if the source environment is on the 24.08 update, the target environment must also be on 24.08.
Clone After Scheduled Daily Maintenance
You should start cloning after the scheduled daily maintenance for both the source and target environments. On the source environment, if the daily maintenance starts while cloning is happening, the cloning process will stop. On the target environment, the cloning process isn't affected even if daily maintenance starts at the start time. In that case, daily maintenance will run after cloning is done.
If cloning takes a long time, on the source environment, reschedule the start time for daily maintenance. This action prevents the cloning process from being stopped. For information about resetting the daily maintenance start time, see the following help topics in the Oracle Help Center:
If you want to start service maintenance manually instead of waiting for the scheduled time, use the runDailyMaintenance EPM Automate command. For more information, see the help topic runDailyMaintenance.
Cloning Options and Key Considerations
The following table lists your cloning options and the key considerations for each one.
Clone Options |
Considerations for Cloning |
---|---|
Users and Predefined Roles |
|
Data Management |
|
Application Audit |
For NetSuite Close Management and Consolidation and NetSuite Tax Reporting, data for Application Audit is included in the snapshot by default. This option isn't available in NetSuite Account Reconciliation. |
Job Console |
This option isn't available in NetSuite Account Reconciliation. |
Stored Snapshots and Files |
|
Daily Maintenance Start Time |
|
Target Account Reconciliation Settings Reset After Cloning
After cloning, the settings for the target NetSuite Account Reconciliation application will reset to their default values.
If you want to keep the target application's settings, follow these steps in order:
-
Export the settings from the source environment by using the exportARApplicationProperties EPM Automate command. See exportARApplicationProperties.
-
Clone the environment.
-
After cloning is done, import the application properties into the target environment by using the importARApplicationProperties EPM Automate command. See importARApplicationProperties.