Chat now with support
지원 담당자와 채팅

NetVault Backup 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

Configuring the plug-in

Perform the following steps on the primary node.

1
In the Navigation pane of the NetVault Backup WebUI on the NetVault Backup Server, click Create Backup Job, and click Create New next to the Selections list.
3
Open Plug‑in for MySQL, and select the All Instances node.
4
From the Actions list, select Configure.
5
On the Configure dialog box, set the applicable configuration options.
IMPORTANT: Add each cluster instance in the Instances field of the Configure dialog box. To add an instance, specify the MySQL Clustered Service name as VIRTUAL SERVER NAME\INSTANCE NAME.
b

Backing up data

Open the Plug‑in for MySQL node on the NetVault Backup Selections page, and select the MySQL Server Virtual Server, or the items contained within, for inclusion in the backup.

The instance name displayed in this page is actually the MySQL Clustered Service. If other MySQL Server Clustered Services are running on this node, those instances are also displayed within the Plug‑in for MySQL node. Data from these other instances must not be selected for inclusion in the backup.

Restoring data

All options available for a restore with Plug‑in for MySQL are also available for Failover Clustering environments, and data selection is performed in the same way. The only difference is that restorable backups are displayed on the Create Restore Job — Choose Saveset page under the name of the primary node that was active during each backup. When a restore job is initiated, NetVault Backup communicates with all member Clients to determine which machine is in control of the failover cluster, and then targets this machine for the restore.

All the instructions offered for performing a restore can be used in the recovery of a failover cluster. For more information, see the various topics in Restoring Data. To restore a failover cluster to a standalone NetVault Backup Client, use the instructions provided in Recovering to an Alternate MySQL Server.

Troubleshooting

This topic describes some common errors and their solutions. In cases where an error occurs and is not described in this table, obtain the MySQL error number from the NetVault Backup logs, and then see the relevant MySQL documentation for resolution.

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.quest.com/netvault-backup/kb/122475.

 

These messages indicate that the selected data was backed up, but the job’s index information was not properly added by NetVault Backup to its database. Without this index information, the data cannot be properly restored.

Method 1:

Access the Manage Devices page of the NetVault Backup WebUI, and perform a scan of the media targeted by the job. NetVault Backup stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. Performing this scan adds the index information to the NetVault Database. To verify that the information was added, open the Create Restore Job — Choose Saveset page and locate the specific job. If you can browse it and set up a restore job, the scan process has corrected the problem.

Method 2:

If the previous method failed, run the backup job again.

Backup fails with a replication error.

If a backup fails with a message similar to “Failed to start Replication slave server,” it might indicate that you selected the Enable MySQL Replication check box but did not configure replication. To correct this issue, either clear the Enable MySQL Replication check box on the Configure dialog box or set up replication, and then run the backup job again. For more information about updating the configuration, see Configuring the plug-in; for more information about replication, see Working with native MySQL replication.

In a Linux or UNIX environment, a backup or restore job fails with the following error:

Cannot establish connection to mysql server. Connection open fails with error “Can't connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2)”

The job is trying to access the default location, "/tmp/mysql.sock," for the MySQL Server socket file, but the file is located elsewhere. The file might be located in "/var/lib/mysql/mysql.sock" or "/opt/mysql/mysql.sock," or any other location. To address this issue, use the following command to create a symbolic link so that the job can access the socket file.

ln -s <existingFile> <symbolicLinkFile>

For more information about updating the path and filename, see Configuring the plug-in.

관련 문서