public:module:mysql_database:restore
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
public:module:mysql_database:restore [2019/09/02 15:53] ronnie.chan [2). Manually recover the databases] |
public:module:mysql_database:restore [2019/09/19 18:16] (current) ronnie.chan [Manually recover the databases] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Restore ====== | ====== Restore ====== | ||
| + | ---- | ||
| There 3 restore options available for MySQL database: | There 3 restore options available for MySQL database: | ||
| - **Original location** – CloudBacko Pro will restore the database(s) from the backup destination and apply them to the original production MySQL instance. | - **Original location** – CloudBacko Pro will restore the database(s) from the backup destination and apply them to the original production MySQL instance. | ||
| Line 5: | Line 6: | ||
| - **Restore raw file** – CloudBacko Pro will restore the database *.sql files to a location on the local machine. Which then can be copied to another MySQL server on another machine for recovery. | - **Restore raw file** – CloudBacko Pro will restore the database *.sql files to a location on the local machine. Which then can be copied to another MySQL server on another machine for recovery. | ||
| - | ---- | + | {{INLINETOC}} \\ |
| - | ===== 1. To Original Location ===== | + | ===== To Original Location ===== |
| + | ---- | ||
| Restore files from your backup destination and automatically apply them to the MySQL database server in the original location. These are the steps. | Restore files from your backup destination and automatically apply them to the MySQL database server in the original location. These are the steps. | ||
| Line 130: | Line 132: | ||
| </code> | </code> | ||
| - | ---- | + | \\ |
| - | ===== 2. To Alternate Location ===== | + | ===== To Alternate Location ===== |
| + | ---- | ||
| 1. Login to MySQL Server using MySQL Command Line Client and verify the database instance is running. | 1. Login to MySQL Server using MySQL Command Line Client and verify the database instance is running. | ||
| Line 213: | Line 216: | ||
| </code> | </code> | ||
| - | ---- | + | \\ |
| ===== Restore Raw Files (Manual Restore) ===== | ===== Restore Raw Files (Manual Restore) ===== | ||
| + | ---- | ||
| Manual restore involves 2 steps: 1). Restore the MySQL databases from your storage destination to a location on disk, and 2). manually recover the databases. | Manual restore involves 2 steps: 1). Restore the MySQL databases from your storage destination to a location on disk, and 2). manually recover the databases. | ||
| <WRAP indent> | <WRAP indent> | ||
| - | ==== 1). Restore the MySQL databases from your storage destination to a location on disk ==== | + | ==== Restore the MySQL databases from your storage destination to a location on disk ==== |
| + | ---- | ||
| 1. In the CloudBacko Pro main interface, click the Restore icon. \\ {{public:mysql-00d.png?200}} | 1. In the CloudBacko Pro main interface, click the Restore icon. \\ {{public:mysql-00d.png?200}} | ||
| Line 238: | Line 243: | ||
| Example: Using Windows File Explorer \\ {{public:mysql-33.png?640}} | Example: Using Windows File Explorer \\ {{public:mysql-33.png?640}} | ||
| - | ==== 2). Manually recover the databases ==== | + | ==== Manually recover the databases ==== |
| + | ---- | ||
| 1. Login to MySQL Server using MySQL Command Line Client and verify the database instance is running. | 1. Login to MySQL Server using MySQL Command Line Client and verify the database instance is running. | ||
| Line 390: | Line 396: | ||
| 37 rows in set (0.00 sec) | 37 rows in set (0.00 sec) | ||
| </code> | </code> | ||
| + | </WRAP> | ||
public/module/mysql_database/restore.1567410835.txt.gz · Last modified: 2019/09/02 15:53 by ronnie.chan
Page Tools
