Skip to main content
By default, Domino runs in a High Availability mode, replicating its core components across three or more nodes in the cluster. Data losses are rare and unlikely to happen. However, in the event of a service disruption which impacts the entire cluster, Domino recommends recovery point (RPO) targets of 0 to 12 hours depending on the service level requirements of your organization. For deployments in the cloud, we strongly recommend deployments across multiple availability zones (AZs). Typically, deployments on multiple AZs can expect an RTO between 0 and 10 minutes. The following systems are canonical stores of critical Domino data, and they are stored and backed up in AWS as described in the following table.

Recovery

If you choose to run “hot” backup instances or additional storage facilities for disaster recovery, you can request an increase in quota limits for one or more of the AWS services if needed. You can check the default service quotas and manage your quotas by logging in to the AWS Service Quotas console. If you need to restore a deployment from backups, submit a maximum severity support request and the Domino operations team assists with the recovery procedure. In the case of instance or service failure, submit a maximum severity support request and the Domino operations team assists with restoring the cluster to normal operation. In the case of critical application failure, submit a maximum severity support request and the Domino operations team assists with restoring the cluster to normal operation. By default, Domino runs in a “High Availability” mode, replicating its core components across three or more nodes in the cluster. Should a fault condition occur, submit an appropriate severity support request ticket and the Domino operations team assists with restoring the cluster to normal operation.

Domino backups on-premises

The following systems are canonical stores of critical Domino data, and they are stored and backed on-premises as described below. These methods can also be applied to other clouds for which Domino does not have native storage integrations.

Support

Domino support coverage is outlined on our Scope of Support Coverage page. You can learn more about our support priority codes, ticket statuses, and business hours on our Support Definitions page. In addition to the support tiers described above, some Domino customers may have unique contractual SLAs defined in the Master Service Agreement. All customers receive a standard service level agreement.
Last modified on July 16, 2026