Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

Migration Manager for Email Archives 9.6 - SQL Guide

Sizing Considerations

Migration Manager for Email Archives uses a single Directory Database, and potentially multiple Item databases (depending on the number of source environment Vault Stores that are configured to migrate).

The Directory Database size requirement is 500 MB. However, to allow for temporary transaction log growth, it is recommended to ensure at least 2 GB is available for the database and logs.

Each item database has an initial storage requirement of 2 GB; 1 GB for the data file, and 1 GB for the transaction log.

The Migration Manager for Email Archives Item databases will grow depending on the items that are being migrated. A basic sizing guide for each item database is 1024 - 1500 bytes for each item collected plus 1 GB for static data, transaction logs and temporary data fluctuations.

Directory Database

500 MB

Each Item Database

2 GB

In an environment when many source environment Vault Stores are considered for migration, we recommend that you configure the SQL Server setting relating to the default database and transaction log location to a drive or folder with sufficient storage space. Further, in this type of environment, we recommend that you move the databases and transaction logs for the Item Databases to separate storage areas, per the table in the previous section.

Virtualized infrastructure

There are important aspects to consider when installing SQL Server in a virtualized infrastructure. Follow the recommendations of the hypervisor vendor and Microsoft when sizing and configuring the environment.

The primary objective is to ensure that the resource requirements described above are dedicated to the virtual machine to ensure minimum impact to the performance from intermediate layers or co-existing guests.

The hypervisor should be type-1 (native) to ensure the minimum impact on hardware resource requirements.

Note the following general guidelines:

Maintenance Plans

There are three aspects of SQL Server Maintenance Plans to consider:

These will be described in the section below.

NOTE: The information provided is for guidance only. Often a SQL DBA team will have their own plans and procedures in place for applications relying on databases.

Database backups

We recommend that you perform regular backups of the Migration Manager for Email Archives Directory Database and the Item Databases. These databases contain important data relating to the configuration of the migration as well as the progress, down to the individual item level.

TIP: It is a best practice to perform nightly full backups of each of the databases. This will ensure the shortest recovery time.

Other backup types are supported; however, it may lengthen the recovery time if a database restore is needed.

Details for configuring database backups for specific versions of SQL Server is outside the scope of this document.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating