Hi @pedro12562 -

Not sure of your error there.

Are you attempting to use the Replication job at your original/source site from previously? When you do permanent failover tasks, you are essentially undoing your source Replica configuration/job. I think what you have to do is just recreate your source job then point to the VMs you have at your DR site. Did you delete/remove your orig job and attempt to recreate it? 

Yes, so permanent failover I needed to use because the production server had to be formatted so I started the replicas on the backup server and then made them permanent, after we managed to reestablish the production server, I recreated the replica routines to replicate to the server production and finally I made it permanent too, at the end of this, I deleted the routines again and created them from scratch pointing back to the backup server, as it was before the problem occurred, however, this problem is occurring:

Process:

1- Enabled replicas on the backup server;

2 - I made the replicas the permanent backup server;

3 - Formatted production server and recreated replica routines pointing from the backup server to the production server;

4 - Enabled replicas on the production server and made them permanent;

5 - Deleted replica routines and recreated them pointing from the production server to the backup server, however, it is failing.

Not sure if this post from Shane will help but something to look in to - Replication Job Errors: "Object Reference Not Set..." and "Failed to Create Processing Task for VM...Host ID not Found" | Veeam Community Resource Hub

Hey Chris...thanks for sharing that! I don’t think that applies here because that had to do when I replaced ESXi Host hardware in Veeam. Error was Host related, not VM. But good share regardless 

@pedro12562 - Hmmm….did you restore your server from DB Config restore? Something may be ‘stuck’ in your DB and needs to be cleaned up. Not entirely sure. At this point, I recommend contacting Veeam Support.

Thanks for the answers, I can try to reconfigure Veeam, it's a possibility, I'll get back to you and let you know if I was successful or not, but I've already registered the ticket via support channel number 07361670, let's see if you can help me, in any case I'll post it here on this page topic as you test it, it may help someone who may be having this same problem.

Ok great. Yes, keep us posted. 

Best of luck as I am sure support will get it resolved.

Hello everyone, you managed to find the solution, unfortunately until I resolved it I did not hear back from support due to the low availability of the support team and my case was archived automatically

However, here is the solution I found, it was a "Hyper-V Virtual Machine Management" service, however, the service was not starting at all, it reported that there was not enough memory available to start, even though it was available, in Searching for articles on the internet, I found the resolution on the Microsoft forum, follow the article below that I found, renaming the file "data.vmcx" to "dataold.vmcx" located in "C:\ProgramData\Microsoft\Windows\Hyper-V" I managed reestablished the service and the replica routines started to execute correctly, thank you everyone for your help.

Here is the Microsoft forum link:

O serviço Hyper-V VMMS não inicia - Microsoft Q&A

Glad you were able to figure things out.

Nice! Thanks for sharing what you did to get working again @pedro12562