Veeam Backup for Microsoft Office 365Architecture, Installation and Design

Dilupa Ranatunga Senior Systems Engineer

Rose HerdenInside Systems Engineer

Agenda

Architecture

Sizing

Summary

Optimisations

VBO – V.Next

Architecture

Tracks proxies and collect sessions data

Pushes configuration to proxies

Configuration database

Veeam Backup for Microsoft Office 365 Server

Handles the configuration and management functions.

Bandwidth limitation can be configured

Partial replica of the main configuration DB

Processing engine

Veeam Backup for Microsoft Office 365 Proxies

Responsibile to execute both backup and restore jobs.

Compression inside

Lightweight, free of charge, ready to use

Microsoft ESE / JET Blue database

Veeam Backup for Microsoft Office 365 Repositories

Location(s) where the Office 365 data is stored.

SAN connected

SMB 3.0**

Direct attached storage

Local disk storage

Supported storage

Supported Storage Types

MicrosoftOffice 365

Repositories Repositories

Console VEX

RESTservice

PowerShellcmdlets

VBO server

VESP VEOD

Architecture overview

VBO proxy VBO proxy

Deployment Methods

All in one solution(1- 3,000 users)

Multi-proxy solution(3,000+ users)

Design & Sizing

Deployment Methods

Recommended Sizing:

4 – 8 CPU

8 – 32 GB RAM

10 GB minimum(800 MB Install + Config DBs + Workspace)

All in one solution(1- 3,000 users)

Multi-proxy solution(3,000+ users)

4,000 users per proxy

1 based on maximum recommendation for a VBO365-Proxy with 8 CPUs and 32 GB RAM2 if using all objects: Mailbox, Archive, OneDrive and (personal) Sites

Maximum Configurations

Max. number of objects per Proxy1 2 16,000

Max. number of users per job² 4,000

Max. number of users per proxy² 4,000

Max. number of proxy per VBO365 instance 10

Max. number of objects per VBO365 instance 160,000

Max. number of users per VBO365 instance 40,000

Max. size per VBO365 repositoryV2: 64 TB/yearV3: no limitation

OneDrive for Business

Group SharePoint site

Personal SharePoint Site

Archive Mailbox

Mailbox

What it is

What are objects?

1 Object User

1 User can use up to 4 Objects!

Size Estimation

Retention Policies

Daily Change Rate

Considerations:

Sizing Repository

Backup Repository Size = C + N(2*R)

Repository Sizing

• Organization Full Backup Size - C• Daily Change Rate - R• Days of Retention - N

10% additional storage space required to allocate transaction logs and checkpoints

Measure-VBOOrganizationFullBackupSize

Use PowerShell

Sizing: Data

$org = Get-VBOOrganization -Name "o365democenter.onmicrosoft.com"Measure-VBOOrganizationFullBackupSize -Organization $org

FullSize : 755,7 MBMailboxSize : 149,6 MBArchiveMailboxSize : 0 BSiteSize : 396,6 MBPersonalSiteSize : 120,6 MBOneDriveSize : 88,9 MB

Sizing Repository: Example

Change Rate (R): 1 %

Retention (N): 1 years (365 days)

Overall size (C): 1 TB (Mail, Sharepoint, OneDrive)

Scenario

1024 + {(365)(2*10.24)} = 8.5 TB

Sizing Repository

Retention Policy

Item Level Retention

Snapshot Based Retention

Optimisations

Performance Tuning: Potential Bottlenecks

Network Throttling Bad Job Design IOPS

Performance Tuning: Potential Bottlenecks

Network ThrottlingPing outlook.office.com (Edge distance)

Limit if needed

Use diagnostics.office.com

Bandwidth

Access Level (Owner, Delegation, Impersonation)

Performance Tuning: Potential Bottlenecks

Global exclusion settings

Create separate jobs for users / resources /…

Don’t overdo exclusions

Job Designing

Bad Job Design

Don’t put 50k users in 1 job

Performance Tuning: Potential Bottlenecks

Don’t use dedupe on repositories

Close unneeded Veeam Explorer sessions

Don’t undersize your proxies & controller

IOPS, CPU and Memory

IOPS

Summary

Architecture

Sizing

Summary

Optimisations

VBO – V.Next

VBO – V.Next

Thank you