From c3bb396de83fadb708e3e5ea077cda6672232f57 Mon Sep 17 00:00:00 2001 From: Dorota Wojcik Date: Thu, 24 Jul 2025 13:36:52 +0200 Subject: [PATCH 1/3] opensearch btar --- .../concepts/backup-to-another-region.md | 114 ++++++++++++++---- 1 file changed, 93 insertions(+), 21 deletions(-) diff --git a/docs/platform/concepts/backup-to-another-region.md b/docs/platform/concepts/backup-to-another-region.md index 547dffc59..42c7cd686 100644 --- a/docs/platform/concepts/backup-to-another-region.md +++ b/docs/platform/concepts/backup-to-another-region.md @@ -5,6 +5,8 @@ sidebar_label: Backup to another region --- import RelatedPages from "@site/src/components/RelatedPages"; +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; In addition to the primary service backup, you can have a secondary backup in an alternative location. @@ -19,26 +21,101 @@ region. BTAR can bolster data resilience and helps improve data protection again disasters in the primary backup region. When the primary region is down, BTAR allows forking the service from an additional copy of the backup residing in a secondary region. -BTAR is supported for the following services: +## Limitations + +- The cloud provider for your additional backup region must match the cloud provider for +your service and the primary backup. +- Secondary backup can only be restored in the region where it was stored. + +### Supported services + +BTAR is only supported for the following service types: - Aiven for PostgreSQL® - Aiven for MySQL® - Aiven for OpenSearch® +### Service-specific limitations + + + + +- To + [restore your service from an additional backup](/docs/platform/howto/btar/manage-backup-to-another-region) + using point-in-time recovery (PITR), set up the time to no earlier than the time of + taking the oldest replicated base backup. +- Secondary backup is generated only after a primary backup is complete, and there might + be a data replication lag between the primary region and the secondary region. + + + + +- The synchronization of snapshots between the regions works only for base snapshots created +after the BTAR activation. +- Point-in-time recovery (PITR) is not supported for + [restoring your service from an additional backup](/docs/platform/howto/btar/manage-backup-to-another-region). +- Although a base snapshot in the primary region and its corresponding BTAR snapshot in + the secondary region are generated at the same time, there might be some negligible data + discrepancies between them. + ## How BTAR works -When you enable the backup to another region (BTAR) feature, an additional service backup -is created in the cloud region of your choice that is alternative to the primary backup +When you enable the backup to another region (BTAR) feature, additional service backups +are created in the cloud region of your choice that is alternative to the primary backup location. +Restoring from a secondary backup, for example in case of an outage of the primary region, +can be done by creating a fork of the service in the region where the secondary backup is +located. + + + + Secondary backups are generated from primary backups, not from the service itself. For this reason, your secondary backup becomes available only after the primary backup is taken. There might be a data replication lag between the primary region and the secondary region. -Restoring from a secondary backup, for example in case of an outage of the primary region, -can be done by creating a fork of the service in the region where the secondary backup is -located. +```mermaid +flowchart LR + subgraph Primary_region + direction TB + subgraph Service_X + end + subgraph Primary_backups + direction LR + PB1 + PB2 + PB3 + PBn + end + end + subgraph Secondary_region + direction TB + subgraph Forked_service_X + end + subgraph Secondary_backups + direction LR + SB1 + SB2 + SB3 + SBn + end + end + Service_X -- Default backups --> Primary_backups + Primary_backups -- Cross-region backups
if BTAR enabled --> Secondary_backups + Secondary_backups -- Secondary backups
to restore service X --> Forked_service_X + Service_X -- Forking service X
if primary region down --> Forked_service_X +``` + + + + +An additional snapshot repository is created in the secondary region. In this repository, +BTAR snapshots are generated directly from the service. They are created and managed in +sync with base snapshots in the primary region. For example, when a base snapshot is +created in the primary region, its BTAR counterpart is created simultaneously in the +secondary region with an identical name. ```mermaid flowchart LR @@ -66,24 +143,19 @@ flowchart LR SBn end end - Service_X -- Default \n backups --> Primary_backups - Primary_backups -- Cross-region backups \n if BTAR enabled --> Secondary_backups - Secondary_backups -- Secondary backups \n to restore service X --> Forked_service_X - Service_X -- Forking service X \n if primary region down --> Forked_service_X + Service_X -- Default backups --> Primary_backups + Primary_backups -- Cross-region backups
if BTAR enabled --> Secondary_backups + Secondary_backups -- Secondary backups
to restore service X --> Forked_service_X + Service_X -- Forking service X
if primary region down --> Forked_service_X ``` -## Limitations + + -- BTAR is supported for Aiven for MySQL®, Aiven for PostgreSQL®, and Aiven for OpenSearch®. -- The cloud provider for your additional backup region must match the cloud provider for - your service and the primary backup. -- To - [restore your service from an additional backup](/docs/platform/howto/btar/manage-backup-to-another-region) - using point-in-time recovery (PITR), set up the time to no earlier than the time of - taking the oldest replicated base backup. -- Secondary backup can only be restored in the region where it was stored. -- Secondary backup is generated only after a primary backup is complete, and there might - be a data replication lag between the primary region and the secondary region. + + + + From d92582f7201d7f2f6fde99d3ad67081482de3323 Mon Sep 17 00:00:00 2001 From: Dorota Wojcik Date: Fri, 25 Jul 2025 13:34:21 +0200 Subject: [PATCH 2/3] diagram --- .../concepts/backup-to-another-region.md | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/docs/platform/concepts/backup-to-another-region.md b/docs/platform/concepts/backup-to-another-region.md index 42c7cd686..5e2e8ded5 100644 --- a/docs/platform/concepts/backup-to-another-region.md +++ b/docs/platform/concepts/backup-to-another-region.md @@ -58,6 +58,9 @@ after the BTAR activation. the secondary region are generated at the same time, there might be some negligible data discrepancies between them. + + + ## How BTAR works When you enable the backup to another region (BTAR) feature, additional service backups @@ -86,7 +89,6 @@ flowchart LR direction LR PB1 PB2 - PB3 PBn end end @@ -98,11 +100,10 @@ flowchart LR direction LR SB1 SB2 - SB3 SBn end end - Service_X -- Default backups --> Primary_backups + Service_X -- Base backups
by default --> Primary_backups Primary_backups -- Cross-region backups
if BTAR enabled --> Secondary_backups Secondary_backups -- Secondary backups
to restore service X --> Forked_service_X Service_X -- Forking service X
if primary region down --> Forked_service_X @@ -113,46 +114,45 @@ flowchart LR An additional snapshot repository is created in the secondary region. In this repository, BTAR snapshots are generated directly from the service. They are created and managed in -sync with base snapshots in the primary region. For example, when a base snapshot is -created in the primary region, its BTAR counterpart is created simultaneously in the -secondary region with an identical name. +synchronization with +[base snapshots](/docs/products/opensearch/howto/manage-snapshots) +in the primary region using the +[native OpenSearch API](https://docs.opensearch.org/latest/api-reference/snapshots/index/). +For example, when a +[base snapshot is created](/docs/products/opensearch/howto/manage-snapshots#create-a-snapshot) +in the primary region, its BTAR counterpart is created simultaneously with an identical +name in the secondary region. ```mermaid flowchart LR subgraph Primary_region - direction TB - subgraph Service_X - end + direction LR subgraph Primary_backups - direction LR + direction TB PB1 PB2 - PB3 PBn end + subgraph Service_X + end end subgraph Secondary_region - direction TB + direction LR subgraph Forked_service_X end subgraph Secondary_backups - direction LR + direction TB SB1 SB2 - SB3 SBn end end - Service_X -- Default backups --> Primary_backups - Primary_backups -- Cross-region backups
if BTAR enabled --> Secondary_backups + Service_X -- Base backups
by default --> Primary_backups + Service_X -- Cross-region backups
if BTAR enabled --> Secondary_backups Secondary_backups -- Secondary backups
to restore service X --> Forked_service_X Service_X -- Forking service X
if primary region down --> Forked_service_X -``` - - - - +``` From 2bcaa5907caf3973eee9a10fa07f9fb5e5ea1972 Mon Sep 17 00:00:00 2001 From: dorota <114921900+wojcik-dorota@users.noreply.github.com> Date: Mon, 28 Jul 2025 10:12:00 +0200 Subject: [PATCH 3/3] feedback Signed-off-by: dorota <114921900+wojcik-dorota@users.noreply.github.com> --- docs/platform/concepts/backup-to-another-region.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/platform/concepts/backup-to-another-region.md b/docs/platform/concepts/backup-to-another-region.md index 5e2e8ded5..70b0d4532 100644 --- a/docs/platform/concepts/backup-to-another-region.md +++ b/docs/platform/concepts/backup-to-another-region.md @@ -24,7 +24,7 @@ forking the service from an additional copy of the backup residing in a secondar ## Limitations - The cloud provider for your additional backup region must match the cloud provider for -your service and the primary backup. + your service and the primary backup. - Secondary backup can only be restored in the region where it was stored. ### Supported services @@ -51,7 +51,7 @@ BTAR is only supported for the following service types: - The synchronization of snapshots between the regions works only for base snapshots created -after the BTAR activation. + after the BTAR activation. - Point-in-time recovery (PITR) is not supported for [restoring your service from an additional backup](/docs/platform/howto/btar/manage-backup-to-another-region). - Although a base snapshot in the primary region and its corresponding BTAR snapshot in