Pre Clone activities

[Nag89]

Hi Everyone,

I need help in pre cloning activities to check. what to exclude as part of cloning and post cloning checklist.

I'd be grateful if someone helps

[SANDEEP DUTTA]

Hi @Nag89 ,

Please refer to these Articles :

https://www.servicenow.com/community/developer-articles/servicenow-system-clone-process/ta-p/2322006

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0547597

[SD_Chandan]

Hi @Nag89 ,

Please Refer :
Pre Requisite before cloning

ServiceNow KB: Post-Cloning Checklist (KB0547597)

Post-Cloning Checklist - ServiceNow Wiki

Post-Clone Checklist, anyone?

How to preserve local user roles while cloning from another instance?

If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

[SD_Chandan · Accepted solution]

Hi @Nag89 ,

Refer this article for all plan :-
https://www.servicenow.com/community/servicenow-ai-platform-blog/using-a-cloning-plan-to-ensure-succ... 

Pre-Clone Checklist

A documented pre-clone checklist enables administrators to share tasks while ensuring a consistent process. Your pre-clone checklist may include the following items:

1. Back up lower environments: Make a backup of the current state of your lower environment in case something goes wrong during the cloning process.
2. Disable scheduled jobs and integrations: Turn off any integrations or scheduled jobs in the lower environment to avoid unintended data processing or API calls during the clone.
3. Extract a backup of any remaining in-progress update sets.
4. Verify that a backup of production has taken place since the last deployment to production. Use a scheduled backup if needed.
   
   

Post Clone Checklist

Similar to the pre-clone checklist, the post-clone checklist will be organization-specific; however, common items may include:

1. Conduct post-clone validation to verify that key data has been cloned as expected.
   • Data integrity: Confirm that important records (like Incidents, Problems, and Change Requests) have populated correctly and align with production.
   • Sensitive Data:  Confirm that excluded sensitive data has not been inadvertently copied.
   • Configurations and scripts: Check that customizations, scripts, and configurations needed for testing are intact.
   • System properties and integrations: Ensure system properties are appropriate for lower environments, especially if they differ from production. Re-enable integrations and scheduled jobs as needed.
2. If required, disable email notifications on the target environment.
3. Restore Notifications and Scheduled Jobs
4. Restore developer roles.
5. Perform a Final Functional Test.
   
   

[Dr Atul G- LNG]

Hi @Nag89 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0547597

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0657100

https://downloads.docs.servicenow.com/enus/paris/upgrade/servicenow-upgrade-planning-checklist.pdf

https://youtu.be/cvvkovcCc4I