Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

How to add SMB repository to Veeam Backup for Microsoft 365

$
0
0

How to add SMB repository to Veeam Backup for Microsoft 365

KB ID: 2971
Product: Veeam Backup for Microsoft 365 | 7.0 | 7a | 8
Published: 2019-06-26
Last Modified: 2024-10-15
Planned Feature Deprecation
Veeam Backup for Microsoft 365 support for SMB-based repositories will be deprecated in a future version.
For more information, see KB4567: Planned Veeam Backup for Microsoft 365 Feature Deprecation.
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, the best practice would be to use iSCSI due to its use of Disk Queue, which acts as a buffer space for data to land on before being sent off to disk.

Purpose

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

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

Cause

Due to the fact that all Veeam Backup for Microsoft 365 services must be run as the SYSTEM account, access to the SMB 3.0 share must be granted to the server itself rather than to a particular user.  

Solution

Scenario 1: Microsoft Windows SMB share with authorization

Prerequisites:

  • To use the SMB 3.0 share as a storage system, make sure you are using Windows 8/Server 2012 or later; older OS versions do not support the SMB 3.0 share as a storage system.
  • The Veeam Servers and the SMB share location must be deployed within the same or a trusted domain.
     
Configuration
  1. Open folder sharing settings for planned repository location and add all Veeam servers using their computer names.

    For example, if your Veeam server is called WIN-F4N92CDLKET, the list would look like this:
SMB Permissions Example
  1. Add the SMB 3.0 repository to Veeam Backup for Microsoft 365.

Scenario 2: Standalone storage appliance

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

  1. Add the Veeam server and all remote backup proxies (if any) to the Active Directory domain.
  2. Create an Active Directory group in this domain and add all Veeam servers to it as “computer” objects:User-added image
  3. Add the storage device to the same domain:
    User-added image
  4. Make sure that SMB 3.0 protocol is enabled, and previous versions are not allowed to use:
    User-added image
  5. Create SMB shared folder and grant read/write access to it for the domain group that was created earlier:
    User-added image
  6. Add the SMB 3.0 repository in Veeam Backup for Microsoft 365.

Scenario 2 Alternate: Add standalone storage appliance using iSCSI protocol (Best Practice)

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

  1. Within the Storage Appliance, open the iSCSI manager and create a new LUN and Target:
    User-added image
  2. On the Veeam Backup for Microsoft 365 server:
    1. Open the iSCSI Initiator
    2. Enter your storage appliance IP address
    3. Click “Quick Connect…”
    4. Click “Done”
      User-added image
    5. Open Disk Management, bring the iSCSI disk online, and initialize it using default parameters:
      User-added image
      User-added image
    6. Create a new simple volume using default parameters:
      User-added image
    7. Create a new repository for the disk in Veeam Backup for Microsoft 365.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Viewing all articles
Browse latest Browse all 4362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>