RestorePoint HierarcyObjRef, HierachyRoot ID / Unique_ID mismatch via API?

[benyoung]

Hi Team

Diagnosing an issue with an integration when moving from v11>v12. I had this on an upgraded server and have since built a new environment, same thing.

Essentially it looks like, unique_id is being returned as the ID when you query HierarchyRoots, then when you try to construct a query to get vmrestore points using this ID via the query server I,e Filter=HierarchyObjRef=="urn:VMware:Vm:b5a60ace-7623-407b-b008-777e956ee555.vm-31017"

Dumpster diving through the database shows me that the ID on the Host record is the on the restore point and not the unique_id - so a bug somewhere in there either incorrectly being constructed on the HierarchyObjRef or the Hierarchy ID is incorrect.

Example ref from the restore point node
<HierarchyObjRef>urn:VMware:Vm:b5a60ace-7623-407b-b008-777e956ee555.vm-31017</HierarchyObjRef>

b5a60...

Hierarchy root query
<Ref UID="urn:veeam:HierarchyRoot:27cfa99b-d35a-41e4-936f-2804a0083074" Name="vcsa....
... <HierarchyRootId>27cfa99b-d35a-41e4-936f-2804a0083074</HierarchyRootId>

27cf...

Looking at the database host table, per above ID == b56... and unique_id for that record == 27cf..

More of a writeup/screenshots here if you need > https://benyoung.blog/investigating-vee ... ning-data/

[benyoung]

Known issue via support, was provided Fix_482670_49d411695f so request that if you come across in anytime soon otherwise assume it will be rolled up into the next major patch/release