The Persistence (the database) layer, as its name implies, is the layer where the data is persisted to disk. The layer primarily consists of a series of databases performing different functions, and having different roles.
vRealize Operations uses two data storage solutions:
- Postgres: This is a relational database that stores the configuration and state of the data
- FSDB: This is a proprietary high-performance filesystem-based repository that stores all the time series data
Understanding the Persistence layer is an important aspect of vRealize Operations, as this layer has a strong relationship with the data and service availability of the solution.
vRealize Operations has five primary database services, as follows:
|
Common name |
Role |
DB type |
Sharded |
Location |
|
Cassandra DB |
User preferences and configuration, alerts definition, customizations, dashboards, policies, view, reports, licensing, shard maps, activities |
Apache Cassandra |
No |
/storage/db/vcops/cassandra |
|
Central ( Repl) DB |
Resource inventory |
PostgreSQL |
Yes |
/storage/db/vcops/vpostgres/data/ |
|
Alerts /HIS (Data) DB |
Alerts and alarm history, history of resource property data, history of resource relationship |
PostgreSQL |
Yes |
/storage/db/vcops/vpostgres/data/ |
|
FSDB |
Filesystem database containing the following: •RAW metrics •Super metrics data |
FSDB |
Yes |
/storage/db/vcops/data /storage/db/vcops/rollup |
|
CaSA DB |
Cluster and Slice Administrator data |
HSQL (Hyper SQL Database) |
No |
/storage/db/casa/webapp/ hsqlbd |
Sharding is the term that GemFire uses to describe the process of distributing data across multiple systems to ensure that compute, storage, and network load is evenly distributed across the cluster.