2 Replies Latest reply on Jun 20, 2017 12:44 PM by jhague

    vRealize Operations Manager 6.6 Sizing

    ppgdtap Novice

      We have an existing appliance that is not sized properly and I am trying to establish a way forward.

       

      The existing appliance is v6.6, but it is single node only showing 890306 metrics in progress which judging by "vRealize Operations Manager 6.6 Sizing Guidelines (2150421)" - the appliance should be sized with 8 vCPU and 32Gb of RAM. In contrast our appliance appears to have only 2vCPU and 8Gb of RAM.

       

      Considering that it has collected few months worth of data already:

      - can we add more resources to existing appliance? is that accepted practice?

      - can we add nodes to form a cluster and if so what will happen to the data collected?

      it may be that what was a trial for 1 vcenter ended up being used in production for our 3 vcenters so looking for advice as to how to transition to a HA setup. If the only way to do that is by losing the data and building a cluster from scratch so be it...

       

      G

        • 1. Re: vRealize Operations Manager 6.6 Sizing
          JimKnopf99 Master

          Hi,

           

          answering your questions.

           

          - can we add more resources to existing appliance? is that accepted practice?

          Yes, you can do so.It is supported to resize the vm.

          See vRealize Operations Manager 6.5 Sizing Guidelines (2148829) | VMware KB

          - can we add nodes to form a cluster and if so what will happen to the data collected?

          yes, you could also add nodes, but i if it fits on one vm, why add complexity. But that is only my opinion.

           

          If you change the vCenter, then your vm´s and other things will end up getting a new id. And the data collected could not be linked to the new data.

           

          Frank

          • 2. Re: vRealize Operations Manager 6.6 Sizing
            jhague Hot Shot
            vExpertVMware Employees

            Hi - scale up and scale out are both supported - scale up means increasing VM resources within the parameters listed in the sizing guide posted above (e.g. there is a range of memory), once you have reached max resources for node type you can also move between node sizes e.g. medium to large or you can scale out e.g. add nodes. Expanding an existing node/cluster is supported without data loss. For an HA deployment you need to go through the expand option in the wizard to add a data node, you will then be able to enable HA which will convert the data node to a master replica (you will then have a master and master replica - these roles also perform the data node function as well as cluster management operations). All nodes must be sized the same for a supported configuration and you should create a DRS rule to separate them to maintain availability in the event of host failure when both nodes are on the same host. You can also put a load balancer in front of them to balance HTTP requests for the UI using a single name and IP though this is not strictly necessary - you can continue to connect to the individual nodes and see the data for the cluster. Hope this helps.