Restore Point existence - No valid restore point found

[dlbenson1979]

Hey, I am a new VDRO user, and I have just setup my vdro server and I am ready to test orchestration plans. I'm running into an issue, and I was hoping that the forum could assist.

I have a Prod site VBR server, with a DR site VDRO server. I have connected both vcenters in the configuration and tagged my cluster/hosts appropriately. I have created my recovery location, and everything seems to be working so far. When I create a orchestrator plan to perform a Restore Plan on either Prod/DR side, it fails during validation at the Restore-recovery step with: [Restore Point Existence] - No valid restore point found. At first I thought that this was due to the backup file(s) being out of the RPO range, so I upped the plan to 240 hours, but I still get the same result.

I have tested with both DR and PROD site, and this is the same across all VMs added to the job. The step [Recovery VM Job/Policy] returns as successful and even shows the correct backup files that are needed to perform the orchestration plan.

I'm sure you need more detail, so please let me know if there is anything else i can provide.

Thanks!

[HannesK]

Hello,
That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Without case number, the topic will eventually be
deleted by moderators.

I found one old hint on that error message... do you have enterprise plugins in your environment (SAP, Oracle)?

Best regards,
Hannes

[dlbenson1979]

Thank you for the response. I will get the ticket created this morning. I believe I have enterprise plugins, but I currently only use SQL, AD, and Exchange plugins.

Edited: Case #05400666

[HannesK]

Hello,
okay, the applications above are without plugin / agent. That's the "normal" agentless approach aka "application aware processing".

In older versions, there were issues with Oracle RMAN / SAP HANA BackInt plugins. But that seems to be irrelevant here. Let's see what support says.

Best regards,
Hannes

[dlbenson1979]

I believe I have found the solution:

On the Veeam DR Orchestrator Administration interface, under Orchestrator Agents, I selected the agent for the PROD site VBR server and selected repair. Once this was done, I performed a data collection using the VDRO server's embedded Veeam One. Once that was done, I ran the orchestration plan and it passed the readiness check without issue.

I will update my Veeam ticket as well, but I wonder what made the agent not work properly. The orchestration plan was reporting that the agent was healthy even when the readiness check was failing.

Anyway, that's the update.

[jklaw91]

Good info. I continue to find Orchestrator very lacking in terms of bugs and providing helpful troubleshooting and/or information. I would rate B&R a 9 out of 10, but Orchestrator a 3 or 4 out of 10. Jury is still out as to whether or not it is worth it. Failover plans weren't fancy but were very predictable.