Permanent Failover Failed

[network.security]

Dears,
I am facing below issue while doing permanent failover. I have mistakenly deleted the original vm server after failover to the replication vm in different host. Now when i run the permanent failover it stated the error message below and grayed out saying in process.

07/12/2022 10:10:59 AM Error Permanent failover failed at 12/7/2022 10:10:59 AM. Error: There is no oib with id '5cac6cfe-cbe7-4952-85ad-044e3a5088e8'


Case #05767690

[Mildur]

Hi Mohamed

Thanks for the case number.
Please give our support team some time to solve this request. The case was just opened minutes ago.
Such issues cannot be effectively analyzed over the RnD forums.
Please also upload your debug logs. They are missing in your case. That's the first thing our support team will ask for.
https://www.veeam.com/kb1832

Best,
Fabian

[network.security]

Hi Fabian,
the logs were uploaded. actually this issue from the failover plan, which doesn't have logs for download. i have downloaded from the component.

[Mildur]

Hi Mohamed

Permanent Failover is processed mainly by the backup server and hypervisor.
If you have downloaded logs from all components, then our support will have everything they need.

The old VM should not be required for a permanent failover. Failovers can also be done when you lose the original VMs.
It must be possible to do a failover/permanent failover even when you have lost your old infrastructure.
Let's see what our support will find out.

Best,
Fabian

[network.security]

Dear Fabian,
Thank you so much for the update. I am waiting for Veeam support for the clarifications.

[network.security]

Dear Fabian,
Just a quick question. If we don't process Permanent Failover will it impact anything on the new production server after some days /time.

[EugeneK]

Permanent Failover is what effectively instructs the system to preserve and commit the changes made during the Failover process to promote the Replica VM to become a permanent Production VM.
As a part of the Permanent Failover operation, the changes written to the delta files (snapshots) are merged into the base disk of the VM. The longer the VM runs off the snapshots (assuming it's a snapshot-based type of replication), the more changes are written to delta's, which may lead to the performance degradation due to the length of the snapshot chain.

More details on the steps performed are available here

[network.security]

Dear Eugene,
Thanks for your reply. In my case what will you suggest as the Permanent Failover was failed and it is showing the status as still Processing. My previous original production server has been deleted before permanent failover. What could be the best practice in this scenario. Please help me to overcome the issues which i might face in future.

Thanks

[EugeneK]

Hi Mohamed,
The best course of action is to continue working with the support team to troubleshoot the issue being experienced, they will be able to recommend to remediation steps depending on the findings.