Skip to content

Commit adb32a8

Browse files
committed
Update Blog “how-to-backup-and-restore-stateful-applications-on-kubernetes-using-kasten-k10-in-hpe-greenlake-for-private-cloud-enterprise”
1 parent 7c8cd39 commit adb32a8

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

content/blog/how-to-backup-and-restore-stateful-applications-on-kubernetes-using-kasten-k10-in-hpe-greenlake-for-private-cloud-enterprise.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -480,7 +480,7 @@ This volume snapshot can be used for MySQL database restore.
480480

481481
Before showing the database restore, I will first delete some table from MySQL database to simulate a loss of data. Then, I will perform the database recovery using the Kasten K10.
482482

483-
##### Delete table
483+
**1. Delete table**
484484

485485
Delete data from the table '*departments'* by typing the following commands:
486486

@@ -568,7 +568,7 @@ $ mysql -h 127.0.0.1 -uroot -pCfeDemo@123 -P 42281 -t <test_employees_sha.sql
568568
+---------+--------+
569569
```
570570

571-
##### Perform MySQL database restore
571+
**2. Perform MySQL database restore**
572572

573573
In order to restore the MySQL database, go to the Kasten K10 Dashboard, locate the MySQL database *'mysql'* from the application list, expand the menu of *mysql*, then click *Restore* button:
574574

@@ -586,6 +586,8 @@ The restore of the MySQL database will be started from the selected restore p
586586

587587
![](/img/k10-dashboard-restore.png)
588588

589+
**3. Verify MySQL database**
590+
589591
Connect to the MySQL database service and re-run the testing script *test_employees_sha.sql*. You should see the testing script now reports everything is *OK*:
590592

591593
```shell

0 commit comments

Comments
 (0)