Why use TransVault for our EAS Migration?
EAS was originally developed in Canada in the late 1990’s by a company called Educom. After a few years this company was bought out by Zantaz which was later bought out by Autonomy, who is now owned by HP.
Throughout EAS’ chequered history, TransVault has had a deep understanding of the EAS architecture and the different challenges introduced by different (and sometimes buggy) versions.
By working with TransVault software you can be assured of a seasoned solution and support capability that can help with issues such as:
- Accessing items that have been orphaned and are not retrievable via the EAS API
- Extracting archives from an EAS service that is non-operational
- Working with an archive service that is heavily loaded
- Support for both SQL and Oracle databases
- Migration of either Notes or Exchange EAS archives
- Support for EAS configurations that use email attachment single-instancing
TransVault also offers extremely high speed migrations, advanced shortcut handling and 100% chain of custody for compliance-led migrations.
EAS journal archives can also be moved to your preferred destination, with TransVault ensuring that all vital meta-data is protected and correctly aligned to your target system. This includes the ability to support the new Office 365 compliance model.
How does TransVault connect to EAS?
TransVault connects to EAS through either an API or Direct Access connector.
The API works by querying the EAS IIS Server for the message and waiting for the G-Zip archive message (which is then migrated by TransVault to your preferred destination).
The direct connector is useful for accessing orphaned archived content. It can also be faster than using the API as you are not required to wait for the EAS IIS Server. Instead TransVault connects straight to the archive database, locate and transfer messages directly from the file stores.
What happens to shortcuts (stubs) when we migrate to Office 365?
TransVault provides a comprehensive shortcut management service that ensures users have a seamless experience when they migrate.
When moving to Microsoft Office 365 (or Exchange), legacy EAS shortcuts are replaced (rehydrated) with the original item. You can also set policies that determine whether items are moved into Primary mailboxes or In-place Archives. For example, you could move items older than 2 years into archives, and keep everything ‘younger’ in the Primary mailbox.
Another key feature designed to ensure a great user experience is that TransVault synchronizes with the current status of users’ shortcuts as they exist in their mailbox at the time of the migration.
For example, where users have re-foldered their shortcuts ‘post-archiving’, TransVault ensures the corresponding items end up in the right folders post-migration.
Similarly, where users have deleted their shortcuts, you can configure TransVault not to migrate the corresponding item, as this is confusing and causes concern for end users when deleted items reappear.
How quickly can we move our archives from EAS to Office 365?
Migration speeds into Office 365 from on-premises archives such as EAS have been measured in excess of 2TB a day.
As well as running multiple threads on a single server and across single mailboxes, multiple TransVault servers can be configured to operate in parallel and:
- Extract from multiple maiboxes and multiple file stores at once from your EAS environment
- Migrate to many Office 365 mailboxes simultaneously
- Have multiple migration tasks operating in parallel on individual extra large mailboxes
The transfer of emails across the network and into Office 365 is achieved using TransVault CloudStream, which ensures the fastest, most efficient mechanisms are used to manage the movement of data into Microsoft’s cloud. This includes the use of traffic flow analysis techniques to ensure we always use the smartest ways to migrate data – minimizing network traffic and maximizing Office 365 ingestion rates.
Note, however, that achieving best performance is dependent on many factors such as:
- Microsoft throttling policies
- Whether you host migration services on-premises or in the cloud
- Available network bandwidth
- Loading on the legacy email archive
- The speed of the storage subsystem on which the legacy archive sits
- The scheduling of other project elements such the commissioning of the target environment.
Your chosen archive migration partner can establish a proof of concept (POC) to establish likely throughput rates in your specific environment.