Datastore in Orchestration Plan not showing any VM

Hi ​@Madi.Cristil ​@safiya please move this question to the VRO Heroes Den.

Thank you. 

​@Dynamic is an expert in VRO. Can you help?

Hi ​@spider32, trigger the Data Collection within the embedded VONE instance is also one of the first steps i run, when VRO not show all existing Inventory Items (e.g. VMs).

The steps you did (clone or recreating to another Recovery Plan) is also a good approach.

For another test, you could tag your specific VMs (instead of the Datastore) and check, if you see them (after running an additional Data Collection).

But if this not resolves your issue, i would contact support. But maybe I’m missing something here. 

I had a similar behaviour almost a year back at a customer site - only option was to create a Support Case. The issue in that case was in regards to the embedded VONE DB. After some steps with support, we received a SQL query to get rid of this problem.

Thanks for the mention ​@lukas.k. 

Yes, I agree. I had to revert back to an older version of the DB to make the Orchestration work again. I still have a ticket open with support (open now for several weeks) but they said they see no issue with the DB side. I informed them that there may some slow corruption going on inside the DB so they are looking at it.

I faced a similar issue before. If the datastore is visible but no VMs are showing in the orchestration plan, try these steps:

• Re-run the data collection to refresh metadata.
• Double-check the scope and filters in the orchestration plan—some VMs might be excluded due to tags or job selection.
• Avoid cloning the plan; instead, create a new orchestration plan from scratch to ensure all references are fresh.
• Make sure Veeam ONE has the right permissions and visibility to access vCenter objects.

If the issue persists, opening a support case with Veeam and sharing the orchestration plan logs would be the best next step.

Thanks for sharng the solution ​@spider32