Cloning instances with AES

Learn how to protect the data, tables, and templates you've created in App Engine Studio when using System Clone to copy instances from production to non-production.

Preserving data and tables when cloning

The following are requirements for cloning instances with AES:

1. Ensure that all of your AES plugins are installed across all instances.
2. If you're cloning a production instance, verify that you've set up a data preserver on the target instances to preserve the Automated Test Framework (ATF) and Instance Scan properties. For more information about data preservers, see Data preservation on cloning target instances.
   Important:

   By default, the ATF system property is disabled to prevent you from accidentally running these tests on a production system. Running ATF on a production instance is neither recommended nor supported due to the potential for data corruption or outages.
3. If you're collecting development and deployment data, the App Engine Management Center (AEMC) plugin must be installed on all instances.

Cloning data and tables from a production instance over a non-production instance can overwrite data in your non-production tables. To ensure that data isn't lost in development environments, create a cloning strategy for collaboration.

1. The following tables have data preservation to ensure that the tables are correctly cloned between instances:
   Note:

   For the following tables, preservation is for global scope only.
   • Collaboration Descriptor tables:
     • App Collaboration Descriptors (sys_appcollab_descriptor)
     • App Collaboration Descriptor Permissions (sys_appcollab_permission_m2m)
   • Collaboration Users and Groups tables:
     • App Collaboration Users (sys_appcollab_user)
     • App Collaboration Groups (sys_appcollab_group)
   The data preservation ensures data is retained on the tables in the development instances.
2. The following tables have clone exclusions:
   • Collaboration Descriptor tables:
     • App Collaboration Descriptors (sys_appcollab_descriptor)
     • App Collaboration Descriptor Permissions (sys_appcollab_permission_m2m)
   • Collaboration Users and Groups tables:
     • App Collaboration Users (sys_appcollab_user)
     • App Collaboration Groups (sys_appcollab_group)
   Clone exclusions ensure data from production instances isn't copied to development instances.
3. If AES is the only application using the Credentials table, consider creating data preservers for Credential Alias, Basic Auth, and Discovery credentials. Otherwise, you must ensure that these tables aren't overwritten when the production instance is cloned to non-production instances.
4. The following users must be reassigned their roles after cloning:
   • Users in the AES Users group
   • Users in the AES User Limited group
   • Users who have the sn_app_eng_studio.user role in non-production instances
5. After cloning, a ReSync Collaborations Permissions post-clone clean-up script runs automatically, so any applications that were the same on production and development instances are automatically have collaborators synced. Developers can resume development on them immediately.
   Note:

   The cloned instance must have the collaboration plugin enabled.
6. If some applications were backed up prior to cloning and retrieved after cloning, you can use the Resync collaboration permissions related link on the sys_app record to reassign users and groups to their appropriate delegated development permissions.
7. If a collaboration descriptor is no longer associated with a user or group after cloning (in the event that development apps were wiped out during cloning as they were not in the source instance), select the Clean up records with empty references related link to remove the unreferenced user or group from the collaboration table. You should run this UI action after the cloning is done and all preserved applications have been retrieved (with Resync collaboration permissions already run on them).

The following tables have data preservation to ensure that the tables are correctly cloned between instances:

• Pipeline Instance
• Request Authorization Key
• Deployment Request
• Deployment Environment Request

Preserving app templates when cloning

Admins must protect custom templates from being overwritten during the cloning process. Without protection, templates created in AES (both from existing applications and from scratch) are in danger of disappearing during a clone.

When you create a template in AES, a scoped app is automatically generated on the Custom Applications [sys_app.list] table in your instance. Though they have different contents, template applications and standard custom applications are treated similarly on the ServiceNow AI Platform. So, preserving app templates during a system clone works the same way as preserving an application.

To protect app templates on your non-production instances, follow the process in Preserve applications and customizations in development during a system clone.

More information on cloning and data preservation

See the following topics for more information on cloning and data preservation:

• For more information on using the System Clone tool, see System clone.
• For more information on data preservation, see Data preservation on cloning target instances.
• For more details on cloning instances with AES, see the App Engine Studio System Administrator Guide on ServiceNow University.

Learn more about cloning instances with AES	Additional ServiceNow resources
ServiceNow provides several additional resources on cloning instances with App Engine Studio.	Cloning basics knowledge article
	Cloning instances tips and tricks knowledge article
	Extensive FAQ knowledge article on cloning instances
	App Engine Enterprise - Data Preservation During System Clone Whitepaper Note: You must log in to ServiceNow University to access this resource.