Exclude and Preserve CMDB tables

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2019 08:27 AM
How everyone excluding and preserving the CMDB data during cloning. We don't want our PROD data to be copied to DEV also we don't want DEV data to be cleared after cloning by cleanup script.
For a note , the existing OOB preserve and exclude option is not working for CMDB tables
Regards,
Vivek

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2019 08:45 AM
We also faced similar issue and out CMDB size is huge.
We added custom solution to preserve CI and relationship data.
Here is summary of solution:
- We have Data pump integration with oracle instance to push daily CI and relationships records from service now to remote oracle instance
- We make sure that these we push only delta records during daily run to avoid any duplicate records.
- After clone, we run ODBC driver imports to import CI and relationship records from remote oracle instance DB to service now.
This works for us all our non - prod instance.
Regards,
Sachin

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2019 08:35 AM
Thanks but this is a hard way and in my opinion ServiceNow would provide some solution for their customers.
Also how did you handle user and role management during cloning. Currently I am cant preserve users with their appropriate roles.