VMware vRealize Operations Manager (vROps) Notes

vROps Notes

VMware vRealize Operations Manager; non-specific (cliff) notes

Capacity Planning Types

Allocation Based

Planning for best performance
– Workloads will have enough resources to run fast and with full allocation

Capacity Based

Planning for highest density
– Workloads will run but may be overcomitted
– Suggested for Dev environment usage



  • Datastore and Network IO Usable Capacity numbers are estimated by the system, whereas CPU, Memory, and Diskspace capacities are defined by actual hardware limits

Capacity Analysis Badge

  • Total capacity (or, provisioned capacity) = total amount of resources assigned to a workload; CPU, RAM, Storage, Etc.
  • Limit= User defined capacity limit for a workload
  • Usable Capacity= Capacity left after taking total capacity and setting aside reservations for High Availability and Buffer Reservations
  • Reservation= User defined reserved minimum capacity made available for a workload
  • Entitlement= System determined value between the Reservation (or minimum) and Limit (or Maximum)
  • Demand = Amount of capacity a workload is asking for immediately
  • Usage = Amount of capacity a workload actually receives
  • Resource Contention = Demand > Usage; or The workload needs (Demand) more resources than the system is currently providing (Usage)

Stress Badge

  • Stress = When demand of a workload is at or above 70% (user changable) of the capacity
  • Reccomnded Size Column = The amount of resources actually needed to run the current workload without contention

Workload Badge

  • Workload = An objects near real-time demand for a resource vs. the actual capacity of that resource OR a simple percentage of how much resource an object wants to use vs. how much it can actually get its hands on.
  • Workload is a near instantaneous value, calulated over the past 5 minutes of activity
  • Reference the Workload badge video @ 4:30 for details on how to properly read IOPS bars for this badge

Time Remaining Badge

  • Uses a logarithmic scale… not linear.
  • Uses same policy and metics as Capacity Badge, just displays them in a “Time Remaining” fashion
  • Provisioning Time Buffer = Amount of time it takes to procure and put a new host into service (Default = 30days)
  • Peak Consideration = Badge considers peak loads; if this is turned off, then it considers average loads

Reclaimable Capacity Badge

  • Reclaimable Capacity = Amount of capacity that can be reclaimed without causing stress or performance degredation

Compliance Badge

  • vROps can do simple compliance checks for hosts and VM’s using vSphere hardening guides
  • For more “out of the box” or taylored compliance, use vRealize Configuration Manager

Anomalies Badge

We have alerts for this metric

  • Uses dynamic thresholds created over time
  • Channel or Normal = Area in between upper and lower dynamic thresholds (DT) for each metric, created over time
  • Anomalies = Metrics that pass above or below (outside) the dynamically created channel (normal)
  • Anamolies Score = total number of monitored metrics vs. the number of metrics that are out the dynamic theshold (channel) at a given time
    • The more metrics acting abnormally the higher the score goes
    • Lower is better
  • Click and drag to zoom in on Anomalies graph and the table below will only show anomalies for that time period
  • HT = Hard Threshold
  • DT = Dynamic Threshold

Fault Badge

  • Not much to say here, this badge just shows faults incoming from systems and collectors
  • There is a “cancel” button on the badge page that can be used to remove faults that have been fixed


  • Alerts = One or more active symptoms across one or many object
  • Symptom(s): Created based on any metric, badge, or object (cluster, host, vm, datastore, switch, OS, application, etc.)
  • One click remediation optons are available <– need to research this further (see video for some details)
  • Ideas for alert usage:
    • Snapshots and their removal
    • Stress, workload, capacity and anomaly badge flags (once these badges are reigned in and tweaked using policies)

Architecture, Scalability & HA

  • Architecture Video (Node types, etc)

  • Node: a single instance of vROps

    • Each node contains all layers of the application.
    • As the need arises vROps should alert you to expand the cluster, either up or out
    • Nodes can be set up on Windows, Linux, or as a Linux VM Appliance (OVF – running on SLES)
      • at this time node OSs cannot be mixed and must be homogenous throughout the vROps cluster (except for remote collectors)
  • Node Roles:

    • Master: Manages global data for the cluster, also assumes data node role
    • Master Replica: recieves replica data from master node; will take over in case of master failure
    • Data: contains core analytics engine to process incoming data, determine dynamic thresholds, and capacity calulations
    • Remote Collector: collects data across high latency links and seeds data back to the cluster
      • Can run on OS’s that are different form the clusters data nodes
  • User interfaces:

    • Admin UI:
      • runs on all nodes and provides cluster management
      • only used when product UI is not available, during upgrade, or configuring first node
    • Product UI:
      • Runs on all nodes except remote collector nodes
  • High Availability:

    • Redundant copies of data are spread around nodes
    • Master node is replicated to “master replica” node
    • Best practice to deploy Master and Master replica nodes on seperate hardware
      • Perhaps replica should be at DR site
    • When a node fails, the secondary then becomes primary and a new secondary is chosen and replicated with, until the failed node is brought back online; it then assumes its original role after data is synchronized back to it
    • Step by step how to set up HA video

Online Resources

How to Remove an Orphaned Domain Controller (2008r2+)

If you ever lose a DC or one gets deleted before it is properly demoted using DCpromo

… or maybe you tried DCpromo but it wasn’t able to clean up AD on your other DC’s.

As of Windows 2008r2, if you right click and delete a computer object that happens to be a domain controller you will be prompted with the message shown below. Just tick off the checkbox and away you go; now you don’t have to go into ADSI Edit and clean out the old server, ADUC does it for you!! 🙂


Don’t forget though… you still have to go into DNS and clean out all the Name Servers and other entries pointing to your old (now dead) DC.

Admittedly, I’m no AD expert…
Did I miss anything? Let me know in the comments.

Upgrading a vCenter Appliance

Upgrading VMware vCenter appliance is fairly straightforward. I have compiled a procedure with screenshots, along with my notes on the subject.

The following pertains to upgrading from 5.1 to 5.5u1. There are some documentation links at the end of the article.

Upgrade Steps:

  1. Upgrade your vCenter Client. image

  2. Deploy Appliance

    • Use a TEMP IP – the appliance will assume the IP and identity of the old server when it upgrades; as well, it will shut down the old server.
  3. Power on and connect to the NEW appliance: https://NEW-Appliance-IP:5480

    • Log in with default values of u:root p:vmware.
  4. Accept License.

  5. Tick Upgrade from a previous version. image

  6. Copy KEY. image

  7. IMPORTANT: Snapshot the Old Appliance

  8. Connect to the OLD appliance: https://OLD-Appliance-IP:5480

  9. Click on the Upgrade tab & paste the key you copied from the NEW appliance, then click Import key and stop vCenter Server. image

    • You will see Loading… – just wait for it to complete and show you: image

    • … then Import successful. image

  10. Now, copy the key that the OLD appliance presents to you and paste it back to the new appliance in the lower box; Click Next> and wait a few moments. image

  11. Tick the box to Replace the SSL certificates, if presented. image

  12. Input new Root password. image

  13. Click next and then let the Host Upgrade Checker run, review the results, then proceed. image

  14. Confirm that you have made a snapshot of the old vCenter Appliance then click START image

  15. While the upgrade runs, you can watch it progress:

    • SSH into the NEW VCSA
    • run: tail -f /var/log/vmware/vami/upgrade.log
  16. You will receive a positive message when the upgrade has completed. image

  17. Check your version in VCSA or vSphere Client; you should see the new version and build number listed.


Upgrading vCenter Server Appliance 5.0.x/5.1 to 5.5 – KB Article gives the basics
VCSA Upgrade.docx – Document written by community member

Veeam Backup and Replication Essentials and Basic Edition Missing Feature – Clone


So I’m trying to clone a backup job in VBR Essential Basic; you know, so I don’t have to waste time going through the wizard again just to change the destination… but ut oh… I discovered the “clone” menu item is greyed out…
Exhibit A: image

After a little trip to the google and back I found an article that states:

The job cloning functionality is available only in the Enterprise and Enterprise Plus editions of Veeam Backup and Replication.

^ boooooo hissssss


Link: http://helpcenter.veeam.com/backup/70/vsphere/clonning_jobs.html

How to Retrieve Windows Server 2008r2 Product Key using Powershell

Magical Jelly Bean key finder and and others like it, as I have just learned, do not work with Windows 2008r2 because MS has encrypted the key in registry.

There are a few pay for programs that can retrieve the key for you, but luckily someone much smarter than me has written a very succinct PS script that returns the key, unencrypted 🙂

You can find the code here, or copy it below.

  • Look in the comments of the above linked page for specific instructions on how to save and run the script (if you’re not to sure on powerscript)

  • Don’t forget to run set-executionpolicy remotesigned first

PS Script:

How to Mount an NFS Share to Windows Server

…It’s not all that difficult. Who knew (shrug).

this should work for Windows 2008r2 and later

  1. Install the File Services Role

  2. If the role is already installed (like it was for me), you just need to enable the NFS Service for that role:


  3. Mount drive just like any other mapped drive:

  4. You will now see the drive mounted under Computer:

    Note: You can now use the mount and umount commands to manipulate NFS mounts through command line:

Source: http://technet.microsoft.com/en-us/library/dd758767.aspx

How to Install vSphere Client on a Windows Domain Controller

As of vSphere 5.5, installing the VIC on a DC errors out.

I read that it was done purposefully, to keep people from installing software on DC’s… which, makes sense for most situations – not so much for others. For instance, a small shop where one might need to utilize a DC for many other functions.


Anyway, to get to the meat of this article; in order to get the VIC to install you need to launch it from the command line with option /V.

  1. Make sure to run command prompt as admin: img2

  2. Then run the following command: VMware-viclient-5.5.exe /VSKIP_OS_CHECKS="1"

There you have it… you can now run through the install like usual. 🙂

Source: http://www.josephturley.com/install-vsphere-5-5-client-domain-controller/