Chat now with support
Chat mit 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

Running the restore

With the prerequisites met, perform the following steps to restore a MySQL backup to a different machine.

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 user name established for the target instance on the new restore target, that is, what was set up in the Username field of the Configure dialog box.
•
Password: Enter the password established for the target instance on the new restore target.
•
Instance Name: Enter the NetVault Backup name established for the target instance of MySQL on the new restore target.
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.

Working with native MySQL replication

•
Using the plug-in in a native environment: an overview
•
Enabling replication support
•
Backing up replication servers
•
Restoring replication servers

Using the plug-in in a native environment: an overview

When you are using replication, all updates to the tables that are replicated should be performed on the master server. Otherwise, you must avoid conflicts between updates that users make to tables on the master and updates that they make to tables on the slave.

Replication offers benefits for robustness, speed, and system administration:

•
Robustness is increased with a master and slave setup. If problems occur with the master, you can switch to the slave as a backup.
•
You can improve response time for clients by splitting the load for processing client queries between the master and slave servers. SELECT queries may be sent to the slave to reduce the query-processing load of the master. Statements that modify data should still be sent to the master so that the master and slave do not get out of synchrony. This load-balancing strategy is effective if nonupdating queries dominate, which is the normal case.
•
An extra benefit of using replication is that you can perform database backups using a slave server without disturbing the master. The master continues to process updates while the backup is being made.

Plug‑in for MySQL supports backup and recovery of single-master replication environments.

Enabling replication support

Replication support is enabled using the Configure dialog box. For information about accessing this dialog box, see Configuring the plug-in.

•
Enable MySQL Replication: If native MySQL Replication is enabled for this instance, select this check box.
•
Slave Instance: If the instance is configured as a Slave, select this option.
•
Master Instance: If the instance is configured as a Master, select this option.
•
Enable Point-In-Time Recovery: If you want to enable PIT backups and restores, select this check box.
•
Binary Log Index Path: If you selected the Enable Point in Time Recovery check box, use this field to specify the complete path to the Binary Log Index file.
•
Relay Log Index Path: If you are configuring a Slave Instance, enter the complete path to the Relay Log Index file to include it in backups.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen