System Requirements

Veeam Backup for Microsoft Office 365 is shipped as a separate distribution package that can be downloaded from Veeam website. This tool is compatible with all editions of Veeam Backup & Replication 9.5, including Veeam Backup Free Edition.

As described in this guide, the solution comprises two components, which can run on a physical or a virtual machine.

1. The Veeam Backup for Microsoft Office 365 component can be deployed as a standalone program on the machine that meets the requirements listed in the section below.

2. The Veeam Explorer for Microsoft Exchange component can be deployed in any of the following ways:

• On the same machine with Veeam Backup for Microsoft Office 365 component, which should be installed first. For details, see the Installation section below.
• Together with Veeam Backup & Replication server (or console) during its setup - in this case, make sure that all necessary system requirements for Veeam Backup & Replication 9.5 are met; also, refer to the "Working with Veeam Explorer for Microsoft Exchange" section of the Veeam Explorers User Guide.

Veeam Backup for Microsoft Office 365 Server

Backup Target

Backup can be performed to the following disk-based storage accessible from Veeam Backup for Microsoft Office 365 backup server:

• Local (internal) folder of the backup server (default target).
• Direct Attached Storage (DAS), connected to the backup server, including external USB/eSATA drives and raw device mapping (RDM) volumes.
• Storage Area Network (SAN); backup server must be connected to the SAN fabric via hardware or virtual HBA, or software iSCSI initiator.
• SMB 3.0 share (experimental support); backup server’s computer account must have corresponding permissions on the network share (see the next section).

Using Network Share as a Repository

By default, the Veeam Backup for Microsoft Office 365 Service operates under the Local System account, that is, <VBO_server_name>\LocalSystem. To be able to set a network drive\UNC path to the repository on a share, you can use any of the following options:

• If you want the service to run under the default account, ensure this account (<VBO_server_name>\LocalSystem) has sufficient rights to access the corresponding network share.
• Alternatively, you can change the default service account and make it run under the account that already has been granted access rights to that network share.

If you prefer the second option, then after changing the service account, you should edit the settings of all organizations that were added to the product scope, following the steps of the wizard. The Veeam Backup for Microsoft Office 365 Service will be stopped and started automatically when its account is changed. Alternatively, you can perform these steps manually:

1. Stop the Veeam Backup for Microsoft Office 365 Service.
2. Change the service account.
3. Start the service.
4. Edit organization settings using the wizard.

Completing the Edit Organization wizard will ensure that organization configuration data will be accessible to the service after its account has been modified.

With modification procedures completed, you should be able to enter the UNC path in the Location field of the Repository tab.

Considerations and limitations specific to the tool installation and operation are listed in the corresponding section of this guide.

For more information on solution components and their interaction, refer to the How It Works section.