Copyright 2021 Veritas Technologies LLC. All rights reserved USER GUIDE. Version MIGRATE

(1)

MIGRATE

(2)

LEGAL NOTICE

The software described in this guide is furnished under a license agreement and may be used only in accordance with the terms of the agreement.

Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third-party software for which Veritas is required to provide attribution to the third party (“Third-party Programs”). Some of the Third-party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the Third-party Legal Notices document accompanying this Veritas product or available at:

https://www.veritas.com/about/legal/license-agreements.

The product described in this document is distributed under licenses restricting its use, copying,

distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,

REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS

DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and

Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.

Veritas Technologies LLC 2625 Augustine Dr Santa Clara, CA 95054

(3)

SETTING UP MIGRATE ... 13 INSTALLING MIGRATE ... 14 Installation ... 14 SQL Database Configuration ... 18 Upgrading Migrate ... 23 ACCESSING MIGRATE ... 24 ACTIVATING MIGRATE ... 25 NAVIGATING TO MIGRATE ... 28 MIGRATE UI STRUCTURE ... 29 DASHBOARD TAB ... 30 MIGRATIONS TAB ... 31 MONITORING TAB ... 33 REPORTING TAB ... 35 Web Interface ... 35 Running Reports ... 43 PowerShell Scripting ... 43 ABOUT TAB ... 44 Logging Settings ... 44

Web Log Level Settings ... 45

(4)

General Tab ... 53

Groups Tab ... 54

Management Tab ... 55

Advanced Tab ... 56

SOURCE TYPE CONFIGURATION ... 58

EAS Source ... 58 EmailXtender Source ... 60 SourceOne Source ... 64 EV Source... 67 EWS Source ... 72 EML Source ... 75 MSG Source ... 76 PST Source ... 78 Office365 Source ... 80 MANAGE GROUPS ... 82

FILTER, COMPONENT TARGET CONFIGURATION ... 84

(5)

Message Class Filter ... 101 Folder Filter ... 102 Metadata Filter ... 103 Recipient Filter ... 105 Shortcut Filter ... 108 Subject Filter ... 109 AutoTune Manager ... 110 Envelope Reconstructor ... 113 Shortcut Converter ... 114 Shortcut Creator ... 115 Shortcut Deletion ... 117 Verifier ... 119 ENUMERATING ARCHIVES ... 122 MANAGING ARCHIVES ... 123 Overview ... 123

Setting Target Id and Associated Mailbox Addresses ... 123

Marking Archives for Migration and Setting Groups ... 124

RUNNING MIGRATION ... 125 NOTIFICATION MESSAGES ... 126 AFTER MIGRATION ... 127 SCRIPTING MIGRATE ... 128 OVERVIEW ... 129 STARTING POWERSHELL ... 130 MANAGING MIGRATIONS ... 133

(6)

Listing Migrations ... 133

Updating Source Archives ... 134

Updating Migration Settings... 134

MANAGING TASK ... 135

Creating a New Task ... 135

Removing Tasks ... 135

Listing Available Tasks ... 136

Starting and Stopping Tasks ... 136

Setting Tasks ... 136

Managing Task Flows ... 136

COMPONENT CONFIGURATION ... 138

Showing/Obtaining Configuration ... 138

Setting Configuration ... 138

Testing Configuration ... 139

MANAGING GROUPS ... 140

Creating a New Group ... 140

(7)

License Management ... 143

NODES ... 144

APPENDIX ... 145

SOURCE AND TARGET TYPE DESCRIPTIONS ... 146

SOURCE TO TARGET SPECIFICATIONS ... 149

POWERSHELL EXAMPLES ... 151

(8)

WELCOME TO MIGRATE

CHAPTER 1 Welcome to Migrate 7.8

This chapter gives a general overview of the Veritas Migrate product. It includes:

• Introduction

(9)

Introduction

Dear Migrate User,

We are very excited you have chosen Migrate as the archive migration software solution for your organization.

For over 20 years, we have worked with industry leading technical and subject matter experts to design software solutions that provide the most comprehensive tool to migrate on-premises or cloud-based archived data directly into another archive or mail platform.

We continuously put our best effort together to eliminate the risks of potential data loss during the migration process by keeping our products up to date with the available technology. We take pride in our efforts and give special importance to maintain the highest standards in providing the most powerful software solutions to our clients.

We have designed and developed the following user guide to help you configure and operate Migrate to get you the most value out of your investment. Review and apply the approaches before starting your installation and configuration. Additionally, you can always contact Veritas Customer Support, we are just an email away.

Please feel free to drop us a note with any comments or suggestions as well!

We value our relationship with you and appreciate your business and thank you for the opportunity to be your Migration tool of choice.

(10)

System Requirements

Hardware

To run Migrate Manager and Nodes, below you will find the list of recommended hardware components. A typical Migration uses 1 SQL Server and 1 Migrate server with both the Node and

Manager services installed. If more Node processing is needed or available, those should go on dedicated resource servers.

Component Manager and Nodes Min Requirements SQL Server Min Requirements

Quantity 2 or more. For migrations of 10TB or less, 1 server is sufficient.

Nodes are added for each 10-20TB to be migrated.

1

Cores Quad core minimum 16+

Architecture 64-bit recommended 64-bit

RAM 12GB minimum

32GB + preferred

32GB minimum (more, if possible)

OS Windows 2012/2012 R2 or newer (Standard or Enterprise, 64 bit and 2012 R2 recommended) | also Windows 2016

Windows 2012/2012 R2 or newer (Standard or Enterprise, 64 bit and 2012 R2 recommended) | also Windows 2016

Application Microsoft Visual C++ 2013 Redistributable Packages for Visual Studio, Microsoft .NET

Framework Version 4.7.2

Microsoft SQL Server 64bit 2012, 2014 or MSSQL 2016 (preferred)

Storage 0 (C drive) 500GB free minimum - Local Default

Storage 0 (D drive) 1TB free - Local Database Files – 2 TB - Raid 1+0

Storage 2 (Destination drive space adequate for PST’s, NSF, or MSG data etc.) can be NAS

Database Log - 1 TB- Raid 1+0

Storage 3 If all the logs are required to be saved, then it is likely that the 1TB D Drive will be exceeded.

DB manual Backup space – 3 TB- Raid 5

Note: Backing up SQL is the client’s

(11)

Technical Requirements

• Minimum of two migration servers unless noted otherwise for a small migration (10TB or less). Additional servers can be added later.

• One dedicated SQL server with backup and maintenance routines set up.

• Make the Data Source Service account a local administrator on the migration & SQL servers. • Make the Data Source Service account a DBA admin/SA on the SQL server.

• Install MS Outlook on a workstation, not one of the Migrate Manager, Node, or SQL servers. Preferably use a VPN access server.

• Exchange servers must be set up with permissions according to the Destination (Install and Configuration Document - service Account Send As/Receive As permissions, impersonation rights etc.) as necessary.

• Data Source Service account with db_datareader access to all source archive databases. • Data Source Service account with rights to log in remotely to Migrate servers.

• Data Source Service account with read access to the source & read, write & delete access to the target.

• Disabled Virus scanner on Migrate migration servers.

• Microsoft .Net Framework 4.7.2 as well as the latest update of the Microsoft Visual C++ 2013 Redistributable Package installed on the Migrate Server(s) being used for migration from the Data Source.

• Internet Information Services (IIS) Version 7.0 or above, with ASP.net v4.0 run-time installed and configured to run with IIS, along with ISAPI & CGI filters.

• Run SQL maintenance against Source Databases and Destination Databases:

https://www.veritas.com/support/en_US/article.TECH168905.

• For EV, Application Runtime/API (same version on the Data Source servers) always needs to be installed on the Migration & Node servers.

• For Manager to Node & Node to Manager communication Migrate uses ports 9052 & 9090. • Port 807 on local machine for accessing web services, and for the console.

• For Exchange source and targets Migrate uses port 443. • Port 1433 for SQL, 80 and 443 for HTTP and SSL respectively.

• EV API calls use DCOM over RPC. The default behavior is using port 135 to handshake, and then a dynamic port range. To limit the ports in use, see this article:

https://www.veritas.com/support/en_US/article.TECH69642.

(12)

Document Version Control

This section includes:

• April 19, 2021 • February 24, 2021

April 19, 2021

The changes are represented in the table below:

Chapter/Section

Changes

Office365 Target Added Insertion batch size (MB) and Target Root Folder fields for advanced configurations.

Reporting Tab Failure Report and Item Condition Status Report are renamed as Cannot Migrate Report and Not Migrated Report respectively.

February 24, 2021

The changes are represented in the table below:

Chapter/Section

Changes

EULA Updated the End User License Agreement.

Reporting/Shortcut Archive Report Added a new Archive report type on the Reporting tab.

(13)

SETTING UP MIGRATE

CHAPTER 2 Setting Up Migrate 7.8

This chapter includes the following sections:

(14)

Installing Migrate

You can download MIGRATE 7.8 installation package directly from the Product Purchase e-mail sent to you by Veritas Technologies LLC Team. Additionally, you can contact Veritas Customer Support to request the download link. You can install and configure all the five components of Migrate7.8 (Manager, Node, PowerShell, UI, and Database) when you run the single Setup.msi file. In case you intend to install the Node component on another server, or you want to install multiple Nodes, the installation package also includes NodeSetup.msi file.

Important: To smoothly run Migrate, we recommend installing the Manager on one server and the Node on another.

If you encounter any problems at any point during the installation, do not hesitate to contact Veritas Customer Support. We are ready to help you 24 hours a day, 7 days a week.

Installation

Once you have downloaded the Migrate installation file (make sure the properties of the ZIP file were not “Blocked” before extracting), open a Command Prompt as administrator (Figure 1).

Figure 1։ Opening Command Prompt

(15)

Figure 2: Setup.msi

Figure 3: Migrate Platform Setup

2. You will be redirected to the License Agreement screen. Read the License Agreement

(16)

Figure 4: License Agreement

3. In the next step of the installation process, choose one from the three setup types that best suits your needs (Figure 5).

Figure 5: Setup Types

• When choosing the Complete setup type, you enable the Migrate Setup Wizard to install all the program features. If selected, on the next screen you will be asked to provide the relevant folder where Migrate platform will be installed. The default path is: C:\Program Files\.

(17)

Figure 6: Complete Setup Type

• For advanced users, Custom Setup type is recommended. You can select the relevant components and their setup locations (Figure 7).

Figure 7: Custom Setup Type

• When choosing the Typical Setup type, you enable Migrate Setup Wizard to install the most common program features.

(18)

Figure 8: Database Configuration

Important: The Create Database and Update Database actions cannot be reverted. So, if you intend to upgrade the database, make sure that you have back up of the current database you are using.

SQL Database Configuration

Now you are ready to configure the SQL Database.

1. Provide the SQL server name or an IP address (Figure 9).

(19)

• In case you have chosen the Create Database option (Figure 8), you will have to provide a totally new Database name.

• On the other hand, if you have chosen the Update Database option (Figure 8), input the name of the relevant database you intend to upgrade.

• And finally, if you have chosen the Skip Database Create/Upgrade option (Figure 8), you will connect to an already existing database by providing the name of the database․

3. Select the SQL Authentication Type and click Next (Figure 9). In Migrate we have two types: • Implicit login, which is done through Windows Authentication method.

• Explicit login, which is carried out through SQL Server Authentication. 4. Configure the Migrate Management Service. Select from the two options:

• Migrate can use the Local System credentials. By default, this option will be selected. • You can manually input the credentials. To do so, select the Custom Account option and fill

the Account, Password and Confirm password fields with relevant information and click Next (Figure 10).

Figure 10: Migrate Management Service Credentials

Important: If you have selected Windows Authentication as an SQL Authentication Type, you will have to run Migrate Management Service as a Custom Account. If you have selected SQL Server Authentication as an SQL authentication Type, you can choose either Local System or Custom Account as a Migrate Management Service Credential. The Local System account or the Custom Account used to log into Node Service should have read, write, and delete permission on the target and read permission on the source.

(20)

11).

Figure 11: Account Management Information

• Base URL. This is the URL that was sent out to you. It is the Migrate 7.8 webpage URL. • SMTP options. Provide all the SMTP credentials (Host, Login, Password) so that the admin

can send out invitation e-mails. This information is also used for Automatic Report. • Administrator Credentials. Provide the Email, Password and Confirm Password for the

Administrator to either create or upgrade Migrate 7.8 administrator account during the installation.

6. Once you have input all the relevant information, click Next.

(21)

Figure 12: Specifying the Manager URL

Figure 13: Manager URL for the Web Client

8. The installer will check if IIS ISSAPI and CGI Filters are installed and allowed on the machine. If not, a warning message will appear, and the installation will stop.

(22)

Figure 14: Beginning the Installation

Figure 15: Installing Migrate Platform

(23)

Figure 16: Migrate Platform Installation Finish

Upgrading Migrate

Upgrade can be done directly over the current version.

(24)

Accessing Migrate

After the installation is complete, you are ready to launch the Migrate for the first time.

Before launching the software, make sure that the Migrate Manager and Migrate Node are running in the Window Service Control Manager.

Under the Status column next to the Migrate Default Processor Node and Migrate Management, you should see the status Running (Figure 17).

Figure 17: Migrate Default Processor Node Status

Now you are ready to open the User Interface. There are two options how to launch Migrate:

Option 1: From the shortcut that was added in the Startup Menu during the installation. Double click the shortcut and the URL will launch.

Option 2: You can open the Migrate UI through the following link in your browser (Google Chrome is currently the best choice): http://<servername>:807/Default.aspx by replacing

(25)

Activating Migrate

Once you have purchased Migrate you will have to activate the license. You can either activate Migrate for all source types or select some of them. To obtain the license key:

1. Open Migrate UI.

2. Click the About tab on the top right corner of the page. 3. Select Add New License.

Figure 18: Adding New License

4. Copy the Host Activation Code (Figure 19).

Figure 19: Host Activation Code

(26)

button (Figure 20).

Figure 20: Obtaining License

6. The License will be activated, and you will be directed to the About Us page. Click the License Information to open the license related information (Figure 21).

Figure 21: Navigating to License Information

7. A pop-up screen will be opened, and you will see a table with the license related information (Figure 22):

• License Code is a two-letter code that denotes the relevant component the license has been obtained for.

• You can always view whether the counting for Volume, Archive or Item is enabled or not. • The License Data Volume, License Archive Count Value and License Data Count Value show

the maximum allowed values for the specific counter. • You can view the Current Value for the specific counter.

(27)

(28)

NAVIGATING TO MIGRATE

CHAPTER 3 Navigating to Migrate 7.8

This chapter includes the following sections:

(29)

Migrate UI Structure

Migrate web platform is an easy-to-use platform which provides functions such as reporting, migrations and monitoring. On the top menu you will see the following five menu tabs that will help you throughout the migration process (Figure 23):

• Dashboard • Migrations • Monitoring • Reporting • About

(30)

Dashboard Tab

When you open Migrate web platform, the first screen you will see is the Dashboard. Here you can find the general information related to each migration (Figure 24).

Figure 24։ Migrate Web Interface: Dashboard Tab

1. In case you have more than one migration running, you can select the relevant one from the drop-down list and view its statistics on the Dashboard. Additionally, you can select the (ALL) option and view the general statistics related to all migrations.

2. For each migration there will be the below listed statistics. Namely, here you can view the statistics related to the

• migrated data size based on your Migrate License • number of items that were migrated

• number of tasks

• number of known error types

3. The pie-chart represents statistics related to the migration status. Next to the chart you will see a color code with explanation.

4. Processor Online Status represents information on the Processor Node, Its Status and API Version.

(31)

Migrations Tab

The second tab in the menu is the Migrations tab, where you can create new migrations or configure the already existing ones. Additionally, this is the screen where you can view the archives, create, or

configure tasks and groups.

If you have just installed Migrate you will see the screen as in Figure 25. To create a migration, click the Create New Migration button.

Figure 25: Migrations Tab Without Created Migrations

Meanwhile, if migrations have already been created, the last migration will be displayed when you open the Migrate UI (Figure 26).

(32)

Migration drop-down menu.

2. With the help of the Create New Migration button, you can create new migrations. 3. Click the Configure Source button to update all the information related to source for the

migration.

4. To find available archives for migration, click the Enumerate Source button.

5. With the Manage Groups button you will be able to set up groups for the migrations. Groups allow a migration to be structured into logical, project or sequence-based process by enabling migrations to revolve around a flexible architecture. Archives cannot be members of more than one group at a time.

6. After Enumerating the Source, the list of available archives is found by clicking the Manage Archives button.

7. For information on the Enumeration Progress bar, see How Enumeration Options work. 8. Task Information is required to migrate data. Configuration of these tasks are found by clicking

Create Task. More details are found in the Creating New Migration section.

9. The pie-chart represents statistics related to the Migration Status. Next to the chart there is a color code with explanation.

10. The Statistics section shows data in real-time.

(33)

Monitoring Tab

The third tab in the menu is the Monitoring tab as the screen in Figure 27.

Figure 27: Monitoring Tab

If you are a first-time user, you will see the screen as in Figure 25. To setup a migration, click the Create New Migration button. Use the Task Status Filter to view Running or Stopped migrations. To view the whole list of migrations, select the (All) option.

(34)

Figure 28: Example of Migration

As you can see there are two tasks. The archive task Figure 29 is with the Status of Running and the Default task in Figure 30 is with the Status of Stopped.

Figure 29: A Running Migration Task

Figure 30: A Stopped Migration Task

(35)

Reporting Tab

Migrate includes a complete reporting engine, accessible both through the Migration Web Interface and Microsoft PowerShell. As the reporting interface is available through PowerShell, reports can be scripted and scheduled as appropriate.

Figure 31: Reporting Tab

Web Interface

To run a report in the web interface, click the Reporting tab on the toolbar and select the migration you wish to report on. Click the relevant report icon that you wish to run. A window will pop-up showing the report you have selected.

(36)

side of the toolbar. Reports can be exported to XLS, XLSX, RTF, MHT, HTML, TXT, CSV, and Image. Once you have selected a file type, click the disk icon (indicated above) to the left of the drop-down box. Your report will then be downloaded via your browser’s download protocol.

To print the report, click the printer icon. The standard print dialog will be displayed, and you can print your report.

Reports can be exported to PDF, CSV, DOC, XLS and other formats as appropriate allowing simple redistribution and display.

1. Archive Report shows a list of each archive (by name), its migration status, and the number of migrated, skipped, and remaining items (Figure 33).

Figure 33: Archive Report

(37)

Figure 34: Shortcut Archive Report

3. Chain of Custody Report shows the chain of custody information identifying the items that have been migrated from source to target (Figure 35).

Figure 35: Chain of Custody Report

4. Cannot Migrate Report shows the proper categorization of issues/message status,

(38)

Figure 36: Cannot Migrate Report

5. Not Migrated Report shows unsupported message class types, Failed to Prepare Archive Items, Corrupt Messages, and other applicable types (Figure 37).

Figure 37: Not Migrated Report

(39)

Figure 38: Skipped Items Report

7. Summary Report shows a chart with the overall migration status (Figure 39).

Figure 39: Summary Report

(40)

Figure 40: Audit Report

9. Verification Report provides information on the list of migrated items, their subject, date, verification level, and verification type applied for the process, and the actual verification status and date (Figure 41).

Figure 41: Verification Report

(41)

Figure 42: Enumeration Report

11. Performance Report provides information on the list of processors with the number of processed tasks, idle and offline times, and the number of processed messages per second (Figure 43).

Figure 43: Performance Report

(42)

Figure 44: Shortcut Processing Report

Important: The Status filter works only when the chain of configuration contains any of the Shortcut components.

13. Generate Support Package creates diagnostic information packages that you can share with the support team. The package is provided in a ZIP file. It can include sample messages for all error types in the selected migration, as well as all logs generated for that migration, Archive Report, and Summary Report. If you do not want to include sample messages, uncheck the box and continue the report generation by clicking Ok. The Manager Service will start to collect the necessary information for this package.

14. Once the package is ready, the user will receive a notification message, and the download link will appear. Click that link and the ZIP file will be downloaded through the Web Interface.

15. The generated ZIP support package should contain: • All logs – manager and processor – compressed

• The Archive Report PDF, Summary Report PDF, and Errors Report PDF in the root of the ZIP • If Include sample messages previously was checked the ZIP package will contain a sample of

each type of Error (if it exists) – the top 5 items in each error category, stored in subdirectories in the ZIP with the Error ID as the folder name

16. The Password for ZIP is the Host Activation Code from the licensing framework. The ZIP file name will take the following format: ZIP file name – Migrate-<ver>#YYYY-MM-DD-HH-mm.zip. For example, Migrate-7.8.1_2019-08-07-15-31.zip.

(43)

18. The Reports are delivered through an SMTP relay. The email address of the Sender and Target should be allow listed to avoid the email going to the Spam folder. The Target address should be the address to which the report is to be delivered.

19. Enter the SMTP server and the Port, and the Username and Password to the SMTP Server. 20. The scheduling is done by the days of the week and the time of the report generation. The

Generation time is UTC based.

Figure 45: Automatic Report Delivery

21. When all the information is filled in, click the Test Connection button to see whether the credentials provided are valid.

Running Reports

Reports can be run either from the web interface, or from the PowerShell command line.

PowerShell Scripting

(44)

About Tab

Information related to Migration product version, license status and logging can be viewed under the About tab (Figure 46).

Figure 46: About Tab

Logging Settings

To change the Logging settings, click the Change button in Figure 46. The pop-up window in Figure 47 will appear.

Figure 47: Logging Settings

There are the following logging levels in Migrate:

(45)

Figure 48: Log Events

• Web Log Level records all the events in the UI of Migrate web application. For this log level additional permissions for the web application must be set. In the following section the steps to set the necessary permissions can be found.

• Log File Size (MB) field has a default value 10 which you can also specify with the size you want.

Web Log Level Settings

To setup Web Log Level Settings:

1. Go to Internet Information Systems (IIS) Manager. 2. Click Applications Pools (Figure 49).

Figure 49: Application Pools

3. Right click the MigrateAppPool.

(46)

Figure 50: Identity - ApplicationPoolIdentity

5. Go to Application Pool Identity configuration and select Custom account (Figure 51).

Figure 51: Custom Account

6. Enter the credentials of an account that has folder creation permissions (Figure 52).

Figure 52: Setting Credentials

(47)

RUNNING MIGRATE

CHAPTER 4 Running Migrate 7.8

This chapter includes the following sections: • Creating New Migration

• Source Type Configuration • Manage Groups

• Filter, Component Target Configuration • Enumerating Archives

(48)

Creating New Migration

When you launch Migrate for the first time, you will see the Create New Migration button. Click the button and the Configure Settings for Migration pop-up screen will open (Figure 53).

Figure 53: Configure Settings for Migration

1. Name. Provide a name for the new migration. You are free to input here any combination of numbers and letters, but not special characters. We advise you to name the migration taking into consideration the source and target names. Example: EV Source to MSG Target Migration. 2. Source Type. For the migration to take place you will have to establish a connection between the

two main components: a single Source and Target(s). From the drop-down menu select the relevant source type for the migration.

3. Click Save and the migration will be created.

4. Once a new migration is created, a Default Group (Figure 54) and Default Task (Figure 55) are added automatically.

Figure 54: Default Group

(49)

• EWS • EML • MSG • PST • EAS • EmailXtender • SourceOne

Figure 55: EV Source Configuration Type

6. Click the Configure Source button to be redirected to its configuration information.

7. The first step of the migration after configuring the source is retrieving the list of existing archives from the source. This is accomplished either by the Enumerate Source or the Import Archives option of the Archive Manager.

• Enumerate Source accesses and searches for archives in the source of the archiving system. While enumeration is in progress, a loading icon appears near the Enumerate Source button, as well as the notification that pops up in the bottom right corner of the manager screen for both, start and finish. Once it is finished, all detected archives are listed in the Archive manager.

• Import Archives option allows uploading a CSV file with the list of the archives that are going to be migrated. The CSV file should have the same fields as the Archive manager (Figure 56). They are and should be set as follows:

o Required Columns: Name, Type, External ID.

(50)

o Target ID, Associated Mailbox; depending on the type of Target, this information will eventually*_{be required or can be left empty - further explanations can be found in Target} specifics.

o Group, Group ID can be configured as you want (make sure that inserted group exists, otherwise it will have Default Group) or leave it empty and Migrate will automatically set Default Group with Group ID.

o Migrate column, if set to TRUE, will be checked.

Figure 56: CSV File

8. It is optional to set up groups for the migrations, but highly recommended. Groups allow migrations to be structured into logical, project or sequence-based processes. For more information on how to set up Groups check the Manage Groups section.

9. Next step is to configure the target. There are few steps involved in configuring the target. These steps are:

• AutoTune Manager (optional) • Adding applicable filters

• Optional data constructions such as envelopes or shortcuts • Selecting the target

• Verification (optional, but recommended) • Configuring the task flow

10. The components in the task flow should be kept in the above-mentioned order for the migration to be run correctly.

11. To configure the target in the Task Information box, from the drop-down menu select the target and click Add. Migrate supports the following targets:

(51)

12. Click the target name to be redirected to its configuration information.

13. Along with migration records to the above-mentioned targets, Migrate can also add, apply filter, or convert data through auxiliary components - such as Shortcut Conversion or Verification components. When you create a new migration, the Default Task is added automatically.

• AutoTune Manager speeds up speeds up lengthy migrations by optimizing their use of system resources by adding and removing worker threads or adjusting buffer sizes. AutoTune manager analyzes source and target servers’ performance to decide about increase or decrease the migration’s worker threads.

• Envelope Reconstructor encapsulates the original message in an envelope. The purpose of the envelope is to provide further information about the message such as the origin, destination, timestamp, recipients, sender, BCC recipients, newsgroup recipients and so forth. Envelope Reconstructor is usually used on journal files from sources EV, EAS, EmailXtender, Source One. Some ediscovery application may require envelope to facilitate the search.

Sample message

Figure 57: Sample Message

(52)

Figure 58: Enveloped Message

• Message Class Filter. The message class for an item is defined by its MessageClass property and is used to identify the form that should be used to display the item. Each source has its own set of message classes that include both common message classes for all sources as well as source specific classes.

• Metadata Filter. Metadata is the data about data. It is a description and context of the data. It helps to organize, find, and understand data. Emails and messages also have metadata stored in them. Often this data is not even viewable in the email client application used to create or view the email. The amount of email metadata available for a particular email varies greatly depending on the email system. This option allows filtering through an archive by the creation date of the messages, availability of attachments, message size, recipients, and message body type.

• Recipient Filter allows filtering through the messages in an archive based on the message participants in From, To, Cc, and Bcc fields. Filtering criteria can also be set to specify if all participants or any of them should apply to the filtering using logical expressions.

• Subject Filter allows filtering through the messages in an archive based on the subject lines or attachment names of the messages.

• Folder Filter allows specifying which folders in the archive to process and which ones to skip. This is useful when there are a lot of folders in the archive and only some of them need to be either processed or skipped.

• LDAP (Lightweight Directory Access Protocol) Filter is an Internet protocol that email, and other programs use to look up information from a server. Using the query, the SMTP and Exchange addresses of users can be retrieved to filter through the senders and recipients (From, To, Cc, Bcc fields) of the archives.

• Header Filter allows filtering through the messages in an archive based on the message headers.

• Shortcut* Filter searches for specified filters in the associated EWS account. The EWS impersonator account should have delegate access to conduct filtering.

(53)

create a shortcut in the connected Exchange mailbox, as the EV API does not provide this functionality.

• Shortcut Deletion deletes the shortcut from the EWS mailbox that is connected to the source. Source can be EV, EAS, EmailXtender, and SourceOne. It is used when the shortcuts are of old files. The EWS impersonation account should have delegate access to the

associated EWS mailbox.

• Shortcut Convertor is used when the original archive was moved to another server, and the shortcuts need to be updated to direct to the correct archive address. The source and the target should be the same, e.g., EV to EV, EAS to EAS, EmailXtender to EmailXtender, or SourceOne to SourceOne. The EWS impersonation account should have delegate access to the associated EWS mailbox.

• The Verifier component verifies messages between the start and end of a task flow, to ensure messages have not been modified. If the Verifier level is set to advanced and the item verification fails, it is deleted from the target.

14. Once the target, component, or filter are configured, it’s time to set up the task flow.

15. Migration Tasks enable the data to be transferred from Source Component to the target, with the help of several task flows. Additionally, tasks can also push data through applying auxiliary components - such as Shortcut Conversion or Verification components. When you create a new migration the Default Task is added automatically.

16. Apart from the Default task, you can setup as many Tasks as you wish. Let’s start exploring the Task Information configuration screen before getting a more detailed look at its Flow

Configurations.

Figure 59: Task Information

17. Click the Create Task button and the relevant config screen pop-up will appear.

General Tab

(54)

Figure 60: Configuring a Task Name

1. Name. Provide the name for the task. Only letters and numbers are allowed, no special

characters. This information will appear in the Migration container right below the default task. 2. Processor Count. This option specifies how many Node Processors installed on servers take part

in the migration task. This is an integer number. The default setting is “1”.

3. Thread Count. Server has a limited number of threads available. This option specifies how many of them can be used. The maximum number is the total number of threads on the server. This is an integer number. The default setting is “1”.

4. Item Processing Timeout (sec.). This option specifies the maximum time a single item can be processed by a single component in the task flow. If it takes longer than the set time, the item is failed. This is an integer number showed in seconds. The default setting is “300”, e.g., 300 seconds.

5. Enumeration. When you check this box, you specify that the task should enumerate (collect) new messages from the source, rather than just work with the set already enumerated by Migrate. If the task is new and it was not run previously then it is, required to run Enumeration at least once. If the Archive is not closed, then Enumeration along with the migration will need to be rerun possibly multiple times.

6. By clicking Save the configurations will be saved.

Important: Thee Enumeration is unchecked automatically after it completes any enumeration run. If the Enumeration is failed, it will stay checked.

Groups Tab

(55)

Figure 61: Connection Setup between the Groups and Tasks

1. Select the groups that are to be associated with the tasks. As additional groups are created, a drop-down list is automatically created and selection can be none, one or more groups. But if none are selected, the task will throw an error and not run.

Management Tab

In the Management tab you can specify the retry failures, skips and overrides (Figure 62).

Figure 62: Management Tab

1. Retry Failures. If this box is checked, during the rerun of the task any items, that were failed, will be retried.

2. Retry Verification Failures. If this box is checked, during the rerun of the task any items, that failed verification set by the Verifier component, will be retried.

3. Retry Skips. If this box is checked, during the rerun of the task any items, that were skipped, will be retried. The items are usually skipped when their message class is not supported.

4. Include Overrides. In case you want to migrate messages that were manually overridden through modifying the database, check this box.

(56)

the migration or as a separate task.

Advanced Tab

The Advanced tab settings are beneficial to understand and to be aware of the potential for unintended consequences (Figure 63).

Figure 63: Advanced Tab

1. Include Existing Migrated Items. If you want previously migrated messages to be migrated again, check this box.

2. Enumerate Only. Check this box if you want only to do enumeration. The General tab must also have the Enumeration box checked and once this task is run, the Enumerate Only box must be manually unchecked to resume migrating messages.

3. Enumerate Batch Size. The number of items to be enumerated in a single batch can be

configured from 1 to 10000. Note that only increasing the batch size will not speed up the item enumeration, as the SQL Server I/O speed should also be considered.

4. Start Date. Is used to schedule the start date of the task.

5. Stop Date. Is used to schedule the end date of the task. If a date is not specified, the task will only be run manually and/or via PowerShell scripting.

(57)

Figure 64: Task Information

You can edit or delete the task from the database.

7. Once everything is configured click the icon to start it. When it is finished it will turn back to from the icon.

How Enumeration Options work

• If only Enumeration in the General tab is selected, enumeration is run simultaneously with the migration.

• If Enumeration in the General tab and Enumeration only in the Advanced tab are selected, only enumeration is performed on the archives, nothing is migrated. Enumeration only works only when the Enumeration is checked.

• The option, when Enumeration is not selected, is used when enumeration has already been done, and only migration is needed.

• If enumeration crashes and you want to run the enumeration again, make sure that the Enumeration box is checked in the task configuration.

More information on various Source-Target pairs and their specifications can be found in the APPENDIX

(58)

Source Type Configuration

This section contains detailed information on each source and its configurations.

EAS Source

Enterprise Archive Solution (EAS) is a software for enterprise file, social media, and e-mail archiving. It can archive data from various sources such as MS Exchange, MS SharePoint, various file systems such as NTFS, social media platforms like Twitter and Facebook, as well as from instant messaging applications like Microsoft Skype.

Migrate provides connectivity to the EAS system using the EAS Retrieval API.

Database Tab

The Database tab is for providing information related to the EAS SQL database (Figure 65):

Figure 65: EAS 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.

(59)

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.

API Tab

Under the API tab, you will be asked to input EAS Retrieval API address information (Figure 66):

Figure 66: EAS Source API Tab

1. Retrieval Url. Specify the HTTP retrieval location URL that is used to retrieve messages from EAS. 2. EAS User Name. You have the option to specify the username for retrieving messages from EAS.

In case you leave the option not specified, the default credential will be used. 3. EAS User Password. Input the password for retrieving messages from EAS. 4. Server ID. Provide the EAS Server ID, used for the message retrieval URL.

5. Verify Retrievals. You can check the box to verify the retrievals during the migration. 6. By clicking Save the configurations will be saved.

AutoTune Tab

(60)

Figure 67: EAS 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.

If an archive selected for migration is a Journal Archive (“Virtual Consolidated Journal” archive), then all items from it will be migrated to the “Inbox” folder of the target.

For more details on AutoTune, view the AutoTune Manager section.

EmailXtender Source

With Migrate you can carry out Migrations from EMC EmailXtender systems, can use either direct connection or API.

Important: Currently, we support only Microsoft Exchange data and support NTFS or Disk-based Containers.

Database Tab

(61)

Figure 68: EmailXtender Source Database Tab

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.

(62)

EWS Tab

Figure 69: EmailXtender Source EWS Tab

1. EWS Impersonation Account. Provide the Username used to connect to Exchange Web Services. You can input information either in <domain\username> format, or UPN <[email protected]> format.

2. EWS Impersonation Account Password. To help Migrate connect to EWS provide the Impersonation Account password.

3. EWS Domain. If the EWS Impersonation Account is not specified in UPN format, include the domain name, i.e., domain.com.

4. Once you have provided all the relevant information, click the Autodiscover Url and Version button.

5. EWS URL. In case you know the EWS URL, you can skip the auto-discovery step and input the https://myserver/ews/exchange.asmx URL in this field. Change <myserver> to your domain.

(63)

7. Personal Archive. When this is box is checked, the items for the migration are searched in the personal archive of the mailboxes.

Storage Tab

To access EmailXtender archives/items, the Migrate Node service should be run as the account with access to the shared storage location (Figure 70).

Figure 70: EmailXtender Source Storage Tab

1. Storage File Path. Provide the file path for the shared 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 can 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.

(64)

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 71).

Figure 71: EmailXtender Source AutoTune Tab

2. Monitor Hosts. To monitor the servers specified in Hosts option by AutoTune component, check the box.

If an archive selected for migration is a Journal Archive (“Virtual Consolidated Journal” archive), then all items from it will be migrated to the “Inbox” folder of the target.

For more details on AutoTune, view the AutoTune Manager section.

SourceOne Source

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

(65)

Figure 72: SourceOne Source Database Tab

(66)

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.

AutoTune Tab

(67)

Figure 74: SourceOne Source AutoTune Tab

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.

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

(68)

Figure 75: EV Source Database Tab

API Tab

(69)

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.

AutoTune Tab

Figure 77: EV Source AutoTune Tab

(70)

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.

(71)

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.

(72)

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.

EWS Source

(73)

EWS Tab

Figure 80: EWS Source EWS Tab

1. EWS Impersonation Account. Provide the Username used to connect to Exchange Web Services. You can input information either in <domain\username> format, or UPN <[email protected]> format.

2. EWS Impersonation Account Password. To help Migrate connect to EWS provide the Impersonation Account password

3. EWS Domain. If the EWS Impersonation Account is not specified in UPN format, include the domain name, i.e., domain.com.

4. Once you have provided all the relevant information, click the Autodiscover URL and Version button.

5. EWS URL. In case you know the EWS URL, you can skip the auto-discovery step and input the https://myserver/ews/exchange.asmx URL in this field. Change <myserver> to your domain.

(74)

7. Personal Archive. When this box is checked, the items for the migration are searched in the personal archive of the mailboxes.

8. CSV File. Provide the path to the CSV file with information about the source archives (user mailboxes) that will be enumerated after the source configuration. This is one option, as the second way to enumerate the source is through importing a CSV file with much more detailed data into the Archive manager section. For more information see Managing Archives. The third option is to use the Enumeration Source option on the Migration Page. The attached CSV file should have the following structure for the “Enumerate Source” operation to successfully retrieve the source archives (user mailboxes):

where Archive is the mailbox SMTP address, External ID is the mailbox ID. 9. By clicking Save the configurations will be saved.

Important: External ID is optional, only the mailbox SMTP address will work.

AutoTune Tab

(75)

Figure 81: EWS Source AutoTune Tab

EML Source

With Migrate you can easily migrate data from EML files as a Source.

General Tab

Figure 82: EML Source General Tab

(76)

EML files at the same path.

2. Subfolder as Archive. When you check the box, Migrate will also include the subfolders in archives while searching EML files in the Source Folder. The subfolder structure is kept in the target.

3. When all the information is filled in, click the Test Connection button to see whether the credentials provided are valid.

AutoTune Tab

Figure 83: EML Source AutoTune Tab

MSG Source

(77)

General Tab

Figure 84: MSG Source MSG Tab

1. Source Folder. Specify the location on the disk (either a UNC or local location) where MSG files are located. The Source Folder is the root location where the MSG Files are to be found. In case of multiple processors, you must use a shared path to make sure all processors try to find the MSG files at the same path. When you Enumerate Archives Migrate looks at the root directory and picks up all the archive names from the first level.

2. Subfolders as Archive. When you check the box, Migrate will also include the subfolders while searching MSG files in the Source Folder. In case of multiple processors, you should use shared path to make sure all processors try to find MSG files at the same path. The MSG Source subfolder has the following look: <Root>\<[email protected]>\<-Folder>\<AnotherFolder>\<Message>.msg.

3. When you have filled in all the information click the Test Connection button to see whether the credentials provided are valid.

AutoTune Tab

(78)

Figure 85: MSG Source AutoTune Tab

PST Source

With Migrate you can easily migrate data from PST Source files to the target of your choice. If you use a PST input component, install MS Outlook on a workstation, not one of the Migrate Manager, Node or SQL servers, the VPN access server is ideal.

Copyright 2021 Veritas Technologies LLC. All rights reserved USER GUIDE. Version MIGRATE

MIGRATE

LEGAL NOTICE

TABLE OF CONTENTS

WELCOME TO MIGRATE

CHAPTER 1

Welcome to Migrate 7.8

Introduction

System Requirements

Hardware

Technical Requirements

Document Version Control

April 19, 2021

Chapter/Section

Changes

February 24, 2021

Chapter/Section

Changes

SETTING UP MIGRATE

CHAPTER 2

Setting Up Migrate 7.8

Installing Migrate

Installation

SQL Database Configuration

Upgrading Migrate

Accessing Migrate

Activating Migrate

NAVIGATING TO MIGRATE

CHAPTER 3

Navigating to Migrate 7.8

Migrate UI Structure

Dashboard Tab

Migrations Tab

Monitoring Tab

Reporting Tab

Web Interface

Running Reports

PowerShell Scripting

About Tab

Logging Settings

Web Log Level Settings

RUNNING MIGRATE

CHAPTER 4

Running Migrate 7.8

Creating New Migration

General Tab

Groups Tab

Management Tab

Advanced Tab

How Enumeration Options work

Source Type Configuration

EAS Source

Database Tab

API Tab

AutoTune Tab

EmailXtender Source

Database Tab

EWS Tab

Storage Tab

AutoTune Tab

SourceOne Source

Database Tab

Storage Tab

AutoTune Tab

EV Source

Database Tab

API Tab

AutoTune Tab

Advanced Tab

Dejournalization

EWS Source

EWS Tab

AutoTune Tab

EML Source

General Tab

AutoTune Tab

MSG Source

General Tab

AutoTune Tab

PST Source