As more and more organisations, both large and small, move to Microsoft Office 365 for their productivity apps, deploying the right technology to protect the data that they generate on the platform is becoming increasingly important. And it’s important to note that Microsoft themselves do not take any responsibility for the long-term protection of yourdata residing on their platform. To help O365 customers to understand where Microsoft’s responsibilities ends and the customer’s begins, Veeam have developed a useful Shared Responsibility Model. In brief, the data that you create and store on Office 365 belongs to you and it is your responsibility to make sure it is fully protected for both recovery and compliance purposes.
With years of experience in the data protection industry, Veeam has developed Veeam Backup for Office 365 (VBO) and in this step-by-step guide, I’m going to show you how I installed and configured a 30-day trial version of VBO, with examples of backup and restore options.
In part 1 of this step-by-step guide, we looked at how to install and configure Veeam Backup for Office 365. But it’s no good to us until we start to actually use it to protect our data, right? So let’s configure a backup job and investigate what recovery options are available to us.
As part of my role as technical sales specialist, I like to build labs to learn and experiment with different products, be they from VMware, Veeam, Nutanix, NetApp or any other vendor that I’m asked to work with. With that in mind, I run a home lab based on Dell PowerEdge T430 server. I was very lucky to acquire this system as it has 16 CPU cores, 48GB of RAM and some decent hard drives giving me approximately 3TB to play with. It runs vSphere 6.7. After much trial and error I decided I needed to build a virtual environment with multiple routed network segments that I could reuse whenever I needed depending on the technology I wanted to test. Here’s how I built my lab using vSphere virtual switches and an open source router package called VyOS.