Migrate allows data transfer from EMC SourceOne systems using direct connection rather than API.
Currently we only support Microsoft Exchange data and support only NTFS or Disk-based Containers.
Database Tab
The Database tab is where you provide information related to the SourceOne SQL database (Figure 72):
Figure 72: SourceOne Source Database Tab
1. Sql Server. Specify the name or IP address of the SQL Server hosting the database.
2. Database Name. Provide the name of the database on the specified SQL Server mentioned above.
3. SQL User Name. Provide a SQL username that is used for SQL Authentication.
4. SQL User Password. Fill in the field with the password used for SQL Authentication.
5. Is Trusted. When you check the box, you indicate that the trusted/windows authentication connection is used to connect to the database. By checking this box, the SQL User Name and the SQL User Password will be ignored.
6. When you fill in all the information, click the Test Connection button to see whether the credentials provided are valid.
7. By clicking Save the configurations will be saved.
Storage Tab
Figure 73: SourceOne Source Storage Tab
1. Storage File Path. Provide the file path for the shared storage. The Storage File Path is the path the Processor Node(s) will use to access the files. In case of multiple processors use the shared path to make sure all processors to find the EMC EmailXtender containers at the same path.
2. Storage Username and Storage Password. For Migrate to access the storage you will have to provide the username and password. The Node Service Account must have access to this location and should be the same account listed here.
3. To make sure that the information input in the fields is correct and Migrate can access the storage click the Test Access button.
4. By clicking Save the configurations will be saved.
AutoTune Tab
The AutoTune tab is designed to speed up lengthy migrations by optimizing their use of system resources through adding and removing worker threads or adjusting buffer sizes (Figure 74).
Figure 74: SourceOne Source AutoTune Tab
1. Hosts. Here you should input the server name (in case there is more than one name, separate them with comma) where AutoTune will monitor CPU performance and Disk queue.
2. Monitor Host. To monitor the servers specified in Hosts option by AutoTune component, check the box.
3. By clicking Save the configurations will be saved.
If an archive selected for migration is a Journal Archive (“Virtual Consolidated Journal” archive) than all items from it is migrated to the “Inbox” folder of the target.
For more details on AutoTune, view the AutoTune Manager section.
EV Source
EV Source is configured by connecting to the SQL database connected to the EV and Veritas Enterprise Vault API Runtime 12.4. It also works with EV API Runtime version 11. The SQL database account used to authenticate the connection should have at least read and write permission and delete permission if Advanced Validation is used. Currently, Migrate supports only Microsoft Exchange data (MSG, EML) and NTFS or Disk-based Containers (PST).
Database Tab
The Database tab is where you provide information related to the EV SQL database. The user, whose credentials are provided, should have Read and Write permissions on the database, and Delete permission if Advanced Validation is used (Figure 75).
Figure 75: EV Source Database Tab
1. Sql Server. Specify the name or IP address of the SQL Server hosting the database.
2. Database Name. Provide the name of the database on the specified SQL Server mentioned above.
3. SQL User Name. Provide a SQL username that is used for SQL Authentication.
4. SQL User Password. Fill in the field with the password used for SQL Authentication.
5. Is Trusted. When you check the box, you indicate that the trusted/windows authentication connection is used to connect to the database. By checking this box, the SQL User Name and the SQL User Password will be ignored.
6. When you fill in all the information, click the Test Connection button to see whether the credentials provided are valid.
7. By clicking Save the configurations will be saved.
API Tab
In the API tab the EV API endpoint name field should be filled to connect to the EV (Figure 76).
Figure 76: EV Source API Tab
1. EV API endpoint name. Specify the EV API endpoint name. Very often this is the EV Site name. In the case of an EV to EV migration, make sure this is the EV Source API endpoint name and not the Target EV API endpoint name.
2. Once you have provided the relevant information, click the Test API button to check Enterprise Vault API connectivity.
3. By clicking Save the configurations will be saved.
AutoTune Tab
The AutoTune tab is designed to speed up lengthy migrations by optimizing their use of system resources through adding and removing worker threads or adjusting buffer sizes (Figure 77).
Figure 77: EV Source AutoTune Tab
1. Hosts. Here you should input the server name (in case there is more than one name, separate them with comma) where AutoTune will monitor CPU performance and Disk queue.
2. Monitor Host. To monitor the servers specified in Hosts option by AutoTune component, check the box.
3. By clicking Save the configurations will be saved.
Advanced Tab
Figure 78: EV Source Advanced Tab
1. Start Date and End Date. In these fields the cutoff date for the data retrieved from the source should be specified.
2. Enumeration Batch Size. Define the number of items that are going to be retrieved from the source and sent to the nodes in a batch at a time. The default number of items that Migrate retrieves in a batch at a time is 10000. The nodes can handle up to 50000 items at a time, so this setting can be modified between 1 and 50000.
3. Enumeration Without Retention Category. As you may know Enterprise Vault assigns archived items a retention category, which specifies the duration how long it can be kept. By default, when you carry out the migration the retention category is provided to each item. However, when you check the box, Migrate will enumerate the data without paying attention to the Retention Category. If the Enumeration Without Retention Category box is checked, retention categories are dismissed, and, in case of EV to EV migration, it can cause issues in the EV target. Therefore, the retention categories should always be set for EV to EV migration, and this option should be left unchecked. Applying this setting makes sense if the target is not EV.
4. Dejournalize. When this box is checked, the retrieved messages will be sent to all the participants in the message.
5. Create Mailboxes. When this option is checked, mailboxes with specific domains can be mapped to specific mailboxes in the EV Source. The next three fields should be configured to finish the set up.
6. Mailbox Pattern. In this field the list of domains that should be migrated can be specified. The listed domains should be comma separated.
7. Map from domains. The domains from where the messages should be retrieved can be added here. Example: gmail.com, yahoo.com, etc.
8. Map to. The destination domains of the messages from the domains added in Map from domains can be added here. Example: gmail.com, yahoo.com, etc.
9. Dejournalize Mailboxes CSV. A CSV file with the list of participants whose messages should be processed can be uploaded here.
10. LDAP Search. List of participants from AD that should receive the messages can be specified through LDAP Search.
Figure 79: LDAP Search
• Server Name. Fill in the name of the LDAP Server.
• Base Domain. Add the section of the directory where the search should begin.
• Port. Define the port of the LDAP Server.
• User Name. Add the username of the LDAP account.
• Password. Add the password of the LDAP account.
• Search Scope. Select one of the following options from the drop-down menu to define the scope of the search starting from the Base Domain:
o Base. Only the specified Base Domain should be considered for search.
o OneLevel. Only the immediate children of the specified Base Domain should be considered.
considered.
• Search Filter. Add filters that can be used to restrict the number of users or groups that are permitted to access an application.
11. Once the information is filled in, click the Download button. The participants based on the entered search will be retrieved.
12. By clicking Save the configurations will be saved.
Please note that if “: " (colon) is included in the folder name, the migrated folder name will appear twice, i.e., the folder name is :samplefolder1, the migrated folder name will be :samplefolder1:samplefolder1.
Dejournalization
1. If you want to create a new virtual dejournalized archive for each actual archive in your environment, activate Dejournalize (and Create Mailboxes if you also want to create a new virtual archive for each recipient of the journaled messages) checkboxes, and then click the Enumerate Source button.
2. If you want to create new virtual dejournalized archives, click Enumerate Source and then activate Dejournalize and Create Mailboxes. The new virtual archives in this case will be created during the item enumeration.
3. You can use Mailbox Pattern to specify for which mailboxes to create the new virtual archives.
E.g., if you only want to create new virtual archives for all the mailboxes with the domain mycompany.com, you can put *@mycompany.com in the Mailbox Pattern field.
4. You can map the domains from one to another, e.g., you can map emails from company1.com to company2.com using Map from domains and Map to fields correspondingly.
5. CSV and LDAP parts are specified in the Advanced Tab.
Once the enumeration is done, in the Manage Archives window, the list of the newly created virtual archives will show up, when we click the Show Dejournalized button. From that point on, regular source to target mapping is applied.
Important: Enumeration is a long process when dejournalization is applied, as it goes through each individual email, parses the sender and the recipient list, and then ensures the email is sent to all the necessary archives based on the configurations given in the above steps.