www.bobcloud.net
Ahsay Online Backup Manager v8
MySQL Database Backup and Restore for
Windows
Ahsay Systems Corporation Limited
8 February 2019
This is the original Ahsay manual
Depending on the service you have with us, some of the content won’t be applicable to you.
Note:
We don’t supply the following services, Open direct, Run Direct, or Run on Server on our
BOBcloud service. These are only provided on our System Provider service.
All accounts must be created on our reseller portal https://portal.data-stor.net
Any Ahsay professional services are provided by them and not us.
Definitions:
Our Desktop version is named ACB \ AhsayACB in this manual.
Our Server version is named OBM \ AhsayOBM in this manual.
The AhsayCBS Web Console is mapped to our own portal https://portal.data-stor.net
www.bobcloud.net
Copyright Notice
© 2019 Ahsay Systems Corporation Limited. All rights reserved.
The use and copying of this product is subject to a license agreement. Any other use is prohibited. No part of this publication
may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any
means without prior written consent of Ahsay Systems Corporation Limited. Information in this manual is subject to change
without notice and does not represent a commitment on the part of the vendor, Ahsay Systems Corporation Limited does not
warrant that this document is error free. If you find any errors in this document, please report to Ahsay Systems Corporation
Limited in writing.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Trademarks
Ahsay, Ahsay Cloud Backup Suite, Ahsay Online Backup Suite, Ahsay Offsite Backup Server, Ahsay Online Backup Manager,
Ahsay A-Click Backup, Ahsay Replication Server, Ahsay BackupBox Firmware, Ahsay Universal Backup System, Ahsay NAS
Client Utility are trademarks of Ahsay Systems Corporation Limited.
Amazon S3 is registered trademark of Amazon Web Services, Inc. or its affiliates.
Apple and Mac OS X are registered trademarks of Apple Computer, Inc.
Dropbox is registered trademark of Dropbox Inc.
Google Cloud Storage and Google Drive are registered trademarks of Google Inc.
Lotus, Domino, Notes are registered trademark of IBM Corporation.
Microsoft, Windows, Microsoft Exchange Server, Microsoft SQL Server, Microsoft Hyper-V, Microsoft Azure, One Drive and
One Drive for Business are registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Oracle, Oracle 10g, Oracle 11g and MySQL are registered trademarks of Oracle Corporation.
Rackspace and OpenStack are registered trademarks of Rackspace US, Inc.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc.
www.redhat.com in the U.S. and other countries. Linux is a registered trademark of Linus Torvalds.
ShadowProtect is registered trademark of StorageCraft Technology Corporation.
VMware, ESX, ESXi, vCenter are registered trademarks of VMware, Inc.
All other product names are registered trademarks of their respective owners.
Disclaimer
Ahsay Systems Corporation Limited will not have or accept any liability, obligation or responsibility whatsoever for any loss,
destruction or damage (including without limitation consequential loss, destruction or damage) however arising from or in
respect of any use or misuse of reliance on this document. By reading and following the instructions in this document, you
agree to accept unconditionally the terms of this Disclaimer and as they may be revised and/or amended from time to time by
Ahsay Systems Corporation Limited without prior notice to you.
www.bobcloud.net
Revision History
Date
Descriptions
Type of modification
22 January 2019
Changed the FAQ link for the system requirements
in Ch. 1; Updated screen shots and command lines
in Ch. 2, Ch. 4.1, Ch. 5, Ch. 7.1, Ch. 7.3, Ch. 7.3,
Ch. 8.1, Ch. 8.2, and Ch. 8.3;
Modification
www.bobcloud.net
Table of Contents
1 System Requirements.....................................................................................................................1
2 Requirements and Recommendations............................................................................................2
3 Limitations.......................................................................................................................................6
4 Starting AhsayOBM ........................................................................................................................7
4.1 Login to AhsayOBM...................................................................................................................7
5 Creating a MySQL Database Backup Set.......................................................................................9
6 Overview on the Backup Process .................................................................................................18
7 Running Backup Jobs ...................................................................................................................19
7.1 Login to AhsayOBM.................................................................................................................19
7.2 Start a Manual Backup ............................................................................................................19
7.3 Configure Backup Schedule for Automated Backup................................................................22
8 Restoring Data ..............................................................................................................................25
8.1 Login to AhsayOBM.................................................................................................................25
8.2 Automatic MySQL Database Restore......................................................................................25
8.3 Manual MySQL Database Restore ..........................................................................................31
8.3.1 Recovering MySQL Databases.........................................................................................35
8.4 Automatic MySQL Database Restore (Alternative Location)...................................................38
www.bobcloud.net 1
1 System Requirements
Refer to the following KB article for the list of supported operating systems & application
versions:
FAQ: Ahsay Software Compatibility List (SCL) for version 8.1 or above
http://wiki.ahsay.com/doku.php?id=public:8001_faq:ahsay_software_compatibility_list_scl_for
_version_8.1_or_above
www.bobcloud.net 2
2 Requirements and Recommendations
Please ensure that the following requirements and conditions are met on the MySQL database
server.
1. AhsayOBM is installed on the MySQL database server.
2. The MySQL database instance is online.
Example: MySQL v5.6 on Windows Server 2016 (64-bit), the default service name is
MySQL56.
Example: MySQL v8 on Windows Server 2016, the default service name is MySQL80.
3. Check the listening port of the MySQL database instance (default is 3306) using the
command netstat –b –a.
C:\>netstat -b -a
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 w2k16-std:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:445 w2k16-std:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:2179 w2k16-std:0 LISTENING
[vmms.exe]
TCP 0.0.0.0:3306 w2k16-std:0 LISTENING
[mysqld.exe]
TCP 0.0.0.0:3389 w2k16-std:0 LISTENING
TermService
[svchost.exe]
www.bobcloud.net 3
TCP 0.0.0.0:5985 w2k16-std:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:47001 w2k16-std:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49664 w2k16-std:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49665 w2k16-std:0 LISTENING
[lsass.exe]
TCP 0.0.0.0:49666 w2k16-std:0 LISTENING
EventLog
[svchost.exe]
TCP 0.0.0.0:49667 w2k16-std:0 LISTENING
[spoolsv.exe]
TCP 0.0.0.0:49668 w2k16-std:0 LISTENING
SessionEnv
[svchost.exe]
TCP 0.0.0.0:49669 w2k16-std:0 LISTENING
PolicyAgent
4. The mysqldump utility is installed on the MySQL database server.
Example: the default location for the mysqldump utitlity for MySQL v5.6.x is located in the
following folder C:\Program Files\MySQL\MySQL Server 5.6\bin
5. The mysqldump utility is the same version as the MySQL database.
To check the mysqldump version use the mysqldump – –version command.
Example: MySQL v5.6
C:\Program Files\MySQL\MySQL Server 5.6\bin>mysqldump --version
mysqldump Ver 10.13 Distrib 5.6.41, for Win64 (x86_64)
C:\Program Files\MySQL\MySQL Server 5.6\bin>
Example: MySQL v8.0
C:\Program Files\MySQL\MySQL Server 8.0\bin>mysqldump --version
mysqldump Ver 8.0.12 for Win64 on x86_64 (MySQL Community Server
- GPL)
C:\Program Files\MySQL\MySQL Server 8.0\bin>
MySQL database version:
Example: MySQL v5.6
mysql> select version();
+------------+
| version() |
+------------+
| 5.6.41-log |
+------------+
1 row in set (0.00 sec)
mysql>
Example: MySQL v8.0
mysql> select version();
+-----------+
| version() |
+-----------+
| 8.0.12 |
+-----------+
1 row in set (0.00 sec)
mysql>
www.bobcloud.net 4
6. A MySQL database user account with the following privileges must be setup for the backup
operation.
Example: MySQL v5.6
mysql> GRANT ALL PRIVILEGES ON *.* TO "username"@"localhost"
IDENTIFIED BY "password";
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO
"username"@"localhost.localdomain" IDENTIFIED BY "password";
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.01 sec)
mysql>
For MySQL 8 the use of GRANT to define account authentication characteristic is
deprecated. For more information please refer to the MySQL 8.0 Reference Manual. As
an alternative, you must first create the user and set the authentication characteristic by
using CREATE USER before setting the privileges of the user using GRANT.
Example: MySQL v8.0
mysql> CREATE USER 'root'@'localhost.localdomain' IDENTIFIED BY
'Abcd123$%';
Query OK, 0 rows affected (0.32 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost';
Query OK, 0 rows affected (0.01 sec)
mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost.localdomain';
Query OK, 0 rows affected (0.12 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.01 sec)
7. Verify that ‘localhost’ on the MySQL database server is resolvable and ‘localhost’ is allowed
to access the MySQL database instance on the MySQL service listening port (default 3306).
C:\>ping localhost
Pinging 10.90.10.40 with 32 bytes of data:
Reply from 10.90.10.40: bytes=32 time<1ms TTL=64
Reply from 10.90.10.40: bytes=32 time<1ms TTL=64
Reply from 10.90.10.40: bytes=32 time<1ms TTL=64
Reply from 10.90.10.40: bytes=32 time<1ms TTL=64
Ping statistics for 10.90.10.40:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>
# telnet localhost 3306
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'
J
5.6.31vB#'8%/kQ3K\n6``Aemysql_native_password
www.bobcloud.net 5
Note: The telnet utility is not installed by default on some Windows versions.
8. Exclude the 'information_schema' and ‘performance_schema’ databases are MySQL virtual
system databases, which contains information about the user databases on the MySQL
instance. They are read-only and cannot be backed up.
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sakila |
| test |
| world |
+--------------------+
6 rows in set (0.00 sec)
9. The databases selected for backup will be temporarily spooled to a temporary directory
before being uploaded to the backup server or destination storage.
Ensure that the temporary directory configured for the MySQL database backup has
sufficient disk space for the backup operation, the free space on the temporary directory
drive should be at least 130% of the database size. As the temporary directory is also used
for storing index files and any incremental or differential delta files generated during the
backup job before they are uploaded to the backup destination.
Please bear in mind the size of the databases may grow over time and you may need to
review the temporary directory free space requirements on a regular basis.
To calculate for the size of your databases run the command below.
+--------------------+-----------+
| Database | Size (MB) |
+--------------------+-----------+
| information_schema | 0.01 |
| mysql | 0.90 |
| performance_schema | 0.00 |
| sakila | 6.44 |
| world | 0.77 |
+--------------------+-----------+
5 rows in set (0.53 sec)
www.bobcloud.net 6
3 Limitations
1. Backup and restore must be to the same MySQL database version.
2. When restoring MySQL databases to an alternate location only one database can be
selected and restored at any one time.
3. Cannot restore the MySQL database nodes to original or alternate location.
4. Restoring databases to another machine can only be done using the Restore raw file
option.
www.bobcloud.net 7
4 Starting AhsayOBM
4.1 Login to AhsayOBM
1. A shortcut icon of AhsayOBM should have been created on your Windows desktop after
installation. Double click the icon to launch the application.
2. Enter the login name and password of your AhsayOBM account provided by your backup
service provider, then click OK to login.
www.bobcloud.net 8
www.bobcloud.net 9
5 Creating a MySQL Database Backup Set
1. Click the Backup Sets icon on the main interface of AhsayOBM.
2. Create a new backup set by clicking the Add button to created new backup set.
3. Select the Backup set type and name your new backup set and enter the login
information for the MySQL server then click Next to proceed.
www.bobcloud.net 10
4. In the Backup Source menu, select the MySQL databases you would like to backup. Click
Next to proceed.
5. In the Schedule menu, you can configure a backup schedule for backup job to run
automatically at your specified time interval.
www.bobcloud.net 11
Click Add to add a new schedule or double click on the existing schedule to change the
values. Click Next to proceed when you are done setting.
Note: The default backup schedule is daily backup at 03:00 with the backup job will run
until completion and the retention policy job will be run immediately after the backup job.
6. Select a backup mode and click the “+” sign icon to select a backup storage destination.
www.bobcloud.net 12
7. Select the backup storage destination. Click on OK to proceed.
Example: AhsayCBS server
8. In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
www.bobcloud.net 13
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system.
User password – the encryption key will be the same as the login password of
your AhsayOBM at the time when this backup set is created. Please be reminded
that if you change the AhsayOBM login password later, the encryption keys of the
backup sets previously created with this encryption type will remain unchanged.
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
Note: For best practice on managing your encryption key, refer to the following KB
article. https://forum.ahsay.com/viewtopic.php?f=169&t=14090
Click Next when you are done setting.
www.bobcloud.net 14
9. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this
option to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step.
www.bobcloud.net 15
10. Windows User Authentication
Enter the Windows login credentials used by AhsayOBM to authenticate the scheduled or
continuous backup job and click on Next to proceed.
Note: If the backup schedule is turned off for the backup set the Windows User
Authentication screen will be automatically skipped. The Windows User Authentication
login credentials can be added or updated post backup set creation.
www.bobcloud.net 16
11. Backup set created.
i. To start a manual backup job click on Backup now.
ii. To verify the backup set settings, click on Close and then click on the MySQL backup
set to complete the setup.
www.bobcloud.net 17
www.bobcloud.net 18
6 Overview on the Backup Process
The following steps are performed during a MySQL database backup job:
www.bobcloud.net 19
7 Running Backup Jobs
7.1 Login to AhsayOBM
Login to the AhsayOBM application according to the instructions in Chapter 3.1
7.2 Start a Manual Backup
1. Click the Backup icon on the main interface of AhsayOBM.
2. Select the MySQL Database backup set which you would like to start a manual backup.
www.bobcloud.net 20
3. If you would like to modify the In-File Delta type, Destinations, or Run Retention Policy
Settings, click on Show advanced option.
4. Click on Backup to start the backup job.
www.bobcloud.net 21
5. Backup job is completed.
www.bobcloud.net 22
7.3 Configure Backup Schedule for Automated Backup
1. Click on the Backup Sets icon on the AhsayOBM main interface.
2. Select the backup set that you would like to create a backup schedule for.
www.bobcloud.net 23
3. Click Backup Schedule.
4. Turn on the backup schedule by switching the “Run scheduled backup for this backup
set” feature to On, then click the + icon next to Add new schedule.
www.bobcloud.net 24
5. Configure the backup schedule settings on this page, then click OK when you are done
with the settings.
6. Click Save to confirm the settings and exit the Backup Schedule menu.
www.bobcloud.net 25
8 Restoring Data
The restore options available:
i. Original location – AhsayOBM will restore the database(s) from the backup destination
and apply them to the original production MySQL instance.
ii. Alternate location – AhsayOBM will restore the database(s) from the backup
destination and apply them to the either the original MySQL instance or another MySQL
instance on the production machine. This option can also be used to clone a database
by changing the database name.
iii. Restore raw file – AhsayOBM 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.
8.1 Login to AhsayOBM
Login to the AhsayOBM application according to the instructions in Chapter 3.1 Login to
AhsayOBM
8.2 Automatic MySQL Database Restore
Restore files from your backup destination and automatically apply them to the MySQL
database server in the original location.
1. Login to MySQL Server using MySQL Command Line Client and verify the database
instance is running.
Enter password: ********
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 36
Server version: 5.6.41-log MySQL Community Server (GPL)
Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights
reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input
statement.
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sakila |
| test |
| world |
+--------------------+
6 rows in set (0.00 sec)
mysql>
www.bobcloud.net 26
2. In the AhsayOBM main interface, click the Restore icon.
3. Select the backup set that you would like to restore the MySQL Database from.
www.bobcloud.net 27
4. Select the storage destination that contains the MySQL databases that you would like to
restore from.
5. Select to restore the MySQL node from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
Note: To restore to either original or alternate location please unselect the MySQL data
node and only select the databases only.
www.bobcloud.net 28
6. Select to restore the MySQL Databases to the Original location and click Next to
proceed.
7. Confirm the temporary directory path is correct and then click Restore to proceed.
www.bobcloud.net 29
8. After the MySQL database(s) has been restored.
www.bobcloud.net 30
9. Using MySQL Command Line Client, you can list the restored databases and tables.
Example: Listing the tables in the database using show tables
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sakila |
| test |
| world |
+--------------------+
6 rows in set (0.00 sec)
mysql> show tables in sakila;
+----------------------------+
| Tables_in_sakila |
+----------------------------+
| actor |
| actor_info |
| address |
| category |
| city |
| country |
| customer |
| customer_list |
| film |
| film_actor |
| film_category |
| film_list |
| film_text |
| inventory |
| language |
| nicer_but_slower_film_list |
| payment |
| rental |
| sales_by_film_category |
| sales_by_store |
| staff |
| staff_list |
| store |
+----------------------------+
23 rows in set (0.00 sec)
mysql> show tables in world;
+-----------------+
| Tables_in_world |
+-----------------+
| city |
| country |
| countrylanguage |
+-----------------+
3 rows in set (0.00 sec)
mysql>
www.bobcloud.net 31
8.3 Manual MySQL Database Restore
To restore the MySQL databases from your storage destination to a location on disk and
manually recover the databases.
1. In the AhsayOBM main interface, click the Restore icon.
2. Select the backup set that you would like to restore the MySQL Database from.
www.bobcloud.net 32
3. Select the storage destination that contains the MySQL databases that you would like to
restore from.
4. Select to restore the MySQL database(s) from a specific backup job then select the files
or folders that you would like to restore and select the Restore raw file option. Click
Next to proceed.
www.bobcloud.net 33
5. Select the location on the local machine you wish to restore the MySQL database files to.
Click Next to proceed.
6. Confirm the temporary directory path is correct and then click Restore to proceed.
www.bobcloud.net 34
7. After the MySQL database(s) has been restored.
8. Check the location on the local machine to verify the MySQL database files have been
restored.
Example: Using Windows File Explorer
www.bobcloud.net 35
8.3.1 Recovering MySQL Databases
1. Login to MySQL Server using MySQL Command Line Client and verify the database
instance is running.
Enter password: ******
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 10
Server version: 5.6.31-log MySQL Community Server (GPL)
Copyright (c) 2000, 2016, Oracle and/or its affiliates. All
rights reserved.
Oracle is a registered trademark of Oracle Corporation
and/or its
affiliates. Other names may be trademarks of their
respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the
current input statement.
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
+--------------------+
3 rows in set (0.00 sec)
mysql>
2. Create the database names that need to be recovered.
Example: classicmodels, sakila, and world.
mysql> create database classicmodels;
Query OK, 1 row affected (0.02 sec)
mysql> create database sakila;
Query OK, 1 row affected (0.00 sec)
mysql> create database world;
Query OK, 1 row affected (0.00 sec)
3. Recover Databases
Repeat the following steps for all databases you wish to restore.
mysql> use classicmodels;
mysql> source d:\restored\MySQL\classicmodels.sql
Query OK, 0 rows affected (0.01 sec)
Query OK, 7 rows affected (0.00 sec)
Records: 7 Duplicates: 0 Warnings: 0
Query OK, 110 rows affected (0.00 sec)
Records: 110 Duplicates: 0 Warnings: 0
Query OK, 122 rows affected (0.00 sec)
Records: 122 Duplicates: 0 Warnings: 0
www.bobcloud.net 36
mysql> use sakila;
mysql> source /restored/MySQL/sakila.sql
Query OK, 0 rows affected (0.01 sec)
Query OK, 148 rows affected (1.9 sec)
Records: 148 Duplicates: 0 Warnings: 0
mysql> use world;
mysql> source /restored/MySQL/world.sql
Query OK, 0 rows affected (0.00 sec)
Query OK, 4079 rows affected (0.03 sec)
Records: 4079 Duplicates: 0 Warnings: 0
Query OK, 0 rows affected (0.01 sec)
4. Check the database status
Example: Listing the tables in the database using show tables
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| classicmodels |
| mysql |
| performance_schema |
| sakila |
| world |
+--------------------+
7 rows in set (0.06 sec)
mysql> show tables in world;
+-----------------+
| Tables_in_world |
+-----------------+
| city |
| country |
| countrylanguage |
| departments |
| dept_emp |
| dept_manager |
| employees |
| salaries |
| titles |
+-----------------+
9 rows in set (0.00 sec)
mysql> show tables in classicmodels;
+----------------------------+
| Tables_in_classicmodels |
+----------------------------+
| actor |
| actor_info |
| address |
| category |
| city |
| country |
www.bobcloud.net 37
| countrylanguage |
| customer |
| customer_list |
| customers |
| departments |
| dept_emp |
| dept_manager |
| employees |
| film |
| film_actor |
| film_category |
| film_list |
| film_text |
| inventory |
| language |
| nicer_but_slower_film_list |
| offices |
| orderdetails |
| orders |
| payment |
| payments |
| productlines |
| products |
| rental |
| salaries |
| sales_by_film_category |
| sales_by_store |
| staff |
| staff_list |
| store |
| titles |
+----------------------------+
37 rows in set (0.00 sec)
www.bobcloud.net 38
8.4 Automatic MySQL Database Restore (Alternative Location)
1. Login to MySQL Server using MySQL Command Line Client and verify the database
instance is running.
Enter password: ******
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 10
Server version: 5.6.31-log MySQL Community Server (GPL)
Copyright (c) 2000, 2016, Oracle and/or its affiliates. All
rights reserved.
Oracle is a registered trademark of Oracle Corporation
and/or its
affiliates. Other names may be trademarks of their
respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the
current input statement.
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
+--------------------+
3 rows in set (0.00 sec)
mysql>
2. In the AhsayOBM main interface, click the Restore icon.
www.bobcloud.net 39
3. Select the backup set that you would like to restore the MySQL Database from.
4. Select the storage destination that contains the MySQL databases that you would like to
restore from.
www.bobcloud.net 40
5. Select to restore the MySQL node from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
Note: To restore to either original or alternate location please unselect the MySQL data
node and only select the databases only.
6. Select to restore the MySQL Databases to the alternate location and click Next to
proceed.
www.bobcloud.net 41
7. Confirm the MySQL database details such as Database name, Host, Port, Username,
and Password.
Example: To restore and clone a copy of the world database on the original server with
new name world-clone.
8. Confirm the temporary directory path is correct and then click Restore to proceed.
www.bobcloud.net 42
9. After the MySQL database(s) has been restored.
10. Using MySQL Command Line Client, you can list the restored databases and tables.
Example: Listing the tables in the restore cloned database using show tables
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| classicmodels | |
| mysql |
| performance_schema |
| sakila |
| world |
| world-clone |
+--------------------+
6 rows in set (0.06 sec)
mysql> show tables in `world-clone`;
+-----------------------+
| Tables_in_world-clone |
+-----------------------+
| city |
| country |
| countrylanguage |
+-----------------------+
3 rows in set (0.00 sec)
mysql>