Purpose?

The purpose of this document is about ServiceNow Clone Process, Frequency, Pre-requisites and Checklist elements to be followed pre & post clone.

Clone Process

System Clone process is to copy everything in a database from one environment to another. Cloning typically used to copy a production environment to a pre-production environment to test changes. In addition, it would be ideal to ensure you have a like-for-like setup between Non-Production and Production so that there are no "missing links" in the items being developed as well as new developments.

Cloning data comes from the most recent, nightly backup.

Frequency?

• This is going to vary from organization to organization. It really depends how often you want to refresh the data in sub-prod environments. That is the big benefit of doing a clone.
• Some people do this once a year, some quarterly, some more often. It’s based on project requirements, development/release cycle, and other parameters (Ex. before any major development efforts).
• Therefore you would want to have frequent refreshes of the development environments, but not too frequent where this should not be a hindrance for your developers.

Frequency: Every quarter for each environment (Recommended in General Scenario)

Order of Environments to be cloned: ACC/UAT, TEST, DEV

How to Do?

Please refer to the below step-by-step procedure to perform a system clone for a service-now environment.

Prior to Request a Clone, remember the below important points before raising a clone request.

1. Lead time to raise/schedule a request – At least 4 hours.
2. At-most backup - 36 hours old. (however latest back up will be picked by clone engine)
3. Cancel a clone – Any time while clone is in progress.
   
   1. System Clone > Active Clone > Open the record > Click ‘Cancel Clone’ related link.(link will be visible until the clone is in-progress).
4. Maximum time for a roll back of clone – within 24 hours reach HI team.
5. Inform to all the developers to take back up of their work.

Terminology

Source Environment – Source for copy

Target Environment – Destination for overwritten

Intended Audience

­­­­­­ Service-now administrators.

Pre-Clone Checklist

On Source Environment

Note: If you want to retain your target instance table data AS IS, please ensure to mention your table in both Preserver and Exclusion list of source instance. For more details, please refer to the KB article Clone results based on Exclusion and Preserver configuration

On Target Environment

Please take the back up (Excel & xml as applicable) for below check items to validate the target environment configurations would not override.

1. Pending Update Sets.
2. Active Plugins. (In Application Navigator, v_plugin.LIST)
3. Active Schedule Jobs.
4. System Properties (Environment Specific).
5. MID Server configurations.
6. (Optional) SSO Configurations. (Environment Specific)
7. (Optional) Integration end-points and environment specific parameters.
8. (Optional) Important table records. Ex. Group Members, User Roles and Group Roles.
9. (Optional) Data source.

Raise a Clone Request

1. Login into Source Environment.
2. Go to System Clone > Request Clone
3. Fill the mandatory fields’ information (Note: Start time is at least with 4 hours lead-time).
4. Review and understand the available “Options” on request form.
5. Select the applicable “Options” with right value. Note: The check box label "Exclude audit and log data" is misleading. It actually means if this is ticked it will honour the exclude tables module, if it is unticked then the exclude tables module will not be honoured.
6. Clikc Submit.
7. In the Usernameand Password fields, enter the username and password for an administrator account on the target environment and then click Authenticate.
8. Review the clone settings and click

Post-Clone Checklist

After clone, please verify the below elements on Target environment,

1. System Properties
2. Welcome Page
3. System Definition > Scheduled Jobs
4. System LDAP
5. User Accounts
6. Glide List (Prevent emails being sent out to non-testers in a non-prod environment)
7. Data Clean-up (to prevent notifications from non-prod systems)
8. SSO Hash Key
9. (Optional) Data Cleanout Checklist

Refer to the attached document (Post_Clone_Check_List.pdf) for step-by-step procedure for the above checklist elements.

1. Finally verify the Pre-Clone Check List elements.
2. Sanity check of the system – Run the ATF Test Suites.

References

Regards,

Vijay Talupula