Best practices to take backup of update set

[shaik_irfan]

Hi,

I am building a custom app now client wants to clone the dev instance ,so there was a ask to take back up of update sets. My current scoped app is in default update set only so when i navigate to studio and open the scoped app in the related link i see the Publish to update set, i belive that will copy all the changes in the update set right ?

So is there any other best way to do ?

Once the instance is clone and i can upload the update set and i can continue the development right ?

[Mark Roethof]

Do be aware, of it concerns Orlando:

Please note that currently this will only work with Global update sets.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0827916

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

---

LinkedIn
Community article list

[Willem · Accepted solution]

Hi Shaik,

You are correct. Steps are:

- Transfer updates into an updateset other then Default.

- Complete update set.

- In related links you then have option to 'Export as XML'.

- After clone load the updateset and Commit.

- Do not reopen the update set. It is bad practice to reopen a closed update set.

Instead create a new update set and continue work from there. When you are done, both updatesets can be moved to another environment accordingly.

[Dlam]

Hi, can you please advise how to import the exported update set XML?

[Dlam]

Never mind, just found the guide how to import update set XML here: https://docs.delinea.com/online-help/integrations/servicenow/server-suite-servicenow/setup/manual-xm...