ServiceNow Things to Know 44: Cloning Best Practices

[PrashantLearnIT]

When conducting any cloning activities, there are risks involved such as loss of data or loss of development work. To minimize the likelihood of this occurring, there are three main things to consider.

1. Clone Scheduling

• What is the agreed lead time?
• Is it regular?
• Is it known by everyone?
• Is there a Change management procedure

2. Communication

• Agree prior that each developer has to actively state they have completed their backup prior to clone commencement.
• Keep your email Out of box auto-reply set up.
• Put your upcoming leave in your email signature.
• Put an instance announcement on of upcoming clone.

3. Backup

• Not everything is in an update set.
• Whole instance backups (daily for 7 days + weekly for 2 weeks).
• Ideally, the person who created the update set should back it up.
• Standard update set update names.

If my content helped you in anyway, please mark this content as BOOKMARK, SUBSCRIBE & HELPFUL

Best Regards,

Prashant Kumar (LearnIT)

YouTube Channel LearnIT: https://www.youtube.com/@learnitwithprashant

Blog LearnIT: https://medium.com/@LearnITbyPrashant

Prashant Kumar LinkedIn: https://www.linkedin.com/in/learnitbyprashant/

ServiceNow Community Prashant Kumar - https://www.servicenow.com/community/user/viewprofilepage/user-id/19635