Archive Shuttle 11.4 - SQL Best Practices

Configuration recommendations for normal migrations

The following configuration enables better tuning of normal migrations, which allows Archive Shuttle to leverage the environment more effectively for superior performance. You may also need consider tuning the following recommendations within your own environment.

Normal mappings to Office 365 need to be configured as wide as possible:

·Try to use smaller batches

oOffice 365 Batch size Bytes - 5242880 (5 Mb)

oOffice 365 Batch size Items - 50

oOffice 365 Timeout seconds - 1800

·Perform a wide migration

oOffice 365 Mailbox parallelism - 150

oOffice 365 Item Parallelism - 5

oOffice 365 Batch parallelism - 2

·Hidden settings configuration

oOffice365NumberOfItemsperContainerMapping (ID - 418)

§The default value (1000) should be sufficient

Confirguration requirements for a large migration

The table below indicates the requirements for SQL Server for a large Archive Shuttle migration (more than 20 Tb).

Archive Shuttle 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.

Configuration recommendations for Journal Transformation migrations

There are two separate cases that could be configured for Journal Transformation migrations:

1.Journal mapping is split into more mappings according to date filter

a.Try to use smaller batches

i.Office 365 Batch size Bytes - 5242880 (5 Mb)

ii.Office 365 Batch size Items - 50

iii.Office 365 Timeout seconds - 1800

b.Perform a wide migration

i.Office 365 Mailbox parallelism - 150

ii.Office 365 Item Parallelism - 5

iii.Office 365 Batch parallelism - 2

c.Hidden settings configuration

i.Office365NumberOfItemsperContainerMapping (ID - 418)

1.The default value 1000 should be enough

2.A big journal is migrated as one migration mapping

a.Try to use smaller batches.

i.Office 365 Batch size Bytes - 1 048 576 (1 Mb)

ii.Office 365 Batch size Items - 5

iii.Office 365 Timeout seconds - 1800

b.Perform a wide migration

i.Office 365 Mailbox parallelism - 150

ii.Office 365 Item Parallelism - 1

iii.Office 365 Batch parallelism - 10

c.Hidden settings configuration

i.Office365NumberOfItemsperContainerMapping (ID - 418)

1.Change the value to 100k. This will allow Archive Shuttle to have items spread across different mailboxes which should increase migration speed.

If there are too many items to migrate just from one big mailbox, consider changing the "Ingest users with most items first" setting:

·Enabled - gets the users with most items to import

·Disabled - get users alphabetically regardless of how many items they have to import

Sharing

Archive Shuttle recommends that Archive Shuttle SQL servers run a single SQL Server instance only, with no other applications or services running on the servers. SQL Server needs to fully utilize the server resources, and another application may introduce contention issues that will result in undesirable performance.