Skip to content

Commit cc321eb

Browse files
AUTO: Docs repo sync - ScalarDB (#1493)
* AUTO: Sync ScalarDB docs in English to docs site repo * Change `disaster recovery` to `high availability` --------- Co-authored-by: josh-wong <[email protected]> Co-authored-by: Josh Wong <[email protected]>
1 parent 3dedf26 commit cc321eb

File tree

4 files changed

+8
-6
lines changed

4 files changed

+8
-6
lines changed

docs/scalardb-cluster/remote-replication.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,19 @@ tags:
55
displayed_sidebar: docsEnglish
66
---
77

8-
# Replicate Data for Disaster Recovery
8+
# Replicate Data for High Availability
99

10-
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.
10+
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.
11+
12+
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.
1113

1214
## What is remote replication in ScalarDB?
1315

1416
Remote replication in ScalarDB uses a hybrid approach, combining synchronous and asynchronous replication. This ensures zero data loss (a recovery point objective, or RPO, of zero) while minimizing performance impact at the primary site. The recovery time objective (RTO) can be flexibly adjusted by controlling the amount of computing resources. This feature is built on top of ScalarDB Cluster, making it cloud-agnostic and database-agnostic. This allows replication from one database in one cloud vendor to another, possibly different kind of database in a different cloud vendor.
1517

1618
## Key benefits
1719

18-
Remote replication provides several key advantages for disaster recovery and business continuity:
20+
Remote replication provides several key advantages:
1921

2022
- Guarantees zero data loss (RPO of 0) for all committed transactions.
2123
- Minimizes performance impact through the combination of synchronous and asynchronous processing.

sidebars.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -839,7 +839,7 @@ const sidebars = {
839839
{
840840
type: 'doc',
841841
id: 'scalardb-cluster/remote-replication',
842-
label: 'Replicate Data for Disaster Recovery',
842+
label: 'Replicate Data for High Availability',
843843
},
844844
{
845845
type: 'category',

src/components/Cards/3.16.tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ const recentFeatures = [
2626
{
2727
cell: 0, // First cell
2828
links: ['scalardb-cluster/remote-replication'],
29-
labels: ['Replicate Data for Disaster Recovery']
29+
labels: ['Replicate Data for High Availability']
3030
},
3131
{
3232
cell: 1, // Second cell

src/data/notifications.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ const notificationsList = [
1414
// },
1515
{
1616
message: {
17-
en: 'Replicate data for disaster recovery in ScalarDB 3.16',
17+
en: 'Replicate data for high availability in ScalarDB 3.16',
1818
ja: 'ScalarDB 3.16 でのデータの災害復旧のためのレプリケーション'
1919
},
2020
url: {

0 commit comments

Comments
 (0)