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.
To accomplish this process, perform the steps outlined in the following topics.
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, regarding MySQL: |
• |
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. |
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 |
5 |
Click Next. |
6 |
On the Create Selection Set page, select the data that you want to restore. |
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 login account name used to access the target MySQL Instance. |
• |
Password: Enter the password associated with the login 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 name is the name established as the MySQL Instance Name in the Configure dialog box ; for more information, see Configuring the plug-in. |
9 |
If applicable, select the applicable options on the Point-in-Time Recovery tab. |
10 |
11 |
In Job Name, specify a name for the job if you do not want to use the default setting. |
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 box. |
13 |
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options. |
14 |
Similar to the plug-in’s ability to restore databases or individual tables to a different MySQL Instance on the same MySQL Server, you can target a different MySQL Server during the restore process. This option is used during disaster recovery operations.
To accomplish this process, perform the steps outlined in the following topics.
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, regarding MySQL: |
• |
NetVault Backup software and Plug‑in for MySQL installed on all clients: NetVault Backup, Client or 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 through 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 exists on the new restore target. This instance serves 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 box on the new restore target: Username, Password, and Instance Name. During setup 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. |
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center