Explore TransVault™

EV Migration to Office 365

How is data extracted from Enterprise Vault?

Developed under the Symantec Technology Enabled Program (STEP), TransVault has connectors that move data directly into or out of Enterprise Vault using the EV approved API.

We recommend using the API wherever possible, as this is the only route that is fully supported by Veritas.

However, TransVault also offers the option of a direct connector into Enterprise Vault.  This is useful where you need to:

  • Extract data from a version of EV that is pre version 7.5 (as there was no published API at this time)
  • Access data where the EV server itself is non-operational
  • Work with an archive service that is heavily loaded (the direct approach avoids impact on end users).

Where high speed is a vital component to your migration, a direct approach can also perform up to 10x faster than using the API.

Where project timelines and operational issues dictate, customers now have the option of using TransVault’s unique hybrid connector, which combines speed with safety:  if an item can’t be accessed using a direct connection, TransVault automatically switches to using the API connector.

For example, not all of the data stored in your EV implementation may be accessible using a direct approach.  This can be the case where data is held on a range of hierarchical storage devices and services (such as Amazon, Rackspace, Dell and Hitachi) that rely on using the EV Streamer API to act as a ‘go-between’.

Ultimately, if your migration needs to meet Veritas recommendations, you can use the API exclusively – the great thing is that TransVault gives you the choice, which is also totally unique.

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 EV 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.

EV usually does a good job of synchronizing the location of shortcuts, however there are some scenarios where deletions might not be picked up by EV.   An example is where users drag their shortcuts into the Outlook deleted items folder, rather than highlighting them and using the delete option that links with EV.

How quickly can we move our archives from EV to Office 365?

Migration speeds into Office 365 from on-premises archives such as Enterprise Vault 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 EV environment
  • Migrate to many Office 365 mailboxes simultaneously

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.

Click here to download the PDF