5.6
Table Of Contents
- VMware vCenter Operations Manager Administration Guide
- Contents
- VMware vCenter Operations Manager Administration Guide
- Configuring and Managing vCenter Operations Manager
- Configuring Adapters
- Configuring Resources
- Configuring Attribute Packages
- Configuring Applications
- Configuring and Managing Users
- Configuring Alert Notifications
- Performing Basic System Administration Tasks
- View Performance Information
- View Status Information
- vCenter Operations Manager Service Names
- Start or StopvCenter Operations Manager Services
- Viewing and Managing System Log Files
- Delete Old Data in the File System Database
- Run the Audit Report
- Modify Global Settings
- Modify Global Settings for Virtual Environments
- Create a Support Bundle
- Resolving Administrative System Alerts
- Analytics FSDB Overloaded
- Analytics Threshold Checking Overloaded
- Collector Is Down
- Controller Is Unable to Connect to MQ
- DataQueue Is Filling Up
- Describe Failed
- Failed to Connect to Replication MQ
- Failed to Repair Corrupted FSDB Files
- File Queue Is Full
- FSDB Files Corrupted for Resources
- FSDB Storage Drive Free Space Is Less Than 10%
- No DT Processors Connected
- One or More Resources Were Not Started
- Outbound Alert Send Failed
- Replication MQ Sender Is Blocked
- Backing Up and Recovering Data
- Using System Tools
- Summary of System Tools
- Check the FSDB and Repair Problems
- Move the FSDB
- View Resources in the FSDB
- Remove System-Generated Metrics from the FSDB
- Monitor vCenter Operations Manager Services in JConsole
- Verify Server to Collector Communication
- Configuring and Running the Repository Adapter
- conf.properties File
- Configure Database Connections for the Repository Adapter
- Set the Repository Adapter Schedule
- Configure the Source and Destination Columns for the Repository Adapter
- Set Operation Options for the Repository Adapter
- Configure Data Export Values for the Repository Adapter
- Start the Repository Adapter
- Configuring and Running runvcopsServerConfiguration
- Managing Dashboards and Dashboard Templates
- Using the FSDB JDBC Driver
- Index
Selecting a Backup and Recovery Strategy for the Server
The vCenter Operations Manager server runs the services that make up the vCenter Operations Manager
application. These services include the vCenter Operations Manager Web service, Collector service, ActiveMQ
service , and Analytics service. Because it is a high-performance and resource-intensive application,
vCenter Operations Manager usually requires a dedicated server.
Many organizations use the vCenter Operations Manager server, and by extension the FSDB, as a mission-
critical application. You can implement vCenter Operations Manager as a set of clustered servers for high
availability, or as a set of remote servers for disaster recovery or failover purposes, or both.
Implementing High Availability for the Server
You can implement high availability for the vCenter Operations Manager server by using shared disks and
clustering software. When a server that hosts vCenter Operations Manager becomes unavailable, the clustering
software maps the shared disk and vCenter Operations Manager services to the backup server and brings them
online.
High availability capability has the following hardware and software requirements.
n
A shared disk (SAN) to install the vCenter Operations Manager software and
vCenter Operations Manager FSDB.
n
Two separate servers on which to deploy vCenter Operations Manager services and environment
variables.
n
Cluster software on both servers to manage vCenter Operations Manager services.
n
A virtual IP address representing the cluster, for end users and remote collectors that point to the
vCenter Operations Manager server to use.
When a server that hosts vCenter Operations Manager becomes unavailable and is remapped by the clustering
software, any users that are logged in to vCenter Operations Manager are logged out and the
vCenter Operations Manager system becomes unavailable for about 15 seconds. Because it is installed on the
shared disk, the FSDB is not affected. The RDB remains accessible from both servers because it is installed on
a different server than the vCenter Operations Manager software.
For more information about how to install and configure of a clustered environment, see your specific
clustering documentation.
Implementing Disaster Recovery for the Server
vCenter Operations Manager has built-in abilities to enable a quick transition to a completely separate backup
vCenter Operations Manager server or cluster if the primary server or cluster is unavailable. You must
manually switch the vCenter Operations Manager software to use the backup server or cluster as the primary
server or cluster.
The separate backup server typically resides in a different location than the primary system for disaster
recovery purposes. The remote backup server or cluster contains a vCenter Operations Manager instance that
serves as a backup replication server. This instance keeps a warm, updated copy of the FSDB.
Disaster recovery has the following hardware and software requirements.
n
A separate remote vCenter Operations Manager instance that is configured as a backup server.
n
A vCenter Operations Manager FSDB replication server that is running the replication service. After the
remote FSDB is synchronized with the local FSDB, the data should be identical.
n
A vCenter Operations Manager database that is synchronized with the appropriate vendor software.
Chapter 10 Backing Up and Recovering Data
VMware, Inc. 127