Object Storage
Backup data is stored in the form of objects on object storage, for Amazon these are objects stored in an S3 bucket.
Amazon S3 buckets are used as backup repositories. VBA supports tiering from S3 standard to S3 glacier storage. There are some special considerations when using an object storage repository regarding sizing.
Object Storage Data Size
Because VBA compresses the source data before putting it in object storage in general the required space in object storage will be only ~50% of the source data. Compression depends heavily on the type and structure of source data and can vary.
| Item | Data size |
|---|---|
| Average size of backup data | 40% - 50% |
| Compression rate of backup data | 50% - 60% |
Object Sizes
Depending on the job type VBA stores different objects on S3. The below table will show the object size per relevant type.
| Object type | Size |
|---|---|
| Backup data (S3 Standard) | 1 MiB compressed (~512KiB) |
| Backup data (S3 Glacier and S3 Glacier Deep Archive) | 512 MiB |
| Metadata | 4KiB per GiB of VM source data |
Amazon S3 Bucket Limits
You can send 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second per prefix in an Amazon S3 bucket. VBA has built-in mechanisms to assure these are not hit. While you could use 1 bucket to store all your data, Veeam recommends using multiple buckets as well as the benefit on using S3 Glacier for long-term archiving to achieve a cost-effective design.
Additionally, it is recommend to use dedicated IAM roles for the repository role as listed in the user guide.
Cost Estimation
VBA comes with a built-in cost calculator. This uses publicly available price lists so may not reflect your exact cost should you have custom pricing or an enterprise agreement in place. Changes are automatically reflected within the policy and can be seen in the top header. Full details can be found on the cost estimation step.