Direct Backup to Object Storage Considerations and Limitations

This section contains the general limitations for direct backup to object storage:

• The periodic compact of a full backup option is not available. For more information, see the following sections related to specific platforms:

• VMware vSphere — Maintenance Settings.
• Microsoft Hyper-V — Maintenance Settings.

• By default, Veeam Backup & Replication uses the forever forward incremental method to back up directly to object storage repositories. If you want to create a new full backup, enable the long-term retention policy (GFS). In this case, Veeam Backup & Replication will create synthetic full backups and, therefore, will produce a forward incremental backup chain.

• In direct object storage repositories, Veeam Backup & Replication stores backup chain in the per-machine backup with separate metadata files format. For more information, see Backup Chain Formats.
• You cannot back up directly to Amazon S3 Glacier Storage, S3 compatible with Data Archiving and Azure Archive Storage object storage repositories. These types of object storage repositories can only be used as archive extents of the scale-out backup repository. For more information, see Archive Tier.
• You cannot use direct backup to object storage to keep backups of applications running on Kubernetes persistent volumes created by Veeam Kasten Plug-in for Veeam Backup & Replication.

Unix-Based Veeam Agent Computers Limitations

Consider the following limitations:

• Veeam Agent for Unix supports only Amazon S3, as well as these types of S3 compatible storage: MinIO, IBM Cloud and Wasabi Cloud.
• [For Oracle Solaris 10 1/13] To enable Veeam Agent connection to S3 compatible storage repositories, you must install the necessary CA certificates. For more information on installing the certificates, see this Veeam KB article.
• Veeam Agent for Unix only supports backup repositories that are configured to have direct connection to object storage.