Help with Datastore Name and Volume/UUID Report

Question

Our Storage team is looking for a report that shows all the datastore names with the volumes and/or storage volume UUID.  They use this report to refer to during our disaster recovery exercises. We had a custom SWQL report that worked prior to the SolarWinds 2026.1 upgrade, but now it no longer returns any results.

Question

Can you advise what process or service is responsible for populating Orion.SRM.LunsToVIMLuns, and what troubleshooting steps should be performed to restore SRM-to-VIM LUN correlation data after the upgrade? Can someone please help me create a new report?

Working Components

The following entities are populated and returning data:

* Orion.SRM.StorageArrays
* Orion.SRM.LUNs
* Orion.VIM.Luns

Storage arrays are healthy and continue to be polled successfully.

Non-Working Component

The following mapping entity exists but contains zero records:

1 SELECT TOP 1000

2    StorageArrayID,

3    LunID,

4    VIMLunID,

5    Manual

6 FROM Orion.SRM.LunsToVIMLuns

Result: 0 rows returned.

Impact

Our custom report relies on Orion.SRM.LunsToVIMLuns to correlate:

1 Storage Array

2 → SRM LUN

3 → VMware LUN

4 → Datastore

5 → ESXi Host

Because Orion.SRM.LunsToVIMLuns is empty, all reports that depend on this correlation return no data.

Additional Validation Performed

* Confirmed Orion.SRM.LunsToVIMLuns entity exists in SWIS metadata.
* Confirmed the entity still exposes:* StorageArrayID
* LunID
* VIMLunID
* Manual

* Confirmed Storage Arrays, SRM LUNs, and VMware LUNs are all present and returning data.
* Confirmed that joins against Orion.SRM.LunsToVIMLuns return no results because the mapping table itself is empty.

PJC · Answer

Orion.SRM.LunsToVIMLuns is populated by SRM’s automatic end-to-end mapping process, so I wouldn’t try to rebuild it directly in SQL. For the affected array(s), open Storage Summary > array > Management and run an immediate Topology poll, then allow it to complete before rerunning the report.

Because this is the SRM-to-VMware side of the mapping, also confirm that VMAN/VIM is installed, integrated, and still polling the vCenter successfully. If the entity is still empty after a successful topology poll, I’d open a support case and include the SRM DataProcessor.log, the relevant SRM.Pollers.Jobs log, and the output of the mapping query so the post-upgrade behavior can be investigated.