President Trump signed an Executive Order (EO) on 5/11 designed to strengthen the cybersecurity of federal networks by continuing a massive shift in how the US Government handles its data aiming to create a single federal IT enterprise. This effort will be quarterbacked by the Department of Homeland Security (DHS) and the Office of Management & Budget (OMB). DHS Security Advisor Tim Bossert explained that there will be a preference in federal procurement for shared IT services among the 190 federal agencies and the goal of this move to the cloud is to avoid defending antiquated and fractional systems.
Can your defense team save additional litigation cost and lower risk by using the cloud to dramatically reduce the number of data transfers?
The cloud has become a ubiquitous tool for most companies (and industries) over the last several years. However, when dealing with legal situations and eDiscovery, companies are still in the habit of shipping hard disks, optical disks, or if they’re lucky, electronically transferring terabytes of data to their external law firms in response to eDiscovery demands. Those same law firms turn around and follow the same data shipping/transfer processes when turning over client eDiscovery data to opposing counsel.
With the continuing explosion of data piling up across organizations around the world, many are turning to the cloud as an economical way to keep pace with the vast amounts of data they must store, manage, and share. Eventually, much of this data is archived for regulatory, legal, and business reasons while all of it is backed up due to disaster recovery practices.
Most of us have been exposed to enterprise file shares during our professional life. These enterprise file shares are what some also referred to as “home drives”; personal folders setup on network drives that employees would have access to store work files etc. Over the last several years, cloud-based individual file shares have become very popular. Dropbox, Google Drive, Box, Apple iCloud, SugarSync, and Microsoft OneDrive are but a few of the more popular ones.
Back in January of this year, we published a blog titled Quarantine your Stale Data about the need to quarantine your stale (or grey) data. In it, we talked about a conversation we had with Alan Daley, Research Director of Gartner Research, about the problems his clients were having with managing stale data – or those files that for whatever reason, become less valuable to the end-user over time.
Archive360 Webinar on 3/14/2017
See how the Power of Azure Manages and Protects your Digital Assets!
Regulatory Data Storage Compliance
Unlock the Enterprise Data Analysis and Search Cost effective SaaS Archive Solution built on the Microsoft Cloud!
Many companies struggle with the long-term storage of low touch data that, because of its nature, does not really fit with the high priced, high performance enterprise storage strategy many companies rely on.
The cloud is an obvious candidate for storing vast amounts of email, files and other forms of unstructured data for compliance. Organizations in highly regulated industries such as financial services, healthcare, government, and energy are very familiar with the regulatory rules that require secure retention of electronically stored information (ESI). However, before you proceed it’s a good idea to carefully review some of the basic requirements for compliance archiving in the cloud.
When someone mentions the modern data center what comes to mind first? Virtual machines (VMs), containers, SSD, flash storage, hyper-convergence? The answer is, "all of the above." But have you considered public cloud storage as a critical element of your modern data center strategy in 2017?
Have you successfully moved your organization’s on premise email service to Office 365? If so, nicely done! You have provided your employees with a rich package of communication and collaboration services.
What are your plans to utilize Office 365 OneDrive? IMHO, OneDrive is one of the most valuable assets of Office 365, second only to Exchange Online. As part of your Office 365 license, Microsoft provides each user with a whopping 1 TB of storage for online file sharing.
Most organizations eventually retire (shut down) aging business applications for several reasons including cost reduction, application consolidation, risk reduction, and because of new regulatory and eDiscovery requirements. However, one question that is not usually addressed early on is; what should be done with the associated application data?
The adage “too big to fail” relates to financial institutions so large and interconnected that their failure would have seismic repercussions in the economy, but what about these same companies’ plans to manage big data? The new question is whether there is a data archive “too big to move?”
Undoubtedly you have heard about the new low cost public cloud storage from Amazon, Microsoft and Google. New terms such as cool, cold, Nearline, coldline, and glacier are just a sample of the new brands being marketed. To better understand these new brands, I thought it would be helpful to review and compare each brand and make note of its preferred use case.
Infrastructure Modernization is a trendy new phrase you will hear from industry experts and read about in IT-related articles. In simple terms, infrastructure modernization describes a major shift taking place from on premise applications to cloud-based applications. When properly deployed, new cloud-based applications can dramatically reduce your CAPEX spending in favor of low cost software services.
Last week I was on the phone with a partner discussing ‘cold’ cloud storage and what is best for the customer. In the middle of the discussion I declared, “we are the Switzerland of cloud storage”, meaning ultimately, it is always up to the customer to decide whether or not they wish to move their data into cloud storage.
As corporate data continues to pile up within the enterprise, a much asked question, at least around the IT water cooler, is why is all of this data accumulating instead of being deleted. Employees create, send, and receive approximately 20 MB of data per day. The vast majority of this data is retained because employees feel that they will need to reuse/reference it at a later date so it accumulates on local storage, on file shares, in the email system and archive, and lately, into employee corporate and private clouds (figure1). In fact, 70 to 80% of corporate unstructured data is unindexed, unmanaged, and invisible to IT.
ATLANTA – September 20, 2016 Archive360™, the leading provider of email archive migration software, today announced that it will be showcasing its Archive2Anywhere™ compliant email archive migration solutions and Archive2Azure™, the industry’s first Microsoft Azure –based long term compliance storage solution for low-touch, inactive, and grey data during next week’s sold-out Microsoft Ignite Conference, in Booth 2144. The solutions, which quickly transform legacy email archives and other unstructured grey data into compliant, cloud-based archive environments, provide collection, migration and long term retention for archived and unstructured data for compliance, legal and business requirements.
Corporate records are usually retained and managed due to government and professional regulations. The vast majority of those corporate records are never searched, reviewed, or ever really looked at once they're filed away. These days, electronic records are a "store and forget it" process. So why do companies keep their records on expensive enterprise-class disk, or more recently, move them to expensive high performance cloud storage? It seems to me the real reason is the popular record management systems have always targeted existing high performance storage systems simply because that’s what organizations were buying and low cost cloud storage was not designed for records management functionality.
A long running issue with Exchange systems is managing inactive mailboxes. An inactive mailbox is simply a mailbox that is associated with a departed employee. With on premise Exchange systems it was relatively straight forward – let them sit indefinitely, or for a specified time period (e.g. 3 years), for legal, regulatory, or business reasons.
If you’re moving a legacy email archive to Office 365, chances are good that you also have Exchange journal data to move as well. If you do, it’s likely that the total amount of journal data is equal to or greater than the total size of your email archive.
With regards to Office 365, you might be wondering where the journal data is stored. It comes down to two possibilities; move the journal into the Personal Archive of an Office 365 active mailbox, or create separate Office 365 mailboxes (e.g. Journal Mail 001, Journal Mail 002, Journal Mail 003) and move the journal data for groups of custodians into those. This practice is called "journal splitting”. To many, an unknown concept that raises many questions, the most important being; is journal splitting the best practice for your organization’s regulatory or legal needs? The answer is it depends… Let’s break it down so you have all the facts before you make a migration decision on your journal.