Chat now with support
Chat with Support

Migration Manager for Email Archives 10.0 - SQL Guide

Contents

Contents

Requirements Overview

To best support your SQL server and the needs of a migration, it's recommended that all production Migration Manager for Email Archives deployments run on a dedicated instance of Microsoft SQL Server.

Migration Manager for Email Archives is a feature-rich product and can therefore result in very diverse SQL Server load profiles between customer deployments. As Migration Manager for Email Archives scales, additional databases and the associated increase in load will require scaling of the SQL Servers to meet the load.

Although Enterprise Edition of Microsoft SQL Server is recommended, Standard Edition may be used if the SQL instance uses the recommended (not minimum) resources associated with the size of migration you are performing. Planning for additional time will be required to accommodate regularly required offline maintenance.

It may be necessary to separate out specific Migration Manager for Email Archives databases such as the Directory and Link databases to dedicated SQL Servers.

There are many factors which may influence the deployment, but an initial server sizing guideline would be to provision the CPU cores and RAM described in the information below arranged in as many servers as desired, evenly distributing the Migration Manager for Email Archives databases if deployed as multiple SQL servers.

Hardware Considerations

Migration Manager for Email Archives requires a number of SQL databases:

The SQL Server that manages these databases must reside on a separate server than the Migration Manager for Email Archives core and modules. The only exception is for a non-production pilot/demonstration system.

The table below indicates the requirements for SQL Server for a small Migration Manager for Email Archives migration (less than 5 Tb).

Processors (cores)

Minimum 4, Recommended 8

Memory

Minimum 16 GB, Recommended 32 GB

Hard disk

Disks should be configured as per Microsoft SQL Server best practices with TempDB, databases and logs on separate disks.

Virtualization

Supported, however performance may be impacted if resources mentioned above are not dedicated.

The table below indicates the requirements for SQL Server for a medium Migration Manager for Email Archives migration (less than 20 Tb).

Processors (cores)

Minimum 4, Recommended 16

Memory

Minimum 32 GB, Recommended 64 GB

Hard disk

Disks should be configured as per Microsoft SQL Server best practices with TempDB, databases and logs on separate disks.

Virtualization

Supported, however performance may be impacted if resources mentioned above are not dedicated.

The table below indicates the requirements for SQL Server for a large Migration Manager for Email Archives migration (more than 20 Tb).

Processors (cores)

Minimum 16, Recommended 32

Memory

Minimum 64 GB, Recommended 128 GB

Hard disk

Disks should be configured as per Microsoft SQL Server best practices with TempDB, databases and logs on separate disks.

Virtualization

Not normally supported. Contact Quest Support if virtualization is the only possibility.

Migration Manager for Email Archives keeps track of every item it exports/imports for auditing purposes. It places a reliance on SQL Server for this task. An adequately prepared SQL Server that meets the recommended specification is essential for a fast migration. Ensuring that an adequately prepared SQL Server which meets the recommended specification is essential for a fast migration.

NOTE: Performance of the migration will be impacted if the SQL Server environment is not sufficient for the needs of the migration.

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating