Migration Manager for PSTs permits the ability to scale out an environment to offload the burden on any given system in the environment. For small and mid-sized projects with no special requirements, a standard deployment may be sufficient. For larger environments or projects with tight time requirements, processing modules may be distributed over several machines to scale the system to match the environment's needs or reduce bottlenecks in the workflow. These computers with module components of Migration Manager for PSTs installed are referred to as "nodes".
When considering the scalability of your Migration Manager for PSTs environment there are many factors to consider. Please consult a qualified Migration Manager for PSTs Architect prior to scaling out an environment.
Part of the flexibility of Migration Manager for PSTs is the modular approach that is taken within its architecture. The functions required to perform a migration can be run over multiple nodes. This permits many of the same modules to be run in parallel or assigned to specific locations.
Module Nodes are servers with Migration Manager for PSTs modules installed on them. They encompass all Migration Manager for PSTs servers containing modules and not included in another node type. Module nodes can be used to scale processing of any module workload to permit rapid processing of items uploaded.
Most Module Nodes do not have any special considerations outside of resource availability and the ability to communicate to the Core. Extraction and repair nodes have high disk requirements and are typically located on the machine with the highspeed disks used for the BITS upload directory.
Ingestion Nodes are Module Nodes that include an Ingestion module. They are typically deployed to support geographically distributed resource allocation within Migration Manager for PSTs. Multiple ingestion nodes may also be leveraged to expedite the timeline to project completion when appropriate.