From 0025a37ee1b0d899f18485e806446af91894cf48 Mon Sep 17 00:00:00 2001 From: josh-wong <23216828+josh-wong@users.noreply.github.com> Date: Thu, 16 May 2024 17:57:45 +0900 Subject: [PATCH] Fix link --- docs/scalar-kubernetes/BackupRDB.mdx | 4 ++-- versioned_docs/version-3.8/scalar-kubernetes/BackupRDB.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/scalar-kubernetes/BackupRDB.mdx b/docs/scalar-kubernetes/BackupRDB.mdx index 6b6fed1a..2a1394e2 100644 --- a/docs/scalar-kubernetes/BackupRDB.mdx +++ b/docs/scalar-kubernetes/BackupRDB.mdx @@ -8,7 +8,7 @@ If you have two or more RDBs that the [Multi-storage Transactions](https://githu To perform backups, you should enable the automated backup feature available in the managed databases. By enabling this feature, you do not need to perform any additional backup operations. For details on the backup configurations in each managed database, see the following guides: -* [Set up a database for ScalarDB/ScalarDL deployment on AWS](SetupDatabaseForAWS.md) -* [Set up a database for ScalarDB/ScalarDL deployment on Azure](SetupDatabaseForAzure.md) +* [Set up a database for ScalarDB/ScalarDL deployment on AWS](SetupDatabaseForAWS.mdx) +* [Set up a database for ScalarDB/ScalarDL deployment on Azure](SetupDatabaseForAzure.mdx) Because the managed RDB keeps backup data consistent from a transactions perspective, you can restore backup data to any point in time by using the point-in-time recovery (PITR) feature in the managed RDB. diff --git a/versioned_docs/version-3.8/scalar-kubernetes/BackupRDB.mdx b/versioned_docs/version-3.8/scalar-kubernetes/BackupRDB.mdx index 903a9ed5..f3872a8c 100644 --- a/versioned_docs/version-3.8/scalar-kubernetes/BackupRDB.mdx +++ b/versioned_docs/version-3.8/scalar-kubernetes/BackupRDB.mdx @@ -8,7 +8,7 @@ If you have two or more RDBs that the [Multi-storage Transactions](https://githu To perform backups, you should enable the automated backup feature available in the managed databases. By enabling this feature, you do not need to perform any additional backup operations. For details on the backup configurations in each managed database, see the following guides: -* [Set up a database for ScalarDB/ScalarDL deployment on AWS](SetupDatabaseForAWS.md) -* [Set up a database for ScalarDB/ScalarDL deployment on Azure](SetupDatabaseForAzure.md) +* [Set up a database for ScalarDB/ScalarDL deployment on AWS](SetupDatabaseForAWS.mdx) +* [Set up a database for ScalarDB/ScalarDL deployment on Azure](SetupDatabaseForAzure.mdx) Because the managed RDB keeps backup data consistent from a transactions perspective, you can restore backup data to any point in time by using the point-in-time recovery (PITR) feature in the managed RDB.