Skip to main content
Solved

I can't create replicas

P

I had a problem with our host server in production and I had to activate the replicas on our second backup host, later I applied permanent Failover, after reestablishing the first host that had the problem, I created replica routines from the backup host server to the main one and I applied permanent Failover, finally, I recreated the replication routines from the main server to the backup server, however, it is no longer working, an error keeps appearing that I couldn't find on the community forum.

 

Failed to process replication task Error: Failed to create planned VM configuration (path: 'D:\9ca0c3d4671a45888343cf0b4ef75605(20)\Virtual Machines\545b475e-2040-49fe-bffb-d9133f3739f4.vmcx'). [WMI] Empty result.

Best answer by pedro12562

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

View original
Did this topic help you find an answer to your question?

10 comments

coolsport00
Forum|alt.badge.img+20
  • coolsport00
  • Veeam Legend
  • 4145 comments
  • July 31, 2024

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? 

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
MarcoLuvisi
P
2 people like this
  • MarcoLuvisi
    MarcoLuvisi
  • P
    pedro12562
P
  • pedro12562
  • Author
  • Not a newbie anymore
  • 3 comments
  • July 31, 2024
coolsport00 wrote:

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.

Chris.Childerhose
coolsport00
MarcoLuvisi
3 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • coolsport00
    coolsport00
  • MarcoLuvisi
    MarcoLuvisi
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • 8502 comments
  • July 31, 2024

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

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
coolsport00
MarcoLuvisi
P
3 people like this
  • coolsport00
    coolsport00
  • MarcoLuvisi
    MarcoLuvisi
  • P
    pedro12562
coolsport00
Forum|alt.badge.img+20
  • coolsport00
  • Veeam Legend
  • 4145 comments
  • July 31, 2024
Chris.Childerhose wrote:

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.

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
MarcoLuvisi
P
2 people like this
  • MarcoLuvisi
    MarcoLuvisi
  • P
    pedro12562
P
  • pedro12562
  • Author
  • Not a newbie anymore
  • 3 comments
  • August 1, 2024

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.

Chris.Childerhose
coolsport00
MarcoLuvisi
3 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • coolsport00
    coolsport00
  • MarcoLuvisi
    MarcoLuvisi
coolsport00
Forum|alt.badge.img+20
  • coolsport00
  • Veeam Legend
  • 4145 comments
  • August 1, 2024

Ok great. Yes, keep us posted. 

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
MarcoLuvisi
P
2 people like this
  • MarcoLuvisi
    MarcoLuvisi
  • P
    pedro12562
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • 8502 comments
  • August 1, 2024
pedro12562 wrote:

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.

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

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
MarcoLuvisi
P
2 people like this
  • MarcoLuvisi
    MarcoLuvisi
  • P
    pedro12562
P
  • pedro12562
  • Author
  • Not a newbie anymore
  • 3 comments
  • Answer
  • August 7, 2024

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

Chris.Childerhose
coolsport00
2 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • coolsport00
    coolsport00
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • 8502 comments
  • August 7, 2024

Glad you were able to figure things out.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
P
1 person likes this
  • P
    pedro12562
coolsport00
Forum|alt.badge.img+20
  • coolsport00
  • Veeam Legend
  • 4145 comments
  • August 7, 2024

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

Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
P
1 person likes this
  • P
    pedro12562

Comment


Terms & Conditions