How to exclude cmdb data when cloning?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2017 11:40 AM
Hi,
Before we begin the process of an upgrade, we would like to clone our PROD instance to our DEV and I'm wondering if anyone knows how can we effectively exclude cmdb data from copying over. The last time we did this, we excluded "cmdb*" and we still ended up with data from PROD in DEV. I'm familiar with the Exclude Tables and Data Preservers but I'm not sure if I need to exclude all extended tables or the wildcard would work.
Appreciate your help!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2017 11:44 AM
I think you can exclude cmdb_ci table which is the master table and cmdb_rel_ci. That should be it.
Please mark this response as correct or helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2017 11:50 AM
Thanks for your reply Sanjiv. Have you ever had to do this and been successful?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2017 11:56 AM
I haven't done this. But I think it should work.
cmdb_ci is the master table. If there are table created with other names and extends cmdb_ci, it will consider those as well, when you exclude cmdb_ci table.
You should also exclude the relationships, which is stored in cmdb_rel_ci.
If you have some asset data, you should exclude them as well by excluding alm_asset table.
Please mark this response as correct or helpful if it assisted you with your question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2017 11:45 AM
You will have to include your CMDB extended tables in exclude tables.
http://wiki.servicenow.com/index.php?title=System_Clone#gsc.tab=0
Regards,
Sachin