Tchater maintenant avec le support
Tchattez avec un ingénieur du support

NetVault Plug-in for MySQL 11.4 - User Guide

Introducing 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-in in a Failover Cluster environment Troubleshooting

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 process, perform the steps outlined in the following topics.

Known limitations and intended uses

Before 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, regarding MySQL:
•
Same OS installed
•
Same version of MySQL installed
•
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 starting the restore

With the prerequisites met, perform the following steps to set up this form of relocation restore job.

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 by creation date.
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, server name, client name, plug-in name, saveset date and time, retirement setting, Incremental Backup or not, Archive or not, saveset size, and snapshot-based backup or not.
5
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 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.
These options are not required to perform this form of restore. For more information, see Setting restore options.
10
To save the settings, click Ok, 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 name that lets you easily identify the job when monitoring its progress. The job name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Linux, the name 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 filename on the target OS. For example, the characters /,\,*, and @ should not be used on Windows. This requirement 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 box.
13
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options.
14
Click Save or Save & Submit, whichever is applicable.
You can monitor progress on the Job Status page and view the logs on the View Logs page. For more information, see the Quest NetVault Backup Administrator’s Guide.

Recovering to an alternate MySQL Server

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.

Figure 2. Example of data path for this form of relocation restore

To accomplish this process, perform the steps outlined in the following topics.

Known limitations and intended uses

Before conducting a relocation restore to a different 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 and 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, regarding MySQL:
•
Same OS installed
•
Same version of MySQL installed
•
Same installation and base directory
•
Same MySQL “Data” directory
•
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.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation