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:
- Back up lower environments: Make a backup of the current state of your lower environment in case something goes wrong during the cloning process.
- 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.
- Extract a backup of any remaining in-progress update sets.
- 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:
- 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.
- If required, disable email notifications on the target environment.
- Restore Notifications and Scheduled Jobs
- Restore developer roles.
- Perform a Final Functional Test.
Thank you
Chandan
