Missing Data in Scoped Tables after Clone

[Nick149]

Yesterday, we cloned our PROD environment down to our QA and DEV environments. After the clone completed, I noticed that many tables in our scoped applications were missing their records/data.

We had a few scoped applications that were in the middle of development. Since I have them all linked to source control, I committed local changes to source control, cloned, then applied the remote changes. Afterward, all configuration changes were correctly restored, but many tables were missing their data.

The part that confuses me is that all of these tables have data in them in both PROD and QA, but they are empty in DEV. These tables in DEV had data in them from before the clone, so I don't see why applying remote changes would remove the data. Furthermore, the primary tables that the fulfillers use to do their work managed to retain the records from PROD (the source instance) but all of the other tables we built - for support & relational purposes - are now empty.

We are in the process of exporting the record data from PROD and importing to DEV, so it's not like we've permanently lost data but it does essentially break the applications until we restore the data, as this is necessary information.

Any idea as to why these records are missing in our DEV environment?

[User658787]

How were your data preservation rules set up in prod?

https://docs.servicenow.com/bundle/london-platform-administration/page/administer/managing-data/concept/data-preservation.html

 Also note: If a clone from backup fails for any reason, the system instead uses the legacy clone engine. The legacy clone engine cannot preserve data from extended tables, relationships, hierarchies between tables, and dot-walked queries. You may want to restore the target instance from a backup and then reschedule the clone in such cases.  

[Nick149]

I did not have any of these table defined in the data preservers. Even so, PROD was the source instance for the clone over QA and DEV, yet the data exists in QA so I'm not completely convinced that it's a data preservation issue.

As for the clone from a backup failing - I did not receive any errors that the initial clone failed. Furthermore, most of these tables are not extended from another table.

[Tanner6]

Hey Nick,

I am by no means technical but what you are describing is something that we help our customers with.

Here is some more information about us: InstanceSync

Also feel free to email me directly at: Tanner.torres@perspectium.com