Victor Wu
3 Argentum

How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

As title. I cannot find any information in admin & deployment guide and EMC KB portal. This is my lab environment, anyone help me ?

Labels (1)
0 Kudos
9 Replies
forshr
4 Beryllium

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

If yoiu are using classic RP then this is not possible.

Regards,

Rich

0 Kudos
Victor Wu
3 Argentum

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

No. It is not classic RP, it is

0 Kudos
forshr
4 Beryllium

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

Have you tried the option in Deployer?

0 Kudos
Victor Wu
3 Argentum

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

Due to that node is corrupted, deployer currently cannot access the original IP address. So I cannot remove it in deployer, I think that only remove it by CLI.

0 Kudos
forshr
4 Beryllium

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

There is a utility that can be used through Support that may resolve the issue with vRPA1 so would recommend raising an SR.

0 Kudos
Victor Wu
3 Argentum

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

Due to we just in POC phase now, so it doesn't have any support contact active now. Do you have this utility ? Can you share to me, thanks.

0 Kudos
forshr
4 Beryllium

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

You could use the replace option. This doesn't require the vRPA to be reachable.

0 Kudos
prabhusingh
2 Bronze

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

Hello,

I do facing similar issue with same config of vRPA Cluter. I was unable to replace the faulty RPA 1. 

Getting following error "Could not retrieve vCenter server credentials for RPA 2" while trying to replace the RPA.

Ref:  SR#12468003

0 Kudos
Idan
DellEMC

Re: How to force remove vrpa from the vrpa cluster (version 5.0 SP1)

Hi there,

In this specific case, it's an issue due to a failed upgrade (as RPVM cannot be upgraded directly to 5.2, has to go through 5.1.1.4/5), we would need to get info on the VMs listed in the SR to further troubleshoot this one.

Hope that helps,

Idan Kentor

Sr. Principal Product Technology Engineer - RecoverPoint and RecoverPoint for VMs

@IdanKentor

idan.kentor@emc.com


Idan Kentor
Tech Staff Engineering Technologist - Data Protection


idan.kentor@dell.com
@IdanKentor
0 Kudos