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 MySQL system database. Selecting MySQL database from
browse and restore converts restore into full instance restore. 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.
Recurring restores of Log files, which allows you to replicate data from
one server to another to be used in Fail over cases. (See
Recurring Restores of
Logs for more information)
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. (See
Restore
Data to a Point in Time for more information)
To enable the non-FULL Recurring Restore job, use bFreshRecRestore
Key. This would clear the earlier history. If you do not enable this
Registry Key, the earlier history will be cleared only for the instances with
FULL restores.
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.
Backup and restore operations do not support non-English database names.
It is recommended not to drop MySQL database
before performing a restore operation. MySQL database should be running
when you perform restore operations.
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.
The following types of cross platform restores are supported:
Same Operating System -
Different Version
Restoring data associated with different versions of the same operating system is
supported. You can also have different versions of MySQL in one machine. You
can restore the data across these same/ different versions too. For example, you can restore data secured from a Solaris
9 to Solaris
10.
Different Operating System - Same/Different Version
You can restore data across different platforms too. You can restore data
across different machines with different operating systems running
same/different versions of MySQL server. However, you should be aware of how the
data is restored under certain circumstances.
Same Machine - Multiple servers/instances
You can have several instances of MySQL databases in one server or multiple
servers. Restoring data across these instance is also supported.
The point-in-time database restore is useful in the following scenarios:
If any undesired transaction occurs in the database, you can revert the
database to a state just before the transaction.
If a database fails, you can restore to the state just before the point
of failure.
When you perform a point-in-time restore for a database, the next
scheduled backup for that database will automatically convert to a full
backup.
Use the following steps to restore a database to a previous
point-in-time:
From the CommCell Browser, navigate to Client Computers|
<Client>| MySQL.
Right-click the <Instance> and then click
All Tasks | Browse Backup Data.
Click Specify Browse Time and select the date and time of the
data backed up to be displayed in the Browse window.
Click OK.
In the right pane of the Browse window, select one or
more
databases and click Recover All Selected.
In the MySQL Restore dialog box, select the name of the client computer with instance to
which you want to
restore the database to in the Destination Server from the list.
Verify that the status of the database is displayed as
On-Line; if necessary click the Refresh button to
refresh the status.
Type or click Browse to select the staging path
for data in the Staging Location box.
Click Point-In-Time and select the date and time
later than the date and time selected in the Browse Options dialog
box.
