---
name: openpages-ha
title: Understanding high availability for IBM OpenPages as a Service
description: High availability (HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure.
last-updated: 2025-07-28
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openpages?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Understanding high availability for IBM OpenPages as a Service
{: #ha}

[High availability](#x2284708){: term} (HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure.
{: shortdesc}

IBM OpenPages® as a Service is a highly available, multi-tenant, regional service. The service workload is distributed across multiple availability zones in a region, so single data center outage does not impact overall service availability. Data that is stored in IBM OpenPages is replicated over the availability zones synchronously and is replicated to separate region asynchronously.

In addition to synchronous data replication across zones in one region, the underlying relational database takes full snapshot backup daily automatically and it is stored to regional S3 storage. The daily snapshot backup is kept for up to 35 days along with transaction logs, which is utilized by the service instance restore operation with point-in-time data.

For IBM Cloud, IBM Db2 on Cloud Performance Plans provide high availability through a two-node High Availability Disaster Recovery (HADR) configuration. Each transaction is synchronously committed on both nodes, and in the event of a failure, the standby node automatically assumes write operations, minimizing downtime. The daily snapshot backup along with transaction logs is kept for up to 14 days.

For more information on the restore operation, see [Backing up and restoring the database and configuration settings for IBM OpenPages](https://cloud.ibm.com/docs/openpages?topic=openpages-backing_up_and_restoring&interface=ui&format=markdown).


## Responsibilities
{: #ha-responsibilities}

See [Shared responsibilities for IBM products.](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities&format=markdown) for details on responsibility ownership between IBM and the customer when using IBM OpenPages.

## What level of availability does IBM Cloud offer?
{: #ha-service}

The level of availability that you set up for your cluster impacts your coverage under the IBM Cloud high availability service level agreement terms.

Service level objectives (SLOs) describe the design points that the IBM Cloud services are engineered to meet. IBM OpenPages is designed to achieve the following availability target.

| Availability target | Target Value   |
|---|---|
|  Availability % | 99.9  |
{: caption="SLO for IBM OpenPages" caption-side="bottom"}

The SLO is not a warranty and IBM will not issue credits for failure to meet an objective. Refer to the SLAs for commitments and credits that are issued for failure to meet any committed SLAs. For a summary of all SLOs, see [IBM Cloud service level objectives](https://cloud.ibm.com/docs/overview?topic=overview-slas&format=markdown).