From 4fa15ab9820bc65e799bf2228ccdf41225ec6d46 Mon Sep 17 00:00:00 2001 From: SK Ali Arman Date: Fri, 20 Dec 2024 15:35:06 +0600 Subject: [PATCH] refactor md,my pitr Signed-off-by: SK Ali Arman --- docs/guides/mariadb/pitr/nfs/index.md | 6 +++--- docs/guides/mariadb/pitr/overview/index.md | 6 +++--- docs/guides/mysql/pitr/volumesnapshot/archiver.md | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/guides/mariadb/pitr/nfs/index.md b/docs/guides/mariadb/pitr/nfs/index.md index fd468ff7b8..05f2580d44 100644 --- a/docs/guides/mariadb/pitr/nfs/index.md +++ b/docs/guides/mariadb/pitr/nfs/index.md @@ -419,8 +419,8 @@ NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RE mariadb-1726549985 true data-mariadb-0 10Gi longhorn-snapshot-vsc snapcontent-317aaac9-ae4f-438b-9763-4eb81ff828af 11m 11m ``` -## data insert and switch wal -After each and every wal switch the wal files will be uploaded to backup storage +## Data Insert and Switch Binlog File +After each and every binlog switch the binlog files will be uploaded to backup storage ```bash $ kubectl exec -it -n demo mariadb-0 -- bash @@ -481,7 +481,7 @@ MariaDB [hello]> drop table demo_table; MariaDB [hello]> flush logs; ``` -We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in which time we want to restore.We can get the specfice time from the wal that archived in the backup storage . Go to the binlog file and find where to store. You can parse binlog-files using `mariadbbinlog`. +We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in which time we want to restore.We can get the specfice time from the binlog that archived in the backup storage . Go to the binlog file and find where to store. You can parse binlog-files using `mariadbbinlog`. For the demo I will use the previous time we get form `select now()` diff --git a/docs/guides/mariadb/pitr/overview/index.md b/docs/guides/mariadb/pitr/overview/index.md index 51d8607d65..da2b686d74 100644 --- a/docs/guides/mariadb/pitr/overview/index.md +++ b/docs/guides/mariadb/pitr/overview/index.md @@ -280,8 +280,8 @@ NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RE mariadb-1726549985 true data-mariadb-0 10Gi longhorn-snapshot-vsc snapcontent-317aaac9-ae4f-438b-9763-4eb81ff828af 11m 11m ``` -## data insert and switch wal -After each and every wal switch the wal files will be uploaded to backup storage +## Data Insert and Switch Binlog File +After each and every binlog switch the binlog files will be uploaded to backup storage ```bash $ kubectl exec -it -n demo mariadb-0 -- bash @@ -342,7 +342,7 @@ MariaDB [hello]> drop table demo_table; MariaDB [hello]> flush logs; ``` -We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in which time we want to restore.We can get the specfice time from the wal that archived in the backup storage . Go to the binlog file and find where to store. You can parse binlog-files using `mariadbbinlog`. +We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in which time we want to restore.We can get the specfice time from the binlog that archived in the backup storage . Go to the binlog file and find where to store. You can parse binlog-files using `mariadbbinlog`. For the demo I will use the previous time we get form `select now()` diff --git a/docs/guides/mysql/pitr/volumesnapshot/archiver.md b/docs/guides/mysql/pitr/volumesnapshot/archiver.md index 659f02da9e..897e82dd9a 100644 --- a/docs/guides/mysql/pitr/volumesnapshot/archiver.md +++ b/docs/guides/mysql/pitr/volumesnapshot/archiver.md @@ -363,7 +363,7 @@ mysql> drop table demo_table; mysql> flush logs; ``` -We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in which time we want to restore.We can get the specfice time from the wal that archived in the backup storage . Go to the binlog file and find where to store. You can parse binlog-files using `mysqlbinlog`. +We can't restore from a full backup since at this point no full backup was perform. so we can choose a specific time in which time we want to restore.We can get the specfice time from the binlog that archived in the backup storage . Go to the binlog file and find where to store. You can parse binlog-files using `mysqlbinlog`. For the demo I will use the previous time we get form `select now()`