NetVault Plug-in for MySQL 12.0 - User Guide

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.

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