The Tetra Data Platform (TDP) has greater than 99.9% availability.

Each TDP environment runs in a specific AWS Region, but is highly redundant because each Region has multiple, isolated locations known as Availability Zones (AZ). Because of this underlying infrastructure, the platform will continue to operate as normal if a platform component in one AZ goes down, or if an entire AZ fails. To preserve data and restore service following a catastrophic event that renders a TDP production site inoperable, TetraScience also creates disaster recovery (DR) sites in a second AWS Region in a different geography for each Tetra-hosted deployment.

There's typically a one-hour period of planned downtime for platform upgrades. For more information, see Planned Downtimes for TDP Upgrades.

Built-In Data Availability and Resilience

The following diagram shows how the TDP uses AWS Global Infrastructure to stay highly resilient and available to customers:

For more information, see AWS Global Infrastructure in the AWS documentation.

Data Retention

The TDP stores data indefinitely unless it's deleted by the customer.

Availability

The TDP uses AWS services that are designed to be highly available, fault tolerant, and scalable. For example, the following services help ensure greater than 99.9% availability for all data in the Tetra Scientific Data and AI Cloud:

• Amazon Simple Storage Service (Amazon S3): Stores files in the Tetra Data Lake. It provides 99.999999999% durability and 99.99% availability of files over a given year by redundantly storing objects on multiple devices across a minimum of three Availability Zones in an AWS Region. An Availability Zone is one or more discrete data centers with redundant power, networking, and connectivity within an AWS Region. For more information, see Data protection in Amazon S3 and Resilience in Amazon S3 in the Amazon S3 User Guide. S3 object backups are made continuously. Data stored in S3 is encrypted at rest.
• Amazon Relational Database Service (Amazon RDS): Provides a scalable, relational database in the cloud that automates time-consuming administration tasks, such as hardware provisioning, database setup, patching, and backups. Amazon RDS provides high availability and automatic failover support for DB instances by using DB deployments across multiple Availability Zones. For more information, see Resilience in Amazon RDS in the Amazon RDS User Guide.
• Amazon OpenSearch Service: Deploys, operates, and scales OpenSearch (an open-source search and analytics engine) clusters in the cloud while providing high availability and automatic failover support across three master nodes and two data nodes deployed across two Availability Zones. For more information, see Resilience in Amazon OpenSearch Service.
• Amazon Elastic Container Service (Amazon ECS): Runs all of the TDP's containerized applications. It provides high availability and automatic failover support for each container by deploying it to two instances across multiple Availability Zones. For more information, see A deep dive into resilience and availability on Amazon Elastic Container Service on the AWS Blog.

For a complete list of AWS services that the TDP uses, see AWS Services.

Planned Downtimes for TDP Upgrades

During TDP upgrades, there's typically an hour of planned downtime. Data is still uploaded to the platform during upgrades, but customers can't access the TDP user interface or the data uploaded during the upgrade until after the process completes.

Upgrade timing is communicated with customers in advance following the Communication Schedule for TDP Releases. If an upgrade requires more than an hour of planned downtime, the expected downtime period is also communicated with customers in advance.

Unplanned Downtime

If any TDP service becomes inaccessible to customers unexpectedly, TetraScience will communicate the service disruption and its impact to customers as soon as possible.

Scheduled Maintenance

The TDP doesn't typically require any planned downtime for scheduled maintenance. However, in the event that platform infrastructure providers require scheduled maintenance, some TDP functionalities could become temporarily unavailable. In the unlikely event that this type of maintenance is necessary, TetraScience will communicate the planned downtime with customers as soon as possible.

Resilience

In addition to the high availability and regional redundancy provided by the AWS Global Infrastructure that the Tetra Data Platform (TDP) uses, the TDP also replicates the following services to a second region for disaster recovery purposes:

📘

NOTE

The TDP automatically handles the data backup and synchronization of all services. No user interaction is required for synchronization. For all Tetra hosted TDP deployments, all of the following backups are also copied to the Disaster Recovery (DR) AWS account. If a customer-hosted TDP deployment doesn't have a Disaster Recovery site set up, then all of the following backups are stored in the Amazon S3 bucket of the AWS account where the TDP is deployed.

• Tetra Data Lake: Amazon Simple Storage Service (Amazon S3) buckets are replicated to a separate AWS Region within 15 minutes for disaster recovery purposes. In addition, versioning is enabled for all buckets in the Tetra Data Lake, which means that you can always retrieve and restore every version of each file. For more information, see Why use replication? and Using versioning in S3 buckets in the Amazon S3 User Guide.
• Relational Database: By using Amazon Relational Database Service (Amazon RDS), the TDP creates and saves automated snapshots of each DB instance every 12 hours, which is then retained for 20 days. For more information, see Backup and restore in the Amazon RDS User Guide.
• Search: By using Amazon OpenSearch Service, the TDP creates and saves automated backups of each cluster's search indexes and state to an Amazon S3 bucket every six hours. For more information, see Resilience in Amazon OpenSearch Service in the Amazon OpenSearch Service Developer Guide.

For more information about how the TDP uses AWS services, including how its architecture adheres to the AWS Well-Architected Framework, see TDP Archictecture and Guidance for Integrating the TetraScience Tetra Data Platform on AWS in the AWS Solutions Library.

Documentation Feedback

Do you have questions about our documentation or suggestions for how we can improve it? Start a discussion in TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘

NOTE

Feedback isn't part of the official TetraScience product documentation. TetraScience doesn't warrant or make any guarantees about the feedback provided, including its accuracy, relevance, or reliability. All feedback is subject to the terms set forth in the TetraConnect Hub Community Guidelines.