Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

6492

August 4th, 2017 13:00

Cannot unprotect VM from previous installation

I am testing RP for VM version 5.1 and had a couple test consistency groups and VM's. I had to reconfigure my RP clusters because I mis-configured some network settings, and didn't remove the consistency groups before doing that. I now have everything working, but if I want to "Protect" those 2 test VM's, it still shows they're protected even though no shadow vm or CG exists. If I select "Unprotect" it just locks the interface and I have to re-login to vSphere. I have tried shutting down, removing from inventory, etc. but nothing seems to work. Is there something I'm missing? Thanks!

675 Posts

August 7th, 2017 01:00

Hi there,

If a former installation wasn't cleaned up properly, including unprotecting VMs, you can try to run Uninstaller (available on support.emc.com) and cleanup the vCenter of the stale RPVM cluster(s). It would, among other cleanup operations, would remove the filters from running VMs w/o shutting them down (the appropriate VMs of course).

Hope that helps,

Idan Kentor

RecoverPoint Corporate Systems Engineering

@IdanKentor

1 Rookie

 • 

26 Posts

August 7th, 2017 07:00

Thanks for the help..I'll download that utility and give it a try. Will it also remove the current installation that I have up and running right now?

1 Rookie

 • 

1 Message

June 14th, 2018 11:00

Had the exact same problem. Yes, running the un-install will remove all RPAs from your VCenter environments you give the IPs of. I did the following:

Verifying that the configuration parameters are empty

1. At the vSphere Web Client, in Inventory, select Hosts and Clusters. Select a VM that was protected by RecoverPoint for VMs. Power off the VM. Right-click and select Edit Settings...

2. In the Edit Settings dialog box, select the VM Options tab. Expand the Advanced column. In the Configuration Parameters row, click Edit Configuration... to edit the advanced configuration parameters.

3. In the Configuration Parameters window, ensure that all configuration parameters with "RecoverPoint" or "ESX splitter" in the name have empty values.

The following parameters must have empty values:

  • RecoverPoint RPA number
  • RecoverPoint CGUID
  • RecoverPoint Cluster ID
  • esx_splitter.globalOptions
  • esx_splitter.scsi0:1.options

I was then able to "unprotect" the VM. It does require the power off of the VM.

I found this on KB 000499081 : https://emcservice.force.com/CustomersPartners/kA5f10000008YNLCA2

Hope this helps someone as it did me.

Cheers.

675 Posts

June 15th, 2018 01:00

All,

It’s important to note that the Uninstaller can be clean these parameters from formerly protected VMs WITHOUT having to power off the VMs. The first priority would be to of course unprotect the VMs through the plugin. Thx.

1 Rookie

 • 

11 Posts

July 25th, 2022 00:00

Dear Dell EMC Community Team,

One of our Customers was facing the exact issue, they did new installation of RP4VMs system with out un protecting Virtual Machines from Previous old RP4VMs system and VMware vCenter System,

when they tried re-protecting the same Virtual Machines, the virtual machines could not re-protect, RP4VMs system interface gave alert/ warning : cannot protect a virtual machine that is already protected

ROOT CAUSE:

The Existing Virtual Machines have Recover point for VMs existing parameters from previous RP4VMs system installation, so its the reason the VMs appear as if they are already protected and therefore, they cannot be Re-Protected in the New RP4VMs System,

WORK AROUND

Browse to the VMware Server Host that is hosting or housing the Virtual Machines that you want to Re-Protect,

Right Click on the Virtual Machines, go to edit settings, select VM Options;

Verifying that the configuration parameters are empty

1. At the vSphere Web Client, in Inventory, select Hosts and Clusters. Select a VM that was protected by RecoverPoint for VMs. Power off the VM. Right-click and select Edit Settings...

2. In the Edit Settings dialog box, select the VM Options tab. Expand the Advanced column. In the Configuration Parameters row, click Edit Configuration... to edit the advanced configuration parameters.

3. In the Configuration Parameters window, ensure that all configuration parameters with "RecoverPoint" or "ESX splitter" in the name have empty values.

The RecoverPoint and ESX Splitter Parameters with empty values will be automatically removed from the Virtual Machine and the Virtual Machines will not have any Recover point for vms parameters tagged to them any more, the Virtual Machines will be ready to be Re-Protected,

Click Save, to save the virtual Machine New Configuration.

Go back to Recover Point and try to protect the Virtual Machine, the Virtual Machine will proceed to be protected.

NOTE: You can edit the virtual machine settings through the VMware Server Host without having to shutdown the Virtual Machine, just edit settings, remove the Recover point for Virtual Machines parameters and you will be good to go,

The following Recover Point for Virtual machines parameters should be with Empty Values;

  • RecoverPoint COPYID
  • RecoverPoint CGUID
  • RecoverPoint ClusterUID
  • esx_splitter.globalOptions
  • scsi0:0 Filter

All the above parameters, should be with empty values so that they are removed from the Virtual machine configuration paraemeters after saving and re-configuring the Virtual Machine.

That IT,

NOTE: All the above can be done with out shutting down the Virtual Machine, the virtual machine can still be in Power on Mode,

HOPE THIS ARTICLE, HELPS SOME ONE WHO COMES OR GETS SUCH AN ERROR ABOVE

Thanks

recover point and Splitter parameters should have empty valuesrecover point and Splitter parameters should have empty values

 

1 Rookie

 • 

11 Posts

July 25th, 2022 00:00

Hello DELL EMC TEAM,

This Solution worked fine, i had the exact same problem as i could not protect VMs from Previous Installation, i followed the above Thread and i was able to protect the Virtual Machines in the New Recover Point for VMs System.

No Events found!

Top