Chat with us, powered by LiveChat

Blog

Back

Scalable Architecture and Workflow

4 Aug 2014 by Andrew Barnes

Scalable Architecture and Workflow

PST FlightDeck is engineered from the ground up to be massively scalable. That means having the potential to migrate hundreds of thousands of files and users spread across multiple geographies. This can only be achieved with a workflow and architecture that is designed to scale.

pst-flightdeck-workflow

PST FlightDeck Workflow

At each stage in the workflow the resources dedicated to migration can be varied across multiple data centers.

Scalability starts with location of PST files. By using an Intelligent Agent the responsibility for location of the files is delegated to the user’s workstation, but under the control of one or more servers to make sure that centralization of the files does not overload available resources. Advanced Centralizing Technology balances workloads across servers and makes use of compression during the network transfer process.

If large amounts of data have to be centralized and bandwidth constraints mean this cannot be achieved in the right timescale disk shipping is available as an option.

After centralization PST files are prepared for ingestion. Multiple servers can be employed to remove passwords, verify against corruption, de-duplicate items and convert from ANSI to Unicode if required.

During the ingestion process again multiple servers can be used, ensuring maximum throughput.

Scalability from an operational management perspective is also covered. Exceptions are managed through an operator interface and there is even a help desk mode to assist users identify the state of a specific PST file, or support specific users during the process, for example the C-Suite.