Chat now with support
Chat with Support

NetVault Plug-in for MySQL 4.4 - User Guide

Introducing Dell™ NetVault™ Backup Plug‑in for MySQL Installing and removing the plug-in Configuring the plug-in Backing up data Restoring data Working with native MySQL replication Using the plug-inin a Failover Cluster environment Troubleshooting About Dell

Restoring to a different MySQL Instance on the same server

In this form of relocation restore, a Plug‑in for MySQL backup is to be restored to the same MySQL Server machine, but to a different instance of MySQL that has been configured there.
Figure 1. Data backed up on one MySQL Instance and recovered to different instance
To accomplish this, perform the steps outlined in the following sections.
Known limitations/intended uses
Prior to conducting a relocation restore, review this list of known limitations and intended uses for this operation:
•
Valid restore sequences can include Full, Incremental, Differential, and Individual Database/Table Copy Only backups.
•
Only restored Binary Logs from an Incremental or Differential Backup can be applied to the destination instance (that is, current Binary Logs from the source instance cannot be applied to the destination instance).

Prerequisites

The following prerequisites must be met before a restore of this type can be set up and run.
•
Existing and target machines must have the same Installation configurations – Both machines must have the following established, in regards to MySQL:
•
Same OS installed
•
Same version of MySQL installed
•
Same installation/base directory
•
Same MySQL “Data” directory
•
New target instance must be successfully configured in Plug‑in for MySQL – The process outlined in Configuring the plug-in must have been successfully performed to add the new MySQL Instance (that is, the target instance must be revealed and accessible within the Plug‑in for MySQL node on the NetVault Backup Selections page).

Setting up and launching the restore

With the prerequisites met, perform the following steps to set up this form of relocation restore job.
To run the restore
1
In the Navigation pane, click Create Restore Job.
2
On the Create Restore Job - Choose Saveset page, select Plug‑in for MySQL from the Plugin Type list.
3
To filter the items displayed in the saveset table further, use the Client, Date, and Job ID lists.
The table displays the saveset name (Job Title and Saveset ID), creation date and time, and size. By default, the list is sorted alphabetically by saveset name.
4
In the saveset table, select the applicable item.
When you select a saveset, the following details are displayed in the Saveset Information area: Job ID, Job Title, name of the NetVault Backup Server, name of the client from which the data was backed up, plug-in used to create the saveset, saveset creation date and time, saveset retirement setting, whether it is an Incremental Backup, whether it is an Archive, and saveset size.
5
To continue, click Next.
6
On the Create Selection Set page, select the data that you want to restore.
Display the individual MySQL Instance that was the target of the backup, navigate the selection tree until the applicable data items are located, and select them for inclusion.
7
With the applicable databases selected, click Edit Plugin Options, and then click the Restore Destination tab.
8
In the Restore Destination Details section, enter the following:
•
Username – Enter the logon account name used to access the target MySQL Instance.
•
Password – Enter the password associated with the logon account.
•
Instance Name – Enter the NetVault Backup name established for the new instance of MySQL, based on what was established during its configuration in NetVault Backup (this is the name established as the MySQL Instance Name in the Configure dialog ; for more information, see Configuring the plug-in).
9
If desired, select the applicable options on the Point-in-Time Recovery tab.
These options are not required to perform this form of restore. For more information, see Setting restore options.
10
Click Ok to save the settings, and then click Next.
11
In Job Name, specify a name for the job if you do not want to use the default setting.
Assign a descriptive title that lets you easily identify the job for monitoring its progress. The job name can contain alphanumeric and non-alphanumeric characters, but it cannot include non-English characters. On Linux, the names can have a maximum of 200 characters. On Windows, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.
 
 
*IMPORTANT: Do not use special characters that are not supported in a file name on the target OS. For example, the characters /,\,*,@, and so on, should not be used on Windows. (This is because Plug‑in for MySQL tries to create a folder with the same name as the Job Title for restoring data temporarily.)
12
In the Target Client list, select the machine on which you want to restore the data.
 
 
*TIP: You can also click Choose, and then locate and select the applicable client in the Choose the Target Client dialog.
13
Use the Schedule, Source Options, and Advanced Options lists to configure the any additional required options.
14
Click Submit to submit the job for scheduling.

Recovering to an alternate MySQL Server

Similar to Plug‑in for MySQL’s ability to restore databases or individual table(s) to a different MySQL Instance on the same MySQL Server, a different MySQL server can targeted during the restore process. This is used during disaster recovery operations.
Figure 2. Example of data path for this form of relocation restore
To accomplish this, perform the steps outlined in the following sections.
Known limitations/intended uses
Prior to conducting a relocation restore to another MySQL server, review this list of known limitations and intended uses for this operation.
•
Valid restore sequences can include Full, Incremental, Differential, and Individual Database/Table Copy Only backups
•
Only restored Binary Logs from an Incremental or Differential Backup can be applied to the destination instance, that is, current Binary Logs from the source instance cannot be applied to the destination MySQL Instance
Software installation/configuration prerequisites
The following prerequisites must be met before a restore of this type can be set up and run.
•
Existing and target machines must have the same Installation configurations – Both machines must have the following established, in regards to MySQL:
•
Same OS installed
•
Same version of MySQL installed
•
Same installation/base directory
•
Same MySQL “Data” directory
•
NetVault Backup software and Plug‑in for MySQL installed on all clients – NetVault Backup (Client/Server version) and the plug-in must be installed and configured on both machines in use for this process (that is, the existing MySQL machine and the new restore target).
•
All Client machines added to the NetVault Backup Server – With all software installation requirements met, the target NetVault Backup Client machines must be added to the NetVault Backup Server via the NetVault Backup WebUI (that is, the existing MySQL machine and the new restore target).
•
Instance of MySQL must exist on the new restore target – The relocation process requires that an instance of MySQL exist on the new restore target. This instance will serve as the target of the relocation restore. This instance must be properly set up and configured in MySQL, and you must add it to the plug-in on the new restore target (follow the steps outlined in Configuring the plug-in).
 
 
*IMPORTANT: Note the following values in the instance’s Configure dialog on the new restore target: Username, Password, and Instance Name.

During set up of a relocation restore, the plug-in requires that you enter these values on the Options tab to gain proper access to the targeted MySQL Instance.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating