ARCHIVE ESSENTIALS: Key Considerations When Moving to Office 365 DISCUSSION PAPER

Transcription

1 ARCHIVE ESSENTIALS: Key Considerations When Moving to Office 365 DISCUSSION PAPER

2 preface The last few years have seen significant changes in the way organisations conduct business. There has been an unstoppable momentum toward the embrace of cloudbased digital platforms that aim to unlock the capacity for greater collaboration and productivity amongst staff.

3 The pre-eminent example of a cloud-based digital platform is Microsoft s Office 365. Since its transition from locally-installed, licensed software to a full-blown Software as a Service (SaaS) platform, Office 365 has been adopted by numerous companies, each seeking to take advantage of its superior collaboration capabilities, flexible configuration options, reduced licensing costs and ongoing improvements via its regular upgrade cycle. With such rapid adoption on the part of enterprise and the tangible benefits that Office 365 can bring to businesses large and small, it s easy to understand why so many businesses are either considering it or actively planning a migration. With any move towards the adoption of a new platform, a bit of specialist advice to complement your planning could be the difference between a successful outcome and major headaches. In particular, this applies to migrating your existing archive data. Your data is valuable beyond measure, with many of us storing important information in our s. Organisations depend on archives of these communications on a regular basis, and anyone considering Office 365 must allocate time to carefully explore the migration of archive data as a distinct component of the overall Office365 mail migration. That s why Insentra has prepared this paper: to inform and help guide your Office 365 data migration strategy, to identify any potential hurdles you may encounter, and suggest the best possible approach to ensure a smooth transition of your archive to Office 365. Insentra knows the ins and outs of migration. Let us share our insights and experience with you. 3

4 Migrations are by no means easy. Let s breakdown some of the essentials, to better allow you to begin planning around your specific circumstances. As ever, it begins with the most basic question: why. defining business drivers and required outcomes Before you start moving your archived , it s important to ensure everyone understands why this move is the best option for your business. You may be seeking to drive down costs, or perhaps to overcome environmental and technical hurdles. It is possible that you are presently using an aging platform and desire an upgrade to improve your overall user experience. It may even be all of the above. Successfully identifying these drivers and understanding the corresponding impact on the outcomes of your migration will help determine the most appropriate approach to take. When it comes to migrating your archive data, there are many ways to manage and move it, each of which will deliver different outcomes. Some outcomes require a more cautious approach resulting in a longer process. In other instances, where the requirements are less complex, you can cut through the rigor to deliver a much faster result. It really depends on your particular needs. Without adequately defining those needs, you may be unnecessarily spending money on technology and processes. Before anything else however, you must know what your compliance requirements are. For example, having chain-of-custody obligations to meet will determine not just what data needs to be moved, but how it will have to be moved. TYPICAL DRIVERS FOR ARCHIVE MIGRATION Cost efficiencies Upgrade from aging technologies Improved employee collaboration Expanded storage capacities and improved search-ability/ediscovery 4

5 know what data you need to move Once you ve defined your business drivers, determined your compliance requirements and established the desired outcomes of such a move, it s time to identify the specifics of your data migration. The type of business you have will also help delineate what and how much data needs migrating. What is necessitating the move? It may be that your organisation is moving data centres, or that your current storage solution is nearing end-of life. Consider also the nature of your typical operational requirements. Will you require your entire historical archive or simply need data for the current set of users? If your users are terminal or kiosk based, you may not need your historical archive. Heavy users, on the other hand, may need their entire archive migrated over. Businesses with heavy regulatory compliance legislation must be able to prove chain-of-custody when their data is moved. Alternatively, some organisations may have compliance requirements dictating that only three years of data is required to be stored. WHAT IS CHAIN-OF-CUSTODY? This term refers to the reliable recording of processes and procedures that occur while evidence - physical or electronic - is being captured, held, transferred, or disposed of. For organisations with strict industry compliance regulations and internal data management policies, maintaining chain of custody is vital. When migrating, organisations must be able to demonstrate that the data has not been altered in anyway as it transits from one archive platform to another. Automated migration tools and services include a complete audit of the migration process, which demonstrates a detailed Chain of Custody for data that is subject to legal or regulatory requirements. All of these considerations will affect the size, scale and price of your migration. Therefore it is crucial that time is taken to adequately assess this aspect of the move. 5

6 in which order should you do your migration? Moving to Office 365 requires two types of migrations one for each of the Primary and Archive data sets. Identifying the key business drivers of your migration will determine the best order to migrate in a way that makes sense for your business. Consider what processes you re going to use to move your primary mailbox: will you use a hybrid Exchange deployment, or a third-party toolset? Your existing environment as well as the software and process by which you choose to migrate your Primary data, will dictate the order you need to move your archive. Generally speaking, moving your archive first will result in the best outcome, guaranteeing that when your users go online in Office 365, everything they need to access is already Helvetica Neau there. In some scenarios, however, this is not possible - i.e., in migrations from Exchange 2007 or when the users will not be licenced for an Online Archive - and the archive migration will need to follow the primary mailbox move. Even in this situation, all data that users need can often be available day zero. WHAT S YOUR BANDWIDTH? Consider any bandwidth limitations of your network infrastructure as it will directly impact the speed of your migration. An archive migration often experiences an average throughput of 15GB to 100GB per hour. Are you able to utilise sufficient bandwidth during business hours? From the outset, is your link even big enough to facilitate an online migration? If your bandwidth is not up to the task, you may need to factor in the additional cost of Microsoft s Ship to Disk approach. 6

7 planning around mailbox and message sizes Microsoft has set a number of limits in Exchange Online impacting the supportability requirements. Some of these include: maximum message size maximum number of messages per folder the number of attachments in your inbox the number of recipients It is also essential to ensure data is being moved in a supported fashion so that if a problem does emerge, it becomes less time-consuming to engage support with your migration vendor or Microsoft Support Services for the required assistance. Understanding the implications of these requirements is critical to ensuring a seamless migration of archive data. Each of these items will have an impact on how data can be migrated. Additionally, Microsoft changes these limits quite regularly: it is vital therefore to remain aware of any such changes, as all will have an impact on how you can migrate your data. 7

8 what is your existing archive policy? When migrating archive data, organisations often need to stay compliant with regulatory requirements and require confidence in data integrity. All archive platforms are policy driven and these are often a good indicator of the business requirements. All data needs to be migrated as efficiently as possible to the new platform, all the while dealing with existing shortcut (aka stub) s. As a business, you will need to determine what gets moved to the primary mailbox, and what gets archived. The approach you take for your migration and the technology you are using will impact upon how you deal with shortcuts before, during, and after the move. You also have to consider how your business currently handles data associated with users that have left the organisation or who no longer use your systems. Decisions need to be made as to whether such user data needs to be migrated at all. If you do decide to migrate departed user data, questions will arise as to when to move it as license implications need to be considered. Deliberations such as these make archive migrations complex and involved projects. Knowing your existing data retention policy will provide a basis for business requirements, and make the decision process for what to move - and how - significantly easier. SHORTCUTS AND STUBS Many third party archiving solutions don t actually store the location of the archived item in user mailboxes. There may be a reference to the item, but many won t be able to tell where in the user mailbox that item is stored (i.e. the location of the shortcut). When doing a migration, that data may get moved into a flat folder structure needing to be synchronised. Your business will need to decide the best way to synchronise locations and decide whether to delete the shortcut before or after migrating the primary mailbox data. 8

9 litigation hold versus journaling Deletion and retention policies are a critical consideration for organisations where regulation and compliance are concerned. Two primary approaches for archival retention are Litigation Hold, and Journaling. Litigation Hold locks in a mailbox and enables all changes and deletions to be captured, stored, and made searchable by auditors as and when required. A mailbox configured with Litigation Hold essentially forces all deleted or altered mail items, tasks, calendar appointments and contacts to be stored in a hidden Recoverable Items Store, in which they remain until the Litigation Hold is lifted from that mailbox. Journaling, on the other hand, is a feature that can track all communications sent or received by an organisation, storing two copies of every message: one in the intended mailbox, and the other in a journal mailbox. The greatest downside to both, over time, is storage. Making sure you have balanced your compliance needs with your data retention capacities should be a key priority. It is also important to remember that while both Litigation Hold and Journaling will preserve mail content indefinitely, Microsoft does not support Journaling to a target mailbox in Office 365. This means that if you are currently using a journal archive, you ll need to decide whether a journal explosion is needed, whether you want to migrate it to Office 365 in its current structure, or whether you should use a third party cloud archiving solution. Risk and compliance teams in some businesses won t accept Litigation Hold as a good compliance solution for example, so they ll want to use Journaling. Other businesses have no issue with Litigation Hold. Be sure to involve your legal/risk and compliance teams as early as possible to obtain direction. 9

10 knowing your next step Archives are a necessity helping us to manage the explosion of data that is typical of today s information-rich environment. When properly implemented, cloud-based archival storage can provide a great boon for efficiency. As such, it pays to get it right. Always seek the best advice and ensure it gets done correctly from the get-go. Know your reasons for migration. Know what data needs to be moved, and how best to move it. Identify any limitations in your infrastructure, and what your compliance requirements are. Knowing where you re coming from will make it that much easier to see where you are going with your migration. Any questions? Insentra can answer them. 10

11 ABOUT INSENTRA Together we are better. Insentra is one of a kind. We believe that collaboration and genuine partnerships create a powerful synergy. Founded in 2010, we developed a unique IT channel model of engagement, which enables the efficient delivery of IT solutions for our vendors, partners and their clients. We are the only organisation in Australia with significant experience in data migration. Over the last five years we have migrated over a petabyte worth of data for our customers. With staff all over the world, we are ready and able to walk you through a migration in a way that is efficient and cost effective for your business. t e info@insentra.com.au Level 3, 110 Pacific Highway St Leonards NSW 2065 Australia insentra.com.au 11