Backup of an S3 Compatible Object Storage with Warning

[GianlucaCroci]

Good Morning,

We've several backups to different S3-compatible object storage devices, and one of them displays a warning when it runs.
In Veeam, the object storage devices (PureStorage S3) are all configured the same way.

In the backup steps, after selecting the proxy to perform the backup operation, the warning displays:

8/25/2026 3:03:26 AM :: Unable to backup "Object Storage Name" bucket property: 'Accelerate Configuration', 'Access Control List', 'Encryption', 'Logging', 'Notification Configuration', 'Ownership Controls', 'Replication Configuration', 'Request Payment', 'Tagging', 'Website', 'Analytics Configuration', 'Intelligent Tiering Configuration', 'Inventory Configuration', 'Metrics Configuration'

How can we resolve this issue? Is the problem Veeam-side or PureStorage configuration-side?

Thanks in advance for your help.
Best regards
Gianluca Croci

[pybfr]

Gianluca, the only way to find out is to look in the logs to see what happens.
Please open a support ticket and communicate the number here, as per forum rules.

[sfirmes]

@GianlucaCroci those bucket properties are typically unique to AWS S3 so most other object storage platforms do not have them implemented, so VBR is generating the warning to notify you that those properties weren't backed up.

This is the expected behavior and not an issue that needs to resolved.

Hope this answers your question.

[GianlucaCroci]

Thanks for the replies.

What I don't understand is why I don't get these warnings with the other two CopyJobs, but always get Success.

Since they're typically AWS S3, isn't there a way to disable them, since they're not AWS?

The important thing is that the information is saved, but having unnecessary warnings isn't nice, especially if you don't know it's correct (just in case someone else checks the jobs and doesn't know this).

We're still using 12.3. Does anything change with 13, perhaps?

Thanks again

[sfirmes]

The behavior in VBR v13 is the same.

Are all 3 jobs backup copy jobs using the same object storage and only 1 of the 3 is producing the warnings?