Preserve Data of User and Group tables at the time of cloning

[d-aizawa]

Hi.

I plan to clone the production instance for the upgrade.

So I don't want to overwrite the user group information of the production instance, so I plan to register the screenshot table in Exclude Tables and Preserve Data.

But, the official documentation says: Which should I trust, the Now Support Frequently Asked Questions or the official documentation?

https://docs.servicenow.com/bundle/quebec-platform-administration/page/administer/managing-data/conc...

Do not use data preservers to transfer large sets of data, such as user groups. If you must preserve table data, such as users, groups, and roles, consider exporting the records to a file and importing them after cloning.

Now Support

Thank you!

[Dipu Joy · Accepted solution]

Preserving Large dataset is always an issue during a clone. But this is more pertaining to task and cmdb tables.

We have customers who preserve these info without any issues. We had an OOB option which is currently disabled with other issues.

There is no set limit for these records as it depends on the size of the records.

sys_user* table numbers will be manageable and also it doesn't have any referenced attachments like task and the fields number of these table are not large as cmdb

The table with the most number of records will be on sys_user_has_role table; but with contextual security plugin enabled and these records have the inheritance count on the records, the count will not that huge.

So sys_user* table can be preserved and excluded during the clone without any issues.

Task and cmdb will work for some customer till it reach the limit and then the clone will fail and support will confirm you that because of the size, it didn't work and the you can remove them from exclusion/preserving.