You can follow these best practices while using remote collectors.

  • Consider using Remote Collectors for local collections with larger vCenter servers

    Using remote collectors helps to reduce the bandwidth across data centers and reduce the load on the vRealize Operations analytics cluster.

  • Create collector groups when using multiple Remote Collectors

    When utilizing multiple remote collectors for one vCenter Server, create a collector group to provide a collector high availability and redundancy`. Collector groups can be configured to fault domains when CA is enabled.

  • Deploy or update Remote Collectors to the same version of the Analytics nodes

    Do not utilize mixed versions of Remote Collectors and Analytics nodes. Not only is a cluster running mixed versions unsupported, it may exhibit potential problems.

  • Use Remote Collectors when using Management Packs or End Point Operations agents

    Use remote collectors to isolate the collection from Management Packs or End Point Operations agents to reduce the load on the vRealize Operations analytics cluster.

  • Size Remote Collectors based on the number of collecting objects/metrics

    Size remote collectors using the default sizing of standard and large nodes to accommodate the number of objects and metrics, which it collects.

  • Remote Collectors are recommended, but not required, to be included in the backup strategy

    Include all remote collectors when taking a backup to restore the entire cluster health.