5.0
Table Of Contents
- VMware vCenter Operations Manager Enterprise Administration Guide
- Contents
- VMware vCenter Operations Manager Enterprise 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 vCenter Operations Manager Performance Information
- View vCenter Operations Manager Status Information
- 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 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 vCenter Operations Manager 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
- 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
- conf.properties File
- Configuring and Running runvcopsServerConfiguration
- Using the FSDB JDBC Driver
- Index
3 Update the server IP address, or the virtual IP address that represents the cluster, to the correct IP address
for the new primary server or cluster.
End users and remote collectors that point to the vCenter Operations Manager server must use the new
IP address.
4 Click Finish to save the configuration.
NOTE Because the vCenter Operations Manager services are reinstalled and restarted when you click
Finish, click Exit, not Finish, to close the utility if you do not make any changes.
What to do next
If you need to switch a vCenter Operations Manager replication server to the primary server, you might need
to make additional changes. See “Switch the Primary and Backup Replication Servers,” on page 113.
Backing Up and Recovering the RDB Server
vCenter Operations Manager uses commercially available relational databases. If the
vCenter Operations Manager RDB is unavailable, vCenter Operations Manager becomes unavailable. If you
require a high availability or remote failover capability, configure the RDB server to use clustering or a remote
warm backup.
Instances that are configured against a single database are unavailable if that database becomes unavailable.
If this situation occurs, a high availability strategy that includes a clustered database environment enables the
cluster to immediately switch the shared disks and the vCenter Operations Manager instance to the backup
server if one database becomes unavailable.
Backing Up and Recovering a Remote Collector Server
The vCenter Operations Manager remote collector is a remote host that has only the
vCenter Operations Manager collector installed. A remote collector does not store data. You might want to
install one or more remote collectors to navigate firewalls, reduce bandwidth across data centers, and reduce
the load on the vCenter Operations Manager server.
If a remote collector server becomes unavailable, the primary vCenter Operations Manager server does not
receive data from the portion of the monitored environment that is configured for that particular remote
collector.
Although you can install a remote collector on a cluster, typical implementations install a separate collector
on another server. This backup remote collector should have the same vCenter Operations Manager collector
adapters folder and the same vCenter Operations Manager collector configuration folder as the primary remote
collector. If the primary remote collector becomes unavailable, you can bring the backup remote collector
online.
Backing Up and Recovering a Remote DT Processor Server
A remote DT processor is a vCenter Operations Manager Server process that performs analytics calculations.
It does not store data. You can distribute the load by starting a separate analytics process on one or more remote
hosts to perform just the dynamic threshold (DT) portion of analytics processing.
If a remote processor server goes down, vCenter Operations Manager continues to collect and store data, but
dynamic thresholds are not recalculated based on the new data.
You do not need to have a backup of a remote DT processor. If the remote DT processor becomes unavailable,
you can configure the analytics process on the vCenter Operations Manager server to perform the dynamic
threshold calculations. See “Configure the Analytics Process to Perform DT Calculations,” on page 120.
You can also install the remote DT analytics process on a different host. See the VMware vCenter Operations
Installation Guide.
Chapter 10 Backing Up and Recovering Data
VMware, Inc. 119