Quantcast
Channel: VMware Communities : All Content - vRealize Operations Manager
Viewing all articles
Browse latest Browse all 5485

vROps DR architecture design

$
0
0

I'm designing vRops for an environment that has a production environment and a DR environment. The customer has a general rule to provide DR between Prod -> DR and I'm considering the best way to do this from a vROps perspective.

 

Key Points:

1. Prod and DR is similar hardware (Vblocks)

2. SRM is deployed and available

 

Options:

Opt 1. Use SRM to failover the nodes and bring up the same vROps instance on DC2 (Is it possible or supported to rename the nodes and/or re-ip if we needed to using SRM? I know some VMware appliances don't like this. )

Considerations: Does it make sense to try and seamlessly failover vRops to the DR datacenter, because even though the hardware, software components will be almost identical it is still physically separate kit. So for instance, an historical hardware alert from DC1 wont be applicable to DC2. There are a number of adapters including one for UCS, vCM, vCD, Hyperic, vCNS

 

Opt 2. Deploy two separate and independent instances of vROps, one monitoring DC1 an one monitoring DC2 - don't fail anything over if DC1 goes down.

Considerations: We'll have no historical alerts or performance baselines, but are they valid as its different hardware? Admittedly, the software services will be failed over and they will be the same but does it makes sense to monitor them as if they were still running on DC1

 

Opt 3??

 

I'm interested in the community thoughts as to ways to deploy vROps across this Active / Passive DC configuration

 

Thanks


Viewing all articles
Browse latest Browse all 5485

Trending Articles