I had an issue that happened repeatedly with RecoverPoint for Virtual Machines. It usually happened with new VMs that were cloned from templates and/or other VM. When I try to replicate it, I found this error message:
After investigation and contacting the support, I found a tricky solution as below:
1- Browse Managed Object Browser (https://<vCenter IP>/mob). And login with an administrator account.
2- Click on “Content”
3- Now we need to find the affected VM. Click on Datacenter as below:
4- Then choose your data center:
5- Under datacenter, you can find the VM by network or storage (if you know any), the easiest way is to browse all VMs and choose the affected VM as below for example:
6- If you need to make sure that you are in the right place, look at the top of the page to know your location:
7- After choosing the VM, head to the bottom of the page to find “ReconfigVM_Task”
8- Remove all the content in the “Value” section, and replace it with the original value (File below)
9- Click on “Invoke Method”
10 Now, try to replicate the affected VM again
Former Nuclear Engineer | University Lecturer | Technology Advisor | Digital Transformation evangelist | FinTech | Blockchain | Podcaster | vExpert ⭐️⭐️⭐️⭐️ | VeeamVanguard ⭐️⭐️ | Nutanix SME | MBA | AWS ABW Grant’23
Hello,
I am very happy.
It works for me.
Thanks so much.
I really appreciate.
regards,
James Ngonyani
Worked like a charm.
Thank you for posting this.
Hi, does any affect like a reboot/power off the VM with this method? Thank you
Bravo. Thank you a lot.
Hi Can you expain if the VM has an extra disk do we need to use
scsiX:Y.filters
OR is this valid:
TYPE::ANY
Thanks
”
TYPE::ANY
“