Backup to Object Storage

You can back up your Mac computer data to a cloud-based or on-premises object storage repository. You can configure the repository in the following types of object storage:

• Amazon S3
• Google Cloud Storage
• Microsoft Azure Blob Storage

• S3 compatible — on-premises (for example, MinIO) or cloud (including Wasabi Cloud and IBM Cloud)
• [For Veeam Agent 2.1.2] Veeam Data Cloud Vault added as a Veeam backup repository or Veeam Cloud Connect repository.

Depending on your backup infrastructure, object storage can be available in different configurations. To learn more, see the following subsections:

• Backup Destinations
• Types of Connection to Object Storage in Veeam Backup & Replication
• Considerations and Limitations

Backup Destinations

You can back up Veeam Agent computer data to object storage in the following ways:

• Directly to object storage. In this case, Veeam Agent connects to an object storage account and creates a backup repository in this storage.

Keep in mind that to connect to object storage, you need to have an account with access permissions to read and write data.

To learn more, see Object Storage Settings.

• To object storage added as a Veeam backup repository. In this case, Veeam Agent connects to the Veeam backup repository and Veeam Backup & Replication connects to object storage and creates a backup repository in this storage.

To learn more, see Veeam Backup Server Settings.

• To object storage added as a Veeam Cloud Connect repository. In this case, Veeam Agent connects to the cloud backup repository and Veeam Backup & Replication connects to the object storage and creates a backup repository in this storage.

To learn more, see Veeam Cloud Connect Settings.

Types of Connection to Object Storage in Veeam Backup & Replication

If you back up data to object storage added as a Veeam backup repository or Veeam Cloud Connect repository, you must configure a repository beforehand on the Veeam Backup & Replication side. Depending on the repository configuration, Veeam Backup & Replication provides one of the following connection types to the repository in the object storage:

• Connection through a gateway server. With this connection type, Veeam Agent connects to the repository using a proxy component — a gateway server that is assigned in the Veeam Backup & Replication console. The backup data is transferred from the Veeam Agent computer to the gateway server, then it is transferred from the gateway server to the repository.

• Direct connection. With this connection type, Veeam Agent connects directly to the repository. The backup data is transferred from the Veeam Agent computer to the repository without proxy components. The access to this repository is managed by Application Programming Interface (API) that is provided by the object storage provider.

Considerations and Limitations

Before you configure a backup job to store backups in an object storage repository, consider the following:

• Veeam Agent does not support direct backup to the Microsoft Azure Blob Storage under the general-purpose V1 storage account type.
• You can store backups only in those S3 compatible storage repositories that are accessible over the HTTPs protocol.
• [For object storage added as a Veeam backup repository or Veeam Cloud Connect repository] If you want to back up your data directly to the S3 compatible storage, you must additionally specify access permissions settings for the storage. For direct access, enable the Agents share credentials to object storage repository or the Provided by IAM/STS object storage capabilities access control option. For more information, see the Managing Permissions for S3 Compatible Object Storage section in the Veeam Backup & Replication User Guide.

• [For object storage added as a Veeam backup repository or Veeam Cloud Connect repository] Data recovery options are not available if you access the object storage repository using credentials with the read-only access permissions.

• Veeam Agent does not support backup to object storage for which lifecycle rules are enabled. Enabling lifecycle rules may result in backup and restore failures.