VROPS REMOTE COLLECTORS - DESIGN CONSIDERATIONS

Written by Simon Eady on 15/2/2021 · Read in about 2 min (390 words)
Published under vRealize Operations

vROps Remote Collectors - Design Considerations

Product Version - vRealize Operations 7.x and 8.x

As part of VMware Validated Designs tyically you would use Remote Collectors not just in different DCs but also local to the analytics cluster. However there are a circumstances where the rules “change”.

When using RecoverPoint or Site Recovery Manager

Design Assumption - you have Remote Collectors on your Primary Site and on your Failover Site.

vRealize Operations supports re-IPing and therefore can be used with DR/BC tools such as Site Recovery Manager. However if you are using Remote Collectors when you failover and want to bring the vROps Cluster back online you will not be able to bring the cluster online as it will be looking for the Remote Collectors on the now offline Primary Site. The only way to remedy this is to remove the Primary Site Remote Collectors from the Cluster and then bring the cluster online.

With the above in mind, it may well be better to have no Remote Collectors on your Primary Site if you are using SRM or anyother similar tooling.

VCF/vRealize Suite Lifecycle Manager

To date VCF/vRSLCM still does not automatically take into account Remote Collectors. It will allow you to deploy the cluster but you will need to then manually deploy Remote Collectors in other DCs which (very important note) sit under other vCenters in vRSLCM. This is important to know as when you go to patch or upgrade vROps in vRSLCM it will fail as it will tell you that there are components in vROps that sit outside of the vCenters in the Logical DC within vRSLCM. This is an annoying limitation with vRSLCM.

Essentially for any upgrades/patches to work, all the components of a vRealize Product have to be in the same logical vRSLCM DC (not vSphere DC). VMware advise that you create an additional DC in vRSLCM. A cross-region-dc where all of the VCs from the various sites you have Remote Collectors deployed to. From here you can then manage the vROps deployment effectively.

Summary

Remote Collectors are super useful, but through no fault of their own there use can given you a headache with regards to design decisions. None of the above is ideal, so you will need to assess what best works for the customer and envirneoment and meets the requirements given.

Share this post