Restore Data - MySQL

Topics | How To | Full System Restore | Related Topics

In-Place Restore
Out-of-Place Restore
Cross-Platform Restores

Overview

The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.

The MySQL iDataAgent supports the following types of restores:

Restoring and recovering entire MySQL server
Restoring and recovering individual MySQL databases
Restoring transaction logs

MySQL databases can be restored to the same instance or to different instances on the current machine. The databases can also be saved to the same instance on a destination machine (cross-machine restore).

You can restore a MySQL database dump too. However, ensure to restore the full instance i.e., the backup data of all the subclients under an instance. You cannot select objects from browse for restore while restoring MySQL dump. MySQL dump uses the default value of max_allowed_packet variable while creating dump from MySQL server. If you want to specify the value of max_allowed_packet explicitly for dump/restores, you can set the value in MySQL iDataAgent Registry keys.

Additionally, the MySQL iDataAgent supports:

Restores with the MySQL database online
Point-in-time restores, which allow you to restore data from the full backup created at or before the point in time based on the date and time that you specify

For the MySQL iDataAgent, restore operations can be performed from the client, agent and instance levels in the CommCell Browser.

When there is a problem with the MySQL database or the client system (operating system, hardware, hard drives, etc.), full system restores may be required. See Restore Data - MySQL - Full System Restore for more information.

Restore Considerations for this Agent

Before performing any restore procedures for this agent, review the following information.

Review the general restore requirements described in What You Need to Know Before Performing a Restore.
Backup and restore operations do not support non-English database names.

Restore Destinations

By default, the MySQL iDataAgent restores data to the client computer from which it originated; this is referred to as an in-place restore. You can also restore the data to another Client computer in the CommCell. Keep in mind the following considerations when performing such restores:

The destination client must reside in the same CommCell as the client whose data was backed up.
Note that when you perform restores other than in-place restores, the restored data assumes the rights (i.e., permissions) of the parent directory.

The following section enumerates the types of restore destinations that are supported by the MySQL iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents supporting each restore destination type.

In-Place Restore

Same path/destination

Out-of-Place Restore

Keep in mind that out-of-place restore operations are also subject to the conditions described in Cross-Platform Restores.

Cross-Platform Restores

Same Operating System - Different Version