Enterprise Vault (Exchange) — Overview & Migration Guide

This article provides a high-level overview of Veritas Enterprise Vault (EV) for Exchange, why organizations move off EV, what to inventory before migration, common migration approaches, how to cut over journaling to Jatheon Cloud, and how to maintain data fidelity and compliance throughout the process.

What Enterprise Vault Does for Exchange

• Centralized archiving for mailbox and journal data with retention categories, legal holds, indexing, and mailbox shortcuts.
• Key components: Directory DB, Vault Store DBs, Fingerprint DB, Index volumes (EV 10 “old” vs EV 11/12 64-bit), storage partitions/collections, Discovery Accelerator (DA) and Compliance Accelerator (CA).

Why Organizations Move Off EV

• Aging infrastructure, index version sprawl, SQL/storage complexity, end-of-life/version lock.
• Desire for simpler cloud/on-prem options with modern search, supervision, eDiscovery, and lower TCO.
• Consolidation to Microsoft 365/Exchange Online and journaling to a dedicated archive.

Inventory and Mapping Before You Start

• Archives: user mailbox vs journal; sizes, item counts, oldest/newest dates.
• Retention: categories, schedules, exceptions; map to new policies 1:1 where possible.
• Legal holds/cases: DA/CA holds and in-flight exports; plan to preserve holds during cutover.
• Shortcuts: count and age; decide on rehydration vs clean-up strategy.
• Index state: EV 10 vs 11/12; rebuild needs; failed/missing indexes.
• Storage: DVS/DVSSP locations, safety copies, collections/recalls; available throughput.

Common Migration Approaches

1. EV native export — Export Wizard or DA to PST, MSG/EML + metadata; preserves headers and can include original journal reports. Pros: predictable, supported. Cons: slower, operator-intensive at scale.
2. API/third-party extraction — parallelized export directly from Vault Stores with chain-of-custody logs; better at scale; can reconstruct journal envelopes and BCC.
3. Journal-first cutover (coexistence) — Day 0: switch Exchange/M365 journaling to Jatheon; keep EV read-only for historical access; migrate historical EV data in waves.

Journal Archives — Specifics

• Preserve the full journal report (envelope) including BCC and DL expansion.
• Deduplication: keep per-envelope identity, not per-recipient duplicates.
• Validate Message-ID, Received headers, and SMTP envelope integrity.

Mailbox Archives — Specifics

• Shortcuts: options include rehydrating items before export, exporting archived items and removing shortcuts, or leaving shortcuts with a read-only EV for a transition period.
• Scope: confirm whether calendars/contacts/tasks are in scope; mail is typical default.

Exchange / Microsoft 365 Journaling Setup with Jatheon

• Exchange on-prem: create a Send Connector to Jatheon SMTP, a Journal Rule to the connector; enforce TLS and size limits; set an alternate journaling mailbox for NDRs. (See your Exchange journaling guide.)
• Microsoft 365: use an external journal address and a secure connector (TLS), safe-listing; confirm data residency and transport encryption; monitor undeliverable journal reports.
• Validation: run controlled tests (small distribution groups, high-volume senders), then cut over.

Data Fidelity and Compliance

• Chain-of-custody: hash at ingest, immutable (WORM) storage, and a full audit trail.
• Preserve original headers, Message-ID, sent/received timestamps, and the journal envelope.
• Map EV retention categories and legal holds to Jatheon retention/hold constructs 1:1 where possible.
• Supervision: define review policies to match or improve upon EV CA policies.

Throughput and Timelines (Planning Ranges)

• EV export: often 50–250 GB/day per EV server depending on index health, storage, and item size mix.
• Parallelization across archives/servers is key; network and disk IOPS are common bottlenecks.
• Jatheon ingest commonly exceeds EV export rates; plan for at least 1.5–2× ingest headroom.

Pitfalls to Watch

• Old/failed indexes causing slow or partial exports.
• Orphaned savesets, missing DVS files, safety copies not cleared.
• Active DA legal holds blocking deletions — coordinate with Legal for hold migration.
• Timezone/encoding edge cases; primary SMTP alias changes over the years.
• Shortcut clean-up that breaks user experience if timing isn’t planned.

High-Level Migration Plan

1. Scope: EV version(s) and index versions; TB and item count; user vs journal split; number of archives; legal holds; retention map; shortcut counts; SQL/storage layout.
2. Pilot: select 2–3 user archives and a slice of journal (e.g., 30–60 days); validate fidelity and search.
3. Journaling cutover: configure journaling to Jatheon; run coexistence while bulk export/import proceeds.
4. Bulk waves: migrate in waves; monitor success rates, hash counts, and spot-check searches/exports.
5. Decommission: only after Legal sign-off, hold verification, and shortcut strategy completion.

What We’ll Ask to Prepare a Precise Plan/Quote

• EV version(s) and index versions; total data (TB) and message count; number of user archives and size of journal archive.
• Retention categories and any legal holds/cases.
• Shortcut policy details and desired end state.
• Exchange/Microsoft 365 topology and TLS requirements.
• Any non-Exchange content in EV (ignore if Exchange-only).