2
Migration Planning and Using the Oracle Email Migration Tool

This chapter provides migration planning information.

This chapter contains these topics:

• Requirements Before Migration
• System Requirements
• Configuration Planning
• Using the Oracle Email Migration Tool

Requirements Before Migration

Before starting a migration, at least one instance of Oracle Collaboration Suite and Oracle Internet Directory must be installed on the target system.

System Requirements

The Migration Tool can be run on either the source system, an intermediate system, or the target system. This section describes the following system requirements for the machine on which the Migration Tool is running:

• Memory
• Disk Space
• Network Bandwidth
• Microsoft Requirements
• Intermediate Storage of Data During Migration

Memory

The minimum memory requirement is 512 megabytes (MB) of random access memory (RAM).

Disk Space

The disk space requirement is:

• 300 MB for migrating 10 users concurrently from MBOX, assuming a quota of 20 MB for each user (including all the intermediate store files)
• 70 MB for migrating from IMAP

  Note: The Microsoft Exchange plug-in has a feature called Statistics Task that you can use to estimate your disk space requirements if you are migrating from a Microsoft Exchange source e-mail system. This feature is available after you install the Migration Tool.

  See Also: "Using Statistics Task to Estimate Disk Space Requirements (Optional)" for information about using the Statistics Task feature

Network Bandwidth

The Migration Tool network bandwidth requirements are the same as those for IMAP4 clients, although, for high speed migrations, more bandwidth is required. Oracle Corporation recommends 100 megabits per second (Mbps).

Note: Migration runs well on a local area network (LAN) with at least 10 Mbps.

Microsoft Requirements

Microsoft Outlook 97, Microsoft Outlook 98, or Microsoft Outlook 2000, and Microsoft Exchange Administrator must be installed on the machine where you want to generate the various files (such as user list, MBOX, and shared folders) if migrating from Microsoft Exchange to Oracle Email.

The following Microsoft Exchange Server Services must be configured and set up properly:

• Microsoft Exchange Internet Mail Service
• Microsoft Exchange Information Store
• Microsoft Exchange System Attendant
• Microsoft Exchange Event Service
• Microsoft Exchange Directory Service

  Notes: If you are migrating from a Microsoft Exchange source e-mail system and running the Migration Tool on a machine other than the one upon which Microsoft Exchange is installed, ensure that Microsoft Outlook and Microsoft Exchange Administrator are installed on the machine from which you are running the Migration Tool. A user profile file cannot be generated from a machine where a Microsoft Exchange e-mail client is not installed.

Intermediate Storage of Data During Migration

During an MBOX based data migration, sufficient disk space must be available for intermediate storage to hold all of the e-mail of all the users being migrated together.

Note: The Migration Tool does not delete generated MBOX files.

See Also: Oracle Collaboration Suite Installation Guide for Oracle Email sizing guidelines

Configuration Planning

Configuration planning involves the following:

• Choosing the Migration Option
• Routing Reconfiguration Planning
• Supporting Different Character Sets

Choosing the Migration Option

Choose one of the following options for data migration:

• IMAP-based (IMAP to IMAP) migration for Microsoft Exchange 5.5 and Oracle eMail Server source e-mail systems
• MBOX-based (MBOX to IMAP) migration for Microsoft Exchange 5.0 source e-mail systems

  Note: MBOX based migration can also be used to migrate from Microsoft Exchange 5.5 source e-mail systems.

For each of these types of migrations, you can choose to retain your source system user names, or to have the Migration Tool generate new target user names on rules you create.

Routing Reconfiguration Planning

The mail system is always available to a user. Prior to migrating a user's data, the Migration Tool routes all of the user's new mail to Oracle Email. The user can still access old mail on the source account until data migration for the user is complete.

Once data migration is complete for a user, an e-mail notification is sent to the user's new account stating that migration is complete and that old and new e-mail can be accessed in the new Oracle Email account.

If you receive an Unable to start directory services error message from the Microsoft Exchange plug-in, the error is logged in the ..\log\msplugin_username@source_domain.log file.

If an error occurs during data migration, the user's e-mail continues to be routed to the user's new account. If the Migration Tool fails to route the user, the migration fails.

Supporting Different Character Sets

See the Oracle Collaboration Suite Administrator's Guide for information about configuring the Oracle Email database to support different character sets.

Using the Oracle Email Migration Tool

The Migration Tool has various menu bar selections and methods for viewing information about users, source domains, batches, and migration status.

Initially, all menu selections except Tools > Migration Setup are disabled. You must run the Migration Setup Wizard at least once for the directory tree on the left side of the screen to be populated and the menu selections to be available.

The Migration Setup Wizard stores migration parameters in the database every time you run the wizard. The Migration Setup Wizard picks up the prior settings from the database each time it is run.

See Also: "Task 3: Setting Up a Migration Session" for information about the Migration Setup Wizard

This section contains the following topics:

• Overview of the Oracle Email Migration Tool Screen
• Displaying User, Domain, Batch, and Migration Status Information
• User States During Migration
• Tuning for Performance
• Viewing Log Files

Overview of the Oracle Email Migration Tool Screen

This section contains an overview of the Migration Tool screen.

This section contains the following topics:

• Migration Tool Screen Menu Selections
• Migration Tool Screen Fields

Migration Tool Screen Menu Selections

Figure 2-1 shows the menu selections on the Migration Tool screen.

Figure 2-1 Migration Tool Screen Menu Selections

Text description of the illustration image4vt.gif

• File: The File menu has only the Exit selection, which shuts down the Migration Tool. Any ongoing migrations are canceled. No rollback or state saving is performed.
• Extract: The Extract menu selections generate the following files in the Migration Tool files directory (except where noted):
  • Users: The users.xml file

    Note: users.xml is not extracted into the files directory. If you are extracting a user-list file for a domain called oracle.com, the file is generated in the files/com/oracle directory.

  • Public aliases: The public_aliases.ldif file
  • Distribution lists: The distribution_lists.ldif file
  • Shared folders: The shared_folders.ldif file
  • User Profiles: The user_profiles.ldif file
• Batch: The Batch menu has only the Create selection, which displays a screen in which you enter the type of batch that you want to create.

  See Also: "Task 6: Batching" for more information about creating batches

• Migrate: The Migrate menu contains the following selections:
  • Create Users on Oracle: Starts the migration of user accounts to the target Oracle Email server
  • Migrate Shared Folders: Starts the migration of shared folders
  • Migrate Public Aliases: Starts the migration of public aliases
  • Migrate Distribution Lists: Starts the migration of distribution lists
  • Migrate User Data: Starts the migration of user data
  • Pre-Migrate User Data: Starts premigration of user data

    See Also: "Performing a Two-Phase Migration" for more information about pre-migrating user data

  • Migrate Address Book: Starts the migration of users' WebMail address books
  • Cancel Migration: Cancels data migration. No rollback is performed and migration is terminated immediately
• Tools: The Tools menu contains the following selections:
  • Migration Setup: Launches the Migration Setup Wizard. If the Migration Tool is being run for the first time or if you have cleared the migration parameters, this is the only menu selection enabled.
  • Load Users: Loads user information into the migration repository for later retrieval
  • Modify User Details: Displays a screen in which you enter the source user name for the user whose details you want to modify, and which contains fields for modifying the user's information

    Note: You can also select a user from the directory tree. Select the user and select Tools > Modify User Details to proceed with modifying the user's details.

  • Modify Migration Parameters: Displays a screen in which you can edit various migration parameters

    See Also: Figure 3-10, "Modify Migration Parameters Screen"

  • Clear Migration Parameters: Clears the migration parameters stored in the migration repository. The only menu option now enabled is Migration Setup to launch the Migration Setup Wizard.
  • Verify New Accounts: Displays the Verification screen and gives information about an individual user's migration status by comparing the source and target accounts

    See Also: "Verifying Migration" for more information about verification

• Help: The Help menu contains the following selections:
  • Contents: Displays the online help
  • About: Displays information about the release of the Migration Tool

Migration Tool Screen Fields

Figure 2-2 shows the right side of the Migration Tool screen when the Migration View node is selected.

Figure 2-2 Migration Tool Screen Fields

Text description of the illustration image4va.gif

• The number of users currently migrating is displayed at the top of the section
• Migrating Users: Displays the Domain, Batch, and User Name of users that are in a current state of migration
• User Details: Displays user details of a user selected from the User Name column of the Migrating Users field

  Note: When more than one Migration Tool instance runs against a single repository, each instance picks up users independently. The Migration View for a particular instance will show only the users that are being migrated by that instance in these two fields. Users listed in the directory tree might not be listed in the Migrating Users field. If you select a user from the directory tree and find that their status is Migrating, it means that the user is being migrated by another instance.

Displaying User, Domain, Batch, and Migration Status Information

You can display user, domain, batch, and migration status information using the Migration Tool screen. You can also edit the scheduled start time for migrating a batch using the Migration Tool screen.

This section contains the following topics:

• Viewing Domain, Batch, and User Information
• Displaying Source Domain Information and Migration Status
• Displaying Batch Information and Migration Status
• Displaying User Information and Status from the Directory Tree View

Viewing Domain, Batch, and User Information

You can expand the various nodes of the directory tree on the left side of the Migration Tool screen to display specific information.

• When you expand MigrationView, all the source domains display
• When you expand a domain, all the batches in the domain display
• When you expand a batch, all the users belonging to the batch display

Displaying Source Domain Information and Migration Status

All the domains on the source system you want to migrate are listed under MigrationView in the directory tree on the left side of the Migration Tool screen. To view the information and migration status for a particular source domain, as shown in Figure 2-3, select the source domain.

Figure 2-3 Migration Tool Screen with Source Domain Information Displayed

Text description of the illustration imageo9c.gif

The following information displays:

• Status (Pending, Migrating, Done, or Failed)
• Number of batches in the domain
• Number of users in the domain
• Scheduled start time of first batch
• Scheduled start time of last batch

Displaying Batch Information and Migration Status

To monitor batch information, expand a domain to view the batches in the domain. Select a batch name to view information and migration status, as shown in Figure 2-4.

Figure 2-4 Migration Tool Screen with Batch Information Displayed

Text description of the illustration imageq9d.gif

When you select a batch from the directory tree on the left side of the Migration Tool screen, the details for the selected batch display on the right side, showing the following information:

• Domain to which the batch belongs
• Status (Pending, Migrating, Done, or Failed)
• Number of Users in the batch
• Scheduled start time (you can edit the date and time field and click Schedule to save the changes)
• Users migrated (the percentage of users migrated)

  Note: If a single user in a batch fails to migrate, the entire batch is marked as Failed and must be rescheduled for migration. Users that migrated successfully are not migrated a second time.

  See Also: "Task 6: Batching" for more information about batches

Displaying User Information and Status from the Directory Tree View

To view all the users belonging to a particular batch, expand the batch. To view a specific user's information and migration status, as shown in Figure 2-5, click their user name.

Figure 2-5 Migration Tool Screen with User Information Displayed

Text description of the illustration imagem7a.gif

When you select a user from the directory tree on the left side of the Migration Tool screen, the details for the selected user display, showing the following information:

• Domain to which the user belongs
• Batch to which the user belongs
• Status (Pending, Migrating, Done, or Failed)
• Number of folders
• Migration start time
• Migration end time
• Folders migrated
• Total bytes written
• Folders migrated in % (the percentage of folders migrated)

  Note: If one folder fails to migrate, the user is marked as Failed and must be migrated again.

User States During Migration

A user is assigned one of the states shown in Table 2-1 during the data migration process.

Table 2-1 Migration States

State	Description
Pending	The user is yet to migrate
Migrating	The user is currently migrating
Done	The user was successfully migrated
Failed	The user's migration failed, for example, due to failure of routing or mail migration Failed users do not receive completion notifications

See Also: "Displaying User, Domain, Batch, and Migration Status Information" for information about viewing user states in the Migration Tool screen

Tuning for Performance

The read and write speeds are displayed at the bottom of the main Migration Tool screen. They indicate the performance of the Migration Tool.

You can increase or decrease the number of users migrating concurrently to optimize performance.

If you have two batches scheduled to migrate at times that overlap each other, the migration speed does not increase. The number of users that are migrated concurrently is a fixed number specified by an administrator in the Migration Setup Wizard.

See Also: "Step 2: Specifying Migration Options" to change the number of concurrently migrating users

Viewing Log Files

Log files are generated in the log directory of the Migration Tool. Every run of the Migration Tool generates a new log file that an administrator can open in any text editor to view the contents. Log files should be viewed frequently throughout the migration process.

The logs should be viewed after each of the following tasks to ensure successful migration:

• Extraction of accounts, shared folders, public aliases, and distribution lists

  Note: Any extraction failures of the Migration Tool are logged in the text.log file.

• Extraction of an MBOX file (Migration_default.log)

  Note: When you select MBOX based migration, MBOX files are generated by the plug-in. View the Migration_default.log file for failed users. If you find that a user has failed, view the msplugin_username@source_domain.log file to find the error message logged by the plug-in application.

• Migration of data, accounts, shared folders, public aliases, and distribution lists
• Routing a user