Duplicate Identifiers Causing Issues with 3rd party backup solutions
search cancel

Duplicate Identifiers Causing Issues with 3rd party backup solutions

book

Article ID: 430944

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Zerto logs show issues getting storage policy information:

VCDStorageProfilesCollector,CollectAsync,Updating Reflection of Storage Profile [ID=<STORAGE_PROFILE_NAME>]. The same identifier returned twice from the environment.,

Environment

Cloud Director 10.6

Cause

The issue is due to stale entries in datastore table.
When a datastore is moved into a storage pod in vCenter, VCD's VC listener removes the datastore reference from "datastore" table and adds the storage pod reference.
In the problematic cases, for some reason this removing part did not work.

Possible causes:

  1. vCenter updates are not received by VCD. This resulted in the above case of stale entries.
  2. vCenter update is received but while processing there is a failure in VCD.
  3. There is a corner case in VCD's update logic, that misses to update the datastore table

Resolution

Workaround:
To work around this issue, open a new case with the Broadcom support referencing KB article 430944. For more information, see How to Submit a Support Request