How does TransVault connect to 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.
How can TransVault help with my Enterprise Vault move?
The first migration solution to be certified for use with Enterprise Vault, and available from global network of TransVault Certified Migration Masters, including Veritas Partners and Veritas Consulting Services, TransVault™ quickly and securely migrates legacy archived email into, out of, and around the Enterprise Vault (EV) platform.
Example migration scenarios include:
- Moving from an ‘unsatisfactory’ or obsolete archive into EV (virtually all third-party email archives and common email formats, including PST, EML, MSG and NSF files, are supported)
- EV upgrades – using TransVault you can migrate EV versions as early as V5 to the latest release
- EV storage moves to protect against obsolescence and lock-in (e.g. extraction from EMC Centera)
- Standardization onto EV (e.g. where merging organizations have incompatible systems)
- Staff relocations between different archive stores (vaults)
- A move to hosted solution (e.g. Enterprise Vault.cloud or Microsoft Office 365)
- Conversion of an EV for Lotus Notes archive to an EV for Exchange archive (and vice versa)
All data movement is fully audited to ensure chain-of-custody, and mailbox shortcuts are fully managed to ensure a seamless experience for end users as they move.
Can TransVault help re-architect our Enterprise Vault archive?
Yes. Although with Enterprise Vault V8 SP4 the Move Archive tool was introduced to enable storage upgrades or moves, this utility is only suitable for moving smaller amounts of data such as individual mailboxes.
Using TransVault you can initially profile your existing archive usage – e.g. how much storage is being used, how many archive stores there are, the average mailbox size, total number of items etc.
You can then be selective in what you migrate and to where. E.g. you might want to migrate a department of users at a time to a specific new archive store or re-group users according to archive storage consumption.
Compliance regulations permitting, it’s also possible to:
- Move just the last n years-worth of data,
- Move only the data that users still have shortcuts to,
- Not move emails that have [SPAM] in the subject, etc
TransVault can also be used to quickly move old vaults into the newer EV OSIS architecture, resulting in great storage benefits.
You might also want to move from a single EV server to a failover cluster or move your data from legacy storage, such as EMC Centera, to a new storage platform.
TransVault can be used to consolidate vaults belonging to different organizations and domains. This includes the ability to re-write internal email addresses (where permissible) such that retrieved emails can be replied to without having to edit the email address manually.
Migrator can filter items by user, groups, folders and dates, thus enabling data to be incisively migrated.
TransVault can also re-write internal email addresses in sender and recipient fields so that the email is usable with any new domain naming or recipient-addressing conventions.
How does TransVault compare with using EV Extraction Wizard?
EV has it own Wizards that enable data to be extracted and imported to/from PST files.
Issues specifically associated with using ‘native’ EV migration tools include:
- It’s slow – This is a single-threaded process which is intended for simple mailbox moves. It is not intended for wholesale migrations. It is also just half of the migration exercise – see notes below.
- It’s manually intensive – The native tool needs to be manually overseen (i.e. you could not batch several mailboxes to migrate unattended overnight).
- There’s no error logging – If a mailbox extraction fails owing to a corrupted email, the extraction will stop with no indication of which item was corrupted and no ability to pick up where you left off.
- Lacks flexibility – There is no support for migrating BCC’d and distribution list recipients from journal archives, no ability to re-write addresses, etc.
- There’s no auditing and minimal reporting.
- No shortcut awareness – The EV Wizard does not have awareness of which items have shortcuts. This means if you export data, it will be everything in the archive, which will mean users are presented with data they believe was deleted years ago. So not only do you have a storage space issue, you have user issues as well. Likewise shortcuts in user’s mailboxes will not be converted or re-hydrated as the corresponding items are migrated.