1-800-691-1991 | 9am - 8pm ET
EN

How to add SMB repository to Veeam Backup for Microsoft Office 365

KB ID: 2971
Product: Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0, Veeam Backup for Microsoft Office 365 3.0, Veeam Backup for Microsoft Office 365 2.0
Published: 2019-06-26
Last Modified: 2021-03-24

Challenge

This article covers two most popular scenarios of adding SMB repository to Veeam Backup for Microsoft Office 365

If it’s a Windows-based shared folder, then it’s recommended to add the server it’s based on as a proxy and connect the same storage as a directly attached disk. 

Experimental Support

SMB repository is considered as "experimental support" in the current version. 

If a storage device supports both SMB 3.0 and iSCSI protocol, then the best practice would be to use iSCSI due to its ability to use Disk Queue which acts as a buffer space for data to land on before being sent off to disk.

Cause

Due to a fact that both Veeam Backup for Microsoft Office 365 services must use \SYSTEM account to run correctly, it would be required to grant access to SMB share for Veeam servers in general rather than to the particular user.  

Solution

Scenario 1: Microsoft Windows SMB share with authorization

Prerequisites:

Consider that Microsoft Windows 7 SP1 and Microsoft Windows 2008 R2 SP1 do not support the SMB 3.0 share as a storage system. To use the SMB 3.0 share as a storage system, make sure you are using Microsoft Windows 8 or Microsoft Windows 2012 or later. Both Veeam Servers and SMB share location must be deployed within the same or a trusted domain.

  • Open folder sharing settings for planned repository location and add all Veeam servers to it using their computer names. In example if your Veeam server is called “WIN-F4N92CDLKET” the list should look like this:
User-added image
  • Add repository in Veeam console as shown in this article
 

Scenario 2: Standalone storage appliance

In this scenario we will use Synology appliance as an example, but the same method should work for any standalone device that supports Microsoft Active Directory and its computer groups. 

  • Add Veeam server and all remote backup proxies (if any) to Active Directory domain.
  • Create an Active directory group in this domain and add all Veeam servers to it as “computer” objects:
User-added image
  • Add the storage device to the same domain:
User-added image
  • Make sure that SMB 3.0 protocol is enabled and previous versions are not allowed to use:
User-added image
  • Create SMB shared folder and grant read/write access to it for the domain group that was created earlier:
User-added image
  • Add new repository in Veeam console and manually type SMB share name in “Path” field as described here
 

Bonus: Adding standalone storage appliance using iSCSI protocol
In this scenario we will use Synology appliance as an example, but the same method would work for storage appliance that supports iSCSI protocol.

  • Open iSCSI manager and create new LUN and Target:
User-added image
  • On Veeam server: open iSCSI initiator, enter your storage appliance IP address, click “Quick Connect…” and then click “Done”:
User-added image
  • Open Disk Management, bring iSCSI disk online and initialize it using default parameters:
User-added image
User-added image
  • Create a new simple volume using default parameters:
User-added image
  • Create a new repository on this disk as shown here
KB ID: 2971
Product: Veeam Backup for Microsoft Office 365 5.0, Veeam Backup for Microsoft Office 365 4.0, Veeam Backup for Microsoft Office 365 3.0, Veeam Backup for Microsoft Office 365 2.0
Published: 2019-06-26
Last Modified: 2021-03-24

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.