Things we can look forward to seeing in #vROps 7.0

| 06/09/2018 | Tags: , , ,

I did a quick search online and could not find a collated list so, by way of a quick summary from all the VMworld 2018 announcements and comments my good friend and PM for vRealize Operations Sunny Dua has made, I have collated a list of what we can expect to see in the next iteration of vROps (7.0). The list is in no order of interest or importance, some of the mentioned improvements have been long standing requests so enjoy and get hyped (I know I am).

Support to identify VMware #SRM Placeholder Virtual Machines in coming in #vROps 7.0. Unlock powerful use cases such as DR Configuration management and Capacity reservation with this tiny little gem.

One click dashboard sharing with URL, Email, and Embed capabilities…”NO LOGIN REQUIRED”

All new dashboard creation canvas with one-click interactions.

Auto create and manage #vSphere DRS rules for in-cluster or cross cluster workload placement with tags.

You can find out more information on what is to come and more regarding the “self-driving” data center (SDDC) vision that VMware have set out here – 

#vROps data retention and the Cleaner

Something that has come up with customers recently is why and when old data is cleaned up from your vROps instance.

I will make the assumption that you have your data retention set to 6 months but the process is the same whether the value is less than or greater than 6 months.

When data reaches and or goes beyond the age threshold set in the global settings it will be cleaned away by a daily process “Old Data Cleaner”.

However, the Old Data Cleaner serves another purpose and in many cases very vital.

If the disk space on the vROps instance becomes less than 10% the Old Data Cleaner thread will automatically run to maintain some free disk space. This is critical to keeping vROps running and prevents it from falling over. However in some cases I have seen a reasonable performance hit on the vROps instance -if- the ingest rate on the vROps instance is very high, thus forcing the Cleaner to work full time.

If you hit the issue outlined above you will need to add additional disk space to the vROps instance.


 #vROps Webinar Series 2017 – Part 3 – What’s New with vROps 6.6

Hello there, we hope you enjoyed the last episode of vRealize Operations Webinar Series.This time around we spoke about the all new version of the product : vRealize Operations Manager 6.6, which was recently released by VMware.
We started with an overview of all the cool new stuff and then drill down into individual areas. We then jumped into a Live Demo as usual to see the new features in action.

We would highly appreciate if you could spend 30 seconds to fill up this quick and simple survey to provide us your feedback. You can also request topics of your choice through this survey.

Here is the recording!

Can I secure #vROps?

vRealize-Operations-Manager-Logo_thumb.jpgThose of you used to using vSphere on a regular basis will already be aware of the hardening guide for ESXi and vSphere but what about vROps?

If the vROps appliance needs to be hardened there is already a VMware provided guide and tool to accommodate.

Secure configuration guide –

“The documentation for Secure Configuration is intended to serve as a secure baseline for the deployment of vRealize Operations Manager.”

The Documentation covers the Virtual Appliance, Linux deployments and Windows deployments.

Update 6th April 2016 –

VMware vRealize Hardening Tool 2.0.0
The vRealize Hardening Tool automates the hardening activity by applying appliance-specific configuration changes to a system. For more information about hardening vRealize and on how to use the vRealize Hardening Tool

The vROps HA conundrum

VMware.jpgOne of the great new features included in vROps is High Availability, however when you look a little closer at how it works careful thought needs to go into whether you want to use it or not.

I have had several discussions with my colleagues on the subject about whether you should or should not enable it in any given deployment of a vROps cluster.

So the following are my thoughts and bullet points for you to consider when faced with same dilemma.

By its very name, I assumed wrongly that it could be used as a way to tackle BC/DR concerns, it turns out the HA feature cannot span multiple logical datacenters – KB article – Forum discussion. I am hoping in future editions this gets resolved as it would be -very- handy.

So what other things do I need to take into account?

  • The Master node behaves like an index for your cluster, lose it and lose your cluster, so HA can protect it although is no substitute for a proper backup solution. “.. Global xDB is used for data that cannot be sharded, it is solely located on the master node (and master replica if high availability is enabled)
  • HA takes several minutes to “kick in” so one could argue why not rely on vSphere HA (especially if your management cluster is tight on resources)
  • HA would protect you against a LUN/Datastore failure assuming you had sensibly separated your nodes.
  • HA adds an additional node so if you are tight on resources it might not be an option for you.
  • Removal of data nodes (if you need to downsize your cluster) will result in data loss unless you have HA enabled.

The bullet points are by no means exhaustive but they are essential information while you muse your design choice for you next vROps cluster.

If you are looking for good reference material I can recommend the book Mastering vRealize Operations Manager by Scott Norris.