preserve data or exclude tables on clone

[yeskaytee]

Hello, i want to clone PROD over lower instance.
However i don't want to loose any data on ATF module and Agile module.
What is the best way to preserve data or exclude tables.

[Tony Chatfield1 · Accepted solution]

Hi, I believe you can identify tables that you want to save/exclude in your clone configuration; However I would be inclined to simply export XML for the tables I wanted to keep (or updatesets if you have used them) and then reload post clone. Another approach with updatesets is to close them out, import to prod but don't deploy, then deploy on your sub-prod instance post clone.

[Balaji Jagannat]

Hi, preserve would be a better option for your case and you will have to set it in your source/production instance. However, in ATF, if you are looking to preserve the test case or suites, the best practice is to promote all of them to production through an updateset before you clone the instance. Though you will not run your ATF in production. 

Additionally this blog has some good information on preserve vs exclude table scenario.

https://community.servicenow.com/community?id=community_question&sys_id=d8d4886adbb557002e247a9e0f96...

[Mark Roethof]

Hi there,

At least you need Clone Data Preservers. Multiple, because both ATF and Agile are made up out of multiple tables. Though I would think you also want to exclude some data being copied from prod to dev? So in that case also Clone Exclude Tables are needed.

So you actually need both for multiple tables. It's up to you which tables and which records specific ofcourse.

Don't know if you are already using this. Though when working with Clone Data Preservers, on share there's a nice feature available: "View Data to Preserve". This UI Action generates a list of the data you are going to preserve with the conditions set on the Data Preserver.

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

Kind regards,
Mark

---

LinkedIn
Community article list