VBO Object Storage Repository | Backup Job cant detect new repository

[Remi27]

Hello all.

I've configured an S3 storage from Minio within the "Backup Infrastructure" in Veeam Backup for Microsoft 365.

I created a repository for the cache (metadata), and I extended it with the S3 storage to this repository.

However, when I try to create a new backup job, the repository I just created does not appear as an option.

I found a similar issue (https://community.veeam.com/discussion- ... -menu-3829), but it seems that the new UI of Veeam Backup for Microsoft 365 has resolved it. When creating a new repository, the wizard now allows you to configure both the cache and the S3 storage extension in a single step.

What am I missing?

Best,
Remi

[Mildur]

Hello Imer

May I ask, are you using an immutable Min.IO bucket for your backup repository? In Version 7/7a, immutable repositories cannot be used for backup jobs and therefore will not be displayed in the job wizard.
Please update to our newest release V8 which will allow you to use immutable repositories for primary backup jobs.
https://www.veeam.com/kb4106

If V8 doesn't solve it for you, then you need to contact our customer support team. Please provide me with the case number if you open a case.

Best,
Fabian

[Remi27]

Hi Fabian,

Yes, exactly! I actually managed to solve the issue by creating new buckets that weren't immutable. So, I also concluded that VBO might not support immutable buckets yet.
Thank you very much for your confirmation and support.

Regarding the in-place upgrade of Veeam Backup for Microsoft 365 from my current version (7), I assume I still need to wait, right? I read on the download site that there are still some unresolved issues.

Best,
Imer

[Mildur]

Hi Imer

I suggest to wait for our first cumulative patch if you "upgrade an existing environment" to v8. Our RnD team is preparing the first patch, but I don't have an ETA for you.
But for a new deployment, you can start with V8 right away. Even an upgrade of a not yet configured V7 deployment should be ok. Especially if you don't have any backups or backup repositories connected to it.

Please note, you will not be able to "migrate your mutable primary repository" to a "immutable primary repository" after the upgrade. If you want to have immutable backups for your primary jobs, then better to start with your backup jobs directly on the new V8.

Best,
Fabian

[Mike Resseler]

There are some issues if you are running v7 which was an upgrade of v8, and it is only in very rare cases depending on your M365 configuration. But yes, we are solving those issues as we speak and hopefully we have a new build very soon that solves them

[Mildur]

Hello @Remi27

The first patch Mike and I have mentioned has been now released:
https://www.veeam.com/kb4656

Best,
Fabian