How is data extracted from EAS?
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. EAS is now supported and developed by a company called Capax.
TransVault was the first vendor to offer EAS migrations and 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 into Enterprise Vault
- 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.
You can also migrate journals that have been archived using EAS directly into EV journal archives, with TransVault ensuring that all vital meta-data is protected and correctly aligned to your target system.
How is data moved between EAS and EV?
EAS archives are moved in one step, directly into Enterprise Vault.
There’s no need for interim disk space or need to convert into interim formats (such as PST or EML files) during migration. This saves both cost and time. It also preserves chain-of-custody as your data is moved.
TransVault moves data into your EV environment using a connector which uses the approved Enterprise Vault API. In fact TransVault was the first migration solution to be approved under the Symantec Technology Enabled Program (STEP). This ensures 100% reliability for your move.
What happens to old EAS shortcuts (stubs) when we migrate to EV?
TransVault provides a comprehensive shortcut management service that ensures users have a seamless experience when they migrate.
EAS shortcuts (aka stubs) are converted into EV shortcuts ‘on the fly’.
This activity can take place whilst users are online – there’s no need for any downtime or for users to logout.
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.
Can we migrate EAS archived journals into EV archives?
Yes. You can move EAS journal archives into EV journal archives. To do this TransVault reconstructs EAS journals into the format required by EV.
It also offers many other capabilities that will ease your move, including the ability to split journals (and other large mailboxes) into a number of separately handled virtual mailboxes of a user-defined size. This allows multiple processing threads to be applied to the migration of a single journal mailbox, significantly speeding up the migration task.
You also get full chain-of-custody and detailed audit tracks as your data is moved, enabling you to satisfy the most demanding compliance needs.
How fast can we migrate EAS archives into EV?
Migration speeds into EV from 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 vaults at once from your EAS environment
- Migrate to many EV archive mailboxes simultaneously
- Process large archive mailboxes (such as journal and Public Folder archives) with multiple tasks
Note, however, that achieving best performance is dependent on many factors such as:
- Available network bandwidth
- Loading on the legacy email archive
- The speed of the storage subsystem on which the legacy archive sits
- How busy your EV servers are
Your chosen archive migration partner can establish a proof of concept (POC) to establish likely throughput rates in your specific environment.