Frequently Asked Questions Akaibu Evolve for Microsoft Exchange & Office 365



Similar documents
Frequently Asked Questions TransVault Migrator for Microsoft Exchange & Office 365

TransVault Migrator Frequently Asked Questions

Frequently Asked Questions: TransVault Migrator for HP Autonomy Archives

Frequently Asked Questions: TransVault Migrator for Migrations to the Cloud

Frequently Asked Questions: TransVault Migrator for EMC SourceOne

Frequently Asked Questions: TransVault Migrator for Symantec Enterprise Vault

Beyond Data Migration Best Practices

Archive Migrator. Publication Date: January, Metalogix International GmbH, All Rights Reserved.

Enterprise Vault Whitepaper

FIVE TIPS FOR A SUCCESSFUL ARCHIVE MIGRATION TO MICROSOFT OFFICE 365 WHITEPAPER

Product Overview Archive2Anywhere Message Stub Management

Archive Migrator Install Guide

Symantec Enterprise Vault.cloud Overview

Enterprise Vault.cloud. Microsoft Exchange Managed Folder Archiving Guide

Microsoft Office 365 Migrations with Symantec Enterprise Vault.cloud

Symantec Enterprise Vault and Symantec Enterprise Vault.cloud

MIGRATING YOUR EMC SOURCEONE ARCHIVE

Veritas Enterprise Vault.cloud for Microsoft Office 365

Take Advantage of Newer, More Powerful and Flexible Solutions: Exchange 2010/2013, or Cloud Solutions such as Office 365

Capstone Compliance Using Symantec Archiving and ediscovery Solutions

EXCHANGE TO OFFICE 365

EMC PERSPECTIVE EMC SourceOne Management

Microsoft Exchange Online Archiving and Symantec Enterprise Vault.cloud

W H I T E P A P E R. Symantec Enterprise Vault and Exchange Server November 2011

Solution Brief. Archiving from Office 365 for Compliance and ediscovery. 1) Capture Everything

Enterprise Vault Whitepaper Move Archive Feature Overview

Four Things You Must Do Before Migrating Archive Data to the Cloud

Symantec Enterprise Vault.cloud Overview

ARCHIVING FOR EXCHANGE 2013

ILM et Archivage Les solutions IBM

WHITE PAPER. Archiving and Sharing with Doclook Reach Extension to Microsoft Outlook

Exchange Mailbox Protection Whitepaper

Envelope (SMTP) Journaling for Microsoft Exchange 2007 and 2010

Enterprise Vault.cloud and Office 365 As you move to the cloud, don t forget your archive

Capstone Compliance Using Symantec Archiving and ediscovery Solutions

Exchange Brick-level Backup and Restore

Data Sheet: Archiving Symantec Enterprise Vault for Microsoft Exchange Store, Manage, and Discover Critical Business Information

RELEASE NOTES Product Version: 7.2 Date: November, 2015

Symantec Enterprise Vault.cloud Giovanni Alberici

White Paper. Mimosa NearPoint for Microsoft Exchange Server. Next Generation Archiving for Exchange Server By Bob Spurzem and Martin Tuip

Comparison Document. Comparison between LepideMigrator for Exchange & Lepide Exchange Recovery Manager

# Is ediscovery eating a hole in your companies wallet?

PST Migration with Enterprise Vault 8.0: Part 1 - Solution Overview. Author: Andy Joyce, EV Technical Product Management Date: April, 2009

8 POINT PLAN TO ELIMINATE PST FILES

Data Sheet: Archiving Symantec Enterprise Vault Discovery Accelerator Accelerate e-discovery and simplify review

GroupWise to Exchange 2010 Migration

10 Reasons Why Enterprises Select Symantec.cloud for Archiving

itg CloudBase is a suite of fully managed Hybrid & Private Cloud Services ready to support your business onwards and upwards into the future.

Symantec Enterprise Vault for Microsoft Exchange

Overview. Datasheet: Centerprise Connector for Salesforce. Key Features. Overview

Solve your PST headaches with or without Archiving

White Paper. Solve Exchange Storage Problems Once and For All. A New Approach without Stubs or Links. By Bob Spurzem. April Mimosa Systems, Inc.

REDCENTRIC MANAGED ARCHIVE SERVICE SERVICE DEFINITION

Performance Optimization Guide

Exchange 2010 migration guide

Envelope (SMTP) Journaling for Microsoft Exchange 2007 and 2010

Archiving Technology Trends May Report #639 Ferris Research Analyzer Information Service

Whitepaper: Globanet Cloud Enablement Service

ANSWERS TO FREQUENTLY ASKED QUESTIONS

Office 365 Migration Performance & Server Requirements

GFI Product Guide. GFI Archiver and Office 365 Deployment Guide

Symantec Enterprise Vault for Microsoft Exchange

Exclaimer Mail Archiver User Manual

How To Use Gfi Mailarchiver On A Pc Or Macbook With Gfi From A Windows 7.5 (Windows 7) On A Microsoft Mail Server On A Gfi Server On An Ipod Or Gfi.Org (

GFI Product Manual. GFI MailArchiver Outlook Addon

Release Notes P/N Rev 01

Why you need Cryoserver for your Office 365 cloud service

Symantec Enterprise Vault E-Discovery Connectors

Symantec Enterprise Vault

The evolution of data archiving

PRODUCT GUIDE. L e p i d e S o f t w a r e P r i v a t e L i m i t e d

WHITE PAPER. Symantec Enterprise Vault and Exchange Alex Brown Product Manager

Archiving Troubleshooting Guide

CA Message Manager. Benefits. Overview. CA Advantage

Using EMC SourceOne Management in IBM Lotus Notes/Domino Environments

SonaVault Archiving Software

GFI Product Guide. GFI MailArchiver Archive Assistant

Information Management Advice 27 Managing

CMT for Notes. Installation Guide

How to successfully migrate from GoogleApps

CompareScope. Office 365 Migration Solutions

ARCHIVING. What it is, what it isn t, and how it can improve your business operations

Addressing Archiving and Discovery with Microsoft Exchange Server 2010

How To Set Up A Journaling Mailbox In Microsoft Office 365 And Gfi Mailarchiver

Archive Attender. Version 3.2. White Paper. Archive Attender is a member of the Attender Utilities family.

Symantec Enterprise Vault.cloud Compatibility List. March 13, 2015

VMware vsphere Data Protection 6.1

CMT Self-Service Archive Migrator 1.2. Comprehensive User Guide

TO BE OR NOT TO BE (Archiving), That is the question!

Transcription:

Table of contents: Q1. What is Akaibu Evolve for Microsoft Exchange & Office 365?... 2 Q2. What archives are supported?... 2 Q3. Will I need to buy services?... 3 Q4. Why not just import our legacy archive to Exchange via PST files?... 3 Q5. I would like to upload users PST files into Exchange/Office 365. How does Evolve help?... 4 Q6. Can Akaibu Evolve help manage what we upload into Exchange?... 4 Q7. How quickly can Akaibu Evolve migrate archived items?... 4 Q8. How can I find out if Evolve has migrated all of the data?... 5 Q9. What happens if an item fails to migrate?... 5 Q10. How does Evolve aid compliance when migrating?... 5 Q11. What do you mean by chain of custody and why is it important?... 6 Q12. Why do Exchange Journal Archives require special care?... 6 Q13. I want to move to a hosted email Exchange service - can Evolve help?... 6 Q14. We are involved in a demerger and need to split up our archive. How does this work?... 7 Q15. How can we remove legacy archive shortcuts or stubs from users mailboxes?... 7 Q16. How is Akaibu Evolve licensed?... 7 Q17. Do I need to provide systems to run Akaibu Evolve on?... 7 Q18. Can new connectors be commissioned for development?... 7 Q19. How can I find out more?... 7 Tuesday, Page 1 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 1

Q1. What is Akaibu Evolve for Microsoft Exchange & Office 365? Akaibu Evolve for Microsoft Exchange & Office 365 is a high-performance application that migrates email from myriad legacy third-party archive platforms into Microsoft Exchange on-premises, Office 365 (Exchange Online Archives), or a hybrid environment. Fully certified to run on the Windows platform and one of the first migration applications to support the powerful Exchange Web Services (EWS) API, Akaibu Evolve moves your email records in one step to maintain chain-of-custody. Your move is also fully audited to ensure peace of mind. As you move you can use Akaibu Evolve to perform selective migrations based on multiple criteria enabling you to take only the data you need and minimize the time and cost of your migration. Akaibu Evolve also includes advanced item selection capabilities, to ensure as seamless as possible experience for end users is provided. For example, you can migrate only the items for which a shortcut still exists in the user s mailbox. Example migration scenarios include: Moving from an unsatisfactory or legacy archive solution into Exchange Volume uploads of PST files into Exchange Standardization onto a common archive (e.g. where merging organizations have incompatible systems) A switch to an cloud-based strategy based on Exchange (i.e. Office 365, including Wave 15) Migration from IBM Lotus Notes to Microsoft Exchange (using an Archive First approach) During the migration process, all actions are fully audited to ensure chain-of-custody. Q2. What archives are supported? Akaibu Evolve supports migration into Microsoft Exchange primary mailboxes and personal archives, onpremise and online (via EWS) from a very wide range of proprietary archive including: GFI Mail Archiver EAS for Exchange (ZANTAZ) NearPoint (Mimosa) EMC EmailXtender for Exchange EMC SourceOne for Exchange EML files Metalogix Archive Manager: Exchange Edition Microsoft Exchange On Premise (MAPI) Barracuda Message Archiver Microsoft Exchange Online*/Office 365 (EWS) Microsoft Exchange Personal Archives (EWS) MSG files PST files Quest Archive Manager Symantec Enterprise Vault for Exchange & EV.Cloud Tuesday, Page 2 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 2

You can also use Akaibu Evolve to: Export data out of Microsoft Exchange primary mailboxes and personal archives, on-premise and online. Import and export data from/to industry standard file formats including PST, EML and MSG files Accelerate migrations from/to hosted systems, including Office 365, Mimecast & Enterprise Vault.cloud Perform migration and conversion from Lotus Notes archives to Microsoft Exchange (see also Q14) More platforms are being added all the time. Please visit http://www.akaibu.com/or email Akaibu to ask whether your particular archive platform is supported. Q3. Will I need to buy services? No. Evolve automates most of the data migration process, you will need minimal service and support to plan the migration, install and configure Evolve, and oversee a successful completion. We are so confident in our product that we include service and support free as part of your licensing purchase. Many of our partners are also able to provide and implement your Exchange /Office 365 environment. To contact Akaibu or to find a reseller or partner, please see http://www.akaibu.com/for more information. Q4. Why not just import our legacy archive to Exchange via PST files? Many third-party archive platforms offer the ability to export archived mailboxes to PST files, conversely, Exchange/Office 365 offers tools to assist with PST file ingestion. It s tempting, therefore, to consider a manual approach that uses PST files as an interim format. There are many issues with this manual, PST-driven approach, which include: It s slow and intensive. Native archive extraction and import tools are typically single threaded and needs to be manually overseen (i.e. you could not leave several mailboxes running overnight). This significantly increases the migration time-frame and manpower costs involved. There s no error management. If an extract or import fails, the process stops with no indication of what the problem was and no ability to resume where the process left off or skip (and identify) just the items that fail. There s no logging or auditing. With PSTs there is no record of what data has been moved. All checking of PST actions needs to be done manually and this is subject to human error. PSTs risk the security and integrity of your data. The multi-step process involved in PST migrations mean that files need to be held in an interim location for a length of time, during which they are potentially open to tampering. Chain of custody is broken as a consequence, making a PST-driven migration unsuitable for organizations that have a compliance remit. Large PST files are prone to corruption. This creates problems when extracting large mailbox archives or Journal archives. You ll need lots of interim storage: You ll need to set aside a large amount of space to pre-stage your data as it is migrated. Given that PSTs are notoriously space-inefficient and that you will lose single instance storage, this may be up to 10 times the size of your legacy archive. No ingestion flexibility. With the PST approach you will typically need move all data in a mailbox there s rarely the ability to filter or be selective over what you extract or ingest. By comparison Akaibu Evolve offers automated, multi-threaded, high-speed extraction with full error- logging and chain-of-custody. It also offers advanced data selection and mailbox management capabilities. Tuesday, Page 3 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 3

Q5. I would like to upload users PST files into Exchange/Office 365. How does Evolve help? Evolve offers the most advanced and scalable PST ingestion capability available today. Its features include: Automated, high-speed upload - direct into either Exchange 2007 SP1 and the Personal Archive service introduced with Exchange 2010 Pre-upload analysis of PSTs The ability to filter what is uploaded, e.g.: o Upload emails less than 3 months into the primary Exchange server o Upload emails between 3 months and 2 years old into the Personal Archive service o Don t migrate emails with [SPAM] in the subject or in Personal folders Full logging and auditing of all upload activity Throughput control parameters to limit loading on your live Exchange environment Q6. Can Akaibu Evolve help manage what we upload into Exchange? Yes. Prior to your migration Akaibu Evolve helps analyze 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. Evolve then lets you be selective in what you migrate and to where. For example, you might want to migrate a department of users at a time to a specific Exchange server or re-group users according to 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 data according to criteria including To, From, Subject, Folder, Attachment, Date A migration is therefore a great opportunity to significantly reduce the quantity of email you retain. Q7. How quickly can Akaibu Evolve migrate archived items? Migration speeds from an on-premises archive into Office 365 have been measured at a rate equivalent to 1.2TB a day. Note, however, that achieving best performance is dependent on many environmental factors such as: Available network bandwidth Speed of the storage subsystem on which the legacy archive sits as well as the destination storage The ingestion performance of the target archive system (typical speeds may range from 5-50 GB/hour) The scheduling of other project elements such as the commissioning of the target environment. As well as running multiple threads on a single server, multiple Akaibu Evolve servers can be configured to operate in parallel to ensure that the performance of the Evolve services is never a limiting bottleneck for the duration of the project. Akaibu Ltd., or certified partner, can establish a proof of concept (POC) to find likely throughput rates in your specific environment. Tuesday, Page 4 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 4

Q8. How can I find out if Evolve has migrated all of the data? Akaibu Evolve includes auditing functions that keep track of the migration of each individual item. If the migration of an individual item fails (e.g. owing to data corruption, system configuration or connectivity issues) tasks can be automatically re-run to target just these items, adding them into the new Exchange mailbox alongside items that were previously successfully migrated. Reporting is also available to highlight how much data has been moved for each user in the legacy archive. Q9. What happens if an item fails to migrate? Failures may simply be temporary failures owing to environmental issues such as poor network bandwidth or high loading on the legacy archive system, in which case Evolve will automatically re-process the relevant item(s) a specified number of times and/or at a different time of day. In the event of a permanent failure, a full log of the item(s) in question is produced, enabling further sitespecific investigation. Permanent failures tend to be low typically.001% of the overall email quantity. They are also usually attributable to pre-existing problems in the source archive (i.e. not caused by the migration process). If your organization requires further investigative work to be carried out in the event of a corrupted item, a simple SQL query can be run on the Evolve database to find the root cause of the item failure. All failures are logged to provide full chain-of-custody. Q10. How does Evolve aid compliance when migrating? Manual migration methods that rely on problematic PST files (see response to Q5 & Q6) are subject to human error and have no tracking or auditing mechanism to prove that a migration was 100% successful. As described earlier in this document, Evolve eliminates opportunity for human error. It also includes complete auditing of the migration process. For example, detailed reports show 1:1 mappings of the ID of the item in the source archive and the ID of the new item as it now exists in Exchange, enabling you to demonstrate of a complete Chain of Custody for the data whilst undergoing migration. Importantly, Evolve is the only solution available that is able to preserve BCC d recipients and distribution list information from Journal mailbox archives. These messages may be part of legal proceedings or may be subject to regulatory requirements, so the loss of such vital information could be extremely costly and potentially damaging. Tuesday, Page 5 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 5

Q11. What do you mean by chain of custody and why is it important? Chain of custody refers to the reliable recording of processes and procedures that occur while evidence (physical or electronic) is being captured, held, transferred or disposed of. It is vital that the evidence in question has remained free from alteration and that secure handling has been provided at all stages. Akaibu Evolve s logging and reporting capability provides chain-of-custody evidence demonstrating that data has been successfully transferred into Exchange or Office 365. This is important since any later data investigation or discovery against migrated emails will seek to validate that the data has been handled correctly and that nothing was missed out. Q12. Why do Exchange Journal Archives require special care? Firstly, Journal archives tend to be extremely large, making a manual extraction approach slow and subject to size-related problems that can be encountered when relying on PST files as an interim store. Evolve allows journal and large mailboxes to be split into a number of separately handled virtual mailboxes of a user-defined size. This allows multiple processing threads to be applied to the migration of a single mailbox, significantly speeding up the migration task. Secondly, most of the organizations that capture emails into Exchange Journal mailboxes, for compliance reasons, have now standardized using the Envelope Journaling feature. This feature was developed by Microsoft as a way to preserve vital P1 email header information which includes BCC'd recipients and the expanded members of any distribution lists. From a compliance perspective, P1 data must be preserved and available for access. The important thing to note is that different archive platforms store the additional P1 envelope information in different ways. For example, some store the P1 data separately in the archive index as a means of preserving single instance storage, whereas others store it in the archive store itself. This creates a very special requirement at migration time that neither manual methodologies nor vendor extraction tools can support. Evolve has a special capability known as Envelope Reconstruction designed to ensure P1 data is properly captured and re-associated with the original P2 data during a migration. Contact Akaibu to discuss this feature and its relevance to your project. Q13. I want to move to a hosted email Exchange service - can Evolve help? Yes. Customers wishing to switch to a hosted email service such as Office 365 or Mimecast can use Akaibu Evolve to migrate their archived data. Also bear in mind that Akaibu Evolve can help you move out of a hosted service at a later date. Tuesday, Page 6 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 6

Q14. We are involved in a demerger and need to split up our archive. How does this work? Evolve can filter items by user, user groups, folder and dates, thus enabling data to be incisively selected and migrated to Exchange or Office 365. Evolve also has the capability to re-write all email addresses in sender and recipient fields so that the email is usable with any new domain naming or recipient-addressing conventions. Q15. How can we remove legacy archive shortcuts or stubs from users mailboxes? Akaibu Evolve includes extensive mailbox management services which include the ability to delete shortcuts to legacy archives as users are switched to the Exchange/Office 365 environment. Additionally Akaibu Evolve can survey mailboxes for legacy shortcuts so that data items can be migrated into Exchange/Office 365 only when the user has kept their shortcuts for these items. If items that had been deleted by end users were migrated back into Exchange this could be confusing. Evolve can also account for the scenario where shortcuts have been moved between folders or forwarded to other users, ensuring emails are in the correct place post-migration, and that all shortcut owners still have access to the emails they had access to pre-migration. Q16. How is Akaibu Evolve licensed? The core Akaibu Evolve is licensed according to the volume of data you wish to migrate. For more information please contact Sales@akaibu.com. Q17. Do I need to provide systems to run Akaibu Evolve on? Unless provided by your chosen Evolve partner, you will need to make available one or more servers for a short time-period. You will also need access to an SQL database. Akaibu, or an Akaibu partner can advise you on pre-requisites. Q18. Can new connectors be commissioned for development? Yes. Some of the current product functionality has been sponsored by other platform vendors. However, if you would like other connecter types added, please contact Akaibu Ltd. Q19. How can I find out more? You can visit our website at www.akaibu.com or contact Akaibu Ltd. By phone, at +1 817 887 8470 (North America), +44 020 3287 3221 or info@akaibu.com. Tuesday, Page 7 October 7, 2014 Copyright Akaibu, Inc. 2011-2015 PAGE 7