Today we are announcing that Enterprise Vault.cloud supports journal archiving from Microsoft Exchange Server 2013, which is great news for our customers considering an upgrade to the new platform. It is also great news for organizations that may not have an archive in place yet, but are looking to add one to help streamline their migration process (more on that here), while meeting their long-term information retention requirements and eDiscovery needs.
Any time I discuss the migration process with a customer, the conversation almost always turns to ingestion, which makes sense (if you are taking it out of one place, you likely need to put it in another place, right?).
Let’s cover what I mean by “ingestion” when talking about Enterprise Vault.cloud – this is a carefully outlined process followed by our specially-trained Data Management team that allows us to import our customers’ legacy information into Enterprise Vault.cloud. With so many organizations currently considering a move to a cloud archive, this is an important piece of the process. Some of these organizations have an existing on-premise archive and want to migrate to a cloud service, while other organizations are deploying an archive for the first time.
In either instance, these customers have legacy data that needs to be ingested into Enterprise Vault.cloud in order to meet their long-term information retention requirements. They also want to give their end users the ability to search, retrieve and restore business-critical information that may no longer reside in their inboxes.
Below are responses to some of the frequently-asked questions I get about this process -
What do you mean by legacy data?
Legacy data means information stored in an old or obsolete format that is difficult to access or process. Some examples include:
- Local archives (e.g., PST/NSF files) on desktops, laptops and servers
- Email stores (e.g., Microsoft® Exchange and IBM Domino®) on servers
- Legacy email archives (e.g., EMC EmailXtender®, Zantaz®, Mimosa®)
- Backup tapes
What formats of legacy data do you accept?
The Data Management team accepts data from customers in a variety of formats including PST, EML, MSG and NSF.
Is chain of custody preserved throughout the ingestion process?
Yes. Each team member is focused on preserving chain of custody throughout the ingestion process and working with the customer to ensure that their legacy data is properly ingested into the archive.
Is legacy data indexed and available for search in the archive?
Yes. Information is indexed as part of the ingestion process and then made available for search to end users via their personal archives and to administrators via the discovery archive.
Can you preserve folder structure for my users upon ingestion?
Yes. If you provide us with the legacy data in PST format, the Data Management team can preserve folder structure upon ingestion so that users see their legacy folder structure within their personal archives.
Can legacy data be exported out of the archive?
Yes. Information can be exported out of the archive in EML, PST, MSG, and NSF formats, with or without EDRM XML files, and this includes anything that was converted during import (it gets converted to the requested format on export when necessary).
How can I get more information on this process?
Please contact your Symantec account manager or reseller today for more information or call 877-253-2793.