Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal CMDB11.0

Use > Configuration Manager > Appendixes > Importing and Exporting System Data > Importing and Exporting System Data Overview

Importing and Exporting System Data Overview

You can import and export Configuration Manager data using the JMX console. You might perform these operations, for example, if you want to move the system data from a staging to a production environment, or during recovery following a system crash.

The exported data includes the following resources:

The list of views managed by Configuration Manager and the managed CI types defined for each view in the Views module. The TQLs which the views reference are not exported.
The configuration policy setting defined in the Policies module. The TQLs that are referenced are not exported.
The saved configuration analysis results in the Configuration Analysis module, including the saved model and the composite CIs. The actual CI information for the composite CIs, for example its attributes, are not exported.

The export operation migrates the data and stores it in the file system of the machine on which Configuration Manager is running. You can also provide a network path and store the exported data on a different server. The data is exported as an XML file.

You can import the XML file containing the system data from Configuration Manager's file system to another Configuration Manager system of the same version. You can also provide a network path to import the exported data from a different server.

Caution

When importing system data from one Configuration Manager system to another, you must ensure that the Configuration Manager version is the same or compatible.

Before migrating data between two Configuration Manager instances, which means that each Configuration Manager instance is connected to a different Universal CMDB instance, you must first export the relevant TQLs and views from one Universal CMDB instance to the other.

If you applied a baseline policy, you need to export the TQL selected in the Advanced Filter box in the Policies module.

If you applied a topology policy, you need to export the Condition TQL in the Condition TQL box and the TQL selected in the Advanced Filter box in the Policies module.

To export the referenced TQLs, use the Package Manager in Universal CMDB. For details, see the Universal CMDB Administration Guide.

Log File for the Import Operations

During each import operation, an amber_import_export.log file is generated to the <Configuration_Manager_installation_directory>\servers\<Configuration Manager server extension name>\logs directory.

All import actions are written to amber_import_export.log, including error messages and the reason for the error. For example,

Managing view 'View1'
- View 'View1' already exists
- View 'View1' was created
- View 'View1' was not created: reason...
Adding configuration analysis (adhoc) model 'Model1'
- Configuration analysis (adhoc) model 'Model1' was created
- Configuration analysis (adhoc) model 'Model1' already exists
Adding policy rule 'Rule1'
- Policy rule 'Rule1' was created
- Policy rule 'Rule1' already exists
- Policy rule 'Rule1' was not created: reason...

For information on how to set the message severity levels of the log file, see Set Log Verbosity Levels.

Send Help Center feedback