Hi,
While reviewing the behavior of backup copy jobs to S3-compatible object storage, we noticed that there is no explicit documentation or configurable option describing how multipart upload is handled.
To better understand the product behavior from a design perspective, we would like to confirm the following points:
1. When Veeam Backup & Replication uploads backup data to S3-compatible object storage, does it internally use S3 Multipart Upload based on object size or other conditions?
2. Is this behavior fully automatic and not configurable by users (that is, no supported option to enable, disable, or limit multipart upload usage)?
3. Are there any official considerations or recommendations regarding incomplete multipart uploads (for example, cleanup or lifecycle handling), or is this entirely managed by the object storage side?
We would appreciate your clarification to ensure an accurate understanding of the product behavior.
Thanks,
Rin
-
rin
- Novice
- Posts: 8
- Liked: 2 times
- Joined: Jun 24, 2025 6:40 am
- Full Name: Rintaro Tamura
- Contact:
-
david.domask
- Product Manager
- Posts: 3658
- Liked: 888 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Multipart Upload Behavior for S3 Backup Copy Jobs?
Hi Rin,
Veeam uses a unique structure for backups to Object Storage repositories; the data blocks from the backup file are "chunked out" into smaller objects and sent to S3 instead of sending the entire backup file as a single entity.
In short, there is no need for end-users to adjust anything regarding MultiUpload.
Veeam uses a unique structure for backups to Object Storage repositories; the data blocks from the backup file are "chunked out" into smaller objects and sent to S3 instead of sending the entire backup file as a single entity.
In short, there is no need for end-users to adjust anything regarding MultiUpload.
Neither, it is all managed by Veeam. It is imperative that you do not enable life-cycle policies or manually alter data on the bucket, the data must be managed by Veeam exclusively.3. Are there any official considerations or recommendations regarding incomplete multipart uploads (for example, cleanup or lifecycle handling), or is this entirely managed by the object storage side?
David Domask | Product Management: Principal Analyst
-
rin
- Novice
- Posts: 8
- Liked: 2 times
- Joined: Jun 24, 2025 6:40 am
- Full Name: Rintaro Tamura
- Contact:
Re: Multipart Upload Behavior for S3 Backup Copy Jobs?
Hi Domask,
Thank you very much for your detailed explanation.
This clarified the internal behavior and helped me better understand how Veeam manages data in object storage. The explanation about the chunked structure and lifecycle handling was especially helpful.
I appreciate your support.
Thanks,
Rin
Thank you very much for your detailed explanation.
This clarified the internal behavior and helped me better understand how Veeam manages data in object storage. The explanation about the chunked structure and lifecycle handling was especially helpful.
I appreciate your support.
Thanks,
Rin
Who is online
Users browsing this forum: No registered users and 8 guests