CDP Quick Tip #21 – Best Practices for Restoring Entire MySQL Instance

Posted by R1Soft on Jan 6, 2012 9:00:00 AM

Today’s Quick Tip focuses on restoring MySQL instances more efficiently in CDP 3.0.  This is a key desire of many of our customers who need to restore a large number of databases.*Please note that this quick tip assumes you have the MySQL for CDP add-on enabled, as it is needed to lock and flush tables before a MySQL backup takes place.

If you are restoring an entire MySQL instance, it is more efficient to perform a file restore of the MySQL data directory than to restore databases individually. When databases are restored individually (see Restoring a MySQL Database), each row must be selected and inserted and this can take a long time.  In this case, we recommend shutting down your MySQL instance and restoring your MySQL data directory using the file restore feature (see Restoring Files).

We recommend following the following 5 steps to restore an entire MySQL instance:

1)     Identify the MySQL data directory

2)     Stop the MySQL instance

- Windows users use the Windows MySQL Administrator utility OR type net stop MySQL at a command prompt
- Linux users type the following command: /etc/init.d/mysql stop
- Linux users type /etc/init.d/mysql start

3)     Move the contents of the data directory to another location as a backup just in case (best practice)

4)     Use CDP to perform a file restore of the MySQL data directory

5)     Start the MySQL instance

- Windows users use the Windows MySQL Administrator utility OR type net start MySQL at a command prompt

Get complete instructions including screenshots in our wiki.

Topics: mysql, CDP Server 3.0, CDP Quick Tips, restore

Recent Posts

Posts by Topic

see all