Interpreting warnings from the import report

When you import a file into Global Mailbox, the information can be validated. Warnings are issued for possible problems. You can take action to correct these problems before proceeding with the migration.

About this task

The importUtility script validates data elements within the import file. There are two options to do the data validation:
--validateAppUsers
Enables data validation for mailboxes and virtual roots, validating application users. (no value)
--validateEventData
Enables data validation for event rules, validating custom data. (no value)
For more information, see importUtility script.

Procedure

  1. Run the importUtility with an action of report, so that you can verify the contents of the import file without making changes to Global Mailbox.
  2. View the import report, --reportFileName or import.rpt.
    You might find the following error conditions are in the import report:
    • Mailbox/Event Rule/Virtual Root already exists and import mode was CREATEONLY
    • Attempt to import an ER that already exists with a different 'all mailboxes' value, and import mode is MERGE
    • Attempt to import an ER where none of the specified mailboxes exist
    • Attempt to import an ER or VR where the referenced application does not exist
    • Attempt to import a VR for a mailbox that does not exist
    • Attempt to import a VR for a user id that is not valid (only if --validateAppUsers is enabled)
    • Attempt to import an ER with custom data that is not valid (only if --validateEventData is enabled)
    • General system errors (such as, datastore [Cassandra] unavailable)
    You might find the following warning conditions in the import report:
    • A user permission was not added because the mailbox path is invalid
    • A user permission was not added because the application does not exist or the user ID is not valid for application (only occurs if --validateAppUsers is specified)
    • A mailbox was not associated with an imported event rule because the mailbox does not exist.
  3. Determine what must be changed to clear the items in the log.
    Some of the following changes might clear the items:
    • Change the options specified when you run the importUtility script.
    • Change the importSelectionFileName file to add or remove items in the list of the resource instances to be imported.
    • Determine that the listed item is what is intended, and is acceptable to retain.
    • If there are missing resources, such as a referenced mailbox does not exist, you might need to repeat the export step to generate another import file that contains the missing resource.
  4. After you make any necessary changes, run the importUtility script again.
  5. Continue this process until you are satisfied with the contents of the import report.
  6. Run the importUtility with an action of import to import the resources into the target system and enable them for use.