Clone / Upgrade / Update sets

[Kenny_vl]

I need some help in understanding what has happened here but let me first give you the scenario.

On the 13th of March, we cloned production to a sub-production target. Before this clone action, I removed all remote update sets with a state of “Previewed” from production and retrieved the update sets.

Sub-production was then upgraded on the 14th of March.

When I retrieve update sets on production today, I noticed that certain update sets (which were already committed before the clone) appear again with a state of “Previewed”.

At this point, it is only about ~10 update sets and I can do the verification manually but in the future this number will most likely be higher. This is why I am trying to understand the process here so that I can prevent this from happening again in the future.

Maybe it’s because it is Monday morning, but I can’t manage to wrap my head around this to understand completely and I would like to count on the community to help me out here. 🙏🏻

[OlaN]

Hi,

I'm guessing a bit here since I can't follow in all the steps... but,

I would think that the issue is that you removed some data in the production instance, and when doing the clone over to the sub-prod instance the process always uses the latest backup available.

So I'm guessing that the changes you made, didn't have time to make it into the backup.

[Kenny_vl]

Which steps can't you follow in ? Maybe I did not explain properly but it was clear in my head 🙂 

This is not going to be the case though. One of the update sets was already committed to production on the 6th of March. I'm hoping this was not the latest backup available 😄

[OlaN]

So I reread the question, and it became a bit more clear.. 😀

I believe the thing that's happened was that the update sets are marked as complete in the prod instance, and when cloning over that data to the sub-prod, the completed sets are in the clone, and therefore can be transferred again (from subprod to prod), as they now exist in the subprod as completed.

According to the docs, you should set completed update sets to ignore after the commit is done.

Personally I've worked with a little different approach, I've created a Table exclusion on the Clone so that the table Local update sets is always empty, on the target instance after the clone is completed.

[tiagomacul]

HI @Kenny_vl ,

ServiceNow clone will bring the last backup, not the current x ray from production instance

You can see on support what is your last backup.

Clone FAQs - Frequently Asked Questions

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715621

System clone

https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/managing-data/...

https://www.servicenow.com/community/br-brazil/como-solicitar-clone-de-ambiente/ta-p/2304200