In VRO version 13.0.0.1167- Unable to perform Commit failback from VRO its failed.

What the underlying hypervisor?

Hello Jason ,

Thank you for your interest. The underlying hypervisor being used is VMware.

Regards.

Sumit

Hello Sumit, 

Can you confirm that you performed the RUN action on the plan again, after failback was complete?
The process is VRO is to run the replica plan for every stage - Failover, Failback, Commit Failback. After the 3rd run, the replicas will be back in a state where replication job can run.
If you ran the plan while it was in “failback complete” stage, what was the result? (the expected result is that the plan would very quickly process all the VMs and move to “Commit failback complete”)

Hey Jason, FYI: as Sumit is speaking from VRO and Replication - so there’s only VMware as the Hypervisor, who can handle this 😉

Besides that: what Alec mentioned should do the trick.
I wouldn’t recommend to do your steps within VBR, as VROP should be aware of it.

Otherwise, opening a Support case could help here.
Best, Markus

Dear ​@AlecKing , ​@Dynamic 

Thanks for your responce.

As per the design of Veeam Recovery Orchestrator (VRO), the Commit Failback operation should be performed directly from VRO. This is the expected behavior. However, when we attempt to perform Commit Failback from VRO, the operation does not complete successfully.

Currently, the “Commit Failback” action cannot be triggered via VRO.

As a temporary workaround, we log in to Veeam Backup & Replication (VBR) and manually perform Commit Failback from VBR. If this step is not performed, we are unable to run or re-run the replication job.

After manually performing Commit Failback in VBR, the replication status changes to Ready, and the job is also cleared from VRO.

Therefore, at present, we are unable to perform Commit Failback directly from VRO and must complete this step manually from VBR. Under normal circumstances, this operation should be executed entirely through VRO, without the need to access or perform any actions in VBR.

Please find below message after perform failback.

State | Failback | Complete, no errors, no warnings, no malware issues |Error| Type |Replica

Please share your valuable inputs.

Regards

Sumit

Did you read what Alec said about the run process?  Did you attempt it?  He knows VRO so I would suggest following his advice.

Hi ​@sumit.saini - as others have mentioned...we suggest you attempt what Alec suggested or, if doing so doesn’t work, it would be best to open a Veeam Support case to take a look at what’s going on in your VRO environment. Please keep us posted.

Best.

Thanks for your responce. ​@coolsport00 ​@Chris.Childerhose 

I will execute the process again and share the results once completed.

Regards

Sumit

Hi ​@sumit.saini , 
The message you provided  - "State | Failback | Complete, no errors, no warnings, no malware issues” - means exactly that , that failback is complete - not commit failback. If you have failback complete status, you should run the plan again (click >Run in the main toolbar). You will be offered options “Commit failback” and “Undo failback” (undo would return you to failover state). Choose “Commit failback” and the plan should quickly complete and the status of replicas in VBR should be moved to Ready.

If you are getting an error when you run the plan from Failback state, then I would also suggest you open a support case, so that our team can dive into your logs to find the issue.

​@AlecKing , Thanks for your reply.

I will execute the process again and share the results once completed.

Let us know how you make out with the process. At that point if it doesn’t work open the case with support. Good luck!

Dear ​@kciolek ​@AlecKing ​@coolsport00 

Thank you for your response and for showing interest.

This is essentially a bug in VRO, specifically in version 13.0.0.1167.

Thanks & Regards

Sumit Saini , Oman

Subject: VRO Commit Failback Issue

Dear All.

Basically, we cannot perform Commit Failback from VRO due to a bug.

Temporarily, we have been performing this task from the VRO side, and the challenge has now been resolved. after that respication is also run automaticall as per sechedule.

Thanks & Regards,
Sumit Saini

​@sumit.saini , could you please explain what is the “bug”, what is the behaviour or error? You have not provided enough information for anyone to comment meaningfully on your problem. Have you raised a support case? If so could you share the ID?

Dear ​@AlecKing 

Yes, I have raised a support ticket, and this has been confirmed by the Veeam Support team.

BR

Sumit

Thank you for the update ​@sumit.saini . Please keep us posted on the resolution Support offers for this “bug” so it benefits the Community if they run across the same issue.

Thank you.

​@coolsport00 I will definitely share an update after finding a solution.

Well at least you determined it was a bug and can be fixed in a patch. Looking forward to the patch results.

​@Chris.Childerhose 

Yes, I am also waiting for the fix because currently I need to perform the Commit Failback manually from VBR.

Regards

Sumit

Great...thanks!

glad to hear it was a bug, and hopefully have the patch available soon. Let us know if it fixes the issue

Dear ​@kciolek Sure I will.