지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Plug-in for MySQL 11.2 - 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

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.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택