Jatheon Support Center

Your go-to place for product documentation, guides, and troubleshooting tips.

Search

Autonomy Message Manager (CAMM)

Steven Tobolar
Steven Tobolar
  • Updated

Autonomy Message Manager (CAMM) Migration to Jatheon Cloud

This guide explains how to migrate email archives from Autonomy Message Manager (CAMM) to Jatheon Cloud. It covers prerequisites, discovery, export options (EML/MSG/PST), metadata transformation, ingestion, and validation to ensure full integrity and compliance. Note that CAMM is historically related to CA Message Manager and earlier iLumin Assentor, so you may encounter those names in tools and documentation.

Prerequisites

  • Inventory of CAMM repositories (custodians/journals), data volumes, retention/hold policies, and integrations.
  • Admin access to CAMM management console and underlying storage (databases/indexes/file shares/object storage).
  • Export/read permissions for message and metadata stores.
  • Pilot plan (sample custodians/journals) and a CSV mapping for target mailboxes or archive custodians.
  • Access to your Jatheon Cloud tenant for ingestion and verification.

Tip: CAMM is often referenced under legacy names such as CA Message Manager or iLumin Assentor. Use these aliases when searching for connectors and migration references.

Overview

Autonomy Message Manager (CAMM) was used to archive, supervise, and discover emails for Microsoft Exchange and sometimes Notes environments. A successful migration should account for user and journal archives, envelope/recipient context, retention and legal-hold states, and supervision/quarantine metadata where present.

Supported Source Scenarios

  • User mailbox archives (Exchange).
  • Journal archives (preserve full envelope/recipient detail, including BCC where available).
  • Mixed/legacy environments referenced as CA Message Manager or iLumin Assentor.

Export Options

  • Preferred formats: EML (full RFC822 headers) or MSG (MAPI) with attachments and original timestamps.
  • PST as intermediary: acceptable if later itemized; plan manifesting/deduplication.
  • Selection: filter by custodian, date range, folder class; exclude Junk/Deleted by policy; include legal-hold items.
  • Journal context: include envelope headers (e.g., BCC, original recipients) for auditing.

Sample CSV manifest header (extend as needed):

FullPath,RelativePath,FileName,SizeBytes,LastWriteUTC,SHA256,Custodian,Folder,InternetMessageId,IsJournal

Example PowerShell to compute SHA-256 and build a manifest:

$Root="D:\CAMM\Exports" $Out="D:\CAMM\manifests\camm_manifest.csv" $files=Get-ChildItem -Path $Root -Recurse -File -Include *.eml,*.msg $rows=foreach($f in $files){$h=Get-FileHash -Algorithm SHA256 -Path $f.FullName;[pscustomobject]@{FullPath=$f.FullName;Relative=$f.FullName.Substring($Root.Length).TrimStart('\');FileName=$f.Name;SizeBytes=$f.Length;LastWriteUTC=$f.LastWriteTimeUtc;SHA256=$h.Hash}} $rows|Export-Csv -NoTypeInformation -Path $Out -Encoding UTF8

Technical Notes

  • Data layout — CAMM repositories typically store items plus indexes/metadata; ensure access to both to preserve fidelity.
  • Supervision/Discovery — Export supervision/quarantine state and discovery tags where applicable to maintain compliance context.
  • Deduplication — Use a composite key (e.g., SHA-256 + InternetMessageId + SizeBytes) pre-ingestion.
  • Chain of custody — Keep export logs, manifest hashes, and transfer checksums.

Migration Scope

  1. Discovery — Inventory custodians/journals; capture item counts, sizes, date ranges, legal holds.
  2. Export — Extract messages, attachments, and metadata (EML/MSG preferred) with envelope context for journals.
  3. Transform — Normalize fields (sender/recipient, InternetMessageId, folder path, retention/hold flags) to Jatheon’s schema.
  4. Ingestion — Import to Jatheon Cloud in phased batches; throttle as needed; monitor exceptions.
  5. Validation — Reconcile counts; spot-check headers, attachments, and date ranges; verify search parity and hold mapping.
  6. Cutover — Activate retention policies and obtain stakeholder sign-off.

Troubleshooting

  • Long paths / invalid characters — Normalize file/folder names; log mappings; for Windows copies consider robocopy /256.
  • Missing attachments — Confirm export includes attachments; re-run failed batches; check tool filters.
  • Journal envelope lost — Ensure export includes envelope headers (incl. BCC) and ingest them as journal metadata.
  • Encoding — Prefer UTF-8; verify body/headers render correctly post-ingestion.
  • Throughput — Batch by custodian/date; limit concurrency to avoid I/O/API bottlenecks; throttle ingestion if required.
  • Access denied — Re-validate read permissions to CAMM repos, DBs, and file shares; use a service account with explicit rights.

What We Preserve

  • Message bodies and attachments (original formats)
  • Headers and delivery metadata (incl. InternetMessageId)
  • Custodian/mailbox relationships and (where present) journal context
  • Folder hierarchy and labels (as exported)
  • Retention markers and legal-hold/supervision flags (mapped)

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.