Direct Backup to Object Storage Considerations and Limitations
This section contains the following limitations for direct backup to object storage:
- The periodic compact of a full backup option is not available.
- 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.
Note |
To produce an independent full backup, you can also run the active full backup manually or specify a periodic schedule for it. Note that this method will significantly increase object storage space consumption. |
- 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.
- You cannot use direct backup to object storage to keep backups created with Veeam Plug-ins for Enterprise Applications.
- You cannot use direct backup object storage repositories to keep backups created with Veeam Agent for Oracle Solaris and Veeam Agent for IBM AIX.
Note |
Note that you can use direct backup object storage repositories to keep backups created with backup copy jobs for Veeam Agent for IBM AIX and Veeam Agent for Oracle Solaris. |