Shire produce incredibly fast speeds of 7TBs per day whilst moving its legacy email records using TransVault
With customer archives growing exponentially, the timelines involved in migrating data workloads to the cloud are becoming a critical factor in choosing the optimum onboarding strategy.
The rush to re-locate is being fuelled by the fact that organizations are looking towards Office 365 to meet their compliance and eDiscovery needs relating to sensitive, personal information held in historic archives and email journals.
Migration leader, TransVault, offers a proven, end-to-end cloud migration capability for sensitive data, and is continually working on enhancing its performance.
Recently in Australia, Shire recorded a sustained migration throughput between an on-premises legacy archive and Microsoft Office 365 of 6.7 TB a day.
This incredible performance was sustained across multiple days and the project completed in record time, much to the delight of the Shire team responsible.
TransVault has ultimate confidence and pride in its technology and support for Partners around the globe. Migrations can be complex and aren’t just about speed. TransVault was at the inception of the email archive migration market some 12 years ago and has the longest experience of any company in the world alongside the widest, optimized support for 22 source archives and 18 targets.
Read more about Shire’s overall journey to Office 365 here:
https://customers.microsoft.com/en-us/story/shire-healthcare-office-365
Facts & Figures
Office 365 –Â Throttling not removed
TransVault Environments =Â 2 x TransVault 32 bit servers* & 1 x SQL database
Peak Individual Environment Performance =Â 3.6TB/day, 21.1 million items
Migration Task Setup =Â 40 retrieving threads, 40 processing threads and 40 max running threads
*64bit TransVault Servers now available!
NOTE:Â Â
It is important to note that achieving best performance for your own migration will always be dependent on environmental factors such as available network bandwidth, the speed of the storage subsystem on which your archive sits and scheduling of other project elements such the commissioning of the target environment.
