6.3
Table Of Contents
- vRealize Operations Manager vApp Deployment and Configuration Guide
- Contents
- About vApp Deployment and Configuration
- Preparing for Installation
- Creating the Master Node
- Scaling Out by Adding a Data Node
- Adding High Availability
- Gathering More Data by Adding a Remote Collector Node
- Continuing With a New Installation
- Connecting to Data Sources
- VMware vSphere Solution
- Endpoint Operations Management Solution
- Endpoint Operations Management Agent Installation and Deployment
- Prepare to Install the Endpoint Operations Management Agent
- Supported Operating Systems for the Endpoint Operations Management Agent
- Selecting an Agent Installer Package
- Install the Agent on a Linux Platform from an RPM Package
- Install the Agent on a Linux Platform from an Archive
- Install the Agent on a Windows Platform from an Archive
- Install the Agent on a Windows Platform Using the Windows Installer
- Installing an Endpoint Operations Management Agent Silently on a Windows Machine
- Java Prerequisites for the Endpoint Operations Management Agent
- Configuring JRE Locations for Endpoint Operations Management Components
- System Prerequisites for the Endpoint Operations Management Agent
- Configure the Endpoint Operations Management Agent to vRealize Operations Manager Server Communication Properties
- Activate Endpoint Operations Management Agent to vRealize Operations Manager Server Setup Properties
- Specify the Endpoint Operations Management Agent Setup Properties
- Configure an Endpoint Operations Management Agent Keystore
- Configure the Endpoint Operations Management Agent by Using the Configuration Dialog
- Overriding Agent Configuration Properties
- Endpoint Operations Management Agent Properties
- Encrypt Endpoint Operations Management Agent Property Values
- Adding Properties to the agent.properties File
- agent.keystore.alias Property
- agent.keystore.password Property
- agent.keystore.path Property
- agent.listenPort Property
- agent.logDir Property
- agent.logFile Property
- agent.logLevel Property
- agent.logLevel.SystemErr Property
- agent.logLevel.SystemOut Property
- agent.proxyHost Property
- agent.proxyPort Property
- agent.setup.acceptUnverifiedCertificate Property
- agent.setup.camIP Property
- agent.setup.camLogin Property
- agent.setup.camPort Property
- agent.setup.camPword Property
- agent.setup.camSecure
- agent.setup.camSSLPort Property
- agent.setup.resetupToken Property
- agent.setup.unidirectional Property
- agent.startupTimeOut Property
- autoinventory.defaultScan.interval.millis Property
- autoinventory.runtimeScan.interval.millis Property
- http.useragent Property
- log4j Properties
- platform.log_track.eventfmt Property
- plugins.exclude Property
- plugins.include Property
- postgresql.database.name.format Property
- postgresql.index.name.format Property
- postgresql.server.name.format Property
- postgresql.table.name.format Property
- scheduleThread.cancelTimeout Property
- scheduleThread.fetchLogTimeout Property
- scheduleThread.poolsize Property
- scheduleThread.queuesize Property
- sigar.mirror.procnet Property
- sigar.pdh.enableTranslation Property
- snmpTrapReceiver.listenAddress Property
- Managing Agent Registration on vRealize Operations Manager Servers
- Securing Communications with the Server
- Launching Agents from a Command Line
- Managing an Endpoint Operations Management Agent on a Cloned Virtual Machine
- Understanding Agent Uninstallation and Reinstallation Implications
- Install Multiple Endpoint Operations Management Agents Simultaneously
- Roles and Privileges
- Registering Agents on Clusters
- Manually Create Operating System Objects
- Managing Objects with Missing Configuration Parameters
- Mapping Virtual Machines to Operating Systems
- Endpoint Operations Management Agent Upgrade for vRealize Operations Manager 6.3
- Endpoint Operations Management Agent Installation and Deployment
- Installing Optional Solutions
- Migrate a vCenter Operations Manager Deployment into this Version
- Post-Installation Considerations
- Updating Your Software
- Index
Adding High Availability to
vRealize Operations Manager 4
You can dedicate one vRealize Operations Manager cluster node to serve as a replica node for the
vRealize Operations Manager master node.
This chapter includes the following topics:
n
“About vRealize Operations Manager High Availability,” on page 27
n
“Run the Setup Wizard to Add a Master Replica Node,” on page 28
About vRealize Operations Manager High Availability
vRealize Operations Manager supports high availability (HA). HA creates a replica for the
vRealize Operations Manager master node and protects the analytics cluster against the loss of a node.
With HA, data stored on the master node is always 100% backed up on the replica node. To enable HA, you
must have at least one data node deployed, in addition to the master node.
n
HA is not a disaster recovery mechanism. HA protects the analytics cluster against the loss of only one
node, and because only one loss is supported, you cannot stretch nodes across vSphere clusters in an
aempt to isolate nodes or build failure zones.
n
When HA is enabled, the replica can take over all functions that the master provides, were the master to
fail for any reason. If the master fails, failover to the replica is automatic and requires only two to three
minutes of vRealize Operations Manager downtime to resume operations and restart data collection.
When a master node problem causes failover, the replica node becomes the master node, and the cluster
runs in degraded mode. To get out of degraded mode, take one of the following steps.
n
Return to HA mode by correcting the problem with the master node, which allows
vRealize Operations Manager to congure the node as the new replica node.
n
Return to HA mode by converting a data node into a new replica node and then removing the old,
failed master node. Removed master nodes cannot be repaired and re-added to
vRealize Operations Manager.
n
Change to non-HA operation by disabling HA and then removing the old, failed master node.
Removed master nodes cannot be repaired and re-added to vRealize Operations Manager.
n
In the administration interface, after an HA replica node takes over and becomes the new master node,
you cannot remove the previous, oine master node from the cluster. In addition, the previous node
continues to be listed as a master node. To refresh the display and enable removal of the node, refresh
the browser.
VMware, Inc.
27