Solved

Protecting Prism Central

  • 14 August 2020
  • 4 replies
  • 492 views

Userlevel 1
Badge +12

Are there any recommendation for protecting Prism Central - I’m actually using PC Scaleout so have 3 PCVM’s and am curious if I should place these in a Metro or Async Protection Domain in the event that we perform a datacenter failover.

I know that this cluster wouldn’t be critically needed in such a scenario but it would be nice to have. Any pro’s/con’s to using either PD type (Metro vs Async) for this?

icon

Best answer by Alona 20 August 2020, 05:23

Hi mandg, in short, that’s correct.

View original

4 replies

Userlevel 5
Badge +5

Hi mandg,

 

I can tell that you are definitely not the only person thinking of protecting PC.

When you migrate VMs from one site to another PC on the recovery site identifies new entities and is able to collect all the stats and metrics for them as well as to perform their management.

I can see how it can be desirable in a situation where a PC instance manages both the source site and the recovery site, agree. Unfortunately, it’s a choice to make: to either run it on the source, or on the recovery site, or have more than one PC instance.

While it’s not impossible, it’s not recommended to protect/failover PC as it has a long list of pre-requisites and as long a list of manually executed tasks to be performed post failover.

Let me know if that answers your question or if there are further queries.

I am installing PC to create the Leap Runbooks to re-IP the VMs when they are brought online in the DR site.   Is this automation stored in the PE in the DR site?   I hate to ask - am I supposed to install another PC in the DR site?

Userlevel 1
Badge +12

Thanks, Alona- so, based on your response, my 3 PCVM’s should just be kept in a local storage container and not included in any Protection Domain for replication to a remote site, correct?

Userlevel 5
Badge +5

Hi mandg, in short, that’s correct.

Reply