Table of Contents

Importing elements, services, etc. from a .dmimport file

With .dmimport packages, you can not only import elements, but also services, service templates, views, redundancy groups, properties, protocols, documents, SLAs and Automation scripts. This way you can migrate entire structures from one DMS to another.

To import a .dmimport file:

  1. In the DataMiner Cube Surveyor, right-click the view where you want to import the package and select Actions > Import.

    Note
    • This option is also available from a card’s header menu.
    • If you do not have the Config permission for a particular view, export and import actions will not be available for this view.

  2. From DataMiner 9.6.3 onwards, in the Import window, select Import DataMiner package.

  3. In the Import window, click the Browse button.

  4. Browse to the file you wish to import and click Open.

  5. In the Options section of the Import window, if you do not want to include trend or alarm templates, Visio files, etc., clear the selection from the options in question.

  6. In the Structure to be imported section, clear the selection from any items you do not want to include in the import.

    Note

    If you have selected to include a redundancy group, any elements within that group will automatically be included in the import. Similarly, if you have selected an SLA, the SLA service and its service children will automatically be included.

  7. Click Import.

  8. If necessary, resolve any conflicts concerning names and/or IDs.

  9. In the Import window, check the progress messages until the import is ready, and click Finish.

Note
  • To import a package with a size of more than 1.2 GB, we recommend to use the 64-bit version of DataMiner Cube. See Installing & configuring the DataMiner Cube software.
  • If you import an element that uses a protocol version marked as Production, different options for the import will be available depending on whether the protocol version is more recent than the Production version used in the DMS:
    • If the imported version is more recent than the version marked as Production in the DMS, you will be able to select whether the imported protocol becomes marked as Production in the DMS or not.
    • If the imported version is less recent than the Production version in the DMS, you will be able to choose whether the element switches to the protocol version marked as Production in the DMS or not.
  • If you import a package that includes a custom information template that already exists in the DMS, you will be able to choose one of the following options:
    • Keep the existing information template in the DMS, and not import the information template from the package.
    • Overwrite the existing information template in the DMS.
    • Import the information template from the package with a new name.
Propose changes