A SaaS Backup & Restore solution is a crucial data protection need if your organization is operating in the cloud. In order to choose the solution that’s right for you, it’s important to understand the essential aspects of cloud data protection and why you should consider each of them when weighing your options.
If your organization is contemplating a migration from G Suite to Office 365, it’s best to first consider three questions: Why migrate?… What is the current data landscape?… and how should you proceed with the migration? Answering these questions and understanding how Spanning can help will make your migration seamless and pain free.
There are no two ways about it, data loss is devastating for any organization. Data loss results in lost customers, lost revenue and damaged reputation. It can happen to anyone, so make sure you’ve got a backup and restore solution that has you covered.
Spanning’s Matt McDermott details how customers can use a Microsoft Flow feature called Custom Connectors to craft their own solutions with REST API endpoints like the Spanning Backup for Office 365 API.
While moving to O365 brings a host of exciting features and capabilities, rushing into it can lead to a tedious migration and impact the ROI of the solution. Moving to O365 should be viewed from the long-term lens of adoption, rather than a one-time migration, to realize the benefits of its numerous solutions/tools. In this blog we list key pointers for a smooth transition, along with post-migration tips.
If you (or someone you know) is thinking of making a major tech career pivot, Matthew McDermott’s story might help. After 20 years of working in Austin as a consultant, starting with web technology then landing on SharePoint and Office 365, he made a pivot recently to work for Spanning Cloud Apps in Austin, Texas. Read his latest blog post for his personal advice on starting a new job.
SharePoint admins need to understand that the same risks for data loss due to accidental or malicious deletions apply to SharePoint Online content associated in Sites, OneDrive, Groups, and Teams. The native protections Microsoft offers don’t meet the need for fast, accurate recovery in those scenarios, as you’ll learn in this blog post by Matthew McDermott, Microsoft MVP.
In Part 1 of this two-part series, we discussed how you need to rely on more than the default retention times for Office 365 to fully protect your data from accidental deletion. In Part 2, we’ll discuss if Exchange Online Litigation Hold and In-Place Hold are good-enough data protection solutions for Office 365, or if your organization may need something purpose-built for Office 365 backup and restore.
Data protection in Office 365 is a shared responsibility, with Microsoft taking on the tasks that would have typically been done on-premises for disaster recovery. But your IT team is still ultimately responsible for data protection, and it’s up to the IT team to decide how to protect and recover any data that is lost by human error or even malicious attacks. In Part 1, we look at Microsoft’s disaster recovery and retention times.