From ee8023c148f6e7fbe052b0ddfb8a84229bd22fee Mon Sep 17 00:00:00 2001 From: Jags Ramnarayan Date: Sun, 30 Jun 2024 20:31:44 -0700 Subject: [PATCH] minor edits --- docs/Data offloading/README.md | 4 ++-- docs/Scaling horizontally, HA.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Data offloading/README.md b/docs/Data offloading/README.md index cafedf99..5bce62c8 100644 --- a/docs/Data offloading/README.md +++ b/docs/Data offloading/README.md @@ -4,7 +4,7 @@ There are multiple options to copy/offload data from a SkySQL DB. You can do a l You can then use the offloaded data to resurrect the DB elsewhere. You can also optionally setup "outbound replication" to keep the new DB in sync with SkySQL. -## ** (1) Offload your Database using `mariadb-dump`** +## **(1) Offload your Database using `mariadb-dump`** The [`mariadb-dump`](https://mariadb.com/kb/en/mariadb-dump/) utility is a powerful command-line tool that allows you to export databases, tables, or specific data from your MariaDB instance in SkySQL. @@ -214,6 +214,6 @@ curl --location 'https://api.skysql.com/skybackup/v1/backups/status' \ This API call will return the status of the backups, including whether they are in progress, completed, or failed. -## [** (4) Replicating changes from SkySQL to a compatible external DB**](./Replicating%20data%20from%20SkySQL%20to%20external%20database.md) +## [**(4) Replicating changes from SkySQL to a compatible external DB**](./Replicating%20data%20from%20SkySQL%20to%20external%20database.md) diff --git a/docs/Scaling horizontally, HA.md b/docs/Scaling horizontally, HA.md index e146b0b0..2452cdf3 100644 --- a/docs/Scaling horizontally, HA.md +++ b/docs/Scaling horizontally, HA.md @@ -58,7 +58,7 @@ In SkySQL you can control routing using 2 strategies: - Using the ['hint filter'](https://mariadb.com/kb/en/mariadb-maxscale-24-hintfilter/) (TODO: provide detailed example using SkySQL node names) -## **Level 3 Resiliency - Disaster Recovery – Across Regions, Cloud Providers, or “Self-managed” Environments ** +## **Level 3 Resiliency - Disaster Recovery – Across Regions, Cloud Providers, or “Self-managed” Environments** The major cloud providers tout disaster recover across regions, ensuring resilience against natural disasters impacting an entire geographical region. But in reality, such disasters are exceedingly rare. Whatʼs far more common are technical issues impacting an entire region for a specific cloud provider. For instance, we’ve encountered DNS-level failures in GCP regions, rendering all services dependent on DNS, including SkySQL, inaccessible. One effective strategy to mitigate such risks is to replicate data to a data center owned by a different cloud provider within the same geographical area, minimizing network latencies. Disaster recovery across cloud providers is of course something an individual provider such as AWS or GCP simply donʼt support. Alternatively, customers can maintain their own “standby” database for emergencies—an environment entirely under their control, ensuring a near-real time copy of the data at all times.