Backing up data
Backing up data using Plug‑in for MySQL that has been set up for use in a Virtual Client is relatively simple. 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 that is established as the Virtual Client during the installation process, as outlined in Creating a Virtual Client. 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.
|
NOTE: When you back up or restore data, run the process using the Virtual Client and not from one of the nodes. If you open or expand one of the nodes and drill down through the hierarchy, you see the MySQL Clustered Service and, depending on which node is active, you might be able to drill down and select items. While the system might use this instance in maintaining log information, do not attempt to run any processes at this level. |
Restoring data
Restoring data to a Virtual Client is conducted in the same manner as a restore performed to a traditional NetVault Backup Client. 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 of a Virtual Client are displayed on the Create Restore Job — Choose Saveset page under the name of the Virtual Client, not the specific NetVault Backup Client or 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 target this machine for the restore.
All the instructions offered for performing a restore can be used in the recovery of a Virtual Client. For more information on restoring a NetVault Backup Virtual Client, see the various topics in Restoring Data. To restore a NetVault Backup Virtual Client to a standalone NetVault Backup Client, use the instructions provided in Recovering to an Alternate MySQL Server.
Troubleshooting
|
NetVault Backup 10.x service (netvault-pgsql) does not start on Windows® |
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. |
|
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. | |
|
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 on updating the configuration, see Configuring the plug-in; for more information on replication, see Working with native MySQL replication. |