Chat with us, powered by LiveChat

Blog

Back

Part 1 of Our Interview with CTO Michel Zehnder

27 Nov 2014 by olpa

In the first part of a 3-part interview with our CTO, Michel Zehnder, we explore the key differences in using Archive Shuttle over more traditional migration methods.

Michel, would you tell us why Archive Shuttle is a next generation Migration Tool? What is the difference between QUADROtech’s approach versus traditional methods?

MICHEL:
That’s a very interesting question. We’ve found that 1st and 2nd generation solutions are working much like a normal copy process just with some additional preparation.

The traditional 3-step approach to archive migration

First, you need to create new archives for the users you want to migrate and disable them on the old archiving system.

Second, create a mapping table in excel or as a CSV to map source to target archive. Next, the content will be copied to the new archive. The risk here is that because extraction and ingestion are performed simultaneously, the migration application or server itself may become the bottleneck due to every single byte flowing through it.

Last but not least you will have to process all the shortcuts in the mailboxes. All these steps have to be taken more or less manually, without the advantage of a specified workflow.

Why is Archive Shuttle better than the traditional approach to migration?

Unlike the traditional method, we take a modular approach and can spread the load over the archiving servers in a simpler way without letting the migration software become the bottleneck. In our concept, no migration content flows through the migration server which results in faster migration speeds and more flexibility in terms of planning your project.

Second, we don’t try to migrate every item in an archive in a single shot. We use a multi-stage migration approach called “sync ‘n switch” which allows us to uncouple data from user migration. We synchronize the items between source and target up-front to the user-migration. When I talk about synchronization, I include the ability to migrate deltas. You can even keep the archiving active on the source site during the migration and everything will catch up automatically.

Last but not least, we have included several workflows into the product that allows for automation of provisioning and ensures no user disruption during the migration. The shortcut conversion or deletion is performed automatically too as a part of the workflow.