Zsoldier's Tech Blog

Applies to vROPs running in NON-HA mode, below was thanks to help from VMware support.  They have an internal KB on this so it should eventually be published or more likely fixed in the future.  Mostly for my own notes, but interesting for those tinkerers out there. Case: Attempting to remove remote collector node from vROPs to replace w/ larger remote collector.  Correct way would have been to move 'instances' to other collector or data nodes before putting collector node offline.  Instead, I just removed the collector node from the admin console.  That's when it got stuck in this state. It's supposed to move the 'instances' to other collectors, but that didn't seem to work and it got stuck in a state of taking the cluster offline.  So to remove the remote collector and get back to a stable state, VMware support walked me through below. Resolution to Case: DO NOT ATTEMPT BELOW STEPS UNLESS YOUR CASE MATCHES ABOVE EXACTLY OR YOU REALLY KNOW WHA...

Found this on a community board  and well, thought it might be useful to repost.  Also looking to add to this as time permits. Term Definition Ascendant Any object higher in the "tree", includes parent (and grandparent, great-grandparent, etc) Parent Object directly above selected object (VM's parent is a host, for example.  Host parent is cluster, etc) Child Object(s) directly below selected object in the "tree" (host child(ren) is any VM on host) Descendant Any object lower in the "tree", include child, grandchild, great-grandchild etc The above information is useful when creating group objects and what not in vROps.