Logging onto Target Instance after Cloning

[Renee-17]

If we clone Prod to Dev instance, will we then have to log onto the Dev instance with our userids and passwords that were used to logon to the Prod instance?

[Robbie · Accepted solution]

Hi @Renee-17,

Take a look at the following article from ServiceNow where they play through 6 different examples when configuring the Exclude and Preserve settings.

For the user (sys_user) table, as well as the below user related tables, I would configure the settings as follows:

- Table Exclusion: Yes (For each table)

- Data Preserver: Yes, plus Conditions field is empty. (For each table)

Additional user related tables to consider:

- sys_user
- sys_user_role
- sys_user_has_role
- sys_user_group
- sys_user_grmember
- sys_group_has_role
- sys_user_role_contains

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

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie

[Danish Bhairag2]

Hi @Renee-17 ,

This scenario will occur only when u have not excluded the user table from cloning from prod to dev and also ur instance is not SSO enabled.

In both the above case if it satisfies then yes u need to login using prod creds

Thanks,

Danish

[Renee-17]

Our instance is not SSO enabled, so if I "exclude" and "preserve" the user table during the clone process, then I should be able to login with the dev credentials... right? 

In trying to understand the documentation I read earlier, does exclude just truncate the data in the new database after all the data is copied from the source to the new database that will become the new target? 

And does the preserver copy data from the target and load the data back into the tables that were marked as preserver?

Are there any other tables that are recommended to be excluded outside of the default OOB Clone Excluded Tables list?

[Robbie · Accepted solution]

Hi @Renee-17,

Take a look at the following article from ServiceNow where they play through 6 different examples when configuring the Exclude and Preserve settings.

For the user (sys_user) table, as well as the below user related tables, I would configure the settings as follows:

- Table Exclusion: Yes (For each table)

- Data Preserver: Yes, plus Conditions field is empty. (For each table)

Additional user related tables to consider:

- sys_user
- sys_user_role
- sys_user_has_role
- sys_user_group
- sys_user_grmember
- sys_group_has_role
- sys_user_role_contains

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

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie

[Danish Bhairag2 · Accepted solution]

Hi @Renee-17 

Adding to Robbie's point also refer this article from servicenow

Inconsistent Data in tables User [ sys_user ] and Group[ sys_user_group] , Contacts [ customer_conta...

Thanks,

Danish