Requirements overview
To best support your SQL server and the needs of a migration, its recommended that all production Archive Shuttle deployments run on a dedicated instance of Microsoft SQL Server.
Archive Shuttle is a feature-rich product and can therefore result in very diverse SQL Server load profiles between customer deployments. As Archive Shuttle 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 Archive Shuttle 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 Archive Shuttle databases if deployed as multiple SQL servers.
Hardware considerations
Archive Shuttle requires a number of SQL databases:
·The Archive Shuttle Directory database holds the configuration information.
·EachArchive Shuttle Item database holds item information for a link. For every source link, there needs to be an item database.
The SQL Server that manages these databases must reside on a separate server than the Archive Shuttle core and modules. The only exception is for a non-production pilot/demonstration system. Its also recommended that it has a dedicated SQL Server instance thats not shared with other applications.
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.
|
|
CAUTION: ·Performance of the migration will be impacted if the SQL Server environment is not sufficient for the needs of the migration. ·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. |
Configuration requirements for a small migration
The table below indicates the requirements for SQL Server for a smallArchive Shuttle migration (less than 5 Tb).
|
Component |
Configuration |
|---|---|
|
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 practies with TempDB, databases and logs on separate disks. |
|
Virtualization |
Supported, however performance may be impacted if resources mentioned above are not dedicated |
Configuration requirements for a medium migration
The table below indicates the requirements for SQL Server for a medium Archive Shuttle migration (less than 20 Tb).
|
Component |
Configuration |
|---|---|
|
Processors (cores) |
Minimum 8, Recommended 16 |
|
Memory |
Minimum 32 GB, Recommended 64 GB |
|
Hard disk |
Disks should be configured as per Microsoft SQL Server best practies with TempDB, databases and logs on separate disks. |
|
Virtualization |
Supported, however performance may be impacted if resources mentioned above are not dedicated |