Object Storage Repositories

Veeam Backup for Microsoft 365 uses object storage repositories to store backups and backup copies created for Microsoft 365 and on-premises Microsoft organizations. Veeam Backup for Microsoft 365 supports the following cloud and on-premises storage systems:

• S3 Compatible object storage

Any S3 Compatible object storage device fully compatible with the AWS S3 operations and AWS S3 Signature Version 4 standard.

• Amazon S3 object storage

For more information about Amazon S3 object storage, see this Amazon article. For more information about Amazon S3 storage classes that Veeam Backup for Microsoft 365 supports, see Supported Amazon S3 Storage Classes. For more information about required permissions, see Amazon S3 Storage Permissions.

• Microsoft Azure Blob storage

For more information about Microsoft Azure Blob storage, see this Microsoft article. For more information about Azure storage account types that Veeam Backup for Microsoft 365 supports, see Supported Azure Storage Account Types. For more information about Azure Blob storage permissions, see Azure Blob Storage Permissions.

• IBM Cloud Object Storage

For more information about IBM Cloud Object Storage, see this IBM article.

• Wasabi Cloud Object Storage

For more information about Wasabi Cloud Object Storage, see this Wasabi article.

The following table lists supported object storage depending on vendor and purpose of usage:

Object Storage Usage Scenarios

Veeam Backup for Microsoft 365 offers the following usage scenarios for object storage repositories:

• Data backup. In this scenario, you create a backup job to back up your data directly to the supported cloud or on-premises storage system. This is not applicable to Azure Blob Storage Archive access tier and all Amazon S3 Glacier storage classes.

You specify a target object storage repository for a backup job at the Specify Backup Repository step. During a backup job, data is compressed and backed up directly to the object storage repository. To save cache with backup metadata, Veeam Backup for Microsoft 365 uses the PersistentCache database created by Veeam Backup for Microsoft 365 on the PostgreSQL instance. Metadata is saved separately for each object storage repository to the file located by default in the C:\Program Files\PostgreSQL\15\data folder on a machine with the PostgreSQL instance. For more information, see Cache.

• Backup copy. In this scenario, you create a backup copy job to transfer your backed-up data as backup copies from one object storage repository to another. For more information, see Getting Started with Backup Copy.

Data Protection

Veeam Backup for Microsoft 365 allows you to prohibit deletion of data from the object storage repository by making that data temporarily immutable and to protect data against malware activity. To do this, you need to enable immutability when adding an object storage repository to Veeam Backup for Microsoft 365. For more information, see Immutability.

Data Validation

Veeam Backup for Microsoft 365 provides a self-check mechanism that allows the product to validate if backed-up data appears in the object storage repository uncorrupted after compression and transfer.

The process of data validation involves the following steps:

1. Before sending data to the object storage repository, Veeam Backup for Microsoft 365 calculates hash: for Amazon S3 object storage repositories and S3 Compatible object storage repositories both the MD5 and SHA256 checksums are calculated, for Microsoft Azure Blob storage — the MD5 checksum only.
2. When the backed-up data appears in the object storage repository, checksums are calculated again and are compared with values obtained before data was sent to this object storage repository.

In This Section

• Object Storage Repository Structure
• Cache
• Compression
• Data Encryption
• Immutability
• Adding Object Storage Repositories