Issues after Cloning

[Linda_G]

Last night, we had a clone.  After the clone, nobody was able to login to our dev environment, not even with a local (non-ldap) account.

When I reached out to ServiceNow they said that the ldap_server_config was listed in the preservers table and not the excluders table.  I guess I don't fully understand  the reasoning here, if in the preservers, why would it be in the excluders as well?

And if it was only the Ldap issue, why couldn't I login with my local account?

ServiceNow had me role back the clone, but that didn't fix the problem, why wouldn't rolling back a clone fix this issue? Does rolling back a clone not put the environment back to the state it was in before it was cloned?

I've read up on a few of the forums about cloning and still don't quite understand, hence the questions above.  If someone would maybe try to help me understand this in simple terms, it would be much appreciated.

Thanks,

Linda

[Harish KM · Accepted solution]

Check the link below, they have mentioned with examples how preserve and exclude works together

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

[Linda_G]

This was helpful with the preserve and exclude, thank you.  The logging in issues were actually due to a certificate issue on the ServiceNow side.  

[Mahendra RC]

Hello Linda,

If you specify a table say(ldap_server_config) in excluded table list than the data for that table will be excluded and will not clone from your source (Prod) instance to target (non-prod) instance.

If you specify the same table (ldap_server_config) in preserver table list than the data for that table will be preserved on your target (non-prod) instance

So in your case you have not specified your table (ldap_server_config) in excluded table and only specified in preserver table list. Hence the data which was present in ldap_server_config table in your target (non-prod) instance was preserved and the data that was there in your source (prod) instance but were not present in your target (non-prod) instance was copied from your source (prod) instance to from your target (non-prod) instance.

refer KB Article for more details on this

Please mark my respsone as helpful/correct, if it answer your question.

Thanks