Part 2 of Our Interview with CTO Michel Zehnder
Last week we kicked off the first part of our 3-part interview with our CTO, Michel Zehnder. We explored some of the advantages of using ArchiveShuttle over more traditional archive migration approaches. This week we discuss the benefits of ArchiveShuttle’s modular approach.
Would you explain in more detail, what benefits ArchiveShuttle’s modular approach provides the customer?
Of course. As I mentioned before, utilizing ArchiveShuttle offers much more flexibility, improved performance and reliability throughout the migration.
Let me give you an example. Consider a migration from Enterprise Vault into another system, it doesn’t matter if it’s another enterprise vault system, Exchange or cloud platform.
Even in medium size environments you’ll typically find more than one server running Enterprise Vault. Each server can handle multiple vault stores. We typically deploy extraction modules to each Enterprise Vault Server. Within ArchiveShuttle we can assign exactly which module is responsible for which task which provides greater flexibility in terms of scaling the migration.
As our Modules are deployed locally to the archiving servers, we avoid additional network hops during the extraction. From a performance perspective, it’s important to get them as close as possible to the archiving backend and in the case of the Enterprise Vault example, as close as possible to each storage service of EV which is responsible for a vault store.
If you are going to migrate 100 million items, and the network/API delays take just 100 additional milliseconds for each item, we’re talking about 2700 hours or 115 days additional migration time which we can avoid via local deployment.
Last but not least, the reliability of the migration will be increased. Consider if you need to reboot one of the EV Servers, or the EV Services are down for some reason. This would only affect the particular vault server and the particular module. If you have a longer outage, you just create another module running on another server responsible for those vault stores residing on the server that’s down.
Next week, in the last of our 3 part series, we look at how Sync’n’Switch contributes to the ArchiveShuttle approach to migration.
Missed part 1? Find it here