Backup of target instance before cloing

[d-aizawa]

Hi.

I've seen that it's better to back up the target instance before cloning.

But I don't really understand what to do when i hear that it is a backup of the target instance.

What I'm assuming at this point is a backup of the updateSet.

I'm assuming that it is a backup to spit out updateSet and Scheduled Job to XML and import it after cloning, but is there any difference in recognition?

Thank you!

[Mark Roethof · Accepted solution]

Hi there,

ServiceNow makes backups of your instance, so you don't need to create a backup yourself.

I suppose this is more about work in progress, like work done in Update Sets. Yes you would need to export these (or complete them and retrieve them on the higher instance which you are using as source for the clone).

When requesting a clone, there is also an option to preserve update sets. Though this only works for global update sets which are in progress. So not a real good option!

Maybe also specific data or specific changes which only apply to that instance (dev or test for example). In such cases, use the Clone Definitions for this. Create Preservers, Excludes, Cleanup Scripts.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark
2020-2022 ServiceNow Community MVP
2020-2022 ServiceNow Developer MVP

---

LinkedIn
Community article, blog, video list

[michaelalmond]

ServiceNow automatically backs up your instances.  You can check when these are taken in HI.

Instances, Instance Dashboard, Select <Instance Name>, Actions, List of backups of the instance, <Select time>, [Submit]

Regards, Michael