5.8.5

Backing Up and Recovering Processing Components
You must follow certain guidelines when you back up and recover the vCenter Operations Manager
processing components. The processing components include the vCenter Operations Manager server, the
vCenter Operations Manager Remote Collector server, the DT processor server, and the database server.
n
Selecting a Backup and Recovery Strategy for the Server on page 134
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.
n
Backing Up and Recovering the RDB Server on page 136
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.
n
Backing Up and Recovering a Remote Collector Server on page 136
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.
n
Backing Up and Recovering a Remote DT Processor Server on page 136
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.
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.
VMware vCenter Operations Manager Administration Guide
134 VMware, Inc.