Migrator for Notes to Exchange 4.16.1


	NOTE: Statistics reported by MNE are based on uncompressed data sizes provided by the Notes APIs. The APIs extract data in compressed form and provide the data to MNE in an uncompressed state. Data volumes reported by MNE are often higher than the values observed natively in Notes or transferred over the network to the migration servers.

The first five summaries in the list provide pre-migration assessments of your existing Notes infrastructure. These summaries derive their data from runs of the two Notes Discovery Wizards, followed by the Directory Export Wizard, and the Notes Data Locator Wizard (for the All Users and Resources collection):

•

User and resource details: A valuable information resource for migration planning, this summary lists all resources and user mailboxes eligible for migration and reports the number of items and size of the data store in Notes, identifying information such as department, location and server. Use this information to define collections of resources and mailboxes to be migrated together. Typically, collections contain users in the same department and location. The use of the data store size estimates permits you to create collections of appropriate sizes so they can be completed in your intended time frame.

•

Distribution list details: This summary shows the groups (distribution lists) defined in the Notes environment, which MNE can migrate to Exchange. Information such as owner, group type, Notes and Internet Address can help you collect similar groups together and have MNE provision them in the same Organizational Unit (OU) in Active Directory. Many administrators prefer this approach instead of placing an extremely large number of groups into the same OU container.

•

Internet domains: Sometimes, usually in large Notes installations, an additional Internet domain is configured on some servers. In cases such as mergers or acquisitions, the Notes infrastructure may support some domains that are unknown to the staff performing the migration. This summary documents domains that are currently configured on the Notes servers and identifies whether each domain is considered primary or secondary by Notes, so you can configure Internet domains for the Exchange environment.

•

Notes domains: Large Notes installations sometimes contain multiple Notes domains, some of which may be unknown to migration administrators—for example, in the case of a merger or acquisition. Administrators should carefully review this summary to ensure it includes all Notes domains. The Data Migration Wizard can migrate only the servers and domains listed in this summary. For additional domains not listed, use the NAB Discovery Wizard to add an appropriate Name and Address Book to the MNE configuration.

•

Datastore design classes: Notes permits the use of different design classes to support different types of data. Some examples include STDR6Mail for mail, and STDR6PersonalAddressBook for personal address books. Notes also supports the creation of custom design classes, either by creating a new one or making modifications to an existing design class. When migrating data, MNE uses the design classes to determine the types of data and how they should be mapped to Exchange. All default design classes are mapped. This report shows you all the different design classes in use in the data scanned by MNE. For each class, the summary indicates if it is mapped or not, and identifies a specific example of a data store using each design class. If your enterprise has customized data classes, review the unmapped data classes to determine if they contain standard data, such as messages and calendar data, and if they should be mapped for migration. If expected design classes are missing from the summary, you can add them to the database in the User Collection: Manage Design Classes screen of Notes Migration Manager.

Other summaries are migration status summaries that help you understand what is happening during a migration:

•

User migration status per collection: This summary reports, for each user or resource in the collection, the amount of data migrated and how many errors were encountered. Use this summary to identify mailboxes and resources that require cleanup, re-migration, or other attention. You can also use the data to calculate throughput and estimate the throughput of subsequent migrations. Adjusting the size of different collections based upon these numbers lets you optimize migration resources.

•

Distribution list provisioning: This summary shows which distribution lists have and have not been provisioned, and also documents any changes to previously migrated lists, so you can use Notes as the authoritative source for a list and periodically re-migrate the list.

•

Datastore status: This summary reports the migration status of specific user mailboxes or resource reservation databases. You can report on NSF files specific to a server, or select specific user mailboxes or resource reservation databases and determine if and when they were migrated, error counts, and how much data was migrated. You can filter results for runs with errors, and group migration runs by user and datastore.

From the pop-up display, you can:

•

Export to TSV: Export the displayed data to a TSV-format (tab-separated-values) data file.

•

Refresh Data: Regenerate the display, to include any new data from tasks currently running or recently concluded.

•

OK: Close the pop-up window.

If the summary pertains to a particular collection, you can use the Collections drop-down list to view the data associated with some other collection.

View Logs

This screen launches the Log Viewer to view the program log file associated with a particular task run. You can view the log of any task run by selecting it from the Task runs table and clicking View log file. You build the Task runs table by defining the filters for its contents. In most cases, a combination of task type and the collection to which the task was applied limits the run list to a manageable length.

Filter list:

•

Operation type: Use this drop-down list to specify a task whose runs you want to add to the Task runs table. You can filter the displayed list by collection.

•

Collections labeled as: A drop-down list that lets you filter the contents of the collection name list to show only collections associated with the specified label. Labels are a device for classifying and sorting collections. For more information, see the note under User Collections: Manage Users.

•

Collection name: Use this drop-down list to specify the collection to which the task was applied.

Task runs table:

•

View log file: Launches the Log Viewer for the selected task run.