Skip to main content
info
This documentation is for version v2.6 of the product.
For the latest version(v2.7) documentation click here
Version: v2.6 print this page

Amorphic Services and Recovery Options

Amorphic's DR strategy will help recover the following different types of data:

  • Application Metadata - The service level metadata is replicated in real-time. This is achieved through the DynamoDB global tables feature. The DynamoDB global tables functionality is designed to ensure synchronization across distributed instances. In most of the scenarios, data synchronization happens instantaneously, allowing for seamless recovery without any risk of data loss.
  • DWH User Data - Amorphic DR strategy will manage the restoration of the DWH cluster to the secondary region using the most recent backup.

The following Amorphic services will be operational under read-only modes, allowing users to access and view data without the ability to make any modifications or perform any write operations:

Catalog Services

  • Tenants: Tenants data will be replicated as a part of Data Warehouse (DWH) replication, with Recovery Point Objective (RPO) of 30 minutes and Recovery Time Objective (RTO) of 60 minutes.
  • Domains: Domains data will undergo replication as part of the Data Warehouse (DWH) & Glue Catalog replication process, with a Recovery Point Objective (RPO) of 30 minutes and a Recovery Time Objective (RTO) of 60 minutes.
  • Datasets: Datasets will be replicated as a component of the Data Warehouse (DWH) and Glue Catalog replication procedure, featuring a Recovery Point Objective (RPO) of 30 minutes and a Recovery Time Objective (RTO) of 60 minutes.

Analytics Services

  • Views: Views are replicated as part of the Data Warehouse (DWH) and Glue Catalog replication process which includes a Recovery Point Objective (RPO) of 30 minutes and a Recovery Time Objective (RTO) of 60 minutes.
  • Query Engine: All the replicated Datasets & Views can be queried from the data storage of DR application and the recovery duration involves the Recovery Point Objective (RPO) of 30 minutes and a Recovery Time Objective (RTO) of 60 minutes.

Management

  • Users: Users will be replicated as the application metadata is restored and user migration is performed during the recovery process, thus the Recovery Time Objective(RTO) is 60 minutes.
  • Roles: Roles are maintained as part of applications metadata and restored instantaneously when the metadata is restored.
  • Infra Management: Infrastructure and system health of the DR application can be monitored.
  • User Agreement: User Agreements are replicated as part of restoration of the application metadata.