In this blog, we’ll be focusing on a new easy-to-read technical guide we recently released called, #1 Office 365 Backup by Veeam. You can download it here, or read an overview of the excerpts below.
Since the inception of Veeam Backup for Microsoft Office 365, Veeam has made it our mission to educate the IT community on the importance of protecting data in Office 365. Fortunately, as time has gone by, more and more organizations understand the “why” of SaaS backup and want to focus on the “how”. So, we have created a new technical guide on Veeam Backup for Microsoft Office 365 which explains everything from what the components are, to how to get up and running creating your first backups and restores. Let’s cover a few important aspects of deploying Veeam Backup for Microsoft Office 365.
The Veeam Backup for Microsoft Office 365 installation package consists of the following four MSI files:
Installs Veeam Backup for Microsoft Office 365 with the following services:
- Control global configuration settings
- Manage backup proxy servers
- Process REST commands. (This component is disabled by default and can be enabled)
Installs Veeam Explorer for Microsoft Exchange.
Installs Veeam Explorer for Microsoft SharePoint and Veeam Explorer for Microsoft OneDrive for Business.
Installs Veeam Explorer for Microsoft Teams.
You can download the Veeam Backup for Microsoft Office 365 installation package from the official Veeam website.
Veeam Backup for Microsoft Office 365 is a comprehensive solution that allows you to back up and restore data of your Office 365 organizations, including Microsoft Exchange, Microsoft SharePoint, Microsoft OneDrive for Business and Microsoft Teams data, as well as data of on-premises Microsoft Exchange and on-premises Microsoft SharePoint organizations.
There are three core components of this solution — backup server, backup proxy and backup repository.
The Veeam Backup for Microsoft Office 365 server is the central configuration and control component. It is responsible for setting up and managing other components, job scheduling, task coordination and more.
The server can be installed on a physical or virtual windows-based machine. The server includes access to Console UI. RESTful API and PowerShell are also components.
The Veeam Backup for Microsoft Office 365 proxy is the workhorse behind the scenes which conducts all the read and write activities, and intelligently converts objects to smaller, manageable items.
Backup proxies provide an optimal route for backup traffic and enables data transfers to happen efficiently.
The Veeam Backup for Microsoft Office 365 repository is the location where Office 365 data is stored. Repositories can also store important metadata used during backup and recovery operations. Backup repositories are supported on the following types of storage: object storage (on-premises and cloud), directly attached storage (DAS), SAN, SMB (Server Message Block 3.0).
Simple versus advanced deployments
With Veeam Backup for Microsoft Office 365, you can use both simple and advanced deployment options. Find out which one will work best for you.
Simple deployment includes the installation of all components onto a single server. This machine can be either virtual or physical. Specs should follow configuration maximums. In this scenario, all the major components (i.e., the server, proxy and repository) are installed on the same machine.
A simple deployment scales out by adding multiple repositories that are operated by the same built-in proxy server. Simple deployments are suitable for small-to-medium-sized businesses (SMBs) that want to have a local backup copy of their Office 365 data on-premises. This applies to public cloud deployments like Azure Cloud, AWS and other offering too. In this case, backup data can be stored on disk/file-based repositories attached to the servers, as well as object storage repositories sitting in the public cloud and on-premises.
Advanced deployment gives the option to scale out installations by adding proxy and repository components to meet demanding business requirements. The process of adding these components is handled by the main server. When scaling out to an advanced deployment, the server installs the necessary components onto the required servers. It works by deploying the main veeam.archiver.proxy service along with a copy of the infrastructure configuration.
This newly added proxy benefits from the view of the entire infrastructure and provides the option to configure backup jobs by using additional repository targets. This entire process is wizard driven. Full automation is also possible using native PowerShell commands and RESTful APIs. As of v5, servers and proxies can be part of the same domain, a separate domain (with trust relationship) and even part of workgroups.
Typically, the size of an environment dictates the deployment model. The size of an environment is not necessarily related to the number of Office 365 users to protect. Instead, it’s based on the number of objects to protect.
Getting started with sizing is easy: you can size your environment with the Veeam Backup for Microsoft Office 365 Capacity Calculator!
If you’ve read this far, you’re probably interested in the full technical guide! Download here to keep reading!
- Still not convinced you need an Office 365 backup? Read about the Office 365 Shared Responsibility Model
- Download a 30-day FREE trial of Veeam Backup for Microsoft Office 365
- Join a technical demo by a Veeam Systems Engineer