CMDB exports

[Royal Sirrine]

I am looking at export sets and I am trying to understand the best way to export the CMDB using XML. I know that I can go into each class table and create a set to export, but I would like to know if I can export a table that will drop ALL CI's into one XML. I tried to create an export set at the Configuration Item table CMDB_CI, but the XML was only 96KB. Is there a way to do this to reduce the number of sets, and imports required? 

[Alexey7]

Exporting XML from the [cmdb_ci] table does work for me, try it one more time.

Tested in both Demo and PDI instances.

[Mary Vanatta]

I think the ability to export the entire CMDB would depend upon the number of CIs in your CMDB.  A PDI does not have many CIs. 

How many Ci's do you have?  
What is the need to export the whole CMDB? 

A CMDB would also need the cmdb_rel_ci table to be exported so that if putting in another instance the CI relationships are maintained. 

[Royal Sirrine]

There is just under 60k CI's. I have already tested the relationship export. That is one table so that was an easy export. I will test and try again. 

[DaveHertel · Accepted solution]

Hi - beware that depending on what starting class you export from at top of hierarchy... like cmdb_ci... will probably limit the attribute/fields that are exported to XML.  Since classes deeper in CMDB hierarchy add attributes, (i.e. windows servers), fields will probably be missing from the export.  Maybe this doesn't matter for your use case - but be informed.   An export from the root of the CMDB could provide base CI info and sysid, fundamental stuff, etc. but unlikely to provide details defined (added attributes) per class table.  i could be wrong - I haven't tried this - but I'd be sure to check your export results.

If a true, complete copy of every CI is required something beyond a simple XML export may be needed.

Hope this helps?