Bug Report (+ Workaround) - Cannot delete repository which was used as Entra cache

[FSM365]

Hi,

Bug: Cannot delete a repository which is used as cache for Entra ID Tenant, if the Tenant was deleted.
Workaround: Create a new Tenant and change the cache repository, afterwards you can delete it.

Long version:
I had the following problem: For testing purposes I added our Entra ID Tenant in Veeam (Inventory -> Microsoft Entra ID -> Add Tenant Wizard). On the first page you can select a cache repository.
I changed this to a specific repo, let's call it "Repo1".

After I tested the Entra ID functionalities, I deleted the Entra ID Tenant from Veeam. Some time later I wanted to delete Repo1 but I couldn't "because it is in use". In the details there was my Tenant and in the description "File share". Here is a screenshot:
https://imgur.com/aA1DKBV

I searched for anything related to this in the Veeam console but couldn't find anything as we had not Tenants added at this point and no file shares.
Finally I remembered, there is the cache option on adding a new tenant. You cannot change the cache without finishing the wizard. So I fully added the tenant again, changed the cache to the "Default repo" and voila - afterwards I could remove Repo1 without a problem.

[Mildur]

Hello Fabian

Thank you for the report.
It's a known issue and scheduled to be fixed in one of the next patches.

Best,
Fabian

[dtwiley]

Was this addressed? We're running 12.3.2.4165 and just ran into this issue when migrating to a new repository as we don't use Entra ID backup any more.

[Mildur]

Yes, the issue discussed in this topic was addressed with version 13.

Best,
Fabian

[dtwiley]

17GB download and 2 hour install later (still installing loads of components we don't need by default), I still can't delete a backup repository which has an orphaned reference to an Entra ID backup cache. How can I get rid of this repo without setting up a new Entra ID backup that I dont want and creating the same issue on the new repo?

[Mildur]

Hi Dave,

The bug discussed in this topic is marked as resolved in our system.
If you’re still experiencing issues, please contact our customer support team so they can review your log files.
Kindly share your case number with me as well.

Thanks,
Fabian

[dtwiley]

Dont worry, I created a new Entra ID connection and moved the cache, deleted the Entra ID connection and then deleted the old repo.
It seems you've fixed the problem where deleting the Entra ID connection leaves a cache reference behind on the repo, but that's no good for repos which already have orphaned Entra ID caches.

I'm sure you guys can recreate.