From dca4fd975e510e39e74ee3ebe3b334ba2b2a760a Mon Sep 17 00:00:00 2001 From: josh-wong Date: Mon, 8 Sep 2025 04:31:17 +0000 Subject: [PATCH 1/2] AUTO: Sync ScalarDB docs in English to docs site repo --- docs/scalardb-cluster/remote-replication.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/scalardb-cluster/remote-replication.mdx b/docs/scalardb-cluster/remote-replication.mdx index 7e74a9fe..70e0d007 100644 --- a/docs/scalardb-cluster/remote-replication.mdx +++ b/docs/scalardb-cluster/remote-replication.mdx @@ -5,9 +5,11 @@ tags: displayed_sidebar: docsEnglish --- -# Replicate Data for Disaster Recovery +# Replicate Data for High Availability -ScalarDB Cluster can replicate its managed data to a remote site for disaster recovery. The remote replication feature provides near-real-time replication of write operations from a primary site to one or more backup sites. This feature ensures business continuity by enabling failover to a backup site when disasters or other critical failures affect the primary site. +ScalarDB Cluster can replicate its managed data to remote sites for high availability and workload distribution. The remote replication feature provides near-real-time replication of write operations from a primary site to one or more backup sites. + +This feature ensures business continuity by enabling failover to a backup site in the event of disasters or critical failures affecting the primary site. Additionally, the backup sites can function as read replicas, helping to offload analytical queries, reporting, and business intelligence workloads. ## What is remote replication in ScalarDB? @@ -15,7 +17,7 @@ Remote replication in ScalarDB uses a hybrid approach, combining synchronous and ## Key benefits -Remote replication provides several key advantages for disaster recovery and business continuity: +Remote replication provides several key advantages: - Guarantees zero data loss (RPO of 0) for all committed transactions. - Minimizes performance impact through the combination of synchronous and asynchronous processing. From 3874302f4241fe66866e3d367f5bc0b905e2c13a Mon Sep 17 00:00:00 2001 From: Josh Wong <23216828+josh-wong@users.noreply.github.com> Date: Tue, 9 Sep 2025 10:00:26 +0900 Subject: [PATCH 2/2] Change `disaster recovery` to `high availability` --- sidebars.js | 2 +- src/components/Cards/3.16.tsx | 2 +- src/data/notifications.js | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/sidebars.js b/sidebars.js index ceac20c0..1d76a07d 100644 --- a/sidebars.js +++ b/sidebars.js @@ -839,7 +839,7 @@ const sidebars = { { type: 'doc', id: 'scalardb-cluster/remote-replication', - label: 'Replicate Data for Disaster Recovery', + label: 'Replicate Data for High Availability', }, { type: 'category', diff --git a/src/components/Cards/3.16.tsx b/src/components/Cards/3.16.tsx index bb64a9ce..754266b2 100644 --- a/src/components/Cards/3.16.tsx +++ b/src/components/Cards/3.16.tsx @@ -26,7 +26,7 @@ const recentFeatures = [ { cell: 0, // First cell links: ['scalardb-cluster/remote-replication'], - labels: ['Replicate Data for Disaster Recovery'] + labels: ['Replicate Data for High Availability'] }, { cell: 1, // Second cell diff --git a/src/data/notifications.js b/src/data/notifications.js index d0db214c..9ea3b675 100644 --- a/src/data/notifications.js +++ b/src/data/notifications.js @@ -14,7 +14,7 @@ const notificationsList = [ // }, { message: { - en: 'Replicate data for disaster recovery in ScalarDB 3.16', + en: 'Replicate data for high availability in ScalarDB 3.16', ja: 'ScalarDB 3.16 でのデータの災害復旧のためのレプリケーション' }, url: {