Skip to main content
  • EN

After upgrading to v 12.3.2.3617, I have found a default setting which breaks certain elements of VBR and VCC.

When creating an object storage repository, Automatic bucket creation enabled is the default!

Step 4. Specify Object Storage Settings - User Guide for VMware vSphere

Leaving this option on creates issues when using this repository for the following backups.

  1. Veeam Cloud Connect

 

  1. EntraID

Configuring Log and Cache Repositories - User Guide for Microsoft Entra ID

 

  1. Unstructured data backup

 

  • The problem is that going back and unchecking this option does not actual disable it.
  • In addition, removing the repository and re-adding it with the option disabled also does not disable it.
  • The repository needs to be created the first time with this option disabled.
  • This is a major issue if one is unaware of the consequences of this option and just click “Next” through it or if repositories are being created with a script and this option is not disabled.
  • If the repository is created with that option disabled, it can be enabled afterwards

I hope this discovery helps you before you bang your head against the wall trying to fix it. I also hope that Veeam changes this to be disabled by default.

 

Thanks,

 

Hin

Hi ​@HangTen416 

Yes, It’s on my list to discuss the limitation with the team.

 

Best,

Fabian

Thanks for sharing this Hin.  We both work together and discovered this today when testing VCC with Pure Flashblade using S3.

Hi ​@HangTen416 

Yes, we are aware and It’s on my list to discuss the limitation with the team.

 

Best,

Fabian

Please tell them to have it Disabled by default and you need to turn it on. 😉

Hi ​@HangTen416 

Yes, It’s on my list to discuss the limitation with the team.

 

Best,

Fabian

Thanks Fabian! ✌️🤞

For Veeam 13 if it sees full SOSAPI support (at least for the Beta version 🙂 ) it will disable the automatic bucket creation. I think the confusion was because Veeam switched it to default setting in Version 12.3 whereas (if I remember it correctly) when it appeared in version 12.2, you had to turn it on manually. 

For Veeam 13 if it sees full SOSAPI support (at least for the Beta version 🙂 ) it will disable the automatic bucket creation. I think the confusion was because Veeam switched it to default setting in Version 12.3 whereas (if I remember it correctly) when it appeared in version 12.2, you had to turn it on manually. 

 

That is correct. This was a change for 12.3.

Hi Geoff

 

v12.3 → release of Multi Bucket feature for S3 compatible object storage, default for new repositories “multi bucket disabled”

v12.3.1 → default for new repositories updated to “multi bucket enabled”

 

For Veeam 13 if it sees full SOSAPI support (at least for the Beta version 🙂 ) it will disable the automatic bucket creation. 

Already in v12.3.2. Maybe also in earlier v12.3 builds. 
Multi-Bucket option gets disabled when creating a repository with ObjectFirst:

 



Best,

Fabian

Hi Geoff

 

v12.3 → release of Multi Bucket feature for S3 compatible object storage, default for new repositories “multi bucket disabled”

v12.3.1 → default for new repositories updated to “multi bucket enabled”

 

For Veeam 13 if it sees full SOSAPI support (at least for the Beta version 🙂 ) it will disable the automatic bucket creation. 

Already in v12.3.2. Maybe also in earlier v12.3 builds. 
Multi-Bucket option gets disabled when creating a repository with ObjectFirst:

 



Best,

Fabian

Thanks for the clarification, Fabian!

Hi Geoff

 

v12.3 → release of Multi Bucket feature for S3 compatible object storage, default for new repositories “multi bucket disabled”

v12.3.1 → default for new repositories updated to “multi bucket enabled”

 

For Veeam 13 if it sees full SOSAPI support (at least for the Beta version 🙂 ) it will disable the automatic bucket creation. 

Already in v12.3.2. Maybe also in earlier v12.3 builds. 
Multi-Bucket option gets disabled when creating a repository with ObjectFirst:

 



Best,

Fabian

yup thanks for the correct numbering 😉. I noticed in 13 beta they removed the yellow warning as well when successfully created without multibucket 

Comment


Terms & Conditions